<!-- source: openspec/changes/establish-translation-quality-track/verification.md -->

# establish-translation-quality-track — verification

## What "done" means for this scaffold (Phase 1)

This change folder is verified when:

1. The four standard files exist (`proposal.md`, `design.md`, `tasks.md`, `verification.md`) and pass `node tools/check-openspec-refs.mjs`.
2. The seed suspect-string inventory (`research/suspect-strings-2026-05-25.md`) cites at least one concrete `file:line` per named class.
3. The proposal cites the audit findings it closes: 2026-05-25 delta § D, 2026-05-22 corpus audit § D pattern.

This change does **not** verify that RU/RO copy is correct. It verifies that the process to make it correct exists in writing.

## Verification commands

```bash
# Refs guard — every openspec ref in the new folder resolves
node tools/check-openspec-refs.mjs

# Sanity — the seed inventory cites real files
rg -nF "packages/i18n/messages/ru/web.json:7" \
  openspec/changes/establish-translation-quality-track/research/
rg -nF "packages/i18n/messages/ro/web.json:11" \
  openspec/changes/establish-translation-quality-track/research/

# Sanity — the cited file:line still contain the suspect string
sed -n '11p' packages/i18n/messages/ro/web.json
sed -n '7p' packages/i18n/messages/ru/web.json
```

## What is NOT verified here

- That `echipe curate` is the *only* RO false friend
- That the 131-line RU code-switch count is the *exhaustive* count
- That the named suspect-string classes are the *only* classes worth a reviewer's attention

The reviewer's pass produces the exhaustive list. This scaffold only seeds it.
