[PM seat] domain:spec @ objectui — 🟢 os-bill (session_012W3vMLTFY9SPr2LyxhSeYi, R1 since 2026-09-09T04:21Z) · concurrency 3

[os-sam]

Seat registration post for the domain:spec @ objectstack-ai/objectui lane. Body is authoritative; title and assignee are derived views. Single writer: the sitting seat PM; comments are audit only. Position description lives in references/lanes/spec.md (objectstack) — this post carries state only.

⚠️ Refreshed 2026-09-09T07:2xZ. ⛔ Before publishing any claim about this body's size, MEASURE it — a predecessor declared a shrink and had GROWN to 13,870 B.

1 · 🟢 seated — os-bill, session session_012W3vMLTFY9SPr2LyxhSeYi, since 2026-09-09T04:21Z

⭐ Seated by MAINTAINER ARBITRATION; the mutex did NOT clear. Four readings at 5595739765: reading 3 failed (card branches pushed after the incumbent's stand-down), and a second incumbent held the seat by forced consolidation with no stand-down. The maintainer was given the readings with self-exit as an explicit option and answered 「我接管，通知两席停手」. ⇒ This seating rests on that and nothing else. Both predecessors were asked to stop; os-warren's patrol timer is confirmed gone from the account.

Tier — MEASURED, ⛔ not asserted

get_session: configured_model, session_context.model, last_served_model all claude-opus-5 ⇒ this seat is NOT at CONTRACT_REVIEW_TIER. ⛔ It never clears a clause-② carrier itself. Every ceiling review is a subagent with model passed explicitly, adopted only after transcript verification (count model stamps; require all claude-fable-5-1, zero residue, plus a positive control token). One non-fable stamp voids a verdict whole.

Standing maintainer instructions

• 「优先派 fable 卡」 (04:1xZ) — read against the single source of truth: CONTRACT_REVIEW_TIER = 'claude-fable-5-1', and since objectstack PR #16915 (2026-09-09T02:17:47Z) clause-② cards are BUILT at TIER_DEFAULT, REVIEWED at the ceiling. ⇒ "fable cards" means contract-surface cards, and the fable work is the review.
• 「后续并发降到3」 (06:4xZ) — cap 3, down from 5.
• Enqueue bar: 「无席内契约复审档 PASS 在案 ⛔ 禁止入队」.

Clause-② first-pass ceiling FAIL rate (mandated report item)

Inherited 2 FAIL / 5. This shift added four first-pass verdicts — #8221 PASS · #7562 PASS · #8499 FAIL · #7917 PASS. ⇒ cumulative 3 FAIL / 9. ⛔ Nine is not a rate. ⭐ Every FAIL was a defect no pin caught: #8499's was a green→red on a per-PR gate in a package its implementer never ran.

2 · ledger

Landed this shift (all verified merged-BY-CONTENT on origin/main, ⛔ never the merged field)

#8756 (#8318) · #8758 (#8221) · #8765 · #8766 (#7562) · #8768 · #8737 (#8071) · #8776 (#8478). ⚠️ Four of them closed their card without sweeping labels — the Fixes-closes-the-card-never-the-labels trap; all swept by this seat, and the patrol is the only catcher.

Live

card	PR	state
#8499	#8763 90fcf4f2	ceiling re-review FAIL (5597738741), patch round 2 in flight — 3 delta items. ⛔ draft, carrier on
#8174	—	dev in flight (re-dispatch; the first attempt was killed by the usage wall with zero pushed)
#7917	#8777 a5eaf49c	ceiling PASS (5597620492), carriers dual-cleared, enqueued — follow to MERGED, then sweep

Owed / parked

• finding(types): 27 published .describe() schema descriptions in packages/types/src/zod/** cite source line addresses — the authorable surface carries a citation nothing reads #8478 → back in pm:queue with a 15-address remainder: complex.zod.ts 6 (free now), form.zod.ts 8 + layout.zod.ts 1 (free when fix(types): arm AnyComponentSchema for seven registered node-slot renderers (objectui#8499) #8763 lands). Cheapest slot refill.
• retire(types): EventHandlersSchema — 公开导出的 z.record(z.string(), z.function()),每个值 JSON 不可作者、无任何组合消费、census 与 parity 台账双双结构性不可见(ADR-0049 enforce-or-remove) #6910 → pm:blocked, Blocked-by: #8499. WIP commit 0b99a5f42 on its branch, INCOMPLETE — ⛔ diff it, do not rebuild. Remaining: the EXCLUSIONS row ~:2952, a changeset, and the false prose at handler-keys-json-refusal-6124.test.ts:328 (a fourth file the original brief missed).
• Decision box: DetailViewSchema.related[].columns is typed TableColumn[], but RelatedList deliberately accepts bare strings — the type and the runtime disagree #7997 (four-axis + 速读, rec A) · 27 keys across 18 pairs have a zod mirror that ACCEPTS a spelling its TypeScript declaration refuses — each needs a narrow-the-mirror / widen-the-declaration ruling #7759 (six proposals; ⭐ group E needs NO ruling — objectui#6124 already answered it; group A is the tail of finding(types): two competing SchemaNode declarations — core's interface vs types' union #4580's). ⛔ Confirmed decision-shaped, do not dispatch: plugin-gantt/types: the registered gantt node spelling has no declared schema type — ObjectGanttSchema.type is the literal 'object-gantt', so a typed author cannot write the key the registry (and the README's table) teaches #8008 · finding(types,plugin-kanban): the ruled KanbanSchema carries three zero-read members (allowCollapse, cardTemplates, columnWidths) and the board reads an undeclared titleField — enforce-or-remove on the shape objectui#7664 declared #7742 · normalizeFilterOptions accepts a bare-string globalFilters[].options shorthand that @objectstack/spec rejects at publish #4356 · ChatbotSchema.body accepts more than the declared contract #8572 · finding(types): CollapsibleSchema.open is declared on both faces and read by no renderer — the collapsible renderer passes only defaultOpen #8236.
• Filed this shift, ⛔ do not re-file: finding(types): after #7562 the filter-builder doc IS the authority, but no pin catches the doc WIDENING — the exact direction that recreates #7562 #8774 · tooling(types): nothing enforces "every AnyComponentSchema arm is a named zod export" — objectui#7917 restored the invariant at 107/107, and the next omission is invisible again #8784 · objectstack#17053. finding(plugin-grid,plugin-view): #8221 retires the string sort clause at the shared sink, but ObjectGrid lowers sort itself — so a grid, AND object-view in its default grid mode, still honour the retired spelling silently #8764 closed as duplicate_of finding(plugin-grid): object-grid lowers schema.sort with its OWN private code, so a bare grid still honours the retired string clause that object-view now refuses — the per-block divergence the #8221 ruling rejected by name #8767 (my duplicate; my correction is on finding(plugin-grid): object-grid lowers schema.sort with its OWN private code, so a bare grid still honours the retired string clause that object-view now refuses — the per-block divergence the #8221 ruling rejected by name #8767).

3 · hot-file serial queue

⭐ FILE-BOUND, ⛔ not capacity-bound, and measured from git diff --name-only on live branches — ⛔ never from prose or prediction.

surface	held by	serialises
types/__tests__/zod-mirror-parity.test.ts · zod/layout.zod.ts · zod/form.zod.ts · layout.ts · form.ts	PR #8763 (#8499)	#6910 · #8236 · #8478's form/layout remainder
zod/objectql.zod.ts — the ObjectKanban/ObjectCalendar mirrors only	#8174 (in flight)	region-level; #7917's object-tree region was disjoint

⭐ The lane's structural fact: nearly every domain:spec card lands in a mirror and the parity ledger is one file, so the lane is file-blocked rather than capacity-blocked. ⚠️ But ⛔ do not over-apply it — this seat wrongly deferred #7759 (p2, first in order) twice on a predicted ledger collision that measurement then refuted (5596053904). An occurrence count is not a reading of what a file measures.

4 · notes

⭐ The standing reference is TWO comments — 5593530582 and its addendum 5594362585 (the corrected auto-merge fact lives in the addendum). ⛔ Every future refresh must carry both pointers forward.

⛔ Discipline that must not regress

• A green PR head is NOT a green merge candidate. The queue builds the merged-with-main candidate; an ejection is invisible in get_check_runs and lives in the event log and the PR's comments. This seat enqueued an already-ejected PR by reading only its head checks (corrected at objectui#8068 的过渡背书：58 个 array/object 类 input 仍无 per-block 成员 pin（逐条转 pin，删豁免） #8071 5596176398).
• enable_pr_auto_merge returns a content-free success string; on this repo it enqueues, auto_merge stays null, and the only reading is a positive probe on gh-readonly-queue refs — allow for propagation delay and re-probe once before concluding.
• ⛔ Never write a predicted issue or comment id. This seat did it twice in one shift while quoting the rule.
• A declared file surface is not a measured one — build it from git diff --name-only on the branch, not from a PR body's prose.
• ⭐ A mechanism that explains the observation is not a measurement. This seat relayed an implementer's react-page mechanism to the maintainer as fact; the ceiling review refuted it at the code.
• ⭐ The Zone-2 "these are my assumptions, falsify them" section of a dispatch is this lane's highest-yield instrument. Seven of seven devs this shift corrected something upstream of them — a card's census, its grouping, its line anchors, the PM's file surface, the PM's collision prediction, a PM-offered option, and their own harness — and every correction held.

Standing prohibitions

⛔ Never touch #8225 (hotlong). ⛔ Never git stash. ⛔ Never kill by name. ⛔ Worktree-first. ⛔ Never edit content/docs/releases/ in a code PR. ⛔ Never approve or hand-merge a governed PR. ⛔ Never touch the framework chunk ceiling or its baseline.

[os-sam]

Round-open marker — R2, 2026-08-23T04:4xZ, session session_01E7snar5mwF7qoXJazqKhys. Audit only; §1 of the body still reads "R1 closed / standby" and is refreshed at the R2 boundary, per the write-side rule. Mid-round state is carried by the Claim: comments on the cards, not here.

Why the seat came out of standby: the 04:38Z standby sweep found the lane refilled. The maintainer directed a bulk triage of objectui's unlabelled backlog this session (verbatim, recorded on #5741: 「objectui 有 79 张卡在车道视图之外（占该仓 35%），你帮我分批处理」·「继续 批 2 批 3」), and it routed six cards into domain:spec — including all three R1 follow-ups.

Unlock sweep: no unlock. objectstack#11195 is still open (pm:queue, unassigned), so #5435 stays pm:blocked. Reminder for the next sweep: it is blocked twice — #11195 landing and the spec pin bump that #5716 holds at 17.1.0. Releasing one is not enough.

In flight (2, batch capped at 3, both mode:subagent, both clause-② no):

• Migrate the remaining ListView legacy vocabulary to spec-canonical keys, and audit ObjectView/DetailView (#2231 phases 4–5) #2890 — opus, branch claude/issue-2890-objectview-drift-guard. pm:blocking, so first by the lane's selection order. Scope is the triage-limited one (ObjectViewSchema drift guard + four phase-3 alias folds), not the card body's much larger project; A6 / viewType / conditionalFormatting / exportOptions are excluded as upstream packages/spec faces.
• Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738 — opus, branch claude/issue-5738-row-predicate-phase0. Phase 0 of the row-predicate deprecation, the sibling of R1's [Decision] Row-predicate spelling contract: does the canon narrow to record.*, or do the bare shorthand and data.* spellings stay? (the uncarried "#4075 step 3" question) #5330.

Hot-file serial queue (R2):

surface	held by
packages/types/src/__tests__/ · packages/core/src/utils/normalize-list-view.ts	#2890
content/docs/** · example apps · schema-catalog · plugin READMEs	#5738

Serialised behind #2890 — packages/types is one package, and batch independence is per-package, not per-file: #5740 (view: 'agenda' residue) and #5494 (ReferenceRailEntry extra icon key). Both dispatchable the moment #2890's PR merges. fold-or-serial answered: serial — #5740 and #2890 fail gate ① of the five (different defect shapes: a value-level enum residue vs a declaration-drift guard), so they do not fold.

Also queued, not yet dispatched: #5741 (Phase 2 survey carrier). Triage graded it pm:queue with the note that establishing the data source is the first deliverable, and returning pm:blocked with the access channel named is the correct outcome if none exists — ⛔ explicitly not "guess a population and call it sized". That resolves the routing question this seat raised at R1 close; it does not need the maintainer.

#2890 assignee provenance, checked before claiming: cleared 02:36Z by the skills seat under maintainer ruling objectstack#11196 as assignee-field residue from the 07-28 filing session (shared agent identity, no Claim: comment, no branch). Not a live claim; claimable by protocol.

---

Generated by Claude Code

[os-sam]

⛔ CORRECTION to §3's standing lane constraint — the pin blocker has lifted. Audit comment; the body still carries the stale text and is corrected at the R2 boundary.

§3 currently reads: "any card whose fix is 'align objectui on the spec pin' is blocked twice — on the spec-side change landing in objectstack, and on the pin bump, which #5716 holds at 17.1.0."

The second half is no longer true. #5716 closed completed 04:57:58Z via merged PR #5752 (c9327c9), taking the Localize branch — objectui now owns Theme / ThemeMode / ColorPalette rather than re-exporting them from the retired @objectstack/spec/ui surface. #5716's own body stated the consequence it was gating: "any objectui spec-pin refresh past the retirement breaks @object-ui/types and @object-ui/providers builds." That is what localization removes.

Consequence for this lane: #5435 is now single-blocked, on objectstack#11195 alone (still open, pm:queue, unassigned). When #11195 lands, the next unlock sweep should find only one condition to satisfy, not two.

⚠️ Do not over-read this. What is established is that #5716's blocker is discharged — by its own closure and merged PR. I have not measured that a pin refresh now succeeds end-to-end, and the manifests still declare the range ^17.0.0, which 17.1.0 already satisfies. Whether a bump past 17.x is clean is a separate, unmeasured question, and #5716's body names related guards designed to trip at exactly that moment (the ThemeModeSchema deny-list row in spec-ui-schema-reexports.test.ts). The unlock sweep re-verifies on the merged ref rather than trusting this note.

R2 landing so far: #5738 → PR #5758 merged 702c48a (17 success + 3 skipped, zero red, zero pending). #2890 still in flight.

---

Generated by Claude Code

[os-sam]

R3 interrupted by the 5-hour usage wall, and resumed. Audit comment; §1 of the body still reads "R2 closed / ready for R3" and is refreshed at the R3 boundary.

What happened. Both R3 devs — #5740 and #5741, dispatched ~05:45Z — were terminated mid-task at ~05:50Z by an account-level session limit, with the reset time carried in the failure itself: 07:00Z. Per the seat's own discipline, the authoritative wall signal is the failure report, and the reset moment is available at that instant and not afterwards, so it is recorded here.

Neither card was withdrawn, and that was the deliberate call:

• finding(types/plugin-calendar): view: 'agenda' is declared by CalendarViewMode and the zod enum but the calendar-view renderer silently falls back to 'month' #5740 — its dev had pushed a branch before dying: claude/issue-5740-calendar-view-mode-agenda at 1f94b4c9, verified on the remote. The reclaim rule is explicit that a claim carrying a live branch with commits is never reclaimed, so withdrawing would have discarded real work.
• Carrier for Phase 2 of the row-predicate deprecation: the stored-metadata survey that must size the removal window before any spelling retires #5741 — no branch, but the interrupted-dev protocol is resume-first and withdraw only if resumption is unavailable.

Both were resumed via SendMessage at ~07:55Z, after the wall lifted. The original briefs stand; each resume message re-stated only the load-bearing constraints rather than re-issuing the brief.

A finding salvaged from #5740's dying words, verified before passing it back. Its last output was "More surface than the card cites — objectql.ts, i18n locales." Spot-checked on origin/main: CalendarViewMode appears in packages/types/src/complex.ts, packages/types/src/index.ts, packages/types/src/zod/complex.zod.ts and packages/types/src/zod/index.zod.ts — re-exported through both barrels, wider than the card's two cited files. The objectql.ts and i18n-locale legs are not confirmed and were handed back as the dev's to establish.

This matters because it feeds the card's load-bearing question directly: if CalendarViewMode has consumers beyond CalendarViewSchema.view, narrowing the shared enum is too wide a cut, and the correct fix may be narrowing CalendarViewSchema.view alone. That was already Zone 2 item 3 of the dispatch; the dev's own measurement is now evidence for it rather than a hypothetical.

Standing note for the next wall: a killed subagent is not a dead claim when it has pushed commits. Check git ls-remote --heads origin 'refs/heads/claude/issue-<n>*' before deciding between resume and withdraw — the two paths differ by whether work exists to lose.

---

Generated by Claude Code

[os-sam]

AUDIT (R6 standby) — did R1–R3's five PRs also merge ahead of their test shards?

Audit only; carries no state. Closes the open question §4 flagged as "unaudited" after #5794.

Method: merge time taken from the merge commit itself (git show -s --format=%cI on each squash sha, so it is main's own record, not a PR field), compared against each Test (shard n/4) completed_at read by name from the PR head's check runs.

PR	merged	last shard to finish	margin
#5737 d1ab06f	03:23:48	shard 2/4 @ 03:23:03	+45 s
#5739 065bba7	03:30:56	shard 2/4 @ 03:26:12	+4 m 44 s
#5758 702c48a	05:06:05	shard 3/4 @ 05:01:23	+4 m 42 s
#5760 af3861f	05:34:56	shard 1/4 @ 05:34:21	+35 s
#5782 b55a346	08:38:38	shard 2/4 @ 08:29:13	+9 m 25 s
#5794 —	09:27:58	shard 2/4 @ 09:33-ish	⛔ merged first
#5806 bec062d5	12:05:47	shard 2/4 @ 12:04:49	+58 s (farm read first, then armed)

Verdict: all five R1–R3 PRs merged AFTER their four shards reported. #5794 is the only instance.

So no PR beyond #5794 landed on incomplete shard evidence, and nothing needs revisiting on main.

⚠️ But "five were clean" is the wrong lesson to take

Two of the five cleared by 35 and 45 seconds. That is not a margin produced by any decision I made — it is merge-queue latency happening to exceed the tail of the test farm.

What I can state as measured: the six PRs' outcomes differ. What I cannot state as measured, and am flagging as inference rather than fact: I do not have arming timestamps for those five, so I cannot prove the arming practice was identical across them. It very likely was — same seat, same round, no rule changed between them — but that is reasoning from consistency, not a reading.

If the inference holds, the honest summary is: the practice was the same in all six and only the timing differed. A 35-second margin is a near miss, not a control. It would be self-serving to read this audit as "the pattern was fine five times out of six" when the mechanism that made it fine was not under the seat's control.

The corrective stands unchanged and is now the seat's practice (demonstrated on #5806): read the full farm by name, then arm. Under that rule the margin stops being luck.

Two side-readings worth keeping

• Build Docs failed for real on feat(types,plugin-calendar): converge CalendarViewSchema on the calendar-view renderer's read set #5739 (3 m 52 s) and feat(types): retire 'agenda' from CalendarViewMode and the zod enum #5782 (3 m 43 s) and both merged anyway — independent confirmation that it does not gate the queue, and that its real failures run ~3–4 min against the ~10 s cached greens. Consistent with §4.
• Test shards can themselves be cache hits. On docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758 (docs-only) all four shards completed in 11–13 seconds. Legitimate there — nothing in the test graph changed — but it means the "implausible duration" rule in §4 is not specific to Build Docs: a shard green can also be a cache hit rather than a run. Worth knowing before using one PR's shard timing as a control for another's.

---

Generated by Claude Code

[yinlianghui]

Round-open marker — R1 of a new shift, fire 2026-09-02T01:45Z, session session_01V3hPr7riucnMfhcHY86Msd, summoned interactively as /pm-dispatch spec@objectui. Audit only; the body (§1 still reads "离岗 2026-08-24") is refreshed at the round boundary.

Mutex readings taken before this write: (1) newest shift-end brief = the 2026-08-24T09:50Z body edit (vacancy notice — a release marker); (2) no round-open marker later than it; (3) zero pm:dispatched cards in domain:spec @ objectui; (4) newest CLOSED lane card (#6140, 08-31T20:36Z) claims session session_01PBjwYLS6BciTQW3c9xQiD2, more than a round old. Sibling seat objectstack#6017 (domain:spec @ objectstack, seated 00:42Z today) lists no objectui cards in its ledger — disjoint territory.

Lane inventory at fire (17 open): pm:queue #2731 · #6153 (assignee residue, ruled 09-01) · #6650 (pm:retriage, skipped by rule) · pm:blocked ×4 · pm:on-hold ×6 · pm:awaiting-maintainer #5741 · finding #7200 #7023 (triage's) · tracking #4043. In flight 0. Unlock/restart scan running.

---

Generated by Claude Code