Rotate completed BEARING history

[flyingrobots]

Summary

• reduce docs/BEARING.md from a completed-slice ledger into a compact live signpost
• add a rotation retro preserving the completed v18 slice-history summary and evidence pointers
• keep the current v18 release state and live checklist visible

Verification

• npm run lint:md -- docs/BEARING.md docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md
• npm run lint:links -- docs/BEARING.md docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md
• git diff --check -- docs/BEARING.md docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md
• pre-push IRONCLAD M9 gate: link check, static gates, 521 unit files / 7126 tests

Summary by CodeRabbit

• Documentation
  • Refreshed the BEARING guidance to reflect the v18 cycle: reworded intro, condensed status section, and updated guidance on priorities and next-cycle posture.
  • Removed lengthy historical planning checklists in favor of a concise live checklist for v18 tagging/publishing and follow-up updates.
  • Added a rotation retrospective summarizing what was archived and where detailed evidence now lives.

[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: 79ce9a62-6c3a-4d6f-9819-cd8db7413126

📥 Commits

Reviewing files that changed from the base of the PR and between 2195ae2 and a3a18c2.

📒 Files selected for processing (1)

• docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md

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

• docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md

---

📝 Walkthrough

Walkthrough

BEARING.md is consolidated to focus on live status by removing detailed v18 completed-slice history and moving it to a new retro document. The main file is restructured with an updated intro, condensed release facts, and clarified next-cycle guidance, while the new retro doc captures the rotation context and v18 outcomes.

Changes

V18 BEARING Rotation

Layer / File(s)	Summary
BEARING.md restructuring docs/BEARING.md	Intro reworded to reference the rotation retro; "Where Are We" condensed to current release facts and v18 implementation posture checklist; "What Feels Wrong," "Where We Are Heading," and "Live Checklist" updated to clarify work modes and focus on v18 publish steps and next-cycle branch decisions. Net: +68 lines, −785 removed.
V18 rotation retro documentation docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md	New retro document records what v18 completed-slice content was rotated out of BEARING.md, where evidence now lives (design docs, v18 backlog, CHANGELOG, PR history), summary outcomes for slices 103–112 across convergence/migration/wet-run/release-candidate/post-merge phases, repository state after PR #108 (commit 59beefed, v18.0.0 versions set, preflight passed, publish pending), and next actions (publish v18, then choose next-cycle branch by mode).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• git-stunts/git-warp#105: Both PRs directly update docs/BEARING.md v18 planning content and checklist/running-task material in the same document sections.
• git-stunts/git-warp#100: Both PRs are docs-only updates that edit docs/BEARING.md sections to reflect v18 state boundaries and adjust "Where We Are Heading" slice and runway guidance.
• git-stunts/git-warp#108: Related PR that, together with this change, records repository state at the v18 rotation point and coordinates v18 publish/tag decisions.

Poem

🐰 Git-warp hops forward, slice by slice so true,
Old history tucked away—BEARING shines bright anew,
Rotation complete, the path is now clear,
Live status signposts guide the next frontier!
✨📚

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description provided covers the summary of changes but does not include the required ADR checks section from the repository's template, which is a required part of the formal description.	Add the 'ADR checks' section with the four required ADR compliance checkboxes as specified in the repository's description template.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Rotate completed BEARING history' clearly and concisely describes the primary change: reorganizing BEARING.md documentation by archiving completed history into a rotation retro while keeping current status visible.
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 chore/rotate-bearing-history

---

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.}

[flyingrobots]

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

Severity	File:Line	Type	Finding	Recommended mitigation prompt
Major	docs/BEARING.md:41	Release-state accuracy	Latest merged PR: #108 will become false as soon as this PR merges. BEARING is intended to be a live signpost on main; merging PR #109 would immediately make #109 the latest merged PR.	"Update docs/BEARING.md so release facts are not self-invalidating after this docs PR merges. Replace Latest merged PR: #108 with a stable statement such as Latest v18 release-prep merge: PR #108 or remove the latest-PR claim entirely."
Major	docs/BEARING.md:42 and docs/BEARING.md:48	Release-gate evidence ambiguity	The file says the current release commit on main is 59beefed and that release preflight passed from aligned main. After this PR merges, main will no longer point at 59beefed, and the release preflight evidence will not correspond to the new branch tip. This can mislead the tag/publish operator.	"Reword BEARING to distinguish the v18 release-prep merge commit from the current main tip. State that the last recorded release preflight passed on 59beefed, and that release preflight must be rerun from the exact commit that will be tagged before publishing."
Major	docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md:89	Historical/present-tense drift	The retro says main points at 59beefed in present tense. That is true only before this PR merges. Once merged, the retro records a false current-state claim.	"Change the retro's current-state paragraph to historical wording, e.g. At the rotation point after PR #108 merged, main pointed at 59beefed..., and avoid implying that remains true after the rotation PR lands."
Minor	docs/BEARING.md:6 and docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md:13	Archive precision	BEARING says completed history was rotated to the retro, but the retro only summarizes the removed material and points to other evidence. That is probably the right design, but the wording overstates archival fidelity.	"Rephrase the pointer to say completed v18 slice detail was summarized in the rotation retro, while full evidence remains in design docs, backlog lane summaries, changelog, and PR history."

Issue count: 4 total — 3 Major, 1 Minor.

[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]

@codex Self-review resolution update.

Finding	Severity	Resolution	Commit
Latest merged PR: #108 would self-invalidate after this PR merges	Major	Reworded as Latest v18 release-prep merge: PR #108 ... at 59beefed, so the statement remains stable after PR #109 lands.	2195ae21
Release preflight evidence was ambiguous relative to the eventual tag commit	Major	Split release-prep merge evidence from future tag evidence and added an explicit instruction to rerun release preflight from the exact commit being tagged if main moves after 59beefed.	2195ae21
Retro used present-tense main state that would become false after merge	Major	Converted the retro paragraph to historical wording: At the rotation point after PR #108 merged....	2195ae21
Archive wording overstated relocation fidelity	Minor	Changed rotated to / removed from language to summarized in / summarized out of, with full evidence still pointed to design docs, backlog summaries, changelog, and PR history.	2195ae21

Verification:

• npm run lint:md -- docs/BEARING.md docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md
• npm run lint:links -- docs/BEARING.md docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md
• git diff --check -- docs/BEARING.md docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md
• pre-push IRONCLAD M9: link check, static gates, and unit suite passed (521 files, 7126 tests)

[coderabbitai]

Actionable comments posted: 1

🤖 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
`@docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md`:
- Around line 5-9: Reword the sentence that begins "Completed v18
implementation, release-prep, and post-merge planning history through slice 112
now lives in the design docs, changelog, backlog lane summaries, PR history, and
this rotation note instead of staying inline in BEARING." so it no longer
implies the full history is contained here; instead state this file is a summary
and point readers to the actual artifacts (design docs, changelog, backlog lane
summaries, PR history) as the sources of detailed history—keep the same list of
artifacts and mention that evidence/pointers to the full history are provided
rather than claiming the history "lives" in this rotation note or BEARING.md.

🪄 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: 0b966107-eb81-4a02-9b6a-988233336ccb

📥 Commits

Reviewing files that changed from the base of the PR and between 59beefe and 2195ae2.

📒 Files selected for processing (2)

• docs/BEARING.md
• docs/method/retro/0146-bearing-v18-completed-rotation/bearing-v18-completed-rotation.md

[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 CodeRabbit archive-fidelity wording feedback in commit a3a18c2. The retro now says the completed v18 history is summarized in the rotation note, with full evidence distributed across design docs, changelog, backlog lane summaries, and PR history. Validated targeted markdown, links, diff check, and pre-push IRONCLAD M9 including 521 unit files / 7126 tests.

[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.