Refresh BEARING after v18 property projection

[flyingrobots]

Summary

• update BEARING to reflect the post-PR-99 state on main
• record that v18 slices 26 through 30 are complete
• record the cleanup checkpoint after closing obsolete PR Advance v18 evidence and receipt projection #92 and deleting stale remote non-main branches
• point the next implementation branch at slice 31

Verification

• npx markdownlint-cli2 docs/BEARING.md
• git diff --check
• pre-push IRONCLAD M9 gates passed: link check, static gates, Markdown gates, surface validator, and npm run test:local with 484 files / 6945 tests passed

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 (N/A: docs-only BEARING update)
• If this PR touches wire compatibility, I confirmed canonical-only ops are still rejected on the wire pre-cutover (N/A: docs-only BEARING update)
• If this PR touches schema constants, I confirmed patch and checkpoint namespaces remain distinct (N/A: docs-only BEARING update)

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates docs/BEARING.md to reflect the completion of PR #99 (v18 slices 26–30). It establishes the new main branch boundary, documents the current graph-model capabilities (property projections and compatibility records), summarizes the shipped work, and adjusts the forward roadmap starting at slice 31.

Changes

v18 Bearing Documentation Update

Layer / File(s)	Summary
Current v18 state and graph-model posture docs/BEARING.md	Boundary context updated to origin/main after PR #99 merge. Current posture extended with bullets describing runtime-backed legacy property projection nouns, node/edge property projections, and projection-backed compatibility records powering public query property reads.
PR #99 completion details and roadmap adjustment docs/BEARING.md	"What Just Shipped" section documents PR #99 work on property-projection runway, node/edge legacy property nouns, WarpState projections, compatibility-record routing, and follow-up behaviors. "Where We Are Heading" section rephrased and implementation batch list updated.

---

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

🐰 Progress hops from slice to slice,
v18 projections now precise!
Legacy nouns aligned with care,
Compatibility records everywhere. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the main change: refreshing the BEARING documentation after v18 property projection work.
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.
Description check	✅ Passed	PR description includes a Summary section, Verification subsection, and completed ADR checks matching the template requirements.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/post-pr99-bearing-checkin

---

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: 17.0.1
• prerelease: false
• npm dist-tag on release: latest
• npm pack dry-run: passed
• jsr publish dry-run: passed

If you tag this commit as v17.0.1, release workflow will publish.

[github-actions]

Release Preflight

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

If you tag this commit as v17.0.1, release workflow will publish.