`content/docs/utilities/index.md` still documents the `ObjectStackProvider` phantom API that #4124 removed from the page one file over

[os-support-ai]

Out-of-scope finding from #5343 (the fabricated-export sweep over content/docs/guide/** + content/docs/api/schema-reference.md). This site is in content/docs/utilities/**, outside that card's file surface, so it is filed rather than fixed there. Filed unassigned, not claiming.

Fact (measured on origin/main = bdf8cf76e, against the packages' built dist/index.d.ts)

content/docs/utilities/index.md:161-173, section Data Integration:

import { ObjectStackProvider } from '@object-ui/data-objectstack'

function App() {
 return (
 < ObjectStackProvider
 apiUrl="https://api.example.com"
 apiKey="your-api-key"
 >
 < SchemaRenderer schema={schema} />
 < /ObjectStackProvider>
 )
}

Compiled against the built types by the same harness scripts/check-doc-snippet-types.mjs uses:

content/docs/utilities/index.md:163 TS2724: '"@object-ui/data-objectstack"' has no exported member named 'ObjectStackProvider'. Did you mean 'ObjectStackError'?

After #5343 lands this is the only missing-export diagnostic left in the entire scanned corpus (637 blocks, 541 semantically judged) — it is named as such in the UNGATED_DOCS header note.

Why it matters, and why it is not a duplicate

#4124 established the finding and PR4129 fixed it — but only on content/docs/utilities/data-objectstack.mdx. The identical phantom shape survived one file over, in the utilities index, and the whole argument of #4124 still applies verbatim: @object-ui/data-objectstack is headless (no react in any dependency field, no React import in src/), so ObjectStackProvider has no home in that package — this is not an export that moved.

content/docs/utilities/index.md is on the UNGATED_DOCS ledger, so the gate does not report it today; the entry names the symbol by hand.

Fix direction (not pre-judged)

Same direction PR4129 took on the sibling page: rewrite the section against the real surface (createObjectStackAdapter / ObjectStackAdapter, wired through the renderer's dataSource per Commandment #1), and rewrite the page's ledger entry to its new measured mix. ⛔ Not by adding the export — that is a contract change.

Searched for duplicates

ObjectStackProvider, data-objectstack docs, utilities index fabricated export over open issues: zero open hits. #4124 and #4130 are closed and cover the sibling .mdx page and its README, not this file.

---

Generated by Claude Code

[os-zhuang]

Triage: promoted pm:queue, type Bug (docs). content/docs/utilities/index.md:161-173 teaches a phantom export; direction is settled by the PR4129 precedent on the sibling page (rewrite against createObjectStackAdapter/ObjectStackAdapter), plus the UNGATED_DOCS ledger update. Nothing to ask.

---

Generated by Claude Code

[claude]

Claim: PM loop round 21
Session: session_01RV6yuVCxymHYE16PL9vQkE
Branch: claude/issue-5360-phantom-objectstackprovider
Worktree: objectui-issue-5360
Domain: repo:objectui
File surface: content/docs/utilities/index.md + the UNGATED_DOCS ledger (stop on breach; explain in the report)
Container & model: S, mode:subagent
Clause-②: no
Serial constraints cleared: none — sibling page already fixed by PR4129; follow that precedent

---

Generated by Claude Code

[os-support-ai]

{
 "issue": 5360,
 "status": "done",
 "branch": "claude/issue-5360-phantom-objectstackprovider",
 "pr": "https://github.com/objectstack-ai/objectui/pull/5460",
 "premise_still_valid": true,
 "summary": "The Data Integration section of content/docs/utilities/index.md is rewritten on the PR4129 precedent: the phantom `ObjectStackProvider` import is gone, replaced by `createObjectStackAdapter` returning a plain DataSource injected through @object-ui/react's `SchemaRendererProvider`, with `apiUrl`/`apiKey` corrected to the config's real `baseUrl`/`token`. The block is now self-contained (imports every name it uses, types its schema literal as the real `ObjectGridSchema` from @object-ui/types), which also retired the two TS2304 undefined-name diagnostics the ledger entry carried. Because that was the page's only ts/tsx block and it now measures zero diagnostics, content/docs/utilities/index.md LEAVES check-doc-snippet-types.mjs's UNGATED_DOCS ledger entirely (covered 158 -> 159, ungated 64 -> 63) and two now-false header claims in the same script were corrected: the '20 .md pages' count is 19, and 'exactly one entry still names a missing export' now records what became of it — no ledger entry names a missing export any more. File surface held to three files: the doc, the ledger script, and the changeset; content/docs/guide/react-pages.md was not touched (sibling card #5413 in flight).",
 "tests": "All on 7b289c91b (branch head = final commit); heavy runs serialised through flock /tmp/os-heavy-verify.lock. BUILD FIRST: `pnpm turbo run build $(node scripts/check-doc-snippet-types.mjs --build-filter) --concurrency=2` -> '32 successful, 32 total'. BEFORE (origin/main content, same harness the gate uses — analyze()+compileSnippets() imported from scripts/check-doc-snippet-types.mjs, every other doc declared ungated so only this page compiles): 'content/docs/utilities/index.md:163:10 TS2724: \"@object-ui/data-objectstack\" has no exported member named ObjectStackProvider. Did you mean ObjectStackError?' + ':171:8 TS2304 Cannot find name SchemaRenderer' + ':171:31 TS2304 Cannot find name schema' — 'Semantic phase: 1 of 1 block(s) judged, 1 failed', total 3 diagnostics, matching the ledger's hand-written TS2724x1 + 2 undefined-name. AFTER: 'Syntax phase: 0 block(s) failed to parse. Semantic phase: 1 of 1 block(s) judged, 0 failed. Total diagnostics: 0'. Harness controls green on every run: resolution landed on packages/types/dist/index.d.ts (built artifact, not src), planted sentinel produced TS2305, positive control 0 diagnostics, 0 src leaks. COUNTER-PROBE on the zero (the direction I predicted and observed: RED, this file by name): re-planting ObjectStackProvider beside the real import turned BOTH the targeted probe and the FULL gate red — 'content/docs/utilities/index.md:166:36 TS2724 ... ObjectStackProvider', 'Semantic phase: 88 of 88 block(s) judged, 1 failed' — proving the ledger removal really enrolled the page in the gate; reverting restored green (mutation applied and reverted ON TOP of the commit, so the pushed file is byte-identical; git status clean). Every grep zero counter-probed: ObjectStackProvider in packages/data-objectstack/dist/index.d.ts = 0 (grep exit 1) vs ObjectStackAdapter = 16; ObjectStackProvider in the fixed page = 0 vs createObjectStackAdapter = 3. FULL GATE, exit code captured directly (not through a pipe): GATE_EXIT=0 — 'Scanned 222 document(s): 159 covered, 63 ungated / Covered blocks: 98 — 88 to compile, 10 declared fragment(s) / Semantic phase: 88 of 88 judged, 0 failed / Every covered documentation snippet compiles against the built types.' OTHER GATES: `npx vitest run scripts/__tests__/check-doc-snippet-types.test.ts --maxWorkers=2` -> 'Test Files 1 passed (1), Tests 20 passed (20)', VITEST_EXIT=0; check-doc-component-types.mjs -> 'Every documented component type is registered' (object-grid is a registered key); check-doc-links.mjs -> 'Links are valid across 13 scan roots'; check-control-bytes.mjs -> 'OK (scanned 4520 tracked text file(s); skipped 85 binary)'; check-changeset-presence.mjs -> '1 changeset(s) added', exit 0; check-changeset-fixed.mjs + check-changeset-no-major.mjs -> both exit 0; `pnpm type-check:scripts` -> exit 0; `npx eslint scripts/check-doc-snippet-types.mjs` -> exit 0; control-byte self-scan over the three changed files -> no matches (grep exit 1). No ablation was needed: this change is documentation prose, not a guard, so there is no built artifact to re-derive.",
 "open_questions": [],
 "out_of_scope_findings": []
}

PR4129 precedent followed (read from the PR, not invented): (1) delete the phantom React API rather than adding the export — @object-ui/data-objectstack is headless, so ObjectStackProvider has no home there; (2) teach createObjectStackAdapter returning a plain DataSource, with new ObjectStackAdapter(config) as the class form; (3) inject at the renderer boundary via @object-ui/react's SchemaRendererProvider, noting SchemaRenderer's explicit dataSource prop as the per-render alternative; (4) apiUrl/apiKey become the config's real baseUrl/token; (5) keep the schema node's own dataSource key distinct from the adapter — the spec's per-element binding says what to query, the adapter says how to reach the backend.

Ledger disposition, with the measurement: the page can and does leave UNGATED_DOCS. It holds exactly one ts/tsx fenced block (six others are ```bash), and that block now measures 0 diagnostics, so it is removed from the ledger rather than re-measured — the ledger's own rule is that it can only shrink. The sibling content/docs/utilities/data-objectstack.mdx stays ungated for a different reason: 16 undefined-name diagnostics across its many blocks, untouched by this card.

---

Generated by Claude Code

[os-support-ai]

os-dev-report

(The HTML-comment marker on the previous comment did not survive GitHub's sanitizer — read back and confirmed stripped — so this comment carries the same report with a literal-text marker instead. This one is the authoritative copy; the previous comment is identical in content.)

{
 "issue": 5360,
 "status": "done",
 "branch": "claude/issue-5360-phantom-objectstackprovider",
 "pr": "https://github.com/objectstack-ai/objectui/pull/5460",
 "premise_still_valid": true,
 "summary": "The Data Integration section of content/docs/utilities/index.md is rewritten on the PR4129 precedent: the phantom `ObjectStackProvider` import is gone, replaced by `createObjectStackAdapter` returning a plain DataSource injected through @object-ui/react's `SchemaRendererProvider`, with `apiUrl`/`apiKey` corrected to the config's real `baseUrl`/`token`. The block is now self-contained (imports every name it uses, types its schema literal as the real `ObjectGridSchema` from @object-ui/types), which also retired the two TS2304 undefined-name diagnostics the ledger entry carried. Because that was the page's only ts/tsx block and it now measures zero diagnostics, content/docs/utilities/index.md LEAVES check-doc-snippet-types.mjs's UNGATED_DOCS ledger entirely (covered 158 -> 159, ungated 64 -> 63) and two now-false header claims in the same script were corrected: the '20 .md pages' count is 19, and 'exactly one entry still names a missing export' now records what became of it — no ledger entry names a missing export any more. File surface held to three files: the doc, the ledger script, and the changeset; content/docs/guide/react-pages.md was not touched (sibling card #5413 in flight).",
 "tests": "All on 7b289c91b (branch head = final commit); heavy runs serialised through flock /tmp/os-heavy-verify.lock. BUILD FIRST: `pnpm turbo run build $(node scripts/check-doc-snippet-types.mjs --build-filter) --concurrency=2` -> '32 successful, 32 total'. BEFORE (origin/main content, same harness the gate uses — analyze()+compileSnippets() imported from scripts/check-doc-snippet-types.mjs, every other doc declared ungated so only this page compiles): 'content/docs/utilities/index.md:163:10 TS2724: @object-ui/data-objectstack has no exported member named ObjectStackProvider. Did you mean ObjectStackError?' + ':171:8 TS2304 Cannot find name SchemaRenderer' + ':171:31 TS2304 Cannot find name schema' — 'Semantic phase: 1 of 1 block(s) judged, 1 failed', total 3 diagnostics, matching the ledger's hand-written TS2724x1 + 2 undefined-name. AFTER: 'Syntax phase: 0 block(s) failed to parse. Semantic phase: 1 of 1 block(s) judged, 0 failed. Total diagnostics: 0'. Harness controls green on every run: resolution landed on packages/types/dist/index.d.ts (built artifact, not src), planted sentinel produced TS2305, positive control 0 diagnostics, 0 src leaks. COUNTER-PROBE on the zero (direction predicted and observed: RED, this file by name): re-planting ObjectStackProvider beside the real import turned BOTH the targeted probe and the FULL gate red — 'content/docs/utilities/index.md:166:36 TS2724 ... ObjectStackProvider', 'Semantic phase: 88 of 88 block(s) judged, 1 failed' — proving the ledger removal really enrolled the page in the gate; reverting restored green (mutation applied and reverted ON TOP of the commit, so the pushed file is byte-identical; git status clean). Every grep zero counter-probed: ObjectStackProvider in packages/data-objectstack/dist/index.d.ts = 0 (grep exit 1) vs ObjectStackAdapter = 16; ObjectStackProvider in the fixed page = 0 vs createObjectStackAdapter = 3. FULL GATE, exit code captured directly (not through a pipe): GATE_EXIT=0 — 'Scanned 222 document(s): 159 covered, 63 ungated / Covered blocks: 98 — 88 to compile, 10 declared fragment(s) / Semantic phase: 88 of 88 judged, 0 failed / Every covered documentation snippet compiles against the built types.' OTHER GATES: `npx vitest run scripts/__tests__/check-doc-snippet-types.test.ts --maxWorkers=2` -> 'Test Files 1 passed (1), Tests 20 passed (20)', VITEST_EXIT=0; check-doc-component-types.mjs -> 'Every documented component type is registered' (object-grid is a registered key); check-doc-links.mjs -> 'Links are valid across 13 scan roots'; check-control-bytes.mjs -> 'OK (scanned 4520 tracked text file(s); skipped 85 binary)'; check-changeset-presence.mjs -> '1 changeset(s) added', exit 0; check-changeset-fixed.mjs + check-changeset-no-major.mjs -> both exit 0; `pnpm type-check:scripts` -> exit 0; `npx eslint scripts/check-doc-snippet-types.mjs` -> exit 0; control-byte self-scan over the three changed files -> no matches (grep exit 1). No ablation was needed: this change is documentation prose, not a guard, so there is no built artifact to re-derive.",
 "open_questions": [],
 "out_of_scope_findings": []
}

PR4129 precedent followed (read from the PR, not invented): (1) delete the phantom React API rather than adding the export — @object-ui/data-objectstack is headless, so ObjectStackProvider has no home there; (2) teach createObjectStackAdapter returning a plain DataSource, with new ObjectStackAdapter(config) as the class form; (3) inject at the renderer boundary via @object-ui/react's SchemaRendererProvider, noting SchemaRenderer's explicit dataSource prop as the per-render alternative; (4) apiUrl/apiKey become the config's real baseUrl/token; (5) keep the schema node's own dataSource key distinct from the adapter — the spec's per-element binding says what to query, the adapter says how to reach the backend.

Ledger disposition, with the measurement: the page can and does leave UNGATED_DOCS. It holds exactly one ts/tsx fenced block (six others are bash), and that block now measures 0 diagnostics, so it is removed from the ledger rather than re-measured — the ledger's own rule is that it can only shrink. The sibling content/docs/utilities/data-objectstack.mdx stays ungated for a different reason: 16 undefined-name diagnostics across its many blocks, untouched by this card.

---

Generated by Claude Code