docs(census): 29 bare const schema = { literals across 14 content/docs pages compile against nothing — a one-pass annotation sweep instead of page-by-page cards (objectui#7778 / #7972 class)

Filed by the domain:devx @ objectui execution seat (PM session session_01FhBNJcLRZLe8M87VcUgpKr, R46) on the triage seat's own suggestion in objectui#7972's grading (5557184611: consider a one-pass census rather than a card per page). ⛔ Filed finding only; grading and domain:* are the triage seat's. Left unassigned. Dedupe: one MCP semantic search (45 hits, none a census of this class; #7778, #7840 and #7972 are the single-page instances).

The population, measured on `origin/main` `083e1abbf` at 2026-09-06T17:28Z

Triage's spelling: git grep -c "const schema = {" (bare) vs git grep -c "const schema: " (annotated) over content/docs/**.

reading	count	pages
bare `const schema = {`	29	14
annotated `const schema: TYPE = {`	22	9

Per page (bare): core/schema-renderer.mdx 1 · guide/objectos-integration.mdx 1 (PR #8124, in the queue, takes it to 0) · guide/plugin-development.md 1 · guide/quick-start.md 1 · guide/schema-playground.md 1 · guide/schema-rendering.md 3 · plugins/plugin-calendar.mdx 2 · plugins/plugin-charts.mdx 8 · plugins/plugin-editor.mdx 4 · plugins/plugin-form.mdx 1 · plugins/plugin-grid.mdx 1 · plugins/plugin-map.mdx 1 · plugins/plugin-markdown.mdx 3 · utilities/vscode-extension.mdx 1.

Movement: triage read 30/15 at 05:26Z; #7778's sweep (PR #8040) took plugin-gantt.mdx's four to the annotated side; #7972 (PR #8124) takes one more. The ratchet is shrinking, one card at a time, at roughly the rate new bare literals are written.

Why a sweep and not fourteen cards

Every bare literal is compiled by check:doc-snippets (the block is judged) against nothing (no declared type is consulted). objectui#7972 measured what that costs: objectui#7713's wrong-shaped filter sat green on objectos-integration.mdx for its whole interval, and one annotation would have turned it red with exactly one diagnostic. The repair is the same two lines on every page (import type { XSchema } from '@object-ui/types' plus const schema: XSchema = {), which is a family in the fold sense: same defect shape, same fix, same measurement (pnpm check:doc-snippets), each member independently checkable by that gate's per-block verdict.

What the sweep must carry (from #7972's rulings, unchanged)

⛔ The honest ceiling: BaseSchema closes with [key: string]: any (objectui#7927), so an annotation does NOT catch a misspelled key; it catches a key whose declared type is wrong. The PR must say so.
Annotating may turn a block red on a real README-vs-shipped-type contradiction (that is the point). A contradiction between the docs and the shipped type is fixed in the docs; a contradiction between two shipped surfaces is fixed to the type in the docs and filed, never widened.
Exclusion to rule at dispatch: utilities/vscode-extension.mdx's bare literal is the Export to React command's product reproduced verbatim (PR docs(vscode-extension): state what Export to React actually does #8112, objectui#7977); annotating it would make the example diverge from what the command emits. Either leave it bare with a stated reason or take it up with the template (objectui#7976's class).
No gate, no pin, no new scan population in the sweep itself. Whether a gate should refuse a bare const schema = { in a content/docs block afterwards is a separate ruling.

Back-links

objectui#7972 (the measured instance and its two controls), objectui#7778 (the plugin-gantt.mdx sweep, PR #8040), objectui#7840 (closed, measured to zero), objectui#7927 (the ceiling), objectui#7713 (the defect an annotation would have caught), objectui#6143.

Triage: lands in domain:devx (content/docs/** snippets); rationale: class (b) on the over-claim — check:doc-snippets reports these blocks as judged while consulting no declared type for them. Task, because the deliverable is a sweep.

⭐ The cost is measured, not predicted: objectui#7972 established that objectui#7713's wrong-shaped filter sat green on objectos-integration.mdx for its whole interval, and that one annotation would have turned it red with exactly one diagnostic. ⇒ A gate that judged the block and could not have failed on it.

priority:p3: nothing is currently known-wrong (the one measured instance is fixed), and each member is individually cheap. The value is preventive.

⭐ The argument for a sweep over more single-page cards is the movement reading, and it is the strongest sentence on the card: triage read 30/15 at 05:26Z; #7778's sweep took plugin-gantt.mdx's four across; #7972 takes one more — "the ratchet is shrinking, one card at a time, at roughly the rate new bare literals are written." ⇒ Net progress ≈ zero. Fourteen more cards would buy the same nothing, which is exactly why this seat suggested the census in #7972's grading and why filing it was right.

The family test is satisfied: same defect shape, same two-line fix (import type { XSchema } + const schema: XSchema = {), same measurement (pnpm check:doc-snippets), each member independently checkable by that gate's per-block verdict. ⇒ Foldable.

⚠️ All four of #7972's rulings carry forward unchanged and ⛔ none is optional:

⛔ State the ceiling in the PR. BaseSchema closes with [key: string]: any (objectui#7927), so an annotation does not catch a misspelled key — it catches a key whose declared type is wrong. A PR that implies otherwise sells a guarantee the annotation does not provide.
⭐ A block turning red is the point, not an obstacle. A docs-vs-shipped-type contradiction is fixed in the docs; a contradiction between two shipped surfaces is fixed to the type in the docs and filed — ⛔ never widened.
⛔ utilities/vscode-extension.mdx is excluded — its literal is the Export to React command's product reproduced verbatim (PR docs(vscode-extension): state what Export to React actually does #8112 / objectui#7977), and annotating it would make the example diverge from what the command actually emits. ⇒ Leave it bare with a stated reason, or take it up with the template (objectui#7976's class). ⛔ Do not silently annotate it to make a count reach zero.
⛔ No gate, no pin, no new scan population in the sweep itself. Whether a gate should refuse a bare const schema = { in a content/docs block afterwards is a separate ruling — ⛔ and the sweep must not pre-empt it by landing one.

⚠️ Re-measure at dispatch: the population moves under this card. PR #8124 (objectui#7972) takes objectos-integration.mdx to 0, so 29/14 will already be stale. ⇒ Re-run triage's own spelling (git grep -c "const schema = {" vs git grep -c "const schema: " over content/docs/**) and state both numbers in the PR.

⚠️ Lane caveat, recorded once more: domain:devx's label description covers .github/, scripts/ and the release pipeline — ⛔ not content/docs/**. It is used here for consistency with the ~10 other open docs cards routed that way (objectui#8015 today included). ⇒ The discrepancy is real and wants a ruling; ⛔ not on this card.

⛔ This seat grades and routes only: not claimed, not dispatched, no code.

Generated by Claude Code

Claim: PM loop round R46 — domain:devx @ objectui execution seat.
Session: session_01FhBNJcLRZLe8M87VcUgpKr
Branch: claude/issue-8125-doc-schema-annotation-sweep
Worktree: /home/user/objectui-issue-8125
Domain: domain:devx
Dispatch: one os-dev subagent of this session (mode:subagent, model: opus); the dispatch note with the brief follows. Labels pm:queue → pm:dispatched and assignee set in one write, read back and diffed against the union at 2026-09-08T01:55Z.

⚠️⚠️ This seat put FOUR false premises into dispatch briefs today — 660 judged (tree: 663), 1309 fences (read in the shared checkout; origin/main reads 1310), UNGATED_DOCS = {} (it holds 4), and "objectui#8045 is open" (closed 2026-09-07T19:09:04Z). ⭐ The last brief instructed the dev to re-read every referenced card on GitHub while this seat took that card's status from the card's own record table. ⇒ Every fence, number and card status below is a PREDICTION. Re-derive before you act on it, and a corrected brief with zero implementation is a good outcome.

⚠️ SIX cards this shift carried a false premise in the card face itself — #8006 #8029 #8113 #8117 #8122 #7925, three of them repeated verbatim in the triage comment.

⛔ A zero-hit reading means nothing without a control term you know is present, in the same run. ⛔ origin/main is verified on a clean extract or a detached worktree, ⛔ NEVER on /home/user/objectui's working tree. ⛔ A grep over a whole file cannot answer a question about one region of it — three probes did exactly that today and hit a docblock, a different schema, and a deliberately dated historical sentence.

Generated by Claude Code

Dispatched — domain:devx @ objectui execution seat, PM session session_01FhBNJcLRZLe8M87VcUgpKr, R46, 2026-09-08T01:57Z. One of three slots (with #8115 and #8366).

Dev. One os-dev subagent of this session on branch claude/issue-8125-doc-schema-annotation-sweep, worktree /home/user/objectui-issue-8125, from origin/main at ed17be480 or later. Race re-read at 01:55Z: the newest Claim: is 5577907899, naming that branch — and it is the only one. ⛔ No second claim, ⛔ never writes the assignee.

⭐ The argument for a sweep is the movement reading, and it goes in the PR body. Triage calls it the strongest sentence on the card: 30/15 at 05:26Z, #7778's sweep took plugin-gantt.mdx's four across, #7972 takes one more — "the ratchet is shrinking, one card at a time, at roughly the rate new bare literals are written." ⇒ Net progress ≈ zero, and fourteen more cards would buy the same nothing.

⛔ #7972's four rulings carried, none optional — and the first has a worked example from two hours ago. ⛔ State the ceiling: BaseSchema closes with [key: string]: any (#7927), so an annotation catches a key whose declared type is wrong, ⛔ not a misspelled key. ⭐ objectui#7925 landed at 01:44Z doing exactly this correctly — it measured the limit against the built dist (an undeclared key: 0 diagnostics; defaultView: 'agenda' and titleField: 42: TS2322 each, as positive controls) and wrote the limit into the file. The brief tells this dev to copy that discipline, because a reader who infers a guarded key set from an annotation is worse off than one who sees a bare literal. ⭐ And: a block turning red is the finding, not an obstacle — ⛔ do not weaken the annotation, ⛔ do not skip the page.

⚠️ This seat corrected its own error inside the brief. A brief of mine earlier today asserted UNGATED_DOCS = {} and was falsified by the dev who checked: it holds 4 entries, placed deliberately by objectui#7856 card 2 (ADR and audit records — dated decisions, not this gate's to repair). The brief now says so and tells the dev to take the ledger's contents itself. ⛔ Nothing is added to it.

⛔ Re-derive the population. 29 / 14 is from 083e1abbf and the card's own text records the number moving three times; the brief requires it re-taken with triage's own spelling, and flags two pages that moved this shift — objectos-integration.mdx (expected to reach 0 via PR #8124, check rather than assume) and vscode-extension.mdx (edited by PR #8425). Any page that does not fit the family goes in the PR's exclusion list with a reason, per the fold rules — ⛔ it is not forced.

⚠️⚠️ The brief warns the dev about this seat before it warns it about anything else. Four false premises reached dispatch briefs today — 660 judged (tree: 663), 1309 fences (read in the shared checkout; origin/main reads 1310), UNGATED_DOCS = {} (it holds 4), and "objectui#8045 is open" (closed 2026-09-07). ⭐ That last brief instructed its dev to re-read every referenced card on GitHub while this seat took the status from the card's own record table. ⇒ Every fence, number and card status in the brief is labelled a prediction, and a corrected brief with zero implementation is stated as a good outcome.

Generated by Claude Code

os-dev-report

{
  "issue": 8125,
  "status": "done",
  "branch": "claude/issue-8125-doc-schema-annotation-sweep",
  "pr": "https://github.com/objectstack-ai/objectui/pull/8487",
  "pr_number": 8487,
  "head_sha": "a5a67ad472cd0d4d9063ac7d3f916ec0327482b7",
  "base": "76573a1843d46bb9f070a9f97ef45219e23b5a30 (origin/main, past the required ed17be480)",
  "premise_still_valid": true,
  "premise_notes": "The premise holds: a sweepable population of bare `const schema = {` literals exists and annotating them changes what the gate consults. THREE corrections to the card's numbers, all re-derived on origin/main 76573a184 in a dedicated worktree (never the shared checkout). (1) COUNT: 28 bare / 13 pages, not the card's 29/14 (083e1abbf) nor triage's 30/15 (05:26Z). Annotated side reads 23/10, not the card's 22/9. (2) THE CENSUS SPELLING OVER-COUNTS BY 2. `git grep -c \"const schema = {\"` is a whole-file grep, and two of its 28 hits are PROSE outside any fence: plugin-form.mdx:394 and plugin-grid.mdx:612 are sentences arguing FOR annotation. Real population: 26 code occurrences across 11 pages. This is the brief's own warning realised - a grep over a whole file cannot answer a question about one region of it. (3) PR #8124 DID land: guide/objectos-integration.mdx reads 0 bare / 1 annotated. UNGATED_DOCS verified by reading it: 4 entries (2 ADR, 1 ADR, 1 audit - all under docs/adr/** and docs/audits/**, none under content/docs/**). The brief's correction was right; nothing added to it. One brief prediction not matched, reported for the record: the gate's judged-block count on this tree is 632 (`632 of 632 block(s) judged`), not the 660/663 the brief carried from another card.",
  "summary": "Annotated 18 of the 26 real bare literals across 8 pages: one `import type` line plus a declared type on each declaration, the shape PR #8124 used. Types: PageNodeSchema / CardSchema / ObjectMapSchema / ChartSchema from @object-ui/types, and BarChartSchema / CodeEditorSchema / MarkdownSchema from the plugin package each page already documents. Eight code occurrences are excluded with stated reasons in the PR: seven are DECLARED FRAGMENTS, which the gate does not compile at all and which therefore fail triage's own family test (each member independently checkable by the gate's per-block verdict); the eighth is utilities/vscode-extension.mdx, excluded by ruling 3 as the Export to React command's verbatim product. ONE BLOCK TURNED RED and it is a real finding: annotating guide/schema-rendering.md produced TS2353 - a single object passed to a `page` node's `body`, which PageNodeSchema declares as SchemaNode[] (array only), while the sibling `children` on the same interface is SchemaNode or SchemaNode[]. The renderer disagrees with the type: FlatContent in packages/components/src/renderers/layout/page.tsx:266-272 normalizes a non-array body into a one-element array, so a single node does render. Per ruling 2 this is a two-shipped-surface contradiction, so it was fixed TO THE TYPE IN THE DOCS (wrapped in an array) and the divergence is handed over below - the type was NOT widened. A second commit re-declares scripts/__tests__/check-doc-snippet-types.test.ts's README_SAMPLE_FENCE_LINE from 206 to 207: that pin keys objectui#7555's specimen on its fence line deliberately so an edit above it forces a re-declaration, and this sweep added one import line above it on that page. The constant already carries a running record of such moves and this one was appended to it. Per ruling 4 the PR adds no gate, no pin and no new scan population. Assignee was already set to baozhoutao by the dispatch; not written, not touched. The newest Claim: comment (5577907899) names this branch; no second claim posted.",
  "files_changed": [
    "content/docs/core/schema-renderer.mdx (1 annotation, PageNodeSchema)",
    "content/docs/guide/quick-start.md (1, CardSchema)",
    "content/docs/guide/schema-playground.md (1, CardSchema)",
    "content/docs/guide/schema-rendering.md (1, PageNodeSchema + the body-to-array docs fix)",
    "content/docs/plugins/plugin-charts.mdx (6: 2 BarChartSchema, 4 ChartSchema)",
    "content/docs/plugins/plugin-editor.mdx (4, CodeEditorSchema)",
    "content/docs/plugins/plugin-map.mdx (1, ObjectMapSchema)",
    "content/docs/plugins/plugin-markdown.mdx (3, MarkdownSchema)",
    "scripts/__tests__/check-doc-snippet-types.test.ts (fence-line pin re-declared 206 to 207)"
  ],
  "tests": "ALL on final head a5a67ad47, worktree clean. Heavy runs through `bash /home/user/objectstack/scripts/pm/os-verify-lock.sh -c ...` with OS_VERIFY_LOCK_SLOT=issue-8125-docsnip; verdicts read from the wrapper's own VERDICT line, never a bare $?. BUILD: turbo build over the gate's own --build-filter closure - 'Tasks: 35 successful, 35 total', 'VERDICT command-exit 0 - held the lock 171s'. So no gate run below is an unbuilt-tree exit 2. PREDICTION STATED BEFORE RUNNING: the judged-block count would NOT move, because no block is added, removed or re-marked - only what 18 of them are judged against changes. Confirmed. check:doc-snippets BEFORE: exit 0, 'Semantic phase: 632 of 632 block(s) judged, 0 failed.' AFTER the sweep, BEFORE the docs fix: exit 1, '632 of 632 block(s) judged, 1 failed.' with '[semantic] content/docs/guide/schema-rendering.md:35:13 TS2353: Object literal may only specify known properties, and 'type' does not exist in type 'SchemaNode[]'.' FINAL: exit 0, '632 of 632 block(s) judged, 0 failed.', 'Every covered documentation snippet compiles against the built types.' Gate controls passed every run (resolution into packages/types/dist/index.d.ts, sentinel TS2305, positive 0, undeclared TS2307, root-declared TS2307). CEILING MEASURED, three legs on the committed tree, mutating content/docs/plugins/plugin-editor.mdx, each leg restored via `git checkout HEAD -- path` and proven byte-identical by git hash-object against the HEAD blob 5cb59b077c2407f4f468e331d2e936a88a31b400 plus an empty `git diff HEAD`; script carried `trap restore EXIT INT TERM` with an absolute REPO_ROOT path, and each leg printed an on-disk proof (anchor count before, injected-text count after, mutated blob hash differing from base) before the gate ran. LEG 0 (the block really is compiled): `value: zzzUndefinedIdentifier,` -> exit 1, 'plugin-editor.mdx:37:10 TS2304: Cannot find name zzzUndefinedIdentifier'. LEG A (THE CEILING): `zzzUndeclaredKeyNobodyDeclares: 'x',` -> exit 0, ZERO diagnostics. The annotation does NOT catch an undeclared/misspelled key - BaseSchema's index signature absorbs it. LEG B (THE CAPABILITY): `readOnly: 'not-a-boolean',` on a key declared boolean -> exit 1, 'plugin-editor.mdx:37:3 TS2322: Type string is not assignable to type boolean or undefined'. Final state after the trap: 'restored: hash 5cb59b077... matches HEAD blob, git diff HEAD empty'. OTHER GATES reading these pages, all exit 0: check:doc-types (1106 blocks, 891 type literals), check:doc-fences (227 documents), check:doc-examples, check:doc-example-readers, check-doc-links (17 scan roots), check-doc-expression-carriage (report-only), check:control-bytes (6714 tracked files). Plus a manual `grep -naP '[\\x00-\\x08\\x0b\\x0c\\x0e-\\x1f\\x7f]'` over the changed files: no hits. TESTS: `pnpm exec vitest run --maxWorkers=2 scripts/__tests__/` - VERDICT command-exit 0, 'Test Files 121 passed (121) / Tests 3630 passed (3630)'. This suite is owed because the diff edits a file under scripts/. The first run of it failed exactly one test (the fence-line pin); re-declared as that pin intends, green after. CHANGESET: `node scripts/check-changeset-presence.mjs` RUN, not guessed - exit 0, '9 file(s) changed, 0 of them published source of a package the release covers, 0 of them a manifest whose published contract moved ... no changeset is owed.' No skip-changeset label applied: in objectui the gate's verdict line is authoritative and that label is not this repo's mechanism. GOVERNED: `node scripts/check-governed-queue-guard.mjs --test` on all 9 paths - exit 0, 'NOT GOVERNED - 9 path(s) checked against 5 governed surface(s); none matched.' PR nonetheless opened draft and stays draft per dispatch; no maintainer-speed-read section, since the diff is not governed. LINT NARROWING, declared and measured rather than skipped: eslint.config.js scopes every rule block to files: ['**/*.{ts,tsx}'] or narrower, so .md/.mdx are outside the linted population entirely - the population comes from eslint's own config, not from a guess. The single .ts file in the diff is covered by the vitest run above. No type-aware linting is enabled, so nothing in this diff can move the verdict on an untouched file. Repo-wide `pnpm lint` is CI's run.",
  "four_axis_analysis": {
    "decision": "Surfaced by this sweep, NOT decided here: PageNodeSchema.body is declared SchemaNode[] while the page renderer's FlatContent normalizes a single node, and the sibling `children` on the same interface already accepts both. Three options. A: narrow the renderer to the declared type (drop the single-node normalization). B: widen the type to SchemaNode or SchemaNode[], matching `children` and the renderer. C: leave both, document the array form.",
    "实际业务需求": "MEASURED, not assumed. The single-node body spelling is genuinely authored: it was live in content/docs/guide/schema-rendering.md until this PR, i.e. the documentation itself taught it, so readers who copied that page wrote it. The renderer's normalization is therefore load-bearing for already-authored metadata and is not a speculative surface. What is NOT measured, and what triage should measure before choosing: how many single-node `body` values exist in real app metadata and in the example apps. Option A is only safe if that count is zero. This axis alone can flip the answer and is not decoration.",
    "项目长远合理性": "Contract-first says the declared type and the runtime must be one statement, so C (document and leave) is the weakest: it keeps two shipped surfaces disagreeing and preserves exactly the condition that let objectui#7713 sit green. Between A and B, A is the no-workaround direction - the normalization is a tolerance in the consumer, and `content ? [content as SchemaNode] : []` carries its own `as` cast, which is the marker of a shape the type system was talked out of. B is cheaper but ratifies a widening.",
    "防 AI 写代码犯错": "Decisive here, and it points at A. B widens a declared surface so that BOTH spellings become legal, which is precisely the consumer-side tolerance that hides bulk AI error: an agent authoring page metadata gets no signal about which form is canonical, and the two forms then diverge in downstream readers that were only ever written against the array. A makes the wrong form fail loudly at author time. Note the ceiling measured above bounds how much either option buys inside doc snippets: BaseSchema's `[key: string]: any` means a misspelled key stays invisible regardless, so this decision improves the TYPE-wrong case only - it must not be sold as more.",
    "创业阶段不扩散需求": "Startup-stage focus argues against B: widening a published type is capability expansion with no demonstrated pull, and the 2026-08-27 ruling ('项目在创业阶段，用户也很少，短期不考虑渐进') removes the staged-window option that would otherwise make B palatable - no dual-spelling grace period. Retire the tolerated spelling outright rather than blessing it. That said, sunk-cost is not an argument FOR A either: if the business-need axis finds live single-node bodies, A is a breaking change on real metadata and the honest answer becomes B plus an immediate retirement of the single-node form, not a permanent widening.",
    "recommendation": "A (narrow the renderer to the declared type), CONDITIONAL on the first axis: it is right on all three of the long-term, anti-AI-error and startup-focus axes, and it is the only option that leaves one statement instead of two. The condition is the one measurement I did not make and did not have the scope to make - the live count of single-node `body` values in app metadata and example apps. If that count is non-zero, the axes conflict (business need vs contract-first) and the trade-off goes to the maintainer, with B-plus-immediate-retirement as the fallback rather than B alone. ⛔ Under no reading is the type widened inside THIS PR, per ruling 2."
  },
  "mcp_calls": "2 — both `search_issues`, both FAILED (see out_of_scope_findings). Every other GitHub read and write went through repo-scoped REST or git; card body, all comments, the #7972 grading comment, the PR create and the PR read-back were REST.",
  "open_questions": [],
  "out_of_scope_findings": [
    "NOT FILED - handed to PM to file, dedupe channel down. CONCRETE DEFECT, so per this seat's mid-task correction it carries NO LABELS AT ALL (not `finding`, never a domain:*, no assignee) - triage grades it. Title: PageNodeSchema.body declares SchemaNode[] while the page renderer accepts a single node. Landing points: packages/types/src/layout.ts:781 (`body?: SchemaNode[];`, docblock 'Main content array') vs packages/components/src/renderers/layout/page.tsx:266-272 (FlatContent: `const nodes: SchemaNode[] = Array.isArray(content) ? content : content ? [content as SchemaNode] : [];`). The sibling `children` on the same interface is already `SchemaNode | SchemaNode[]`. Reproduction, measured on this branch: annotating guide/schema-rendering.md's page literal as PageNodeSchema produced exactly one diagnostic, TS2353 at :35:13, 'type does not exist in type SchemaNode[]'. Full three-option four-axis analysis is in the four_axis_analysis field of this report - please carry it onto the card. ⛔ Not widened here per ruling 2.",
    "NOT FILED - handed to PM. OBSERVATION (a census-reach gap, not a reproducible defect), so `finding` label ONLY. Triage's census spelling `const schema = {` is keyed to the identifier `schema`, so it counts neither prose mentions correctly (it over-counts: 2 of 28 hits are sentences, see premise_notes) nor bare schema literals under any other identifier (it under-counts). There are 8 of the latter in content/docs: blocks/index.mdx:71, guide/schema-rendering.md:367,370,371,372,374, plugin-markdown.mdx:178,208. Several are prose sketches like `{ /* ... */ }` that could never be annotated, so the actionable subset is smaller than 8 and wants triage before anyone sweeps it. ⛔ Deliberately NOT acted on here: ruling 4 forbids the sweep introducing a new scan population, and this is exactly one.",
    "CHANNEL FAILURE, reported rather than worked around - this is why neither card above is filed. Dedupe was impossible on this seat: (a) REST /search/issues returns HTTP 403 by design ('sessions are bound to their configured repositories'); (b) MCP search_issues fails twice with 'failed to fetch issue field values: API rate limit already exceeded for user ID 6194462' - the server-side unconditional Projects field_values GraphQL fetch, the exact leak rest-channel.md names, and it is NOT this session's own quota: /rate_limit reads core 15000/15000 and graphql 10000/10000 remaining; (c) the only remaining route was a full listing - `state=all&labels=finding` is 300+ issues over 3+ pages, which is the wide-table scan the rules forbid, and a page-1 reading would not be a dedupe reading anyway. Filing without dedupe and silently dropping the finding are both forbidden, so both findings go to PM with their full reproduction. ⛔ Nothing was filed under the old `finding`-on-everything wording, so there is no half-state to repair."
  ]
}

Generated by Claude Code

ACCEPT — domain:devx @ objectui execution seat, PM session session_01FhBNJcLRZLe8M87VcUgpKr, R46, reviewed 2026-09-08T02:35Z against GitHub and the tree, ⛔ never against the report's narrative.

⭐⭐ The census instrument counted its own justification as its own population

The card's spelling is git grep -c "const schema = {" over content/docs/**. It is a whole-file grep, and 2 of its 28 hits are sentences outside any fence. Read both here on origin/main:

plugin-form.mdx:394 — "…so an un-annotated const schema = { … } type-checks whatever is written in it, while const signUpForm: FormSchema makes a wrong validation shape a compile error."

plugin-grid.mdx:612 — "Annotating the literal is the point: an un-annotated const schema = { … } type-checks no matter what is written in it…"

⇒ Both over-counted "members" are prose arguing FOR the very sweep they were counted into. Real population 26 across 11 pages, not 28/13.

⭐ This is the dispatch's own warning landing on the card's own instrument — "a grep over a whole file cannot answer a question about one region of it" — and it is the fourth instance today, after this seat's three landing probes hit a docblock, a different schema and a dated historical sentence. Filed as objectui#8492 (finding only), with the mirror-image half: the spelling is keyed to the identifier schema, so it is blind to bare literals under any other name — 8 of those exist, several of them un-annotatable { /* ... */ } sketches, which is exactly why the dev ⛔ did not sweep them (ruling 4 forbids the sweep introducing a new scan population).

Numbers re-derived, ⛔ none carried

28/13 bare and 23/10 annotated on origin/main, against the card's 29/14 and 22/9 and triage's 30/15. PR #8124 did land — objectos-integration.mdx reads 0 bare — which the brief asked to be checked rather than assumed.

⚠️ And a hazard this seat created, which the dev flagged rather than swallowed. Its report notes the gate's judged-block count is 632, "not the 660/663 the brief carried from another card." Those figures were never a claim about this card — they are in the errata list this seat pastes into every claim comment, where 660 is named as a wrong number and 663 as its correction. ⇒ ⭐ A list of my own past errors, carried verbatim into unrelated briefs, is itself a source of numbers a dev can mistake for facts about its own card. That is a new class, distinct from the four false premises: not a wrong number, but a right number in the wrong place. The errata will be carried as a rule from here, ⛔ not as figures.

UNGATED_DOCS verified by reading it: 4 entries, all under docs/adr/** and docs/audits/**, none under content/docs/**. ⇒ This seat's mid-brief correction was right, and nothing was added.

⭐ The ceiling measured in three legs, not asserted

Each mutation proven on disk by blob hash against HEAD before any result was read, restored under trap … EXIT INT TERM with an absolute root and proven byte-identical:

leg	mutation	result
0 — is the block compiled at all?	`value: zzzUndefinedIdentifier`	exit 1, TS2304
A — the ceiling	`zzzUndeclaredKeyNobodyDeclares: 'x'`	exit 0, zero diagnostics
B — the capability	`readOnly: 'not-a-boolean'`	exit 1, TS2322

⇒ Ruling 1 discharged by measurement rather than by repeating it: the annotation catches a type-wrong value and ⛔ never a misspelled key, because BaseSchema ends [key: string]: any. Same discipline objectui#7925 landed an hour earlier.

⭐ One block turned red, and it was treated as the finding

Annotating guide/schema-rendering.md produced exactly one diagnostic — TS2353 at :35:13: a single object passed to a page node's body, which PageNodeSchema declares as SchemaNode[]. The renderer disagrees: FlatContent normalizes a non-array body through [content as SchemaNode], so a single node does render.

⇒ Per ruling 2 the dev fixed the documentation to the type and handed the divergence over. ⛔ The type was not widened. ⭐ That is the harder call: the tempting fix is one character on the type, and it would have ratified a widening inside a docs sweep.

Both handed-over findings were routed by this seat because the dev's dedupe channels were both down (REST /search/issues 403 by design; MCP search_issues twice rate-limited on another account's user ID, while this session read 15000/15000 core). It refused to file blind — and the dedupe this seat then ran found the first one is a duplicate of objectui#8310, already open, domain:ui, priority:p2. ⇒ ⛔ No card was filed; the corroboration went onto #8310 instead, with one reading it did not have: body?: SchemaNode | SchemaNode[] appears at layout.ts:419 and :617, so :781 is the outlier inside its own file, ⛔ not merely the narrow one. ⭐ This is what the dedupe discipline is for, and it worked because the dev declined to shortcut it.

Scope

18 of the 26 real literals annotated across 8 pages. 8 excluded with stated reasons, per the fold rules: 7 are declared fragments the gate does not compile at all — so they fail triage's own family test (each member independently checkable by the gate's per-block verdict) — and vscode-extension.mdx is excluded by ruling 3 as the Export-to-React command's verbatim product. ⛔ No page forced.

⚠️ The check-doc-snippet-types.test.ts change is a pin re-declaration, not a repair: README_SAMPLE_FENCE_LINE 206 → 207, because that pin keys objectui#7555's specimen on its fence line deliberately so an edit above it forces a re-declaration. It fired, and it was answered the way it intends.

Gate readings: 632 of 632 block(s) judged, 0 failed before → 1 failed after the sweep and before the docs fix → 0 failed final, with the judged count unmoved, as the dev predicted in writing beforehand. Build run over the gate's own --build-filter closure (35/35 tasks) so no reading is an unbuilt-tree exit 2. check-changeset-presence exit 0, run rather than guessed. All paths NOT GOVERNED.

Next: CI convergence → flip ready → post-flip guard → auto-merge SQUASH → queue confirmation → landing probe (scoped to the eight edited pages: each carries an import type and a const schema: XSchema; control: the two prose sentences at plugin-form.mdx and plugin-grid.mdx still present and still un-annotated — they are the population's own false positives, and if they vanished the sweep reached past its subject) → LANDED here and on #8125, which closes via Fixes.

Generated by Claude Code

Armed — domain:devx @ objectui execution seat, PM session session_01FhBNJcLRZLe8M87VcUgpKr, R46.

PR #8487 at a5a67ad47, each step read from its own output:

step	reading
CI convergence	28 checks, all green (`Live E2E (informational)` excluded), read 02:31:50Z
flipped ready	`ready_for_review` @ 02:31:58Z
post-flip governed-surface guard	`completed/success` @ 02:32:14Z — ⚠️ re-read after the flip, ⛔ not the pre-flip run
auto-merge	`SQUASH`
queue	`added_to_merge_queue` @ 02:32:22Z

Landing probe queued, and it is deliberately scoped to the eight edited pages rather than run as a repo-wide grep — this card's whole finding is that a whole-file grep cannot answer a question about one region of a file, and a probe that repeated the mistake would be the worst possible way to verify it:

probe — each of the eight pages carries an import type line and a const schema: XSchema declaration.
control — the two prose sentences at plugin-form.mdx and plugin-grid.mdx are still present and still un-annotated. They are the population's own false positives; if they vanished, the sweep reached past its subject.

⚠️ One thing this PR will merge into a queue where Test (shard 2/4) is currently intermittent — objectui#8493, the plugin-kanban contractEnvelope case that dequeued PR #8462 at 01:10Z and failed PR #8486's CI at 02:23Z. ⛔ It is unrelated to this diff (docs pages plus one pin re-declaration). If this PR is dequeued on that case, the dequeue is that card's, ⛔ not this PR's, and it gets the same single re-queue.

⛔ Not governed surface (Governed Surface Queue Guard green both before and after the flip). LANDED follows here and on the PR.

Generated by Claude Code

LANDED — domain:devx @ objectui execution seat, PM session session_01FhBNJcLRZLe8M87VcUgpKr, R46. PR #8487 merged 2026-09-08T02:49:08Z as 67299bf43; probe run on a clean extract of re-fetched origin/main, ⛔ never on the shared working tree, and ⛔ scoped to the eight edited pages.

page	annotated declarations
`core/schema-renderer.mdx` · `guide/quick-start.md` · `guide/schema-playground.md`	1 · 1 · 1
`guide/schema-rendering.md` · `plugins/plugin-charts.mdx`	2 · 6
`plugins/plugin-editor.mdx` · `plugins/plugin-map.mdx` · `plugins/plugin-markdown.mdx`	4 · 2 · 3

⭐ The control is the one that matters, and it holds: the two prose sentences at plugin-form.mdx and plugin-grid.mdx — the population's own false positives, the ones the census counted as members while they argued for the sweep — are still present and still un-annotated, one occurrence each. ⇒ The sweep reached its subject and nothing further.

The four bare literals remaining on the edited pages are the declared exclusions, verified in the tree rather than taken from the report:

guide/schema-rendering.md:114     const schema = { type: "my-component", // ... component props }
plugin-charts.mdx:290             {/* doc-snippet: fragment — shape excerpt; `salesData` is the reader's own rows */}

⇒ One is an ellipsis fragment that cannot be annotated; the other carries an explicit doc-snippet: fragment marker. Both fail triage's own family test — each member independently checkable by the gate's per-block verdict — which is exactly why they were excluded with reasons instead of forced.

⚠️ This probe's first pattern was wrong, and it is the fourth such slip this round. ^const schema: reported 0 annotations on schema-renderer.mdx; the declaration is at :84 and reads const schema: PageNodeSchema = { — indented, inside a function body in the snippet. An anchored pattern answered a question about a shape it had assumed. ⇒ Re-run allowing leading whitespace, and the reading above is the corrected one. ⭐ Fitting, on a card whose own finding is that an instrument counted its own justification.

pm:dispatched stripped in the same pass; domain:devx, documentation, priority:p3 stay. The card closed via Fixes.

Generated by Claude Code

Navigation Menu

Repository navigation

docs(census): 29 bare `const schema = {` literals across 14 `content/docs` pages compile against nothing — a one-pass annotation sweep instead of page-by-page cards (objectui#7778 / #7972 class) #8125

The population, measured on `origin/main` `083e1abbf` at 2026-09-06T17:28Z

Why a sweep and not fourteen cards

What the sweep must carry (from #7972's rulings, unchanged)

Back-links

⭐⭐ The census instrument counted its own justification as its own population

Numbers re-derived, ⛔ none carried

⭐ The ceiling measured in three legs, not asserted

⭐ One block turned red, and it was treated as the finding

Scope

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

docs(census): 29 bare const schema = { literals across 14 content/docs pages compile against nothing — a one-pass annotation sweep instead of page-by-page cards (objectui#7778 / #7972 class) #8125

Description

The population, measured on origin/main 083e1abbf at 2026-09-06T17:28Z

Why a sweep and not fourteen cards

What the sweep must carry (from #7972's rulings, unchanged)

Back-links

Activity

os-zhuang commented on Sep 7, 2026

claude commented on Sep 8, 2026

claude commented on Sep 8, 2026

claude commented on Sep 8, 2026

claude commented on Sep 8, 2026

⭐⭐ The census instrument counted its own justification as its own population

Numbers re-derived, ⛔ none carried

⭐ The ceiling measured in three legs, not asserted

⭐ One block turned red, and it was treated as the finding

Scope

claude commented on Sep 8, 2026

claude commented on Sep 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

docs(census): 29 bare `const schema = {` literals across 14 `content/docs` pages compile against nothing — a one-pass annotation sweep instead of page-by-page cards (objectui#7778 / #7972 class) #8125

The population, measured on `origin/main` `083e1abbf` at 2026-09-06T17:28Z