release: prepare v18.1.2

[flyingrobots]

Summary

• Bump npm, JSR, lockfile, and private workspace versions to 18.1.2.
• Promote the source-backed reference and corrected manual registry publication flow into the release signposts.
• Prepare v18.1.2 for the runbook flow: release PR merge, autotag on main, then maintainer-dispatched publish workflow.

Issue

Refs #670

Test plan

• git diff --check
• npm run lint:md -- README.md ARCHITECTURE.md CHANGELOG.md docs/topics/README.md
• npm run lint:source-backed-reference
• npm run lint:docs-topology
• npm run release:prep
• pre-push IRONCLAD M9 gates, including link check, static gates, and stable unit-test shards

ADR checks

• This PR does not implement ADR 2 without satisfying ADR 3
• If this PR touches persisted op formats, I linked the ADR 3 readiness issue
• If this PR touches wire compatibility, I confirmed canonical-only ops are still rejected on the wire pre-cutover
• If this PR touches schema constants, I confirmed patch and checkpoint namespaces remain distinct

This release prep changes metadata, release notes, and documentation signposts only; it does not change persisted op formats, wire compatibility, or schema constants.

Summary by CodeRabbit

• New Features

  • Released version 18.1.2.
  • Added updated release notes for the latest build, including new coverage for source-backed references and release publishing checks.

• Documentation

  • Updated the README and topic docs to reflect the new release version and current release scope.
  • Refreshed the architecture and changelog notes to match the latest release posture.

• Chores

  • Bumped package and workspace version numbers to 18.1.2.

[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: e7b4f734-6998-4e41-8c84-4fa3115f41f5

📥 Commits

Reviewing files that changed from the base of the PR and between 19c2066 and f3b5818.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (9)

• ARCHITECTURE.md
• CHANGELOG.md
• README.md
• docs/topics/README.md
• jsr.json
• package.json
• packages/warp-adapters/package.json
• packages/warp-kernel/package.json
• packages/warp-orset/package.json

---

📝 Walkthrough

Walkthrough

This PR updates the release posture, published release text, and package version metadata to v18.1.2.

Changes

Release alignment for v18.1.2

Layer / File(s)	Summary
Release notes and posture CHANGELOG.md, ARCHITECTURE.md	CHANGELOG.md adds the 18.1.2 release entry with release notes and Added/Changed subsections, and ARCHITECTURE.md updates the release posture text to v18.1.2 with the source-backed reference gate note.
Published release text README.md, docs/topics/README.md	README.md and docs/topics/README.md replace the v18.1.1 release descriptions with v18.1.2 text covering the release scope and topic links.
Version manifests package.json, jsr.json, packages/warp-adapters/package.json, packages/warp-kernel/package.json, packages/warp-orset/package.json	The root package and workspace package manifests bump their version fields from 18.1.1 to 18.1.2.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• git-stunts/git-warp#107: Updates the same release-line metadata pattern with version bumps and changelog alignment for the v18.x series.

Poem

A rabbit hopped through release dust bright,
to v18.1.2 by moonlit light.
Changelogs shimmered, docs stood neat,
package tags all landed sweet.
🐇✨ A tidy patch, a happy bite.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the main change: preparing release v18.1.2.
Description check	✅ Passed	The description matches the repository template and includes summary, issue reference, test plan, and ADR checks.
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 release/v18.1.2

---

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

[github-actions]

Release Preflight

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

If this PR is from a release/* branch and merges to main, Release Autotag will run final preflight and create v18.1.2. A maintainer who is a JSR @git-stunts scope member must then dispatch the Release workflow manually.