feat(build): replace alex with direct retext dependencies

[Jamie Kim (jkim323)]

Description

This change removed the direct alex@11.0.1 development dependency in favor
of direct retext dependencies.

• Added exact retext-equality@6.6.0 and vfile-sort@4.0.0 development
  dependencies and regenerated the root lockfile.
• Replaced alex.text() with separate reusable equality and profanity
  processors. Both use retext-english and retext-stringify; only the
  equality processor registers retext-equality, and only the profanity
  processor registers retext-profanities.
• Configured profanity with sureness: 1, a confidence threshold rather
  than a severity scale. Rating-0 matches are excluded with and without
  -FailOnAlex. Each non-allowlisted rating-1 or rating-2 finding is emitted
  once under source: retext-profanities and remains an error.
• Retained source: alex as the equality report-source alias, not a package
  dependency. Equality findings are warnings by default; -FailOnAlex
  promotes only emitted equality findings to errors. It does not change
  the profanity threshold or restore excluded matches.
• Sorted equality messages with compareMessage before allowlist filtering
  and normalization, retaining the equality-before-profanity source-block
  order rather than a global position sort.
• Expanded regression coverage for exact equality positions, single-source
  profanity findings, separate source blocks, paired phrase allowlists, and
  rating-0 exclusion in both -FailOnAlex modes.
• Updated the eval script help and owner documentation to explain the direct
  retext implementation and its threshold and compatibility policy.

The JSON report fields, CLI names, and phrase allowlist were retained, but
the historical finding set is intentionally different: profanity findings
are no longer duplicated under source: alex, and rating-0 profanity matches
are no longer reported. Full historical output equivalence is not claimed.

Related Issue(s)

Closes #2628

Type of Change

Select all that apply:

Code & Documentation:

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to change)
• Documentation update

Infrastructure & Configuration:

• GitHub Actions workflow
• Linting configuration (markdown, PowerShell, etc.)
• Security configuration
• DevContainer configuration
• Dependency update

AI Artifacts:

• Reviewed contribution with hve-builder and addressed all actionable findings
• Copilot instructions (.github/instructions/*.instructions.md)
• Copilot prompt (.github/prompts/*.prompt.md)
• Copilot agent (.github/agents/*.agent.md)
• Copilot skill (.github/skills/*/SKILL.md)
• Copilot hook (.github/hooks/*/*.json)
• Eval spec added/updated for changed AI artifacts (evals/)

Note for AI Artifact Contributors:

• Agents: Research, indexing/referencing other project (using standard VS Code GitHub Copilot/MCP tools), planning, and general implementation agents likely already exist. Review .github/agents/ before creating new ones.
• Skills: Must include both bash and PowerShell scripts. See Skills.
• Model Versions: Contributions MUST target models listed in the model catalog (scripts/linting/model-catalog.json) whose provider appears in providerAllowlist and whose status is ga or preview. Run npm run lint:models to validate references.
• See Agents Not Accepted and Model Version Requirements.

Other:

• Script/automation (.ps1, .sh, .py)
• Other (please describe):

Sample Prompts (for AI Artifact Contributions)

User Request:

Execution Flow:

Output Artifacts:

Success Indicators:

For detailed contribution requirements, see:

• Common Standards: docs/contributing/ai-artifacts-common.md - Shared standards for XML blocks, markdown quality, RFC 2119, validation, and testing
• Agents: docs/contributing/custom-agents.md - Agent configurations with tools and behavior patterns
• Prompts: docs/contributing/prompts.md - Workflow-specific guidance with template variables
• Instructions: docs/contributing/instructions.md - Technology-specific standards with glob patterns
• Skills: docs/contributing/skills.md - Task execution utilities with cross-platform scripts

Testing

• npm ci passed after the final merge.
• npm run test:ps -- -TestPath scripts/tests/evals/Test-EvalSpecText.Tests.ps1
  passed with 10 tests, 0 failures, and 1 informational skip.
• The earlier claim of zero ordered differences across 1,100 files and 3,693 messages is withdrawn: the before/after reports were not retained, so their digests and comparison output cannot be supplied or independently verified.
• The full-corpus comparison remains pending. Independent reconstruction from pre-migration revision e822f3bdf8e0bc816e996ef1e0d8343b1aa1c12d has not completed; installation of that snapshot's locked dependencies encountered TLS failures. Module import checks are not a completed locked install or corpus comparison.
• The current revision intentionally changes profanity source attribution, removes duplicate findings, and includes default-threshold findings in the hard-error pass. A new comparison must demonstrate unchanged ordered equality findings and account for those explicit profanity differences, rather than claim zero differences across all messages.
• Passing focused regression tests and in-memory sort-mutation checks are separate checks, not substitutes for retained full-corpus before/after evidence. No report digests or successful corpus diff count are claimed here.
• npm run lint:public-dependency-feeds passed with zero violations.
• npm run lint:dependency-pinning passed with zero violations.
• npm run lint:tables, npm run lint:frontmatter, and
  npm run validate:devcontainer-lockfile passed.
• npm run validate:docs passed after restoring the independent Docusaurus
  package root.
• npm run spell-check passed.
• npm run validate:local did not complete because markdown link validation
  received non-success responses from external URLs in unchanged files.
• npm run lint:md-links did not complete for the same unchanged external
  links.
• npm run ci:eval:lint:text is pending hosted CI.
• Manual testing was not performed.

Checklist

Required Checks

• Documentation is updated (if applicable)
• Files follow existing naming conventions
• Changes are backwards compatible (if applicable)
• Tests added for new functionality (if applicable)

AI Artifact Contributions

• Used hve-builder review mode to review contribution
• Addressed all actionable findings from the hve-builder review
• Verified contribution follows common standards and type-specific requirements

Required Local Checks

The following local-safe validation commands must pass before merging:

• Local validation aggregate: npm run validate:local
• Documentation validation (if docs changed): npm run validate:docs
• Spell checking: npm run spell-check
• Link validation: npm run lint:md-links

Security Considerations

• This PR does not contain any sensitive or NDA information
• Any new dependencies have been reviewed for security issues
• Security-related scripts follow the principle of least privilege (N/A - no security scripts changed)

Additional Notes

The repository template was used. prebuild-install@7.1.3 remains through
unrelated upstream dependencies and is outside this change. Hosted CI must
complete the text lint lane before merge.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/vfile-sort	4.0.0	🟢 3.1	Details Check Score Reason Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Binary-Artifacts 🟢 10 no binaries found in the repo Maintained ⚠️ 0 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 Code-Review ⚠️ 0 Found 1/30 approved changesets -- score normalized to 0 Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. Branch-Protection ⚠️ 0 branch protection not enabled on development/release branches Security-Policy 🟢 10 security policy file detected SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0
npm/retext-equality	6.6.0	🟢 3.4	Details Check Score Reason Code-Review ⚠️ 0 Found 1/30 approved changesets -- score normalized to 0 Packaging ⚠️ -1 packaging workflow not detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Maintained ⚠️ 0 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 Binary-Artifacts 🟢 10 no binaries found in the repo Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ 0 branch protection not enabled on development/release branches Security-Policy 🟢 10 security policy file detected SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0

Scanned Files

• package-lock.json
• package.json

[Codecov Comments Bot (codecov-commenter)]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.27%. Comparing base (bb0ac58) to head (edd7e60).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2818      +/-   ##
==========================================
+ Coverage   83.14%   83.27%   +0.12%     
==========================================
  Files         183      184       +1     
  Lines       34039    34499     +460     
  Branches       27       27              
==========================================
+ Hits        28302    28729     +427     
- Misses       5734     5767      +33     
  Partials        3        3              

Flag	Coverage Δ
docusaurus	90.60% <ø> (ø)
pester	84.24% <ø> (+0.40%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 12 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Eval Execution

✅ Status: Passed

• Artifacts evaluated: 0
• Specs run: 0
• Assertions passed: 0
• Assertions failed (blocking): 0
• Assertions failed (advisory): 0
• Failed specs (merge-blocking): 0

No changed AI artifacts required evaluation.

[Jamie Kim (jkim323)]

Copilot resolve the merge conflicts in this pull request

[Copilot]

Copilot resolve the merge conflicts in this pull request

Resolved the merge conflicts in docs/contributing/evals-ci.md and scripts/README.md with origin/main in commit e62f99d.