D4: docs sweep for the retired compound-name convention (#12176 stage 4)

[os-trump]

Blocked-by discharged 2026-08-25 — #12195 is CLOSED: D3 landed as PR #12378 (merge commit 7986d973 on main). The three compound arities are un-mounted and the SDK spells one URL encoding, so the docs teaching compound names now teach routes that no longer exist. Released to dispatch and claimed in the same stroke by PM session session_01H9StxQgG2DPA26XzZZqnJB.

Stage 4 of #12176's maintainer-ruled retirement (provenance on #12176 / #12194). ⛔ Not dispatchable until D3 (#12195) lands.

Scope: the live docs that teach compound names — content/docs/api/client-sdk.mdx:213 (getItem('object', 'views/all_leads')) and content/docs/api/error-catalog.mdx:599 (PUT /meta/lead/views/all_leads) per #12176's census, plus any reference D3's diff did not already correct (re-grep on the post-D3 ref; the census command set is on #12176). Replace with the dot-qualified spelling D1 enforces. ⛔ CHANGELOGs are historical records — never edited. ⛔ content/docs/releases/** untouched per the standing rule.

Clause-②: no — docs only.

Refs: #12176 · #12194 (D1) · #12195 (D3).

[os-trump]

Claim: PM direct-dispatch (the #12176 program — maintainer 2026-08-25, verbatim: 「斜杠不该存在，现在就立卡，你负责派发，然后给我结果」)
Session: session_01H9StxQgG2DPA26XzZZqnJB
Branch: claude/issue-12196-compound-name-docs-sweep
Worktree: objectstack-issue-12196
Domain: domain:cli
File surface: content/docs/** only (the two censused pages + whatever a post-D3 re-grep surfaces). ⛔ CHANGELOGs never edited. ⛔ content/docs/releases/** never edited. ⛔ Zero code, zero packages/**.
Clause-②: no — docs only; no gate label.
Blocked-by discharged in the body in this same stroke: #12195 closed via PR #12378 (7986d973). Non-governed docs pages → the normal review + queue flow applies (PM reviews the diff, then ready + auto-merge).

---

Generated by Claude Code

[os-trump]

os-dev-report

{
  "issue": 12196,
  "status": "done",
  "branch": "claude/issue-12196-compound-name-docs-sweep",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/12381",
  "premise_still_valid": true,
  "summary": "D4 docs sweep landed as draft PR #12381 (2 files, +20/-19, commit e68376d4 on base 7986d973). The premise verified: D3's merge touched ZERO files under content/docs, so both censused pages were still live. content/docs/api/client-sdk.mdx — the meta.getItem example addressed 'views/all_leads' and promised compound names 'pass through unencoded'; both halves were dead (the name is refused at D1's publish door, and D3 put encodeURIComponent on every /meta item address), respelled to getItem('view', 'crm_lead.pipeline'), which is the grammar's own published exemplar and exactly ViewItemNameSchema's <object>.<viewKey> identity — no new spelling invented. content/docs/api/error-catalog.mdx — the unmintable-type entry documented TWO served exemptions; the compound-arity one was deleted rather than respelled because an exemption has no dot-spelling, and because it was ALREADY false before this PR: refuseUnmintableMetaType's own header in packages/metadata-protocol/src/protocol.ts records that the slash exemption was removed by #12194 (D1), NOT D3 — refuseUngrammaticalMetaItemName runs first and refuses every slash-bearing name before the probe. The residue that exemption documented (PUT /meta/fieldz/a/b being accepted) is closed with it, and the page now says so; a short retirement note is kept so a caller who knew the old behaviour is not left reading the page as merely incomplete. Two consequential plural references to 'the exemptions' corrected to the singular. No page resisted respelling — no fork to report. Fences honoured: content/docs/releases/** (v14/v16/v17 carry compound-era text), CHANGELOGs, all packages/** untouched. No changeset: docs-only, releases nothing; skip-changeset label applied and READ BACK as ['size/s','skip-changeset'].",
  "tests": "Population measured: 403 .md/.mdx files under content/docs/** on the post-D3 ref, corroborated independently by check-doc-frontmatter's own count ('content/docs (pageSchema, floor 1): 403 page(s) parse'). Instrument proven BEFORE trusting any zero — positive control 'views/all_leads' fires on exactly 2 lines, both censused pages. Swept: crm/task, :section, compound/Compound, sub-resource, unencoded, %2F, all_leads, getItem(, saveItem(, slash, quoted '<snake>/<snake>' shapes, and 3-segment /meta/<x>/<y>/<z>. Every other hit is a true negative and was left alone: surviving literal routes (/publish, /rollback, /history, /audit, /diff, /layers, /references, /tree, /schema, /state/:field), MIME types (application/json, image/jpeg), state-machine/index/view-cell 'compound' vocabulary, and page:section / _sections layout+i18n concepts. content/docs/references/api/protocol.mdx:2336 already teaches the new grammar (landed by D1) — untouched. GATES: family list self-derived by 'node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack' (no paths passed; it read change set = 2 paths, committed 2 / working tree 0), 24 matched families, ALL RUN AND GREEN on the FINAL commit e68376d4, exit codes captured before any pipe (per-gate redirect then EXIT=$?), verdicts quoted from each gate's own output: check:error-status-conformance 'every derivable runtime status is documented, and every documented status is reachable' (the gate owning this exact page); spec check:skill-examples '260 prose examples type-check across 3 surface(s) — every marked block parsed, so tsc ran the SEMANTIC pass on all of them' (this is what type-checks the edited client-sdk.mdx example against the real built @objectstack/client declarations); check:docs-audit-scope 'docs-accuracy-audit scope is in sync with content/docs/: 189 hand-written doc(s)' + 'release-owned pages are in scope and read-only: 9 page(s)'; check:doc-authoring 'doc authoring guard: 390 files clean — no bare metadata literals'; check:doc-anchors '278 internal #fragment link(s) across 408 source file(s) all resolve to a real heading'; check:doc-route-spelling 'route-spelling guard: population clean — every shape-matched literal spells its ledger row'; check:nul-bytes 'OK (scanned 6852 text file(s) ... no raw ASCII control bytes)'; plus doc-frontmatter, docs-single-h1, docs-redirects, docs-section-name, section-landing-index, published-readme-links, role-word, react-page-adapter-contract, cross-package-test-inputs, ci-filter-parity, spec check:docs/liveness/empty-state/variant-docs/strictness-ledger, lint check:doc-formula-expressions/doc-security-posture — all exit 0. Four of those first exited 1 with their own 'PREREQUISITE NOT MET — nothing was measured' text (missing packages/spec/json-schema; unbuilt spec/lint/formula/client-react dist); those are build-artifact prerequisites, NOT findings — after turbo build of those packages all four are green above. NO ABLATION IS OWED and none was invented: the change is prose plus one example, with no guard whose failure mode a mutation would demonstrate; the one executable artifact is covered by check:skill-examples' semantic tsc pass. All heavy commands ran through scripts/pm/os-verify-lock.sh (lock held 17s/170s/144s/45s, waited 0s each).",
  "open_questions": [],
  "out_of_scope_findings": [
    "NOT FILED — reporting to PM instead, because the mandated dedup search could not be run from this seat: content/docs/kernel/contracts/metadata-service.mdx:315 and :349 spell a view item name FLAT — metadataService.get('view', 'account_list') and getEffective('view', 'account_list', ...) — while packages/spec/src/ui/view.zod.ts ViewItemNameSchema pins view item identity on QUALIFIED_ITEM_NAME_PATTERN, which REQUIRES at least one dot ('<object>.<viewKey>', e.g. crm_lead.pipeline). Not slash-bearing, so squarely outside this card's ruled scope, and I did not touch it. Uncertain enough to need triage rather than a mechanical fix: it turns on whether a stored view row's sys_metadata name must satisfy ViewItemNameSchema or only METADATA_ITEM_NAME_PATTERN (which accepts a flat name). WHY UNFILED: rule-3 filing requires a pre-file dedup search over open issues via the REST list endpoints, and the REST channel is unavailable from this dev seat — curl to api.github.com returns HTTP 403 'GitHub access is not enabled for this session' on both the labels POST and a plain issues list probe (GITHUB_TOKEN present but a 14-char placeholder). Only the MCP/GraphQL channel works here, which the standing contract forbids me from spending on dedup. Filing blind risks exactly the duplicate card the rule guards against, so I am handing the PM the evidence to file (or dismiss) with a working channel."
  ]
}

Two deviations, declared

1. skip-changeset applied via the FALLBACK path, not the additive POST. The prescribed additive endpoint returned HTTP 403 (GitHub access is not enabled for this session) — the REST channel is unavailable from this seat, not a permissions problem with the label itself. Fallback used as specified: read (["size/s"], the size labeler had already run) → union → whole-set write → read back, which confirms ["size/s","skip-changeset"]. Both labels survived; nothing was clobbered. get_label confirms the label is a real repo mechanism with the matching description: "PR has no user-facing published change; bypasses the changeset gate".
2. Local verification did not include the repo-wide pnpm lint sweep — that run is CI's. The 24 path-derived families were run in full, so this is not a narrowing of the derived list.

PR is draft; ready-flip and auto-merge deliberately left to the PM. Base main has moved to f6344e7f since my branch point (7986d973) — no conflict expected on two docs files, but CI will merge-test it.

---

Generated by Claude Code

---

Generated by Claude Code