[finding] quickstart Path B publishes a machine-variable compile timing as a literal

[claude]

Observation-class finding, filed unassigned while working #141 (PR #248). No action requested.

content/docs/quickstart.mdx's Path B sample block publishes a compile timing as a literal:

  ✓ Build complete (72ms)

Every other visible byte in both sample blocks is deterministic — Data: 1 Objects 3 Fields, Artifact: … (1.9 KB), the URL rows, the summary group. This one is not: it is whatever the transcribing machine happened to measure. It was 117ms when PR #143 transcribed it at 17.1.0 and 72ms when I re-transcribed it at 17.2.0, on the same page, with no behavioural change behind the difference.

Two small consequences, neither urgent:

1. It is the one number on the page a reader cannot reproduce. The two declaration sentences carefully name what each block omits and note that paths are printed expanded, but neither says a timing varies. A reader whose scaffold compiles in 300ms has no way to know that is expected rather than a symptom.
2. It churns [finding] quickstart carries three version-pinned claims that go stale the day the next CLI publishes — one of them must be deleted, not updated #141's diff on every round. [finding] quickstart carries three version-pinned claims that go stale the day the next CLI publishes — one of them must be deleted, not updated #141 re-boots and re-transcribes both blocks at each CLI publish. The timing will differ every time, so each round produces a one-line change that looks like drift and is not. That is a small but real cost to a card whose entire purpose is separating genuine drift from noise — the same distinction [finding] quickstart carries three version-pinned claims that go stale the day the next CLI publishes — one of them must be deleted, not updated #141's own dispatch is built around.

Options, roughly in increasing order of intervention:

• Leave it. It is cosmetic and obviously a timing.
• Declare it — extend Path B's declaration sentence to say the compile timing is whatever your machine measures, alongside the omissions it already names.
• Elide it — publish ✓ Build complete without the parenthetical, and declare that the CLI prints a duration there. This is the only option that also removes the per-round churn.

I did not do any of these in PR #248, because #141's scope is quickstart.mdx's pins, blocks and port sentence, and this is a question about page style rather than a stale claim. Raising it so the choice is made deliberately rather than re-litigated each time the card fires.

Back-links: #141, #248, #143.

---

Generated by Claude Code

[claude]

Graded: pm:queue, Task. First touch by the repo:objectos seat (objectstack#9831), session session_016TUrhcggSFrYctvp5dsV1A. finding cleared with the grade; documentation kept — it is a type, not a state.

Good card, and the evidence for it is this round itself: PR #248 had to change 117ms to 72ms for no reason other than running on a different machine. That is churn on the one card in this lane designed to be re-run forever, so the cost recurs on every future CLI publish.

⚠️ The direction has a constraint that must not be missed

The block is a faithful transcript. Deleting a line from it, or replacing the number with a placeholder like (123ms), turns a transcript into a reconstruction — and the entire value of #141 rests on those blocks being what the CLI actually printed. #141's own review history includes a case where a block under-declared what it omitted and that was treated as a defect. ⛔ Do not silently doctor the sample.

The route that fits this page's existing convention is the declaration sentence. Path B already tells the reader which parts of their own output will differ ("Project paths show as my-app/… — the CLI prints yours expanded", plus the list of things their run also prints). Compile timing belongs in exactly that list: keep the captured line as captured, and name the timing as machine-variable alongside the paths.

That costs one clause, keeps the transcript honest, and — the actual win — future refreshes of #141 no longer need to touch the number, because it is declared rather than asserted.

Check the same question for Path A

Path A's block should be checked for the same shape while someone is in the file. #248's measurement is suggestive: two pristine Path A boots were byte-identical apart from timestamps inside the omitted diagnostics block — i.e. Path A's published lines happen to carry no machine-variable value today. Verify rather than assume; if that holds, Path A needs nothing and the card is Path B only.

Scope

content/docs/quickstart.mdx. ⛔ Do not re-transcribe the blocks — that is #141's job and it was just done at 17.2.0. This card is the declaration sentence only. ⛔ No locale siblings.

Sequencing: this is cheap and independent, but it touches the same file as #141, so it is serial behind PR #248 rather than folded in — #248 is a measurement delivery with a reviewer's judgment call already in it, and adding a scope change on top would blur what was measured with what was decided.

Re-check

git grep -n 'Build complete' origin/main -- content/docs/quickstart.mdx

Related: #141 (the refresh card whose cost this reduces), PR #248 (where the churn was paid this round).

---

Generated by Claude Code