feat(qa): institutionalize the terminology-fidelity pipeline#203
Merged
Conversation
… + machine-readable) Makes the moat visible and the QA state machine-readable instead of claimed: - _meta gains two QA fields in all 11 dictionaries: lastAudited (stamped by the pre-release LLM audit; 2026-06-10 for the audit that shipped in #197/#199) and nativeReview ("recruiting" -> "reviewed" after a native pass). - generate-docs.js gains a LOCALE_QA marker: the README per-locale QA table (entries / last curated / last audit / native-review status) is generated from _meta by `npm run docs`, so the public table cannot drift from reality. - README "Terminology QA" section: the standing pipeline (drift watcher -> same-day dictionary wiring -> CI gates -> real-dictionary regression suite) with the verifiable same-day proof (2026-06-10: #196 detected morning, #201 wired all 11 locales same day) + the generated table + native-reviewer call. - docs/TRANSLATION_QA.md: the three-layer assurance model, honest about what each layer does NOT catch and why no paid API can sit in CI (free-forever). - RELEASE_CHECKLIST step 0: the pre-release LLM dictionary audit is now a release convention, with the _meta.lastAudited stamping step. - CONTRIBUTING "Native language reviewers" section; recruitment umbrella issue #202 (help wanted / good first issue / i18n) with per-locale checklist. Gates: validate, glossary, check:i18n/dict-coverage/locales/dicts/plugin, 527 unit tests, lint, prettier — green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Item 2+3 of the "category leader" plan: make the speed+verification loop visible and the QA state machine-readable instead of claimed.
_meta.lastAudited+_meta.nativeReviewin all 11 dictionaries — the QA state lives in the data.LOCALE_QAmarker ingenerate-docs.js): entries / last curated / last LLM audit / native-review status, generated from_metabynpm run docs— the public table cannot drift.docs/TRANSLATION_QA.md— the three-layer model (CI structure → release LLM audit → native review), honest about each layer's blind spots and the free-forever constraint.Gates: validate · glossary · check:* · 527 unit tests · lint · prettier — green.
🤖 Generated with Claude Code