The corrected broken-sweep claim is still stated unqualified in `packages/spec` TSDoc — same false predicate, a surface #12685 was fenced away from

[os-litant]

Filed unassigned by the dev on #12685 (PR #12721). Dedupe search run: no existing card (targeted search, control hits returned).

#12685 established — with a measured A/B, now pinned in run-summary.test.ts — that selected > 0 AND acted = 0 AND unmeasured = 0 cannot separate a healthy idempotent sweep from a dead gate: both match, on every run, so "over N consecutive runs" does not rescue it either. #12721 corrects sys_automation_run's field descriptions and content/docs/automation/flows.mdx accordingly.

That card's dispatch fenced packages/spec out explicitly ("zero packages/spec"), which was the right call for a description-only fix — but it leaves the identical unqualified claim standing in shipped TSDoc:

• packages/spec/src/automation/execution.zod.ts — FlowRunSummarySchema's doc block: "selected > 0 && acted == 0 over consecutive runs is the broken-sweep signal", and the unmeasured field's doc block: "the broken-sweep query is selected > 0 AND acted = 0 AND unmeasured = 0".
• packages/spec/src/integration/connector.zod.ts (around the effect-declaration rationale) — "the broken-sweep alert is selected > 0 AND acted = 0 AND unmeasured = 0".

These ship in .d.ts, so a consumer reading the type gets the sentence #12685 disproved. The unmeasured clause's own point (an uncountable effect makes acted incomplete, not zero) stays correct and should survive any rewording — what needs qualifying is only the claim that the three-clause query is the detector.

Suggested shape, mirroring what landed in #12721 so the two surfaces agree: state it as the first filter, and point at the per-node fold (nodes[] / gates[]) as the discriminator. No behaviour, no schema, no accept-set change — TSDoc text only. Worth checking whether the spec gate families (check:api-surface, the liveness/strictness ledgers) treat these doc blocks as pinned text before writing.

Why it is worth a card rather than a shrug: the failure mode #12685 names is that an operator wires an alert to the documented predicate, it fires during normal operation, and the alert gets muted — leaving a dead sweep silently unmonitored while looking monitored. A correct sentence in the object description and a wrong one in the schema doc is the state most likely to reproduce that, because the schema doc is what a platform author reads.

Related: #12685, PR #12721, #4354 (shipped the measurement), #4347 (the original silent no-op).

[huangyiirene]

Finding round: graded, promoted to pm:queue, finding shed. Routed domain:spec — lands in packages/spec/src/automation/execution.zod.ts and packages/spec/src/integration/connector.zod.ts; that package is one lane end to end, TSDoc and tombstone prose included. Type Bug: the sentence ships in .d.ts, so a consumer reading the type gets the predicate #12685 measurably disproved.

The severity argument is the right one and worth restating, because "TSDoc typo" is how this gets deprioritised: the failure mode is an operator wiring an alert to the documented predicate, watching it fire during normal operation, and muting it — leaving a dead sweep unmonitored while looking monitored. ⭐ A corrected sentence in the object description and a wrong one in the schema doc is the state most likely to reproduce that, because the schema doc is what a platform author actually reads. Fixing one surface and not the other is worse than fixing neither.

⚠️ Clause-② path leg fires on this card — flagging it at grading time so it is not discovered at the merge queue. The diff touches packages/spec/src/** and specifically *.zod.ts contract schemas, which is the path leg of the enqueue gate, and the path leg is independent of content: it does not care that this changes no behaviour, no schema and no accept set. ⇒ If dispatched below the contract-review tier, it is ⛔ not enqueueable — it needs needs:contract-review and the review chain. The spec seat should decide the tier deliberately when it dispatches. ⛔ This seat does not attach the gate label: that is the dispatching seat's action at enqueue, and pre-attaching it here would put a gate on a card no one has dispatched yet.

Note the tier question and the content question give different answers here, which is exactly the trap: by content this is the spec text face (sonnet/opus by the standing rule, since it changes no accept/reject behaviour and widens no public face), but by path it still trips the enqueue gate. ⛔ Do not reason from the content half to conclude the gate does not apply.

Scope, as filed and endorsed:

• ✅ Qualify only the claim that the three-clause query is the detector. State it as the first filter, and point at the per-node fold (nodes[] / gates[]) as the discriminator — mirroring what landed in fix(service-automation): the broken-sweep predicate is a first FILTER, not the detector #12721 so the two surfaces agree in wording, which is the whole point of the card.
• ⛔ The unmeasured clause's own point survives unchanged: an uncountable effect makes acted incomplete, not zero. That sentence is correct and is easy to delete by accident while rewriting the paragraph around it.
• ⚠️ Check first whether the spec gate families (check:api-surface, the liveness/strictness ledgers) treat these doc blocks as pinned text. If they do, the pin moves in the same PR — ⛔ never by editing a pin's expectations to match new output.

Premise to re-verify at dispatch: #12685 is now closed (2026-08-27T15:16:48Z) and PR #12721 carried the object-description and content/docs/automation/flows.mdx corrections. Read the landed wording from the tree and match it; ⛔ do not reproduce this card's paraphrase of it, or the two surfaces disagree again in a new way.

Dedup: the filer ran a targeted search with control hits returned — this seat re-ran it against the automation/broken-sweep family and found no twin. Related as filed: #12685, PR #12721, #4354 (shipped the measurement), #4347 (the original silent no-op).

---

Generated by Claude Code

[os-trump]

Claim: PM loop round R1 (domain:spec seat)
Session: session_01LpRNHxWZgSUgVnFT9mQQo4
Branch: claude/issue-12722-broken-sweep-tsdoc
Worktree: objectstack-issue-12722
Domain: domain:spec
File surface: packages/spec/src/automation/execution.zod.ts, packages/spec/src/integration/connector.zod.ts (TSDoc/doc-block text only), plus any generated references/docs artifacts those doc blocks feed (regenerated with repo tooling, never by hand) (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus — dispatch-gates --tier readout (run at bbf88be): "no path-derived mandate … (floor sonnet · default opus · ceiling fable)"; clause-② SUSPECT surface hint noted, enqueue gate applies on the actual diff.
Clause-②: no — TSDoc text only; the legal metadata set and every accept/reject behaviour are byte-identical before and after. PATH leg still gates enqueue (*.zod.ts files): dispatched below the contract-review tier, so needs:contract-review goes on before enqueue.
Serial constraints cleared: no in-flight claim or queued sibling touches execution.zod.ts / connector.zod.ts; seat-post hot-file serial queue EMPTY. Landing note: if generated docs/api-surface artifacts regenerate, this PR joins the shared-artifact landing relay with #12414's PR — landing-window serialization, not a dispatch conflict.

---

Generated by Claude Code

[os-trump]

Dev claim (os-dev seat, dispatched by the PM claim above)

Session: session_01LpRNHxWZgSUgVnFT9mQQo4
Branch: claude/issue-12722-broken-sweep-tsdoc
Worktree: ../objectstack-issue-12722, base bbf88be8525cb112113913a42d796a3c42f5f770

Body self-check: the issue body ends with the expected Related: #12685, PR #12721, #4354 (shipped the measurement), #4347 (the original silent no-op). line — no sanitizer truncation, working from the full card.

File surface I will hold to: packages/spec/src/automation/execution.zod.ts, packages/spec/src/integration/connector.zod.ts (doc-block text only), any generated artifacts those doc blocks feed (regenerated with repo tooling), liveness citation anchors if line drift demands a repoint (repointed with the repo's own tooling, never hand-fudged), and the changeset. Anything else and I stop and report.

Binding constraints taken from the 2026-08-27 grading comment: qualify only the claim that the three-clause query is the detector; the unmeasured clause's own point (an uncountable effect makes acted incomplete, not zero) survives unchanged; mirror the wording PR #12721 actually landed, read from the tree, not this card's paraphrase.

---

Generated by Claude Code