[pm:seat] domain:spec @ objectui — ⚪ vacant (shift-end brief 2026-09-05T18:21Z, os-justin)

[os-sam]

Seat registration post for the domain:spec @ objectstack-ai/objectui lane — the repo-split half of the spec lane (maintainer 2026-08-23 roster ruling).

Body is authoritative; title and assignee are derived views. Single writer: the sitting seat PM. Comments are audit only and never carry state. Position description is versioned in references/lanes/spec.md (objectstack); this post carries state only. Earlier archives are readable through the edit history (2026-08-24 os-sam; 2026-09-02 yinlianghui; 2026-09-05T08:35Z os-sam shift-end ledger; 2026-09-05T10:3xZ … 17:37Z this seat's earlier revisions).

1 · ⚪ vacant — shift-end brief (收班简报), 2026-09-05T18:21Z

• Seat released by os-justin, session session_01BAZFhALsQsGqxui8sNqM8s, seated 10:23Z (maintainer summons /pm-dispatch spec@objectui), unseated 18:21Z by self-retirement: the lane holds no dispatchable pm:queue card, no dev in flight, nothing awaiting review or landing (merge queue empty; origin/main = 2fcefb95 at 18:17Z), and no new maintainer or triage answer on the decision inbox (lane probes with since at 16:52Z, 17:35Z, 17:50Z: every moved card was this seat's). This revision is the brief; the audit comment below it is the release marker. No live timers (list_triggers at 18:19Z: patrol 完善设计器的每一个细节 #9 was the only one, deleted 18:20Z). No sessions to archive (every dev was a subagent of this session; all finished).
• Release marker for the next seat: this brief. Reading 2 (a later round-open marker) — none after this body edit unless a successor writes one. Readings 3 / 4: no pm:dispatched card in the lane carries a Claim: newer than this brief; the last CLOSED card by updated_at is finding(types): AppComponentSchema inherits the renderer's hidden predicate from BaseSchema while its Zod mirror takes the spec's app-catalogue hidden boolean — one name, two meanings #7542 (18:17Z, this session).
• Left in place, nothing in flight:
  • Decision inbox (needs-user-decision, four cards this shift + the chat batch): Carrier for Phase 2 of the row-predicate deprecation: the stored-metadata survey that must size the removal window before any spelling retires #5741 (5551809107), @object-ui/types' Phase-2 ActionCallback surface is a third onSuccess meaning — declared, zod-mirrored, doc-advertised, zero producers #7068 (5552982130), finding(docs,types): the repo has no documented name for "a component node" — AGENTS.md says UIComponent (not exported), the docs said ComponentSchema (a narrow block-family kind, now retired), and the real object half is BaseSchema #7434 (5553465016, naming — recommend BaseSchema), Decision: ObjectViewSchema's ten unmirrored declared keys are LOCAL (objectui#7279 re-derivation) — mirror them, retire them, or defer to #2231? #7779 (the finding: #6058's SPEC-DERIVED remedy split routes ObjectViewSchema's unmirrored keys on a scanner false positive — it references no spec schema #7279 follow-up — recommend B), [finding] ComponentInput.defaultValue?: any (packages/types/src/base.ts:550) is why the marked plugin example in skills/objectui must carry a bare any — tighten the contract to unknown and the baseline row retires with the guide #7493 (5553603343 — ComponentInput.defaultValue has zero readers; recommend A retire, with [finding] ComponentInput.label and ComponentInput.advanced have no production reader — the two remaining keys the manifest serializer does not forward, the same class as #5905 and the defaultValue census on #7493 #7781's label / advanced in the same ruling). Chat batch items 1–4 (the When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 console budget +274.7 KB — recommend B with A filed; who drives PR chore(deps): resolve @objectstack/spec at 17.3.0 in the lockfile #7685; Carrier for Phase 2 of the row-predicate deprecation: the stored-metadata survey that must size the removal window before any spelling retires #5741 Q1 wording — A; When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 Task C) unanswered. Item 8 (finding(types): AppComponentSchema inherits the renderer's hidden predicate from BaseSchema while its Zod mirror takes the spec's app-catalogue hidden boolean — one name, two meanings #7542 direction 1) landed under a veto window; item 9 = [finding] ComponentInput.defaultValue?: any (packages/types/src/base.ts:550) is why the marked plugin example in skills/objectui must carry a bare any — tighten the contract to unknown and the baseline row retires with the guide #7493.
  • pm:retriage waiting on triage: finding(types,plugin-kanban): ObjectKanbanSchema requires groupField (zero read sites) and declares neither groupBy nor limit — no working object-kanban node is assignable to any declared type #7322 (item ② re-lane to domain:ui, 5553513017); finding(plugin-timeline): a null gantt BAR (items: [{ items: [null] }]) is refused through malformedDate as "startDate is undefined, which is not a valid date" — the wrong fault, one level below #7164 #7365, finding(types): EmptySchema.action is read by the shipped renderer through an as any cast and declared by neither the type nor its mirror — a 14th key #6150's sweep missed #7105, ComponentInput does not declare binding, but the manifest serializer publishes it and validateTree reads it — authoring it needs a cast #6950, [finding] richtext registry key 在 @object-ui/types 无 FieldMetadata union 成员(markdown/html 有)——结构上被服务但不可声明 #7083, finding(components): two text primitives, two variant vocabularies — ui:text's nine are published and now enforced, element:text's four are declared nowhere #7450, finding(types,docs): AppComponentSchema.actions[] (AppAction) has no reader — layout, app-shell and the console never render it, while core/app-schema.mdx "Global Actions" teaches it as the app's global toolbar buttons #7469 (earlier this shift).
  • Unlabelled findings for triage: finding: prose still describes text.value as read (skills counter-examples + four read-site comments) after objectui#6951 retired the key #7770, app-shell: the page-block designer's object-kanban inspector writes groupField — a key the renderer never reads and, after objectui#7322, the validator refuses by name; no groupBy / limit control #7772, plugin-view / plugin-list: the kanban adapters write the retired groupField alongside groupBy onto the generated object-kanban node — an inert duplicate write held in place by two pins #7773, finding(docs): four object-gantt blocks on plugin-gantt.mdx are still bare const literals — ObjectGanttSchema has admitted them since PR #7471, so their keys go unchecked by the doc-snippet gate #7778, finding(types): ObjectKanbanSchema requires objectName on both faces while the renderer reads an undeclared inline data ahead of the fetch — the record-source ladder class (#7313) on a fourth view schema #7780 (kanban record-source class), [finding] ComponentInput.label and ComponentInput.advanced have no production reader — the two remaining keys the manifest serializer does not forward, the same class as #5905 and the defaultValue census on #7493 #7781; earlier: contract: should shortcut become authorable on AppAction.items? — the one capability question left after #6854's B2 ruling #7719, A pending changeset (.changeset/7344-handler-string-any-mirrors.md) and its pin test still say "nothing reads AppComponentSchema.actions[]" — measured false, and the sentence ships as CHANGELOG copy at the next release #7721, finding(types): five more renderers read schema.wrapperClass that their shipped types never declare — switch, textarea, date-picker, select, list (read-driven residue outside #6938's 8-type batch) #7722, finding(types): the predicate wire union is still spelled inline in five places beside the shared ExpressionWire, and two content/docs/core rows spell the pre-#7530 union #7725, finding(app-shell/metadata-admin): the conditional-formatting CEL editor lints row predicates in the flattened scope and advertises bare fields — declared-but-unbound once #5741 (Phase 2) retires the bare-field binding #7727, finding(skills): skills/objectui/guides/schema-expressions.md teaches the bare-field and data.* row spellings as "deprecated and warned once in dev" — stale once #5741 (Phase 2) retires them #7728, finding(types): zod-mirror-parity's three LEDGER entry counts are still hand-written prose — the half of #6141 that #7433's scope deliberately left behind #7733, finding(types): the shared @default 'row' on FlexLayoutProps.direction cannot be right for both flex and stack #7734, finding(types): the zod layout mirror substitutes runtime .default() values the renderers never apply — a parsed container renders a different width than an unparsed one #7735, 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, finding(types): the recursion-breaking annotation on 10 zod mirrors erases their published input face to unknown — the single-or-list producer objectui#7069 named systematic is unauditable at the type level because of it #7760, finding(plugin-grid/types): a bare exportOptions array on a directly-authored object-grid node passes the zod mirror unvalidated and silently degrades to the csv/json default #7762, finding(types): CollapsibleSchema.trigger declares string | SchemaNode while its zod mirror, its shipped defaultProps and its docs row each spell a different accept set #7767.
  • The When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 chain stays driven by session_0114Ytxr5sM1vdW19Y9WAx6E on PR chore(deps): resolve @objectstack/spec at 17.3.0 in the lockfile #7685 (branch tip 339885d0 at 16:04Z); this seat's When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 / When the @objectstack/spec pin moves to 17.3: PR #7510 / #7520's comment "repairs" become FALSE — rows and options[].description are now declared keys #7635 claims are released with the seat — the driver's own Claim: is the live one; landing needs the budget ruling.
  • pm:blocked: retire(types): EventHandlersSchema — 公开导出的 z.record(z.string(), z.function()),每个值 JSON 不可作者、无任何组合消费、census 与 parity 台账双双结构性不可见(ADR-0049 enforce-or-remove) #6910 (objectstack#15886). pm:on-hold ×4: normalizeListViewSchema manufactures userActions.group / hideFields / rowColor — three keys ListViewSchema refuses BY NAME, so the fold's own output fails the view save gate #5435 A component type has THREE declared surfaces that disagree (TS schema type / registry meta inputs / renderer prop reads), and nothing reconciles or enforces them #4631 objectui: AddressField 的 AddressValue 只覆盖 spec AddressValueSchema 七个部件里的五个 —— countryCode / formatted 既不可类型化,formatted 还会在编辑后留成旧值(当前休眠)— observation #4052 Migrate the remaining ListView legacy vocabulary to spec-canonical keys, and audit ObjectView/DetailView (#2231 phases 4–5) #2890.
• Where a successor resumes: the take order after this shift holds no dispatchable card — [finding] QueryParams carries [key: string]: any (packages/types/src/data.ts:133), so a misspelled query key (filter for $filter) type-checks and is silently dropped by convertQueryParams — the index signature that let the published testing guide teach a test that could never pass #7497 (p2; stray needs:contract-review with no PR — for triage), filter-builder: FilterFieldSchema still refuses seven live field types, requires a the renderer and the docs both make optional, and its condition shape omits the uid=0(root) gid=0(root) groups=0(root) four read sites match on #7562 (title/body sanitizer-mangled), finding(ci): check-spec-range-floors reports [floor-too-low] on @object-ui/types — its declared ^17.0.0 does not carry FilterCondition, and the blocking copy runs on the publish path #7688 (p2, after the When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 chain), showBorder on record:details sections is the same divergence #7129 just ruled on, one key over — spec REFUSES it, @object-ui/types declares it, the zod mirror declares it, the renderer honours it #7465 (premise moves at 17.3.0), assignee residue finding(fields): two more undeclared-but-consumed metadata keys — dependsOn on select and options[].description on lookup, both reached past the declared type #6153 / normalizeFilterOptions accepts a bare-string globalFilters[].options shorthand that @objectstack/spec rejects at publish #4356; re-verify showBorder on record:details sections is the same divergence #7129 just ruled on, one key over — spec REFUSES it, @object-ui/types declares it, the zod mirror declares it, the renderer honours it #7465, finding(fields): two more undeclared-but-consumed metadata keys — dependsOn on select and options[].description on lookup, both reached past the declared type #6153, finding(ci): check-spec-range-floors reports [floor-too-low] on @object-ui/types — its declared ^17.0.0 does not carry FilterCondition, and the blocking copy runs on the publish path #7688, app-shell: label the upcoming SchemaDiffEntry kind unreachable in ValidationPanel's DIFF_LABEL when the spec dependency next syncs #5831 after the chain lands. A newly triaged card or an answered decision is the resume signal.
• Shift-end findings filed for the skills lane (objectstack, finding): objectstack#16003 (no state transition for a partial Refs dispatch), objectstack#16004 (mutex reading 3 blind to a pm:queue branch pusher), objectstack#16005 (auto-closed cards keep pm:* — a sweep), objectstack#16006 (platform-facts rows for references/platform-readings.md).
• Lane-scoped ruling that governed this shift (maintainer, live chat 10:5xZ, verbatim 「由「包」降到「文件」,限本车道同意」; recorded at comment 5551274423): batch independence at file / region granularity under the four substitute disciplines. Applied to 15 cards; no manual ordering, every conflict to the queue — one adjacent-block merge (finding(types): objectName is declared REQUIRED on ObjectGanttSchema and ObjectCalendarSchema while both renderers resolve data and staticData FIRST — the documented static-data route cannot be annotated #7313 after finding(types,plugin-kanban): ObjectKanbanSchema requires groupField (zero read sites) and declares neither groupBy nor limit — no working object-kanban node is assignable to any declared type #7322 ①) resolved cleanly.
• Served tier for every verdict: claude-fable-5-1 = CONTRACT_REVIEW_TIER (get_session re-read before each of the 9 PASS verdicts).
• Account usage window: 13:36Z–15:20Z (HTTP 429), every subagent terminated mid-run and resumed at 15:26Z with no push lost; two context compactions survived by re-reading GitHub before writing.

2 · ledger (final, 18:21Z)

Rulings executed this shift

card	ruling	execution
#7122 (+ #7635 folded)	six-item chain (director 5549255921): order 2 → 1 → 3 → 6; item 4 = #7714; item 5 = #7716; item 6-B = #7715; upstream objectstack#15843	driven by the session_0114Y… dev on PR #7685: family bump landed on the branch, build 43/43, check:spec-symbols 0, unit red 7 files / 9 assertions all decision-gated; remaining reds: Bundle Analysis +274.7 KB (maintainer), Type Check 1 item (#7635 fold, authorised 5552811950), shards (#7635 family / Task C maintainer items). ⛔ Not landable until the budget question is ruled
#7101	A (5536049455)	LANDED — PR #7717 f96a781 MERGED 11:07Z
#6854	B2 (5548581017)	LANDED — PR #7720 adb2a86 MERGED 12:04Z; stripped (5551709295); follow-ups #7719, #7721
#6972	sanitize remove (triage collapse); components remove (seat discretion, veto window)	LANDED — PR #7718 446d93d MERGED ~12:14Z; stripped (5551759703)
#6938	residue: declare CheckboxSchema.wrapperClass	LANDED — PR #7723 b74a859 MERGED 12:26Z; stripped (5551821448); follow-ups #7722, #7724
#6751	card prescription (triage ×2)	LANDED — PR #7729 a00db9ef MERGED 12:39Z (ACCEPT 5551824286); stripped 12:56Z
#7530	A (5536048209): CEL envelope via a hoisted ExpressionWireSchema	LANDED — PR #7726 c354ce5d MERGED 13:16Z (PASS 5551770555 + delta PASS 5551906272); stripped (5552094677); follow-up #7725
#7578	card candidate confirmed by triage (5548829018)	LANDED — PR #7730 9587fc95 MERGED 13:16Z (ACCEPT 5551911142); stripped (5552095036)
#7433	triage: route 2 mandatory (5548620618)	LANDED — PR #7731 3bde19ba MERGED 13:34Z (ACCEPT 5551960181); stripped (5552799958)
#7295	reading 1 under a declared veto window (triage delegation 5548376176)	LANDED — PR #7732 858cd72e MERGED 13:35Z (PASS 5552020607); stripped (5552800452); veto window stays open
#7361	no ruling; triage 5548503487	LANDED — PR #7736 e546222b MERGED 15:39Z (ACCEPT 5552118929; one infra re-run green); stripped (5552920046); follow-ups #7734, #7735
#7069	no ruling; triage 5548207236	LANDED — PR #7758 2760075f MERGED by 16:20Z (ACCEPT 5552962639; fifth ledger WiderThanDeclared); stripped (5553134701); follow-ups #7759, #7760
#6956	no ruling; triage 5548153733	LANDED — PR #7763 4dfdcc3c MERGED 16:35Z (PASS 5553073374); stripped (5553228393); follow-up #7762
#6951 (+ #7016 folded into PR A)	A1 + B1 (maintainer batch #25; director record 5534412859)	LANDED, both halves — PR A #7761 5ad86dde 16:49Z (PASS 5553212632; #7016 stripped 5553309742), PR B #7769 16a725f9 17:03Z (PASS 5553215517); stripped (5553393450); residue #7770
#7081	no ruling; triage 5527740245	LANDED — PR #7768 4388f713 MERGED 16:59Z (PASS 5553183812); stripped (5553363012); follow-up #7767
#7322	no ruling; item ① only	item ① LANDED — PR #7774 669d71bf MERGED 17:23Z (PASS 5553334000; groupBy REQUIRED ruled A); card → pm:queue + pm:retriage (item ② re-lane, 5553513017), assignee cleared; dev filed #7772, #7773; seat filed #7780
#7279	no ruling; triage 5548347502	LANDED — PR #7776 1b69ca58 MERGED 17:40Z (ACCEPT 5553451329; route LOCAL, counts 1 / 2 + 13 / 94, header pinned); stripped (5553609810); follow-up decision card #7779
#7313	no ruling; triage 5548431295	LANDED — PR #7777 554f2b6b MERGED 17:59Z (PASS 5553491248 + delta PASS 5553558086 after the #7774 merge); stripped (5553729025); dev filed #7778; seat filed #7780
#7542	no ruling; triage classified three directions	LANDED, direction 1 under a veto window — PR #7782 2fcefb95 MERGED 18:16Z (PASS 5553667716); stripped (5553831964); direction 2 open (decision batch item 8)
#7493	no ruling; triage 5548740471	STOPPED at the dispatch's zero-reader condition (report 5553590885: 245 writes, 0 production readers, 11 test reads) → inbox (needs-user-decision, 5553603343; recommend A retire); dev filed #7781
#7434	none	inbox (needs-user-decision, 5553465016; recommend BaseSchema)
#7779	none	inbox (needs-user-decision; recommend B)
#7068	none — triage's split contradicted by measurement	inbox (needs-user-decision, 5552982130; recommend 1)
#5741	B (5511170986) — text contradicted by measurement	inbox (needs-user-decision, 5551809107; recommend A)
#6910	retire EventHandlersSchema (5534414562)	pm:blocked + Blocked-by: objectstack#15886 (5551860736)

Landed this shift (19 PRs, 18 cards)

card	PR	merged
#7101	#7717 f96a781	11:07:34Z
#6854	#7720 adb2a86	12:04:34Z
#6972	#7718 446d93d	~12:14Z
#6938	#7723 b74a859	12:26:16Z
#6751	#7729 a00db9ef	12:39Z
#7530	#7726 c354ce5d	13:16:16Z
#7578	#7730 9587fc95	13:16:16Z
#7433	#7731 3bde19ba	13:34:23Z
#7295	#7732 858cd72e	13:35:51Z
#7361	#7736 e546222b	15:39:52Z
#7069	#7758 2760075f	by 16:20Z
#6956	#7763 4dfdcc3c	16:35:03Z
#7016 (+ #6951 A)	#7761 5ad86dde	16:49:09Z
#7081	#7768 4388f713	16:59:08Z
#6951 (B)	#7769 16a725f9	17:03:44Z
#7322 item ①	#7774 669d71bf	17:23:20Z
#7279	#7776 1b69ca58	17:40:14Z
#7313	#7777 554f2b6b	17:59:53Z
#7542	#7782 2fcefb95	18:16:31Z

Cards filed / appended this shift

Filed by this seat: #7714 · #7715 · #7716 · #7724 · #7770 · #7779 (decision) · #7780 · objectstack#15843 · objectstack#15886 · objectstack#16003 · objectstack#16004 · objectstack#16005 · objectstack#16006. Filed by this seat's devs: #7719, #7721 (#6854); #7722 (#6938); #7725 (#7530); #7727, #7728 (#5741); #7733; #7734, #7735 (#7361); #7759, #7760 (#7069); #7762 (#6956); #7767 (#7081); #7772, #7773 (#7322); #7778 (#7313); #7781 (#7493). Appended with evidence: #6893, #5831, #7716, #7469, #7122 (5552811950), #5560 (5552135024, 5553396008, 5553729725), #7068, #7434, #7322, #7493.

3 · hot-file serial queue (file / region granularity) — nothing of this lane in flight

surface (region)	held by
PR #7685's files (pnpm-lock.yaml (family bump, lockfile-only) · .changeset/7122-* · packages/app-shell/src/views/metadata-admin/** incl. ValidationPanel.tsx · packages/auth/README.md + auth-spec-parity.test.ts · packages/core/src/actions/actionKeys.ts · packages/plugin-form/src/submitRedirect.test.ts · packages/types/src/__tests__/*-spec-parity.test.ts · scripts/check-spec-symbol-derivation.mjs · packages/app-shell/src/__tests__/spec-symbol-parity.test.ts (#7635 fold, authorised))	#7122 chain — session_0114Y… dev, branch claude/issue-7122-spec-pin-17-3-0 (339885d0)
(blocked) zod/base.zod.ts EventHandlersSchema :394 · zod/index.zod.ts:60 · zod-mirror-parity.test.ts ledger row 'base.zod.ts#EventHandlersSchema'	#6910 — after objectstack#15886's readings
(inbox) packages/core/src/evaluator/listConditional.ts + rowPredicateCanon.ts · packages/react/src/hooks/useExpression.ts · their pins · changeset	#5741
(inbox) packages/types/src/crud.ts (ActionCallback, ActionSchema.onSuccess / onFailure) · zod/crud.zod.ts · content/docs/core/enhanced-actions.mdx (three fences) · content/docs/guide/schema-overview.md:277 · pins	#7068
(inbox) zod/objectql.zod.ts — the ObjectViewSchema const (ten keys) · the UnmirroredDeclared entry · pins · changeset	#7779
(inbox) packages/types/src/base.ts ComponentInput.defaultValue (+ label, advanced per #7781) · zod/base.zod.ts ComponentInputSchema · the 245 authoring sites · 9 test files	#7493 (+ #7781)
(inbox) packages/types export only if UIComponent is chosen	#7434
(retriage) packages/plugin-kanban/src/ObjectKanban.tsx ObjectKanbanComponentProps.schema	#7322 item ② — domain:ui after triage's answer

Read-only for the lane by ruling or ownership: packages/core/src/evaluator/declaredPredicate.ts (#7530's ruling); packages/plugin-grid/** (#7762); packages/plugin-kanban/** (the ui seat's #7664); packages/plugin-calendar/** (#7311, domain:ui); packages/core/** (#7493 ②); renderers stay authoritative.

Cross-lane: the domain:ui seat holds #6939 and in flight #7664 (complex.*, barrels, registry.ts, plugin-kanban/**), #7443. Declarations on #5560: 5552135024 (released 5553396008 and 5553729725); nothing of this lane declared there now.

4 · platform facts (inherited 09-05 + this shift's; adopt without re-testing) — rows also filed as objectstack#16006

• REST from this seat is session-gated: GET /rate_limit answers 200 (core 15000) but a repo-scoped read answers 403 "GitHub access is not enabled for this session" ⇒ MCP + git only. Queue membership by git: git -C /home/user/objectui ls-remote origin 'refs/heads/gh-readonly-queue/main/*' (the Bash cwd resets between calls — always pin -C). check-clause2-carriers.mjs --pair N exits 3 from this seat — the three limbs are verified by hand and said so in the landing note. Node resolution of the installed spec pin from the shared checkout fails from an eval script — spec-side readings are the dev's, through the pin from a worktree.
• An account usage-window 429 terminates every subagent mid-run and the seat itself; the MCP servers drop and reconnect. Subagents resume via SendMessage with their transcript intact — re-read origin/main, the cards and every branch tip first, then send a resume order that names what moved. Timers that fired into the gap are delivered after the reset; execute them on re-read state. A context compaction mid-shift is survivable the same way.
• Ready-for-review flip re-runs only Governed Surface Queue Guard and turns mergeable_state momentarily unstable / unknown; enable_pr_auto_merge echoes empty method / enabled at even when it worked ⇒ the queue-ref probe (appears within ~1 min) is the confirmation. A behind PR enqueues fine. The queue lands PRs in order behind each other's queue tips (pr-N-<previous tip>), across lanes; a lone PR drains in ~15 min, three deep in ~30 min. A background until watcher with a fixed poll budget can time out one poll before the landing — re-read the queue live before declaring anything.
• check_suite.completed fires against stale SHAs ⇒ re-read the head, then the full farm by name, before any flip. send_later fire notices are delivered only between turns and can arrive minutes late — act on re-read state; work a timer asks for may already be done.
• Corepack's pnpm download can crash undici (assert(!this.paused)) before a check body runs — infra, eligible for the one permitted re-run (actions_run_trigger rerun_failed_jobs); PR docs(types): align two layout @default docblocks with the renderer fallbacks #7736's Docs Route Eager Closure Check went green on the re-run.
• A Type Check job's failing step need not be tsc; turbo run type-check aborts at the first failing task — add --continue. Actions log retention truncates to post-job cleanup. get_job_logs with the default tail can miss a single eslint error — raise tail_lines. TypeScript 6 refuses baseUrl (TS5101) — a probe tsconfig carrying it compiles nothing; an ablation leg built on it is VOID.
• pnpm update re-introduces duplicate copies by floating peer versions; a family bump goes: temporarily raise the range → resolve → restore the manifests → reinstall (lockfile-only).
• Docs schema rows live in fences of two languages: ts/tsx fences are compiled by Doc Snippet Type Check; plaintext / json fences are not. A docs page whose fences import a legacy type cannot teach the spec's shape ahead of the type change. A dev's local check:doc-snippets needs the full built closure; the substitute is a differential compile of the touched fences against the merge-base. Doc line numbers in a card drift within hours — dispatches cite the section name beside the line.
• CI Lint runs eslint . per package and fails on ONE error.
• MCP search_issues is phrasing-sensitive. list_issues with two labels returns the OR; with one label + since it is the cheapest lane probe. issue_read get_labels does not resolve a PR number — use pull_request_read get. A long get_comments result is spilled to a file.
• skip-changeset is a phantom label in objectui; the "no release" form is an empty-frontmatter changeset. pnpm --filter X exec vitest run is refused by the repo's invocation guard — root-relative path form. Retirement changesets are minor opening "Breaking for authored metadata:"; check-changeset-no-major forbids major. Widenings are graded minor by this seat (finding(types,docs): BaseSchema.hidden is declared boolean, but the renderer evaluates it as a predicate — the third key on visible/disabled's evaluated path, never widened #7455, finding(types): DropdownMenuSchema.trigger declares a single SchemaNode while its zod mirror, its sibling ContextMenuSchema, and its own shipped defaultProps all use the array form #7081, finding(types): objectName is declared REQUIRED on ObjectGanttSchema and ObjectCalendarSchema while both renderers resolve data and staticData FIRST — the documented static-data route cannot be annotated #7313); the 24 catalog entries fail safeValidateSchema because the Zod mirror names a key its renderer never reads (8 components) #6939 precedent graded the record-source widening patch. A tombstone on an extended schema shadows a same-named BaseSchema member on both faces.
• .describe() strings citing a read-site file:line and the issue number are house style. @default is a member-level JSDoc tag. Zod mirrors annotated z.ZodType<any> read unknown on the input face (finding(types): the recursion-breaking annotation on 10 zod mirrors erases their published input face to unknown — the single-or-list producer objectui#7069 named systematic is unauditable at the type level because of it #7760). No objectui gate reads an ADR-0087 disposition marker. The runtime render path runs @object-ui/core's structural validateSchema, not zod. A three-way merge of ADJACENT blocks produced no textual conflict — verify by delta equality (md5 of hunk bodies).
• A card auto-closed by a merged Fixes PR keeps its pm:* label (×18; objectstack#16005). A Refs PR closes nothing: the card's transition is the seat's (objectstack#16003). finding can survive triage grading.
• check-governed-merges.mjs refuses rather than under-reports on a shallow clone; --test <paths> works for objectui paths (run from /home/user/objectstack). Next audit anchor: --since-ref objectstack=d701e657d74d --since-ref objectui=4ce14f125975.
• objectstack's dispatch-gates.mjs does not answer for objectui. The shallow clone has no usable blame / git log -S. The half-state patrol anchor does not exist in objectui (The half-state patrol needs its anchor issue created and HALF_STATE_ANCHOR_ISSUE set — a maintainer action outside GitHub's API surface for agent seats #5986).
• The mutex's reading 3 only counts Claim: on pm:dispatched cards (objectstack#16004).
• Phase-1 of the row-predicate canon shipped in @object-ui/core@17.6.0 while its changeset is still pending on main — for the release seat.
• Install surface: objectui lockfile @objectstack/spec@17.2.0; npm latest 17.3.0; objectui main 2fcefb95 (18:17Z). Console performance budget: main ~3186 / 3191.4 KB; the When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 branch after the family bump 3466.4 KB (+274.7 KB, real growth — see §1).

[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