docs(qa): reconcile the i18n checklist items with the shipped contract (#7686, #7684)

[huangyiirene]

Fixes #7686
Fixes #7684

Five itemised edits to docs/qa/platform-checklist/areas/i18n.json, all falling out of the i18n area run #7640. Docs-only, one file, no code and no coverage.json change.

Per-card checklist

#7686 — items 1–4 (item 5 is #7684 below, not double-edited)

落点	before	after
build-gates-hold step 4	"perturb one committed bundle value … capture the red verdict"	split into a do/don't pair: remove or rename a KEY (the structural perturbation), plus an explicit ⛔ against perturbing a value, with the reason (merge mode makes the committed file its own baseline) and the #7640 /tmp symlink-farm technique that drives it red-then-green without touching a repo file
build-gates-hold acceptance c2	"a perturbed bundle turns the gate red"	"a bundle with a removed or renamed KEY turns the gate red … a VALUE edit is NOT a valid probe of this clause"
build-gates-hold negatives	"a green run after the deliberate bundle perturbation is a FAIL of the gate itself"	qualified to the structural perturbation, plus a second negative: a green run after a value edit is not a finding and must never be filed as one
surface-matrix _sections step	"detail-page section labels (_sections group)"	reads them off a named-section surface — task.view.ts's tabbed/wizard/split form views and contact.view.ts's default form, whose section names the bundle already translates — and records why the task detail page cannot serve
surface-matrix _sections gap	not recorded	fixtures.knownGaps entry: the record:details block on task-detail.page.ts authors label-only sections, and component.zod.ts documents that a nameless section renders its authored label in every locale; the resolver negative gains the matching qualifier so English there can no longer be filed as a resolver defect
surface-matrix emptyState step	"open a view/slice with zero rows and capture emptyState.title/message"	⚠️ marked not afforded by the stock fixture → record blocked(fixture), with an explicit ⛔ against manufacturing coverage from the console's built-in zero-row placeholder
surface-matrix emptyState gap	not recorded	fixtures.knownGaps waiver naming the missing fixture and its debt, pointed at the tracking issue #7714
surface-matrix variants	view empty states (…) · detail section labels (…)	both annotated with what they now mean (blocked(fixture) · via a named-section form view)
studio-follows-app-locale clause 1	"no untranslated declared string sitting next to translated ones"	judged against the bundle: a translated key rendering English is the FAIL, an untranslated key rendering its EN source label is the frozen debt and ticks, a raw dotted key is the unconditional FAIL — reconciled with the ratchet and with the sibling item that already declares that debt legitimate
studio-follows-app-locale fixtures / negative	no knownGaps; unqualified negative	knownGaps mirrors the sibling's (451 untranslated declared labels held flat by check-i18n-coverage.mjs + i18n-coverage-baseline.json; #7640's Announcement / Business Unit / … are inside it), and the negative carries the same qualifier

#7684 — c0/c4 rewritten per the PM ruling

落点	before	after
item title	"zh-CN notification is localized, deep-links localized, and mark-as-read clears"	"…mark-as-read is server-authoritative, the deep-link target is localized — and the title is the flow-authored literal string, because notification copy has no translation group"
acceptance c0	"the bell entry's title renders in the recipient locale (zh-CN)"	the title is the flow-authored literal string with its {record.*} placeholders interpolated; an English title on a Chinese session is the PASS, an unsubstituted placeholder is the FAIL — interpolation, not translation, is what the clause tests
acceptance c4	"localization is per-recipient, not session-global: the same event notifies the en control user in en"	the title is recipient-INDEPENDENT; a per-recipient difference is the finding, because per-recipient localization of app-flow notification copy is a spec-retired capability
acceptance c2/c3	live-server POST /notifications/read + survives-reload re-read	untouched — they remain the item's substance
retirement citation	absent	recorded on the item (fixtures.knownGaps + source): translation.zod.ts:341 guidance verbatim, sys_user has no locale, notify-node.ts interpolates cfg.title with no locale lookup, #3403 moved assignment notifications to app-authored flows (pinned by audit-writers.test.ts)
steps	"set the recipient user's locale to zh-CN"; "trigger a collab.assignment notification"	the unperformable per-user-locale step is replaced by the session-locale procedure (localStorage['objectui-locale'] takes language-only zh; zh-CN is rejected and silently boots en — #7640); the trigger names the showcase flow's task.assigned notify node, with ⛔ not collab.assignment
negatives	route-seam 404/405 only	plus: filing a bug over the English bell title is the misread this item forecloses, and authoring a notifications key to "fix" it is a FAIL of the fix

Every touched item bumps revision and appends a history entry per the README lifecycle rule (build-gates-hold 1→2; surface-matrix 2→3; studio-follows-app-locale 2→3; notification-localized-and-clears 2→3).

Premise verification (before editing, against origin/main @ 21888ab)

• Checklist decision: notification-localized-and-clears c0/c4 assume a per-recipient localized title — a capability the spec retired #7684's ruling premise holds. packages/spec/src/system/translation.zod.ts:341 still carries the notifications retirement guidance verbatim, and no notification-copy translation group has appeared. sys_user declares no locale field. notify-node.ts computes the title as interpolate(cfg.title …) with no locale consulted. collab.assignment survives only in regression pins asserting the kernel does not emit it.
• One refinement, recorded rather than glossed: plugin-audit's collab.mention writer does resolve a per-recipient title (messages.mentionedYou via resolveWriteLocale(tenantId, uid)). That is a different producer resolving the long-declared messages group — not a notifications group and not the app-flow path this item drives — so it is not the fork condition the ruling named, and no fork-report was warranted. It is written into knownGaps so the next author overshoots in neither direction.
• Checklist maintenance (i18n area run): step-4 no-op, unaddressable _sections/emptyState fixtures, clause-1 frozen-debt reconcile #7686 item 2's premise is partly false, and the item is better for it. The card read _sections as having "no addressable surface on this fixture". True of the task detail page; false of the object's form views — task.view.ts (tabbed/wizard/split) and contact.view.ts declare stable section names, and the showcase bundle already translates exactly those (概览/排期/详细信息, 联系方式/工作信息/状态/备注). So the clause is adjusted to what the fixture affords rather than waived, and the nameless record page is documented as the gap.
• Items 1, 3 and 4 verified as stated: merge mode confirmed by the gate's own regenerate hint and by AGENTS.md's Documentation Guardrails row; a grep for emptyState across examples/app-showcase/src returns nothing; the showcase's frozen debt is the 451-label entry in scripts/i18n-coverage-baseline.json.

Gates

• pnpm check:platform-checklist — identical before and after this change: one problem, coverage.json · qa: UNCLASSIFIED, the known base red tracked at finding: check:platform-checklist is red on main — the new qa liveness ledger is neither mapped nor waived in coverage.json #7347. No new structural, revision/history or enumSource finding.
• JSON validity — JSON.parse clean.
• node scripts/check-nul-bytes.mjs — OK, 7104 text files, no raw control bytes; plus a targeted self-scan of the edited file (clean).
• git diff --stat — docs/qa/platform-checklist/areas/i18n.json | 116 +++--, one file, 1:1 with the declared surface.

Docs-only, releases nothing → no changeset; skip-changeset applied.

Out-of-scope finding filed

• showcase: no view authors an emptyState, so the objects._views.<view>.emptyState translation surface has no fixture to test #7714 — the showcase authors no view empty state, so the declared objects._views.[view].emptyState surface has no fixture. Filed unassigned, finding; the checklist waiver points at it.

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectstack	Ignored		Aug 11, 2026 11:53am