Skip to content

Enforce English policy for new text - #24

Merged
VeryComplexAndLongName merged 1 commit into
mainfrom
chore/english-policy-enforcement
Aug 13, 2026
Merged

VeryComplexAndLongName merged 1 commit into
mainfrom
chore/english-policy-enforcement

Conversation

@VeryComplexAndLongName

Copy link
Copy Markdown
Owner

Enforces the repository's English-only policy without risky bulk rewrites of legacy source.

  • scans exactly Git-tracked authored files during the normal lint gate
  • rejects new or modified Cyrillic text with bounded file/line diagnostics
  • records reviewed legacy debt by path and normalized-content SHA-256
  • supports explicit same-line markers for intentional i18n fixtures
  • translates ADR 0001 and the core, server, and web UI package READMEs
  • documents package-scoped baseline reduction toward zero

Verification:

  • npm run verify (274 workspace tests plus 4 scanner tests)
  • npm run build
  • openspec change validate --strict english-policy-enforcement
  • staged-file scanner pass, including all new files
  • temporary Git repository test proving tracked violations fail while untracked/generated files are ignored

@VeryComplexAndLongName
VeryComplexAndLongName merged commit a3ed887 into main Aug 13, 2026
4 checks passed
@VeryComplexAndLongName
VeryComplexAndLongName deleted the chore/english-policy-enforcement branch August 14, 2026 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant