docs(releases): the v17 page's upgrade bullet asserts `os migrate meta` "also prints `runtime 17.0.0` on a 17.3.0 install" — a sentence the CLI repair invalidates, in a file a code PR may not touch

[os-litant]

Filed unassigned for triage, out of scope for the card that found it (#15585). Not addressed there and that card is not addressed here.

Measurement

content/docs/releases/v17.mdx:5363, closing an upgrade-guidance bullet:

- **Expect `os migrate meta --from 17` to report `Nothing to migrate`, and do not
  read that as completion.** *Measured:* it exited 0 with exactly that line while
  **nine** of the items on this page were live and unaddressed on that stack. Its
  scope is the protocol chain; everything else on this list is outside it. (It
  also prints `runtime 17.0.0` on a 17.3.0 install.)

The parenthetical is the defect #15585 reports. Its repair changes the line the sentence describes, so once that lands the CLI prints:

Chain:  protocol 17 → 17 (this runtime implements protocol 17)

and no build prints runtime 17.0.0 any more.

Why this is a separate card and not a rider

content/docs/releases/ is written centrally at release time and is off-limits to a code PR — AGENTS.md, Documentation Guardrails: a factual error there is a dedicated docs-only PR or an issue, never a rider on code changes. A code PR's only input to release notes is its changeset, and the #15585 changeset carries the corrected line.

The judgement this needs, which is why it is triage and not a mechanical edit

It is genuinely unclear whether the sentence is stale or historical, and the two want opposite edits:

• Historical — the bullet documents what a reader upgrading to v17 measured on 17.3.0. Read that way the sentence is still true of 17.3.0 and should stay, perhaps with the version it was measured on made explicit.
• Stale — the bullet is live upgrade guidance on the page a reader lands on today. Read that way it tells a reader on a later 17.x to expect output that build does not produce, which is the same class of "the page describes a build that is not yours" defect as docs(releases): the index's v17 entry still says "current series: 17.2.0" after 17.3.0 shipped — the #10232 / #11649 defect class recurring a third time #15332 (the index's v17 entry still saying "current series: 17.2.0"; different sentence, different file, already dispatched).

Neither reading is safe to pick from a code card, and the file's owner is the release process.

Scope fence

One parenthetical in one bullet. Not a correctness, data or security defect. No package code is implicated: the CLI half is fixed under #15585, and nothing else in the tree quotes the old line (grep over skills/, content/, docs/, packages/*/README.md; the one Chain: hit in skills/objectstack-upgrade/SKILL.md is a report template an author fills in, not a quote of the command's output).