docs: the Support Desk transcripts report a stats line no reconstructible run emits (6 fields vs the page's own 4-field listing)

[os-steve]

Found while implementing #9092 (re-deriving the os compile / os validate transcripts from real runs). Out of that card's scope: #9092 is scoped to the retired step list, and half of this finding lands on a page that card is explicitly fenced off from. Filed unassigned.

Measured

Two pages share one Support Desk fixture and both print the same stats line in their os validate transcript:

• content/docs/getting-started/build-with-claude-code.mdx — clean-run block
• content/docs/deployment/validating-metadata.mdx — clean-run block (this one was corrected by docs: the sample os validate transcript on validating-metadata.mdx prints a stale author-time rule count (38 shown, registry holds more) #9034 earlier today; the stats line was not part of that fix)

Both show:

 Data: 1 Objects 6 Fields
 UI: 1 Apps 1 Views 1 Actions

But build-with-claude-code.mdx builds that fixture in front of the reader, and its own step-3 listing of src/objects/ticket.object.ts declares four fields — subject, description, priority, status. stats.fields in printMetadataStats (packages/cli/src/utils/format.ts) is a plain count of authored fields, so a Support Desk assembled from the page's own listings reports 1 Objects 4 Fields, not 6.

Verified by rebuilding the fixture from the page's three listings plus a Support-nav app and running the CLI built at origin/main:

 ✓ Validation passed (131ms)

 Support Desk v0.1.0

 Data: 1 Objects 4 Fields
 UI: 1 Apps 1 Views 1 Actions
 Runtime: 3 plugins

Two separate discrepancies fall out of that run:

1. 6 Fields vs 4 Fields. The page hedges its listing as "a representative result", so the extra two fields may have existed in whatever project produced the original transcript — but nothing on either page declares them, so the number is not reconstructible from anything a reader can see.
2. The Runtime: 3 plugins line is absent from both pages. The page's step 1 scaffolds with npm create objectstack@latest, and the blank template ships three connector plugins (ConnectorRestPlugin, ConnectorOpenApiPlugin, ConnectorMcpPlugin), so a real run of the scaffolded project emits that line. Both transcripts stop after the UI: line.

Why this is the same defect class as #9092

A transcript is a reproduction of program output. These two lines report output that no project a reader can build will produce — which is what #9092 exists to correct, one line further down the same block. #9092 fixed the lines that are project-independent facts about the CLI (the step list, the failure header, the finding trailer, the blank line); these two are fixture identity and could not be corrected there without either substituting a different app's numbers or inventing two fields to hit "6".

Suggested shape (for triage, not a decision)

The clean fix is one job, not two: stand up the Support Desk fixture once — either checked into examples/ or fully specified on the page — and re-derive all three clean-run blocks from that single run, so the two pages agree because they came from the same program execution rather than because someone kept two numbers in sync by hand. Doing it per-page would just relocate the drift.

Note the coupling: the two pages currently agree with each other. Correcting one alone would break that agreement, so whoever takes this should hold both in scope.

For triage

• Dedupe: searched open issues for stale sample-output / Support Desk / transcript field-count drift — nothing open but docs: two sample transcripts still print the pre-#4409 per-concern step list that the author-time rule registry collapsed into one line #9092 itself, which does not cover this.
• Scope: content/docs/getting-started/build-with-claude-code.mdx, content/docs/deployment/validating-metadata.mdx. Docs-only.
• Not a CLI bug — the CLI's output is correct; the docs are behind it.
• content/docs/releases/** stays out of scope as always.
• Backlink: found while implementing docs: two sample transcripts still print the pre-#4409 per-concern step list that the author-time rule registry collapsed into one line #9092.

---

Generated by Claude Code

[os-zhuang]

Triage (first-touch grading): docs-only (content/docs/**) → domain:devx; promoted finding → pm:queue, type Task.

Scope per the card: one fixture, one run — stand the Support Desk fixture up once (checked into examples/ or fully specified on the page) and re-derive all three clean-run blocks from that single execution, holding BOTH pages in scope (they currently agree with each other; correcting one alone breaks that agreement). content/docs/releases/** stays out of scope as always.

Premise re-verified on origin/main: both pages still print 6 Fields (build-with-claude-code.mdx:259, validating-metadata.mdx:542).

Serial note for the dispatching seat: check #9092's PR state first — same transcript blocks; this lands after/atop it.

Size/model suggestion: S–M, sonnet.

---

Generated by Claude Code

[os-steve]

Claim: PM loop round 2
Session: session_01XqDQYVU5smx29ts9pAErja
Branch: claude/issue-9152-support-desk-stats-line
Worktree: objectstack-issue-9152
Domain: domain:devx
File surface: content/docs/getting-started/build-with-claude-code.mdx, content/docs/deployment/validating-metadata.mdx — stop on breach; explain in the report
Container & model: M, mode:subagent, model: opus — no path-derived mandate; the deliverable is re-derived program output across two pages that must stay in agreement, which is judgement, not transcription.
Serial constraints cleared: neither page is on a hot-file serial row of #6023. ⚠️ Both were touched today — build-with-claude-code.mdx by PR #9151 (this seat, MERGED) and validating-metadata.mdx by #9034 (MERGED) — so all line numbers must be re-derived from current origin/main, ⛔ not from this card's transcript. Batch siblings #9203 and #8901 are both scripts/ and disjoint. #8531/#7276 belong to another account ⇒ ⛔ untouched.

Provenance — this card exists because a dev refused to guess

Filed by the #9092 dev, which declined to paste its own fixture's stats line. That refusal was correct and is the reason this card is well-formed: every line #9151 changed is a project-independent CLI fact, whereas the stats line is fixture identity, and substituting one fixture's identity for the page's would have been manufacturing. It also fenced off validating-metadata.mdx because that page was out of scope then. Both pages are in scope now, which is precisely what makes the fix possible.

Premise re-check on origin/main, 2026-08-17 (not recalled) — holds, and the agreement is the constraint

page	measured
build-with-claude-code.mdx:259	Data: 1 Objects 6 Fields
validating-metadata.mdx:542	Data: 1 Objects 6 Fields

⇒ The two pages currently agree at 6, while the Support Desk listing on build-with-claude-code.mdx declares 4 fields. That agreement is the thing to preserve: ⛔ correcting one page alone breaks it and makes the tree less consistent than it is now. This is why the card insists both pages come from one run.

The card also reports both pages omit the Runtime: 3 plugins line a real scaffolded run emits — verify that independently.

The shape of an acceptable fix

One project, one run, both pages. Either (a) the page's own listing is completed so a 6-field Support Desk is genuinely reconstructible and both transcripts are re-derived from it, or (b) the fixture is built to match the listing and all three numbers move together — the listing, and both transcripts.

⛔ Do not reach 6 by inventing two fields, and ⛔ do not paste a reconstruction's numbers over the page's. If the listing and the transcript cannot be reconciled without inventing product surface, stop and report — premise_still_valid: false with a stated obstruction is a legitimate delivery, and better than a page that agrees with itself by fiat.

⚠️ validating-metadata.mdx is the page that sends readers to the other one "for the bare-reference example verbatim". #9151 just made that word true again for the finding block; ⛔ do not break it while fixing the stats line.

Gates named for this surface at this moment

pnpm check:docs-audit-scope · pnpm check:docs-redirects · pnpm check:role-word (+ check:nul-bytes for any file edit). A lead, not a spec — re-derive from your actual changed paths.

Changeset: docs-only ⇒ almost certainly skip-changeset; judge by the diff, and apply it before your first push (applied after, the stale failure is never cleared by a later skipped, and the PR silently never enters the queue).

---

Generated by Claude Code