docs(upgrading): the Per-release specifics table has no v18.2.0 row — 18.2.0 is published and its upgrade checklist (releases/v18/18-2) is not linked from the upgrade guide

Filing gate: ① product docs defect, shipped text (content/docs/upgrading.mdx), named location.

Business reason: an operator moving a deployment to the published 18.2.0 opens the upgrade guide, which says the per-release specifics live in that release's checklist. The table stops at v18.1.0, so the reader never learns that 18.2.0 has an upgrade checklist. That checklist is content/docs/releases/v18/18-2.mdx, which landed after the release in docs(releases): the 18.2.0 release notes page and its upgrade checklist #26494. docs: the 18.0.0 release text still tells a v17 operator to stay on 17.x — amend the CLI CHANGELOG entry, add the v18 row and ceremony to the upgrade guide and the v18 release page #24904 and docs(releases): write the 18.0.0 upgrade checklist — the v18 page still says curated notes "are not written yet", and Upgrading's per-release table has no v18.0.0 row (nor 17.5–17.7) #24905 closed the same gap for 18.0.0.
Who acts: the docs lane owning content/docs/upgrading.mdx. The fix is one table row, "| v18.2.0 | Upgrade checklist — 18.2.0 |", above the v18.1.0 row, with the anchor checked against 18-2.mdx.
Dedupe (open and closed): "upgrading.mdx 18.2.0 row per-release specifics release notes 18-2 page" gave 10 hits, and "Upgrading per-release specifics table missing v18.2.0 row" gave 8. docs(releases): write content/docs/releases/v18/18-2.mdx for the 18.2.0 cut — 221 changesets since 18.1.0, 53 with a BREAKING banner, grouped under the five release-notes headings #26429 (closed) wrote 18-2.mdx but not the upgrading row. docs: the 18.0.0 release text still tells a v17 operator to stay on 17.x — amend the CLI CHANGELOG entry, add the v18 row and ceremony to the upgrade guide and the v18 release page #24904 and docs(releases): write the 18.0.0 upgrade checklist — the v18 page still says curated notes "are not written yet", and Upgrading's per-release table has no v18.0.0 row (nor 17.5–17.7) #24905 (closed) are the 18.0.0 instances.

QA-source: #26629 · smoke:npm-18.2.0 · C3
type: Bug

Reproduction

git show 27f38ad:content/docs/upgrading.mdx and read "Per-release specifics". Do the same on main (measured at 7c34e5d).
Expected: a v18.2.0 row linking the 18.2.0 upgrade checklist. Actual: the newest row is v18.1.0 in both.
At the release commit, content/docs/releases/v18/ holds 18-0.mdx, 18-1.mdx and index.mdx only. 18-2.mdx exists on main from docs(releases): the 18.2.0 release notes page and its upgrade checklist #26494.

Full evidence chain: the run record #26629, cell C3.

Triage: first grade — `documentation` · `priority:p2` · `domain:devx` · `area:devpath` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T11:59Z

⛔ Not a claim, ⛔ not a dispatch.

p2: content/docs/upgrading.mdx's per-release table stops at v18.1.0. Add the v18.2.0 row linking releases/v18/18-2 (docs(releases): the 18.2.0 release notes page and its upgrade checklist #26494). Small, and it should land soon, while operators are upgrading.

Generated by Claude Code

Claim: PM loop round 6 · 2026-10-27T17:30Z
Session: session_01JQwxbWQbmPGoJDwc2QWoUJ (card thread cmsg_01U5RdnAAmkSQmZbqh6FtqZ847VupnCQ7pTGRjWNeDr1f4, dispatched by seat session session_01JQwxbaFpnMwgpCgneKe2qS)
Account: os-warren (the seat's linked user; the card's assignee)
Branch: claude/project-thread-6xsm3c (the harness-pinned branch of the card thread; it names no issue, so this claim is the identity record)
Worktree: objectstack-issue-26631
Domain: domain:devx
Seat: domain:devx#1
File surface: content/docs/upgrading.mdx (one row in "Per-release specifics"). ⛔ No edit under content/docs/releases/** or content/docs/references/**; anything beyond upgrading.mdx is reported, not widened into
Container & model: S, mode:thread (Warren's 「opus 很多，并发5」, 2026-10-27), model: default (no path-derived mandate, default opus), effort: medium
Clause-②: no
Metadata-protocol: none
Responsibility: #26494 landed releases/v18/18-2.mdx after the release without the upgrading row (named in the card body); QA run #26629 cell C3 found it; triage 6441345560
Thread-read: 6441345560
Premise: holds on origin/main — upgrading.mdx L466 is the newest row (v18.1.0), and 18-2.mdx L910 is "## Upgrade checklist" (read by the seat and re-read by the thread)
Serial constraints cleared: none. No open PR or sibling card thread edits content/docs/upgrading.mdx; no other devx seat is seated

Generated by Claude Code

os-dev-report

{
  "issue": 26631,
  "status": "done",
  "branch": "claude/project-thread-6xsm3c",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/26830",
  "session": "session_01JQwxbWQbmPGoJDwc2QWoUJ",
  "premise_still_valid": true,
  "summary": "Added one row '| v18.2.0 | [Upgrade checklist — 18.2.0](/docs/releases/v18/18-2#upgrade-checklist) |' above the v18.1.0 row of the Per-release specifics table in content/docs/upgrading.mdx (head eab39f53e). Premise held on origin/main 0ea90c7a: 18-2.mdx line 910 is '## Upgrade checklist'. No other list in upgrading.mdx stops at 18.1 and no test or script pins the table rows (searched scripts/, packages/, .github/), so nothing widened past upgrading.mdx. Edited in the shared checkout sitting on the harness-pinned branch rather than a separate worktree (single-thread container, base equal to origin/main).",
  "tests": "n/a — one docs table row, no tested behaviour changed; the anchor is pinned by check:doc-anchors (exit 0).",
  "gates": "dispatch-gates --commands derived 44 families at 0ea90c7a; all 44 exit 0, captured per command before any pipe; --ran reconciliation: 44 derived, 44 run, 0 NOT-MEASURED, 0 UNRUN (exit 0). Five first exited 3 (prerequisite not met) or 1 (spec gen:schema missing) on an unbuilt tree: check:doc-formula-expressions, check:doc-security-posture, spec check:docs, spec check:skill-examples, check:docs-transcript-drift; after turbo builds of @objectstack/lint..., @objectstack/formula, @objectstack/spec, @objectstack/client... and @objectstack/client-react... each re-ran to exit 0. CI check-runs on #26830 not yet cited (just opened).",
  "dogfood_battery": "n/a — no '!' in the PR title and no (narrowing) arm",
  "mcp_calls": "0",
  "api_writes": "2 relay writes — fleet-write pr_create (run 40553765408, 3148 bytes sent = stored, assignee os-warren, label skip-changeset, governed review: ungoverned path, no reviewer requested) and this os-dev-report comment; plus git push of the branch",
  "open_questions": [],
  "out_of_scope_findings": [],
  "body_amendments": [
    "PR body footer uses the platform's 'Generated with Claude Code' + session-URL lines, not os-dev's _Generated by [Claude Code](https://claude.ai/code/session_<id>)_ form; seat may rewrite it if a gate reads that form.",
    "Commit trailers: the pre-push check:commit-card-trailers refused 'Fixes #26631' and a model-named co-author line in the first commit; reworded before the push (model-free pair, no card relation), so the relation lives only in the PR body."
  ]
}

Generated by Claude Code

ACCEPT → PR #26830 comment 6449883858

Generated by Claude Code

Landed: PR #26830, merged as bff1546e63 · 2026-10-27T18:46Z

content/docs/upgrading.mdx's per-release table now has the v18.2.0 row, linking /docs/releases/v18/18-2#upgrade-checklist. ACCEPT → PR #26830 comment 6449883858. pm:dispatched removed; the card's slot is free.

Generated by Claude Code

Navigation Menu

Repository navigation

docs(upgrading): the Per-release specifics table has no v18.2.0 row — 18.2.0 is published and its upgrade checklist (releases/v18/18-2) is not linked from the upgrade guide #26631

Reproduction

Triage: first grade — `documentation` · `priority:p2` · `domain:devx` · `area:devpath` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T11:59Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

docs(upgrading): the Per-release specifics table has no v18.2.0 row — 18.2.0 is published and its upgrade checklist (releases/v18/18-2) is not linked from the upgrade guide #26631

Description

Reproduction

Activity

objectstack-fleet commented on Oct 27, 2026

Triage: first grade — documentation · priority:p2 · domain:devx · area:devpath · pm:queue · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-27T11:59Z

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: first grade — `documentation` · `priority:p2` · `domain:devx` · `area:devpath` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T11:59Z