sweep: docs-audit wave (#10563) — 13 factual corrections across content/docs/** where the page contradicts the enforced platform

[os-zhuang]

Anchor card for the sweep-package promotion of the 2026-08-21 docs-audit finding wave (audit dispatch: #10563, closed). Triage seat authored per the batch-promotion rules (five gates below). This card is the claim/dispatch object; the member cards keep their finding label and are NOT dispatch candidates.

Family criterion (gate ①)

Every member is the same defect shape: a content/docs/** page states something the current enforced platform contradicts, and the fix is a prose/example correction on that page against the cited source of truth. No member changes any contract, schema, or gate.

Members (13)

Issue	Page(s)	One-line defect
#10581	12 pages (list in card)	22 ObjectSchema.create() examples omit sharingModel; os validate errors on every one (SECURITY_OWD_UNSET)
#10582	getting-started/examples.mdx	"Quick Run" omits the required pnpm build, contradicts README.md:210-212
#10583	getting-started/index.mdx	advertises GraphQL via IGraphQLService — contract does not exist, /graphql removed
#10584	data-modeling/field-types.mdx:533, validation-rules.mdx:373	location value documented {latitude,longitude}; enforced contract is {lat,lng} (field-value.zod.ts:251-256)
#10585	data-modeling/validation.mdx	retired partial index key presented as live
#10586	data-modeling/index.mdx	still sells joins + window functions, both retired in protocol 17
#10587	validation-rules.mdx	promises constraints for "each field type", covers 44 of 49
#10588	data-modeling/field-types.mdx	says unknown field keys are "stripped" — FieldSchema is a strictObject that rejects with guidance (ADR-0078)
#10589	validation-rules.mdx	says currency is stored as {value,currency} — it is a bare number
#10590	data-modeling/schema-design.mdx	apiMethods sample says "six primitives" and lists five — silently denies bulk
#10591	data-modeling/index.mdx	"Four database drivers" — there are five; driver-turso omitted
#10578	ui/actions.mdx	rowActions/bulkActions shown at defineView container top level — strictObject rejects it
#10579	ui/ form-section pages	3 of 5 form-section examples omit name

Read each member card in full before editing — each carries exact line numbers, the source-of-truth citation, and (for #10581) the full 22-site table.

Gates ②–⑤

• ② PR body MUST carry a per-member checklist: 落点 (file:line) | before | after — one row per member, and a Fixes #<n> line per member.
• ③ Zero changes outside the listed member sites. Docs-only diff; the PR self-evidences (no source, no gates, no content/docs/references/**, no content/docs/releases/**).
• ④ Out-of-scope discoveries are filed as separate findings, never folded in.
• ⑤ Exclusion list — looks like family, is NOT in this sweep:
  • @objectstack/studio's package header describes a pending boot-path switch that already concluded the other way #10592 — @objectstack/studio package-header prose: not content/docs/**, already queued (domain:cli).
  • finding: the checklist's area-scoped fixtures recipe convention has hit its stated revisit trigger — 3 areas, and a consumer that cannot reference the recipe it needs #10593 — QA checklist fixtures recipe convention: internal QA tooling, not customer docs; graded separately.
  • [finding] 22 object examples across 12 docs pages omit sharingModel — the platform's own os validate rejects every one of them #10581's mechanization idea (run os validate over os:check blocks in packages/spec/scripts/check-skill-examples.ts) — gate work in the spec lane, explicitly NOT part of this sweep; tracked as a separate finding.
  • Any defect in content/docs/references/** — generator territory per docs audit (1/2) — the first-run path: index, build-without-code, getting-started/, concepts/, data-modeling/ #10563; file against the generator.

Dispatch notes (for the devx seat)

• Premise freshness: wave filed 2026-08-21 ~04:0xZ; triage spot-checked [finding] location documented as {latitude,longitude} on two pages; the enforced value contract is {lat,lng} — the deprecated schema's own docblock says exactly this #10584 and [finding] 22 object examples across 12 docs pages omit sharingModel — the platform's own os validate rejects every one of them #10581 against origin/main @ bde0ab9 (2026-08-21 ~06:2xZ) — both hold.
• Same-file serial check at claim time: queued docs cards content/docs/ui/index.mdx credits themes with spacing (retired at #3494) and its Cards grid is missing five of the module's pages #10487 (ui/index.mdx), docs(ui): the react-pages live-data sample reads result.records, which is always undefined — and its Callout misstates what a dropped option does #10469 (ui/ react-pages sample), [docs] ai/agents.mdx still documents agent.tools as a live field — it was tombstoned in protocol 17 #10355 (ai/agents.mdx) touch neighbouring docs — different files on today's reading, re-verify at dispatch.
• Size/model suggestion: M, mode:subagent; prose-vs-source verification per item — default judgment tier.

Triage: lands in content/docs/** ⇒ domain:devx; concrete named landing spots, no open questions ⇒ pm:queue.

[claude]

Claim — PM dispatch (devx seat)

• Session: c970724d-303c-5614-9d20-a3f92205cfad
• Branch: claude/issue-10616-docs-audit-sweep

Premise re-verified on origin/main = dd8172ee22 (fetched 2026-08-21T08:55:41Z), which is
later than triage's bde0ab9 spot-check. Two members re-derived independently:

• [finding] data-modeling/index.mdx says "Four database drivers in this repo" — there are five; driver-turso is omitted and its sibling page documents it as first-class #10591 holds. content/docs/data-modeling/index.mdx:39 reads "Four database drivers in
  this repo" and lists four, while the tree carries five — driver-sql, driver-mongodb,
  driver-memory, driver-sqlite-wasm and packages/drivers/driver-turso.
• [finding] location documented as {latitude,longitude} on two pages; the enforced value contract is {lat,lng} — the deprecated schema's own docblock says exactly this #10584 holds, and its citation is wrong. The docs side is confirmed at
  content/docs/data-modeling/field-types.mdx:533, which still teaches
  { latitude, longitude, altitude?, accuracy? }. But the source of truth is
  packages/spec/src/data/field-value.zod.ts — the card cites field-value.zod.ts:251-256
  without the data/ segment, and that path does not resolve. The real anchor is :250-253
  (lat: z.number().min(-90).max(90), lng: …), and the file's own header at :24-25 names
  {latitude, longitude} as "the never-consumed" / retired shape. So the finding is
  stronger than the card states, not weaker.

⚠️ Because one of the two citations I checked was wrong, the dispatch requires every member's
line numbers and source-of-truth path to be re-derived at the dev's own merge base rather than
adopted. A sweep is exactly where a stale citation gets copied into a diff without anyone
looking.

Same-file serial check at claim time, per the card's dispatch note: #10469 (ui/ react-pages
sample) and #10355 (ai/agents.mdx) are both still pm:queue, unassigned, and not in flight
from this seat; neither names a file in this sweep. #10487 is not on the devx board. No serial
constraint.

No collision with this seat's five in-flight agents — #10653 (packages/lint), #10566
(check-cross-package-test-inputs.mjs), #10667 (the scripts/** entry-guard burn-down), #10490
(new gate + lint.yml) and #10664 (#10687, dispatch-gates.mjs + packages/lint). This sweep
is content/docs/** only and touches none of them.

The 13 member cards keep their finding label and are not dispatch candidates; this anchor
card is the claim object.

---

Generated by Claude Code