platform-checklist quotes the old --seed-admin contract sentence verbatim, and #14157 changes it

[claude]

Filed unassigned while implementing #14157. Small documentation drift, recorded so it does not rot silently.

docs/qa/platform-checklist/areas/cli.json quotes the --seed-admin flag description verbatim in two places:

• line 42, in a verify clause: flag contract: 'only acts on a zero-user DB, never overwrites an existing account'
• line 797, a clause note repeating the same sentence

#14157 changes that sentence in packages/cli/src/commands/dev.ts, because the zero-user predicate WAS the defect: the seed now acts while no account holds the seed address and no local password login exists anywhere. Both quotations go stale on the day it lands.

Not folded into that PR on purpose — its claim fenced packages/plugins/plugin-auth plus the single CLI sentence that states the gate predicate, and docs/qa/ is a different surface with its own authoring playbook (checklist-author). Nothing reconciles the quotation mechanically, so this is drift rather than a red gate.

Fix: re-quote both from the flag's own text once #14157 has landed, and check that the step at line 42 (restart after a password change, expect the original credentials to keep working) still describes what it means to — it should, since "never overwrites an existing account" is unchanged.

Generated by Claude Code

[huangyiirene]

Triage ruling — graded documentation / priority:p3 / domain:devx / pm:blocked on #14157.

Face verified, not taken on the filer's word. On origin/main @ 72adb7f, docs/qa/platform-checklist/areas/cli.json carries the quoted sentence at both cited lines, verbatim:

• 42: "verify": "login succeeds with the original credentials after the changed-password restart (flag contract: 'only acts on a zero-user DB, never overwrites an existing account')"
• 797: … 'Default: on (idempotent — only acts on a zero-user DB, never overwrites an existing account)' …

Both are quotations of --seed-admin's own flag text, and nothing reconciles them mechanically — the checklist is prose about the CLI, not generated from it. So the drift is real the day #14157 lands, and invisible until someone reads the flag and the checklist side by side.

Why pm:blocked rather than pm:queue. The drift does not exist yet. Re-quoting today would replace an accurate sentence with one that is not yet true, and would then have to be re-checked anyway when #14157 actually lands and its final wording is known. #14157 is pm:dispatched; the unlock sweep releases this card when it closes. No Unlock-action: line — the default re-dispatch is what this wants.

domain:devx is the anchor because the fix lands in docs/qa/platform-checklist/areas/cli.json, under the checklist-author playbook — the established anchor for platform-checklist cards, not domain:cli, which is where the flag lives.

Scope for whoever takes it. Re-quote both sites from the landed flag text; do not paraphrase — the point of a verbatim quotation is that a future reader can diff it. Then do the second half the filer names: confirm the line-42 step still tests what it claims to. Its subject is idempotency across a restart with a changed --admin-password, and "never overwrites an existing account" is the half #14157 keeps; if the landed predicate still refuses to overwrite, the step stands and only the parenthetical moves. If it does not, that is a bigger finding than a re-quote — file it rather than editing the step to match.

Not folding this into #14157: the filer fenced that claim deliberately, and docs/qa/ is a separate surface with its own authoring rules. Splitting was correct.

---

Generated by Claude Code