sweep(spec-surface): 5-item description-surface truth sweep — one claim, one PR, per-item checklist review (#6085 #6081 #6137 #6065 #5676)

[hotlong]

First bundled trivia sweep (maintainer 2026-08-07: PM coordinates same-class trivia into one card — economy of a drive-by fix WITHOUT losing the state machine). One dev, one claim, one PR closing all seven via multiple Fixes lines; review is a per-item checklist.

Membership rule (why exactly these seven)

Same class: spec description-surface text that lies or drifted — JSDoc/describe/ledger prose corrections with ZERO open semantic forks (each is either truth-restoration or already ruled). No behavior changes; regen + existing pin conventions carry the verification.

The seven (fix direction per item — each already carries an audit/triage comment)

#	file	fix
#6085 ★	expression.zod.ts dialect table (renders verbatim to the published ref page)	remove retired js row (says "mapping"), add missing template; align with the enum 12 lines below; regen; pin per retirement-docs convention
#6081 ★	stack.zod.ts:396 skills JSDoc	drop "trigger phrases for intent matching" copy — triggerPhrases retired in #3896; point authors at the current spelling; keep the existing pin test honest
#6161	strictness ledger prose (.md, hand-written half)	the two no gate exemplars were re-verdicted (#5020/#5068); refresh the classification-table exemplars to current population (tree-wide no gate = 0)
#6137	theme.zod.ts / chart.zod.ts	delete the two obsolete "no doc block above this" // warnings (#5059 made them wrong)
#6065	ApiEndpointSchema/ApiMappingSchema .describe() ×3	ruled 2026-08-07 direction B: pure describe copy — stop advertising whole-key rejection the publish gate doesn't do; vocabulary stays frozen (#5040)
#5676	DiscoverySchema.environment (3) vs EnvironmentTypeSchema (7)	ruled remaining scope: docs cross-reference both ways + a subset pin test; explicitly NO contract change
#5886	packages/spec/src/data/hook.test.ts:422	re-spell the insert fixture input: { doc: … } to the engine's real shape (spec half of #5671)

Excluded on same-file serialization: #6094 (flow.zod.ts tombstone) collides with in-flight #4415 (flow schema family) — it rides the NEXT sweep after #4415 lands.

Discipline

• ⛔ Nothing beyond the seven listed fixes — a sweep with riders defeats its own review model.
• Spec regen: the sweep touches TSDoc that feeds generated reference pages — expect content/docs/references/** regen. Landing order: in-flight Design: should FlowNodeSchema parse its ADR-0031 regions, instead of a post-parse pass callers must remember to run? #4415 also regenerates spec artifacts; whichever PR lands second follows the generated-artifacts resync four-step (merge main → checkout generated from main → commit the merge → full regen → assert sibling entries survived).
• PR body: per-item checklist mirroring the table, each with before/after one-liner.
• All seven members are assigned + marked "riding this sweep" — they close via the PR's Fixes lines.

[hotlong]

Handoff note (maintainer 2026-08-07): dispatch belongs to the spec seat. This card was assembled by the coordinating PM session (session_01BickTBKm2JYSNnrtPT8ysa) as the first bundled-trivia sweep, and is deliberately left UNCLAIMED in the lane queue — the spec seat picks it up through its own batch selection (it sits on the v17 board, so it ranks high). For the claimer:

• Fix directions per item are in the table; every member already carries an audit/triage comment with evidence.
• On claim: assign all seven members + a one-line "riding sweep sweep(spec-surface): 5-item description-surface truth sweep — one claim, one PR, per-item checklist review (#6085 #6081 #6137 #6065 #5676) #6243" marker each, so no other seat claims one mid-flight; they close via the PR's multiple Fixes lines.
• The fallbackNodeId tombstone prescribes condition: 'fault' — the migration it hands authors does not draw a fault edge #6094 stays excluded until Design: should FlowNodeSchema parse its ADR-0031 regions, instead of a post-parse pass callers must remember to run? #4415 (in flight, same file) lands.
• Landing serializes against Design: should FlowNodeSchema parse its ADR-0031 regions, instead of a post-parse pass callers must remember to run? #4415's PR on the spec generated artifacts (resync four-step for whichever lands second).

---

Generated by Claude Code

[qq9340100]

认领(轮 4·sweep 打包试点):会话 session_011M7UwH25Unfi73UHim7ajY,分支 claude/issue-6243-description-truth-sweep。一 dev、一 PR、七条 Fixes 齐关,评审按逐项清单;⛔ 七项之外零 rider(试点成败判据之一)。试点跑顺后模式写进 SKILL 发现分诊轮条款(维护者 2026-08-07 指示)。容器判定:M/L 级(describe/TSDoc 面 + references 重生成 + 逐项 pin),create_session 独立云容器(opus)—— 兼顾共享容器已载 5 dev 的 flock 压力与试点可观察性。在飞相交提示:与 #6083(全仓别名区)散文区互不相交;与 #5945(hook.zod.ts 本体)不同文件(本单动 hook.test.ts:422);落地序对 #4415 按卡内四步 resync 条款执行。

---

Generated by Claude Code