docs(releases): the v18 landing page — the page check:release-notes needs before 18.0.0-next.0, behind the URL the CLI's @next pointer names

[objectstack-fleet]

Fixes #22919

Clause-②: no

What this is

The short v18 landing page that ruling 6049734955 (Q2 → A, on #22085) asks for, written on the maintainer's word on #22919 (release-owned channel 1). It gives the URL packages/cli/src/utils/protocol-version-gap.ts sends @next installers to (https://objectstack.ai/docs/releases/v18) a page behind it, and it is the page check:release-notes demands once the version pass writes an 18.x heading into packages/spec/CHANGELOG.md. scripts/check-release-notes.mjs is not edited; no release action is taken.

Files, v17's folder shape:

• content/docs/releases/v18/index.mdx (new): a release-status blockquote, the line's purpose, and the rule for its breaking stages.
• content/docs/releases/v18/meta.json (new): "pages": ["index"].
• content/docs/releases/meta.json: "v18" at the head of pages.
• content/docs/releases/index.mdx: one line above the v17 line.
• scripts/docs-audit/handwritten-docs.json: +1 generated entry, outside the card's declared surface (see Deviations).

What the page says, and the source of each claim

Claim on the page	Source on main at 018b077fb
No GA release yet; the line publishes as 18.0.0-next.N on npm's next tag; latest stays on 17.x; a ^17 range never moves; install by @next or an exact 18.0.0-next.N	.changeset/pre.json ("mode": "pre", "tag": "next", landed a87d8be29, PR #22084); .changeset/22080-v18-line-opens.md
The line exists for ADR-0131 (its title), staged in one major per its D14	docs/adr/0131-…md D14; the line-opens changeset ("ADR-0131 … lands on this line in stages")
Every major goes to next at least one RC cycle before latest	ADR-0087 D6
Each breaking stage says so in its own changeset, with its migration; those changesets ship as each package's CHANGELOG	the line-opens changeset ("Each stage that breaks something says so in its own changeset, with its own migration"); AGENTS.md Post-Task Checklist step 3
PROTOCOL_VERSION is 18.0.0; the handshake admits '^18' and refuses '^17'	packages/spec/src/kernel/protocol-version.ts, landed 4e9fe9ff6 (PR #22215); .changeset/22130-protocol-18.md
GA exits pre mode and publishes to latest	the line-opens changeset ("What ends it")

The page names no change beyond those landed facts, states no date, and names no 18.x version other than 18.0.0-next.N. Per H3, the 21 pending changesets carrying an @objectstack/…: major line (33 such lines in all) were read as a source for the staging rule and are not transcribed. One wording choice: the banner reads "v18 has no GA release yet" rather than "no v18 release yet". It stays true after 18.0.0-next.0 publishes, which is exactly what this page unblocks, so the page is not stale on its first prerelease.

H1: the gate this clears fires only on the post-version tree (measured)

check-release-notes.mjs reads majors from packages/spec/CHANGELOG.md headings, unanchored, so on this PR's head it is green with or without the page. The red it clears is the version PR's post-version tree. The simulation ran on scratch copies (git archive of packages/spec/CHANGELOG.md, packages/spec/package.json, content/docs/releases, content/docs/meta.json and content/docs/index.mdx), with the CHANGELOG given a ## 18.0.0-next.0 heading and package.json set to 18.0.0-next.0, which is the shape the version pass writes. The worktree was not touched.

tree	node scripts/check-release-notes.mjs
base 018b077fb, as committed	exit 0
base 018b077fb, simulated post-version	exit 1 (output below)
head 0efecc249, simulated post-version	exit 0 (output below)
head, simulated post-version, "v18" dropped from meta.json (control)	exit 1, "v18.mdx exists but is not listed in content/docs/releases/meta.json"

Without the page:

check-release-notes: 1 problem(s)

  • content/docs/releases/v18.mdx (or content/docs/releases/v18/index.mdx) is missing — @objectstack/spec shipped a 18.x release but there is no curated release page. Write it (lead with breaking changes + migration), then add "v18" to content/docs/releases/meta.json.

That is the message the triage reading 6087315917 quotes from the scheduled run's log. With the page:

check-release-notes: OK — every released major has a curated, navigable release page.

The other release-docs gates the post-version step runs, on the same simulated head tree:

• check-release-page-status: exit 0.
• check-release-section-coverage --strict: exit 0.
• The version-pass rewriter sync-release-index-currency (syncIndex() on the scratch root): no rewrites, no findings, index.mdx byte-identical.

H2: what check:release-page-status asks of this page (measured)

• During the next line: nothing. gaMajors() matches only end-anchored headings, so ## 18.0.0-next.0 is not a GA heading and v18 is outside the set it judges. The package.json cross-check skips a prerelease version. It cannot express "no release yet", and it does not need to.
• At GA it reads exactly two places: the first blockquote after the frontmatter, and the trailing parenthetical of the index.mdx line. The page puts its status in both on purpose. Simulated GA (## 18.0.0, version 18.0.0) with this page unchanged gives exit 1 with three problems: the blockquote never states that an 18.x version is released, and the index status carries the prerelease-word and prerelease-version signals. So the gate forces the status rewrite at the GA cut. This page cannot go stale silently there, which is the v16/v17 status class the gate was built for.

Gates

Derived on this diff with node scripts/pm/dispatch-gates.mjs --commands (no paths): 57 commands for the five paths. The 47 the dispatch named are among them; adding handwritten-docs.json brought 10 more. All 57 exit 0 on head 0efecc249. --ran with recorded exit codes reads: "57 derived, 57 run, 0 NOT-MEASURED, 0 UNRUN". Two prerequisites had to be met first, by building @objectstack/spec, @objectstack/formula, @objectstack/lint, @objectstack/client and @objectstack/client-react. On a fresh tree, check:docs, the two @objectstack/lint doc gates, check:docs-transcript-drift and check:skill-examples answer PREREQUISITE NOT MET (exit 3), not a verdict. MDX: the page compiles with @mdx-js/mdx 3.1.1. NOT MEASURED: Build Docs, which is CI's, and the live URL, because this container's egress denies objectstack.ai.

Deviations

• scripts/docs-audit/handwritten-docs.json (+1 line), outside the card's content/docs/releases/**. check:docs-audit-scope (in lint.yml, Lint & Repo Gates) reds on any hand-written page under content/docs that the generated list does not carry. On this branch's first commit it read: "1 hand-written doc(s) exist but are not listed … + content/docs/releases/v18/index.mdx. Fix: node scripts/docs-audit/check-audit-scope.mjs --write". The entry was regenerated with that command. The 17.7.0 release page carried the same one-line companion edit (21c804c03, PR docs(releases): the curated 17.7.0 release page and upgrade checklist #21994). It is its own commit (62e32ad55) so the seat can judge it apart from the page. Without it this PR cannot pass the required lint job.
• The card asks this PR to follow SKILL.md's path fork "for a governed path". content/docs/releases/** is in no row of GOVERNED_SURFACES (scripts/pm/check-governed-merges.mjs), so the fork lands on the ordinary branch, and this body carries no maintainer quick-read section. The PR stays draft for the seat.

Acceptance notes

• The page links /docs/upgrading, not the generated /docs/protocol-upgrade/18. That page is built at docs-build time into a gitignored directory, so the offline lychee lane (check-links.yml, --root-dir content) cannot resolve it in a fresh checkout.
• The "Versioning policy" section of content/docs/releases/index.mdx (unchanged here) still says a breaking change ships as a minor release and that check-changeset-no-major.mjs fails any pull request declaring a major. In pre mode that guard's RC exemption stands aside, and 21 changesets with a major line are pending on main. Release-side text; noted for whoever compiles the v18 notes, not edited here (the card asks for one index line).

Labels: skip-changeset. The diff moves nothing any package's files[] ships.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 85b4ac634e3f3997bee7cf038090d24d029bc82c → packageMentionDocs.