[pm:seat] domain:spec @ objectui — 🟢 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 / 11:05Z / 11:36Z / 12:07Z / 12:36Z this seat's earlier revisions).

1 · 🟢 current PM

• GitHub os-justin · session session_01BAZFhALsQsGqxui8sNqM8s · seated 2026-09-05T10:23Z (maintainer summons /pm-dispatch spec@objectui; release marker = shift-end brief 5550618996; round-open marker 5551167084).
• Served tier: claude-fable-5-1 = CONTRACT_REVIEW_TIER (get_session 10:24Z; re-read 11:29Z, 11:55Z, 12:17Z, 13:03Z before each verdict). Account usage window resets 15:20Z.
• Lane-scoped ruling in force (maintainer, live chat 10:5xZ, verbatim 「由「包」降到「文件」,限本车道同意」; recorded at comment 5551274423): batch independence at file / region granularity under the four substitute disciplines (region-level surface declaration; merge main before opening the PR; merge again after a sibling lands; conflicts to the merge queue, no manual PM ordering). Scope: this lane only. Applied to Carrier for Phase 2 of the row-predicate deprecation: the stored-metadata survey that must size the removal window before any spelling retires #5741, finding(examples,skills): two in-repo authored nodes put config under the inert props envelope on a component-renderer node #6751, finding(types): zod-mirror-parity's population count rotted AGAIN — #6141 predicted this in writing, the cheap route was taken, and it recurred within ten days #7433, finding(types): ClassNameStylePropsSchema.describe('Style properties') is the same over-broad label the const was just renamed away from #7578, finding(plugin-chatbot): per-message avatar / avatarFallback work end to end but no authoring-facing type declares them — #4424's RuntimeOnlyMessageKeys picked only three keys #7295, finding(types): two layout schemas' @default JSDoc disagrees with the value the renderer actually applies #7361, finding(types): no parity ledger watches the mirror-WIDER-than-declared direction — a key the zod face accepts and the TS face refuses is invisible by construction #7069, Two alias pairs on TextSchema and TreeViewSchema are now DECLARED in both spellings — and TreeViewSchema.data is required while nodes is the documented one (deferred rulings carried out of #6150) #6951 this shift.
• ⚠️ Second session on this lane's When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 branch: session_0114Ytxr5sM1vdW19Y9WAx6E (login os-sam), re-engaged by the maintainer ~10:18Z (PR chore(deps): resolve @objectstack/spec at 17.3.0 in the lockfile #7685 comment 5551127806) before this seat's fire; branch claude/issue-7122-spec-pin-17-3-0 still 36baa6d at 12:32Z, no report on When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 (untouched since 11:34Z), no maintainer answer on who drives (asked in chat 11:2xZ, re-asked 12:31Z). This seat keeps the 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 for review and landing and dispatches nothing on the chain.
• Mid-round state lives on the cards (Claim: / os-dev-report / ACCEPT / PASS / landing-note comments); round comments below this body edit are audit.
• Timers: patrol Implement component reordering via drag-and-drop in designer canvas #5 trig_012y4LKtvv34EeRpLw1DejYA (13:48Z). One-shot flip / review re-checks spend themselves on firing and are recorded on the PR's card. None inherited.

2 · ledger (execution column refreshed 13:17Z)

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; this seat's dev stood down (5551451120). ⛔ Chain-blocking: Console Performance Budget FAIL on the branch (eager closure 4137.7 KB vs 3191.4 KB); ceiling not raised; cause unmeasured; maintainer asked in chat
#7101	A (5536049455)	LANDED — PR #7717 f96a781 MERGED 11:07Z
#6854	B2 (5548581017)	LANDED — PR #7720 adb2a86 MERGED 12:04Z; card closed, pm:dispatched stripped (5551709295); follow-ups #7719, #7721
#6972	sanitize remove (triage collapse); components remove (seat discretion, veto window)	LANDED — PR #7718 446d93d MERGED ~12:14Z; card closed, stripped (5551759703)
#6938	residue: declare CheckboxSchema.wrapperClass	LANDED — PR #7723 b74a859 MERGED 12:26Z; card closed, stripped (5551821448); follow-ups #7722 (types), #7724 (docs)
#6751	card prescription (triage ×2)	LANDED — PR #7729 a00db9ef MERGED 12:39Z (ACCEPT 5551824286, Clause-② no); card closed — strip reading at this boundary
#7530	A (5536048209): CEL envelope on visible / hidden / disabled via a hoisted ExpressionWireSchema	PR #7726 in the merge queue since 13:01Z (pr-7726-a00db9ef…): PASS 5551770555 on 649c920 + delta PASS 5551906272 on a415c0c0 (docs/pin patch round); label cleared 5551907646; landing note 5551993921; next: MERGED by two readings, then strip
#7578	card candidate confirmed by triage (5548829018)	PR #7730 in the merge queue since 13:01Z, behind #7726 (pr-7730-c354ce5d…): ACCEPT 5551911142 (Clause-② no); landing note 5551994546
#7433	triage: route 2 mandatory (5548620618)	PR #7731 40171f5f — ACCEPT 5551960181 (Clause-② no); farm 29 success + 3 skipped at 13:16Z; flipped ready 13:17Z; auto-merge next
#7295	reading 1 under a declared veto window (triage delegation 5548376176)	PR #7732 fdd09f70 — Lint red on 4b0f366c (pin {} type) → patch round 1 (5551976750) → in-seat contract review PASS 5552020607 at tier; PR label cleared with provenance 5552022295; flip once the farm on fdd09f70 completes (6 runs in progress at 13:06Z)
#7361	no ruling; triage 5548503487 (docs correction, renderers authoritative, five boundaries)	in flight (claim 5551918170, 12:47Z), opus, XS, Clause-② no
#7069	no ruling; triage 5548207236 (audit first, ledger second)	in flight (claim 5551965304, 12:56Z), opus, M, Clause-② no
#6951 (+ #7016 folded into PR A)	A1 + B1 (maintainer batch #25, 2026-09-04; director record 5534412859): retire TextSchema.value, retire TreeViewSchema.data, nodes stays optional, no refinement; two PRs	in flight (claims 5552053770 / 5552055050, 13:12Z), fable, S + S, Clause-② yes; PR A claude/issue-6951-text-content-only (Fixes #7016, premise = corpus distribution measurement with a value-majority STOP), then PR B claude/issue-6951-treeview-nodes-only (Fixes #6951)
#5741	B (5511170986) — text contradicted by measurement	in the inbox (needs-user-decision, assignee cleared): retired spellings FAULT rather than "evaluate as absent"; second binding site in packages/react/src/hooks/useExpression.ts; four-facet block + three recommendations (Q1 A / Q2 A / Q3 (i)) at 5551809107; no maintainer answer on the card (last touch 12:26Z) or in chat; dev filed #7727, #7728 (Blocked-by: #5741)
#6910	retire EventHandlersSchema (5534414562)	pm:blocked + Blocked-by: objectstack#15886 (5551860736): objectui + objectstack measured 0 consumers (control live); cloud / hotcrm unreadable from this seat → seam card objectstack#15886 (repo:cloud + repo:hotcrm readers)

Decision inbox (this lane)

• needs-user-decision ×1 raised this shift: Carrier for Phase 2 of the row-predicate deprecation: the stored-metadata survey that must size the removal window before any spelling retires #5741 (above). Three items with the maintainer in chat (unanswered): (1) 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 amendment (recommend A); (2) who drives PR chore(deps): resolve @objectstack/spec at 17.3.0 in the lockfile #7685; (3) the eager-closure budget red (recommend: measure the closure diff between the two pins; ⛔ do not raise the ceiling).
• pm:retriage ×6 raised by this seat's side: 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 (5551668126), 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 (5551789280), ComponentInput does not declare binding, but the manifest serializer publishes it and validateTree reads it — authoring it needs a cast #6950 (5551790023), [finding] richtext registry key 在 @object-ui/types 无 FieldMetadata union 成员(markdown/html 有)——结构上被服务但不可声明 #7083 (5551790914), 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 (5551791755) — each unruled with its minimum option on the manual floor by triage's own table; 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 (5551504738, premise measured false by the contract: should AppAction.items be re-typed to the overlay MenuItem? — the runner reads two overlay fields through as any today #6854 dev). Untouched until triage answers.
• Discretionary dispositions under a veto window: finding(types): MarkdownSchema.sanitize and .components are declared and mirrored but read by no renderer — and sanitize implies a switch that does not exist #6972 components removed (landed); finding(plugin-chatbot): per-message avatar / avatarFallback work end to end but no authoring-facing type declares them — #4424's RuntimeOnlyMessageKeys picked only three keys #7295 reading 1 (PR fix(types): declare avatar and avatarFallback on ChatMessage, on both faces (objectui#7295) #7732, PASS). Each reversible by a re-declaration.
• Next candidate needing a declared choice at dispatch: finding(types/plugin-list): the ListView leg of the exportOptions reconciliation never landed — zod mirror still takes 'pdf' and declares no streaming, and both as any reads survive #6956 (triage 5548153733: derive exportOptions from the spec's ListViewSchema.shape.exportOptions, delete both as any casts, keep ListView's bare-array fold; the ObjectGrid bare-array behaviour — add the same fold or record as unsupported — is a product choice triage asked this seat to answer in-card; Clause-② yes, minor "Breaking for authored metadata" form).

Blocked / on-hold chains (⛔ not dispatchable)

• normalizeListViewSchema manufactures userActions.group / hideFields / rowColor — three keys ListViewSchema refuses BY NAME, so the fold's own output fails the view save gate #5435 → Migrate the remaining ListView legacy vocabulary to spec-canonical keys, and audit ObjectView/DetailView (#2231 phases 4–5) #2890 → Unify hand-written @object-ui/types zod with @objectstack/spec/ui (ListViewSchema drift) #2231 · finding: object-grid.data — two spec authorities disagree on the KIND (ViewDataSchema object vs ComponentPropsMap['object-grid'].data array), so whichever the declaration matches, the other refuses it #6207 + finding: element:number.filter declares the arm 'array', but ElementNumberProps.filter accepts only a record/object — the manifest gate clears a value spec refuses #6206 · Retire BaseFieldMetadata.depends_on — objectui's snake_case twin of the spec's field-level dependsOn (enforce-or-remove; objectui#6153 ruling A follow-up) #7357: wait for the pin in the tree (the When bumping @objectstack/spec past objectstack#14075: list-view spec-parity pins need the CalendarConfig titleField-optional update #7122 chain landing), now also behind the budget question. 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 behind Carrier for Phase 2 of the row-predicate deprecation: the stored-metadata survey that must size the removal window before any spelling retires #5741. retire(types): EventHandlersSchema — 公开导出的 z.record(z.string(), z.function()),每个值 JSON 不可作者、无任何组合消费、census 与 parity 台账双双结构性不可见(ADR-0049 enforce-or-remove) #6910 behind 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.

Queue snapshot (13:17Z; 41 open domain:spec cards read 13:07Z)

• In flight: 3 devs (finding(types): two layout schemas' @default JSDoc disagrees with the value the renderer actually applies #7361, finding(types): no parity ledger watches the mirror-WIDER-than-declared direction — a key the zod face accepts and the TS face refuses is invisible by construction #7069, Two alias pairs on TextSchema and TreeViewSchema are now DECLARED in both spellings — and TreeViewSchema.data is required while nodes is the documented one (deferred rulings carried out of #6150) #6951+ADR-0049 enforce-or-remove: TextSchema.value is a second spelling for the text node's one content slot — its own docblock calls it "a dialect, not a design", and the 2026-08-31 ruling made content the sole evaluation channel #7016) = batch cap. Landing: PR feat(types): declare the CEL envelope on visible / hidden / disabled as one shared ExpressionWire (objectui#7530, ruled A) #7726 + PR fix(types): describe ClassNameStylePropsSchema by its two keys #7730 (queue), PR test(types): derive the zod-mirror-parity population instead of writing it down #7731 (flipped), PR fix(types): declare avatar and avatarFallback on ChatMessage, on both faces (objectui#7295) #7732 (PASS, farm pending).
• Unclaimed, unflagged pm:queue in the lane, in take order: finding(types/plugin-list): the ListView leg of the exportOptions reconciliation never landed — zod mirror still takes 'pdf' and declares no streaming, and both as any reads survive #6956 (p2, next) · @object-ui/types' Phase-2 ActionCallback surface is a third onSuccess meaning — declared, zod-mirrored, doc-advertised, zero producers #7068 (p2) · 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 (p2) · 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 (p2) · finding: #6058's SPEC-DERIVED remedy split routes ObjectViewSchema's unmirrored keys on a scanner false positive — it references no spec schema #7279 · 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 · 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 · [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 · 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 · [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; carries a stray needs:contract-review on the card 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: uid=0(root)… — not dispatchable until repaired) · 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 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 (os-warren) / normalizeFilterOptions accepts a bare-string globalFilters[].options shorthand that @objectstack/spec rejects at publish #4356 (yinlianghui).
• ⚠️ Premise moves at 17.3.0 — re-verify after the chain lands: 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 (5551213208), 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 (domain:ui, on hold; 5551474174).

Landed this shift

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

Cards filed / appended this shift

Filed by this seat: #7714 · #7715 · #7716 · #7724 · objectstack#15843 · objectstack#15886 (the #6910 seam card). Filed by this seat's devs: #7719, #7721 (#6854); #7722 (#6938); #7725 (#7530); #7727, #7728 (#5741); #7733. Appended with evidence: #6893, #5831, #7716, #7469.

3 · hot-file serial queue (file / region granularity)

surface (region)	held by
PR #7685's 19 files (pnpm-lock.yaml · .changeset/7122-* · packages/app-shell/src/views/metadata-admin/** · packages/auth/README.md + auth-spec-parity.test.ts · packages/core/src/actions/actionKeys.ts · packages/plugin-form/src/submitRedirect.test.ts · three packages/types/src/__tests__/*-spec-parity.test.ts · scripts/check-spec-symbol-derivation.mjs)	#7122 chain — session_0114Y… dev, branch claude/issue-7122-spec-pin-17-3-0
packages/types/src/base.ts (three predicate members) · zod/base.zod.ts (:158–:219 region) · zod/form.zod.ts top region (hoist) · expression.ts / zod/expression.zod.ts (new) · index.ts / zod/index.zod.ts (one export each) · 11 packages/types/src/__tests__/* pins incl. zod-mirror-parity.test.ts (one EXCLUSIONS row) · packages/react/src/__tests__/SchemaRenderer.{predicateEnvelopeDeclared,hiddenDeclaredGate}.test.tsx · content/docs/api/schema-reference.md (3 rows) · 27 content/docs/components/** rows	#7530 — PR #7726 (in the queue)
packages/types/src/zod/base.zod.ts (ClassNameStylePropsSchema :433–436 region only) · one pin · changeset	#7578 — PR #7730 (in the queue, behind #7726)
packages/types/src/__tests__/zod-mirror-parity.test.ts (header prose sites + EXPECTED_MIRROR_PAIRS and the derived-count cases in the runtime-census region; ⛔ no MIRRORS / ledger / EXCLUSIONS row) · empty changeset	#7433 — PR #7731 (flipped 13:17Z)
packages/types/src/complex.ts (ChatMessage block) · zod/complex.zod.ts (ChatMessageSchema) · one pin · content/docs/plugins/plugin-chatbot.mdx (three example annotations) · changeset	#7295 — PR #7732 (PASS; flip pending)
packages/types/src/layout.ts — ContainerSchema.maxWidth docblock (:215–:219) and FlexLayoutProps.align docblock (:285–:289) only · one pin · changeset	#7361 — claude/issue-7361-layout-default-jsdoc
packages/types/src/__tests__/zod-mirror-parity.test.ts — a NEW ledger region (mirror-wider-than-declared) + the header's "two covered directions" sentence; ⛔ no existing ledger / MIRRORS / EXCLUSIONS entry moves	#7069 — claude/issue-7069-parity-mirror-wider-ledger
packages/types/src/layout.ts — the TextSchema block only (:76–:114) · zod/layout.zod.ts — the TextSchema const · packages/components/src/renderers/basic/text.tsx:162, :167 (the || schema.value limb) · content/docs/components/basic/text.mdx + corpus text nodes authoring value · pins (#6150 flips + one new) · ≤1 parity-ledger row · changeset	#6951-A (+ #7016) — claude/issue-6951-text-content-only
packages/types/src/data-display.ts — the TreeViewSchema block only (:1270–…) · zod/data-display.zod.ts — the TreeViewSchema const (:336–…) · packages/components/src/renderers/data-display/tree-view.tsx:105 (the || schema.data limb) · content/docs/components/data-display/tree-view.mdx · packages/types/examples/data-display-examples.json (tree-view example) · pins (#7533 flips + one new) · ≤1 parity-ledger row · changeset	#6951-B — claude/issue-6951-treeview-nodes-only (after A)
(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 · @object-ui/core + @object-ui/react changeset	#5741 — after the maintainer answers

Shared files, different regions this batch: zod/base.zod.ts (PR #7726 predicate members vs PR #7730 ClassNameStylePropsSchema, both queued; later #6910 EventHandlersSchema); zod-mirror-parity.test.ts (PR #7726 one EXCLUSIONS row vs PR #7731 header + census vs #7069 a new ledger region vs #6951 at most one ledger row per PR); layout.ts (#7361 two docblocks vs #6951-A the TextSchema block). All devs told to merge main before opening and after the sibling lands; the queue arbitrates. Read-only for everyone this batch: packages/core/src/evaluator/declaredPredicate.ts (#7530's ruling); packages/plugin-chatbot/** (#7295); renderers stay authoritative for #7361. skills/** (governed) is out of every surface this batch.

Cross-lane: the domain:ui seat holds #6939 (pm:dispatched; all groups on main). Declarations posted on #5560 for the #7635 fold and the #6854 runner edit.

4 · platform facts (inherited 09-05 + this shift's; adopt without re-testing)

• 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.
• 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>).
• check_suite.completed fires against stale SHAs ⇒ re-read the head, then the full farm by name, before any flip. send_later fire notices can arrive minutes late (the 13:03Z patrol was delivered 13:07Z) — act on re-read state, never on the fire time.
• A Type Check job's failing step need not be tsc; Actions log retention truncates to post-job cleanup ⇒ "build failed" is a machine reading, the cause is not assertable from that log. This shift's measured cause of the 17.3.0 build failure: SchemaDiffEntryKind gained unreachable (ValidationPanel TS2741). get_job_logs with the default tail can miss a single eslint error — raise tail_lines (420 found PR fix(types): declare avatar and avatarFallback on ChatMessage, on both faces (objectui#7295) #7732's one error).
• Docs schema rows live in fences of two languages: ts/tsx fences are compiled by Doc Snippet Type Check against the built types dist (a row spelled { dialect?, source } fails with TS7008); plaintext fences are not. Read the fence language before editing a schema row; a dev's local check:doc-snippets needs the full built closure or reports PRECONDITION NOT MET (not a measurement). A line-anchored fence pin (check-doc-snippet-types.test.ts README_SAMPLE_FENCE_LINE) turns Test (shard 1/4) red on any edit above the fence in plugin-markdown.mdx.
• CI Lint runs eslint . per package and fails on ONE error (@typescript-eslint/no-empty-object-type on a {} type reddened PR fix(types): declare avatar and avatarFallback on ChatMessage, on both faces (objectui#7295) #7732) — dispatches name pnpm --filter <pkg> lint as a gate.
• MCP search_issues is phrasing-sensitive — a zero without a live control is not a reading. MCP list_issues with two labels returns the OR of them, not the intersection — read the lane with one label and intersect locally. issue_read get_labels does not resolve a PR number — read PR labels with pull_request_read get.
• skip-changeset is a phantom label in objectui; the correct "no release" form is an empty-frontmatter changeset. pnpm --filter X exec vitest run is refused by the repo's invocation guard — use the root-relative path form. pnpm run check:changeset-fixed / check:changeset-no-major are not script names — run the .mjs files directly. Retirement changesets are minor opening "Breaking for authored metadata:" (finding(types): MarkdownSchema.sanitize and .components are declared and mirrored but read by no renderer — and sanitize implies a switch that does not exist #6972, finding(types): designer-surface DashboardConfig.aria / DashboardConfigSchema.aria declare a { label, description } aria object nothing reads — and the panel they document does not consume them #5852); check-changeset-no-major forbids major.
• .describe() strings citing a read-site file:line and the issue number are house style under packages/types/src/zod (26 on main at a00db9ef, wrapperClass among them) — not a review finding.
• A card auto-closed by a merged Fixes PR keeps its pm:* label — strip it at the MERGED reading (reproduced ×5 this shift). finding can survive triage grading (finding(plugin-chatbot): per-message avatar / avatarFallback work end to end but no authoring-facing type declares them — #4424's RuntimeOnlyMessageKeys picked only three keys #7295 carried finding + priority:p3 + pm:queue); the execution seat leaves it — it is triage's to drop at 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; tier and Clause-② here are judged from card content. The shallow clone has no usable blame / git log -S, and git log -- <paths> sees one commit.
• The mutex's reading 3 only counts Claim: on pm:dispatched cards — a re-engaged session working a pm:queue card's branch is invisible to it (this shift's collision). Filed with the shift-end findings.
• Phase-1 of the row-predicate canon shipped in @object-ui/core@17.6.0 (npm 2026-08-24) while its changeset .changeset/row-predicate-record-canon-5330.md is still pending on main (895 changesets pending; the version PR consumed changesets before feat(core,react): declare record.* the row-predicate canon and warn on the two deprecated spellings #5737 merged) — the CHANGELOG will attribute it to 17.7.0. Release-process observation, for the release seat.
• Install surface: objectui lockfile @objectstack/spec@17.2.0; npm latest 17.3.0; objectui main a00db9ef (13:09Z). Console performance budget headroom on main is thin (3186.2 / 3191.4 KB on PR feat(types): declare the CEL envelope on visible / hidden / disabled as one shared ExpressionWire (objectui#7530, ruled A) #7726); 17.3.0 blows it (+~950 KB) — cause unmeasured.

[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