Prepare v18.0.0 release metadata and final gates

[flyingrobots]

Summary

• Records v18 release-prep baseline, gate baseline, residual raw content/property risk decision, public operator notes, version metadata, and final release-prep replan.
• Aligns root package metadata, private workspace manifests, lockfile, JSR metadata, changelog, and release-policy tests to 18.0.0.
• Keeps the public tag and publish steps explicitly pending until after merge to main.

Evidence

• npm exec vitest run test/unit/scripts/release-policy-shape.test.ts
• npm run release:preflight
• pre-push IRONCLAD M9 gates: link check, lint, markdown lint, markdown code sample lint, typecheck, policy, consumer surface, declaration surface, and npm run test:local

Notes

• npm run release:preflight passes with the expected non-main branch warning.
• npm audit --omit=dev --audit-level=high reports no high or critical vulnerabilities; one moderate brace-expansion advisory remains non-blocking.
• TECHNICAL_TEARDOWN.md is an unrelated untracked local side-project file and is not part of this PR.

Summary by CodeRabbit

• Chores

  • Bumped project version to v18.0.0 across manifests and packages.
  • Started CHANGELOG entry for v18.0.0.

• Documentation

  • Added comprehensive v18 release materials: release docs, gate baselines, release-prep checklist, operator release notes, final replan, and a technical teardown.
  • Updated bearing, backlog, and release README content to reflect v18 scope and accepted residual risk.

• Tests

  • Updated release-version alignment test to v18.0.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d1c6e420-487e-4df9-b15c-c10645f1f746

📥 Commits

Reviewing files that changed from the base of the PR and between 82aa746 and 45f721c.

📒 Files selected for processing (1)

• TECHNICAL_TEARDOWN.md

✅ Files skipped from review due to trivial changes (1)

• TECHNICAL_TEARDOWN.md

---

📝 Walkthrough

Walkthrough

This PR finalizes v18.0.0 release preparation by aligning all package manifests to 18.0.0, adding release-prep design and gate evidence, formalizing acceptance of residual raw content/property compatibility risk, updating release status and blockers, and publishing v18 release notes plus a technical teardown.

Changes

v18.0.0 Release Preparation

Layer / File(s)	Summary
Version metadata alignment and test expectations package.json, jsr.json, packages/warp-{adapters,kernel,orset}/package.json, CHANGELOG.md, test/unit/scripts/release-policy-shape.test.ts	All package manifests are updated to 18.0.0; a CHANGELOG heading for v18.0.0 is added; release-policy test expectations updated to assert 18.0.0 alignment.
Release design baseline, gates, and decisions docs/design/0245-v18-release-prep-baseline/..., docs/design/0246-v18-release-gate-baseline/..., docs/design/0247-v18-residual-raw-storage-risk-decision/..., docs/design/0248-v18-public-operator-release-notes/..., docs/design/0249-v18-version-tag-readiness/..., docs/design/0250-v18-final-release-prep-replan/...	Six new design documents (0245–0250) establish the v18 release-prep baseline, record gate evidence, formalize that residual raw content/property compatibility is not a release blocker, specify operator release notes scope, define version/tag readiness, and document the final release replan with preflight evidence.
Release status, backlog, and blockers update docs/BEARING.md, docs/method/backlog/v18.0.0/RELEASE_v18-public-release-blockers.md, docs/method/backlog/v18.0.0/PROTO_content-attachment-plane-cutover.md, docs/method/backlog/v18.0.0/README.md	BEARING and backlog/blocker docs updated with branch-state metadata, completed slices and checklist items 97–102, revised public-release blockers, explicit accepted residual-risk framing with an audit guard, and next-step guidance for tagging/publishing.
Public v18.0.0 release notes and operator procedures docs/releases/v18.0.0/README.md	Adds comprehensive v18.0.0 release notes covering scope, five-phase operator workflow (dry-run, scratch write/report, equivalence review/runtime replay, reviewed-JSON finalization, archive evidence preservation), residual-risk audit command, non-goals, and pre-tag release gates.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• git-stunts/git-warp#93: Related updates to test/unit/scripts/release-policy-shape.test.ts adjusting expected package/jsr version assertions.
• git-stunts/git-warp#74: Also modified release-policy test paths and related release-doc checks; overlaps in test-area evolution.
• git-stunts/git-warp#105: Prior updates to docs/BEARING.md's v18 planning state and checklist content.

Poem

A rabbit hops the changelog track,
From seventeen leaves to eighteen's stack—
Docs and gates all set in line,
Bun-sized notes and tests align. 🐇📦

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the primary objective: preparing v18.0.0 release metadata and establishing final gates before merge.
Description check	✅ Passed	The description provides a clear summary of changes, comprehensive evidence (tests, preflight, pre-push gates, audit), and relevant notes about the release readiness.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch v18-release-prep-slices-97-102

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Release Preflight

• package version: 18.0.0
• prerelease: false
• npm dist-tag on release: latest
• npm pack dry-run: passed
• jsr publish dry-run: passed

If you tag this commit as v18.0.0, release workflow will publish.

[github-actions]

Release Preflight

• package version: 18.0.0
• prerelease: false
• npm dist-tag on release: latest
• npm pack dry-run: passed
• jsr publish dry-run: passed

If you tag this commit as v18.0.0, release workflow will publish.

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@TECHNICAL_TEARDOWN.md`:
- Line 288: The "Learn about Provenance" bullet currently references a
non-existent "Golden Path 9"; replace the "Golden Path 9" mention with an
existing section title or anchor (for example the documented "Golden Paths"
overview or the specific "Golden Path 3" entry) so the link/label points to a
real section—update the string "Golden Path 9" in that bullet to the correct
existing heading/anchor used elsewhere in the document.
- Around line 207-248: The Mermaid public-API diagram is incorrect: update the
WarpGraph shape to match the actual contract in src/domain/WarpGraph.ts by
replacing the incorrect fields (info, patches, query) with the actual surface
properties commitment: CommitmentSurface, folding: FoldingSurface, revelation:
RevelationSurface, governance: GovernanceSurface, and represent the flat
capability aliases (e.g., patches, query) as method-level aliases delegating to
the corresponding surface methods (or document them as aliases of
CommitmentSurface and RevelationSurface methods) instead of typing them as
grouped surface objects; ensure the class relationships point to
CommitmentSurface, FoldingSurface, RevelationSurface and GovernanceSurface
accordingly and that method signatures (createPatch, patch, hasNode,
getNodeProps, worldline, observer, syncWith, createCheckpoint, join, reduce)
match the surface interfaces.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1d3d4c1a-202a-4b91-8165-8e06cb542ee4

📥 Commits

Reviewing files that changed from the base of the PR and between 32371bb and 82aa746.

📒 Files selected for processing (1)

• TECHNICAL_TEARDOWN.md

[flyingrobots]

@codex Self-review findings for PR #107. Please confirm before merge.

Severity	File/Lines	Type	Finding	Recommended mitigation prompt
P1 Blocking	TECHNICAL_TEARDOWN.md:115, TECHNICAL_TEARDOWN.md:321	Release hygiene / Markdown whitespace	git diff --check origin/main...HEAD fails on trailing whitespace. This is a hard hygiene failure for a release-prep PR.	Remove trailing whitespace from TECHNICAL_TEARDOWN.md lines 115 and 321, then rerun git diff --check origin/main...HEAD and markdownlint on the file.
P2 Major	TECHNICAL_TEARDOWN.md:207-246; compare src/domain/WarpGraph.ts:53-113	Documentation correctness / API drift	The public API class diagram does not match the actual WarpGraph interface. The doc shows info, patches, query, and a FoldingSurface with join() / reduce(), while the source exposes graphName, writerId, architectural surfaces (commitment, folding, revelation, governance), flat aliases, and a folding.checkpoint capability.	Rewrite the TECHNICAL_TEARDOWN public API surface section from src/domain/WarpGraph.ts so the diagram reflects the actual WarpGraph, CommitmentSurface, FoldingSurface, RevelationSurface, and GovernanceSurface shapes.
P2 Major	TECHNICAL_TEARDOWN.md:303-318	Documentation portability / release hygiene	The teardown publishes live local repo refs, object IDs, and a local host-derived author string as tutorial evidence. These refs are not guaranteed to exist for readers and make the guide depend on one workstation's transient graph state.	Replace the live local ref dump in TECHNICAL_TEARDOWN.md with a sanitized fixture-style example that uses stable placeholder refs/object IDs, and remove the local host-derived author string.
P3 Minor	TECHNICAL_TEARDOWN.md:288	Broken internal reference	The guide tells readers to read "Golden Path 9", but the document has only three golden-path subsections and no numbered Golden Path 9.	Replace the Golden Path 9 reference with the actual section name or add the missing provenance golden path section before this reference.
P4 Nit	TECHNICAL_TEARDOWN.md:8-28; example actual heading at TECHNICAL_TEARDOWN.md:31	Markdown style / navigation accuracy	The manual table of contents has stale line numbers immediately on introduction. Example: it claims git-warp Overview starts at line 27, but the heading is line 31. Manual line-number TOCs decay quickly and are already wrong.	Remove line numbers from the TECHNICAL_TEARDOWN table of contents or regenerate them to match the committed file; prefer anchor links over static line numbers.

Evidence commands run locally:

git status --porcelain
# clean

git fetch origin

git diff --check origin/main...HEAD
# TECHNICAL_TEARDOWN.md:115: trailing whitespace.
# TECHNICAL_TEARDOWN.md:321: trailing whitespace.

[flyingrobots]

@codex Self-review findings from the teardown audit were resolved in commit 40b303b4.

Severity	File/Area	Resolution	Fix SHA
P1 Blocking	TECHNICAL_TEARDOWN.md whitespace	Removed trailing whitespace and verified git diff --check origin/main...HEAD is clean.	40b303b4
P2 Major	Public API surface diagram	Rewrote the diagram to match src/domain/WarpGraph.ts: architectural surfaces, flat aliases, and capability namespaces now reflect the real interface shape.	40b303b4
P2 Major	Local repo ref examples	Replaced workstation-local refs, object IDs, and author metadata with sanitized fixture-style examples.	40b303b4
P3 Minor	Broken Golden Path 9 reference	Replaced the nonexistent section reference with a provenance-oriented instruction tied to the Domain Dictionary and patch trailers.	40b303b4
P4 Nit	Manual line-number ToC	Replaced stale line-number table of contents with stable Markdown anchor links.	40b303b4

Verification after the fix:

git diff --check origin/main...HEAD
npx markdownlint TECHNICAL_TEARDOWN.md
npm run lint:md:code
git push

The push ran IRONCLAD M9 pre-push gates successfully, including link check, lint/type/policy/surface/markdown gates, and npm run test:local with 521 files and 7126 tests passing.

[flyingrobots]

@codex Self-review findings for PR #107 after the follow-up teardown cleanup. Please confirm before merge.

Severity	File/Lines	Type	Finding	Recommended mitigation prompt
P2 Major	TECHNICAL_TEARDOWN.md:62; compare README.md:44-45, docs/CONCEPTUAL_OVERVIEW.md:84	Documentation correctness / terminology drift	The teardown defines WARP as “Recursive Witnessed Admission over Git,” but canonical docs expand WARP as “Worldline Algebra for Recursive Provenance.” src/domain/WarpGraph.ts describes WARP as a recursive witnessed admission architecture, but that is not the package acronym. A zero-to-hero guide should not teach the wrong expansion for the central term.	Update TECHNICAL_TEARDOWN.md so the WARP glossary entry uses the canonical expansion “Worldline Algebra for Recursive Provenance,” and optionally add a second sentence explaining that the runtime also uses recursive witnessed admission semantics over Git.
P5 Nit	TECHNICAL_TEARDOWN.md:70, TECHNICAL_TEARDOWN.md:74, TECHNICAL_TEARDOWN.md:273	Markdown table style	Three table rows omit the space before the cell delimiter (`Version Vector	, Materialization

Evidence commands run locally:

git status --porcelain
# clean

git fetch origin

git diff --check origin/main...HEAD
# clean

npx markdownlint $(git diff --name-only origin/main...HEAD -- '*.md')
# clean

[github-actions]

Release Preflight

• package version: 18.0.0
• prerelease: false
• npm dist-tag on release: latest
• npm pack dry-run: passed
• jsr publish dry-run: passed

If you tag this commit as v18.0.0, release workflow will publish.

[flyingrobots]

Resolved the self-review findings in 45f721c3 (docs: Fix WARP teardown terminology).

Finding	Outcome	Commit
TECHNICAL_TEARDOWN.md used a non-canonical WARP expansion	Updated the glossary to use Worldline Algebra for Recursive Provenance and retained the witnessed-admission explanation as runtime semantics.	45f721c3
Three Markdown table rows had inconsistent pipe spacing	Normalized table cell spacing for Version Vector, Materialization, and Frozen Capability Bag.	45f721c3

Verification:

npx markdownlint TECHNICAL_TEARDOWN.md
# passed

git diff --check
# passed

pre-push IRONCLAD M9
# static gates passed
# unit tests: 521 files passed, 7126 tests passed

[github-actions]

Release Preflight

• package version: 18.0.0
• prerelease: false
• npm dist-tag on release: latest
• npm pack dry-run: passed
• jsr publish dry-run: passed

If you tag this commit as v18.0.0, release workflow will publish.