spec(qa): TestScenarioSchema/TestSuiteSchema are declared-but-inert — no runtime consumer, no liveness ledger

[baozhoutao]

Recorded while building the standing platform test checklist (branch claude/platform-test-checklist-ocwugl), not claiming or fixing here — filing per Prime Directive #10.

Finding. packages/spec/src/qa/testing.zod.ts declares a full test-scenario protocol — TestSuiteSchema, TestScenarioSchema, TestStepSchema (action + assertions + capture), TestActionSchema (create_record/api_call/run_script/…), TestAssertionSchema — and it is documented at content/docs/references/qa/testing.mdx. But:

• grep finds no runtime consumer: the only references are the domain's own testing.test.ts, type-alias-convention.pin.test.ts, the generated api-surface/qa.json baseline, and the generated reference docs;
• the qa domain has no packages/spec/liveness/ entry, so the ADR-0049/0054 enforce-or-remove machinery never looks at it.

Under ADR-0049 that is declared-but-unenforced surface: the docs advertise a testing protocol nothing executes (declared ≠ enforced, cf. Prime Directive #10's #1475 precedent).

Options (decision for the enforce-or-remove worklist, cf. #2998 Track B):

1. Adopt — give it a consumer (e.g. an objectstack test runner, or serialization target for @objectstack/verify scenarios), and add the missing liveness ledger file; or
2. Retire — remove the domain via the spec-property-retirement route (ADR-0087 registries, generated baselines, docs regen).

Context: the new docs/qa/platform-checklist/ ledger deliberately does not reuse this schema (its action vocabulary is headless-API-only and cannot express browser clauses/oracles/fixtures/evidence) — rationale recorded in that README, so whichever way this lands, the checklist is unaffected.

[claude]

Triage: needs-user-decision + domain:spec.

Landing site. packages/spec/src/qa/testing.zod.ts plus its generated artefacts (api-surface/qa.json, the reference docs) ⇒ domain:spec, and "shared contract surfaces have one owner" makes that seat the owner regardless of who ends up implementing.

Why the maintainer's inbox. The issue offers adopt-or-retire under ADR-0049, and both branches are maintainer calls, not dev work:

• Retire removes a shipped, publicly documented capability (content/docs/references/qa/testing.mdx advertises the protocol), which the triage rules place squarely in the confirm-first bucket. Mechanically it is the spec-property-retirement route: ADR-0087 registries, generated baselines, docs regen — a well-trodden path, but only after someone decides the surface should go.
• Adopt commits the project to building and maintaining a consumer (an objectstack test runner, or a serialization target for @objectstack/verify scenarios). That is a program with appetite and sequencing attached, not a defect fix.

The finding itself is confirmed and is not what needs deciding. declared ≠ enforced here is established: no runtime consumer (references are the domain's own tests, the type-alias pin, the generated baseline, the generated docs), and no packages/spec/liveness/ entry for the qa domain, so the enforce-or-remove machinery never looks at it. The docs advertise a testing protocol nothing executes.

Useful context for whoever takes the card: the new docs/qa/platform-checklist/ ledger deliberately does not reuse this schema (its action vocabulary is headless-API-only and cannot express browser clauses / oracles / fixtures / evidence), and that rationale is recorded in its README — so the checklist is unaffected whichever way this lands. In other words the decision has no hidden dependant, which should make it cheap to answer.

Dedup. No other open issue or PR in the three repos names TestScenarioSchema / TestSuiteSchema. Filed under Prime Directive #10 from the platform-test-checklist branch, unclaimed.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[os-project-manager]

Maintainer ruling — 2026-08-07. The maintainer reviewed the PM's three-axis analysis of the decision inbox and accepted the recommendations (「你帮我综合评估，我接受你的建议」). Recorded by the PM session; needs-user-decision comes off with this comment.

Decision: retire. Remove the qa testing domain (TestSuiteSchema / TestScenarioSchema / TestStepSchema / TestActionSchema / TestAssertionSchema) via the spec-property-retirement route — ADR-0087 registries, generated baselines, reference-docs regen.

Rationale: zero runtime consumers and no liveness ledger entry; the strongest evidence points the other way entirely — the new platform checklist (docs/qa/platform-checklist/) deliberately could not reuse this schema because its action vocabulary cannot express browser clauses, oracles, fixtures or evidence. The declared shape is wrong for the one real need that exists, so adopting it would mean redesigning it anyway. The vocabulary returns with a real runner, implementation-first.

---

Generated by Claude Code

[os-project-manager]

Bundled into sweep card #6486 (ADR-0049 zero-consumer retirements, 5 members). Keeps pm:queue but is excluded from batch selection while #6486 is open — claim the sweep card, not this one; it closes via Fixes when that PR merges. This is the only member whose disposition is already ruled (maintainer, 2026-08-07: retire).

---

Generated by Claude Code