Plan post-v18 release handoff and next goalpost by flyingrobots · Pull Request #108 · git-stunts/git-warp

flyingrobots · 2026-05-25T20:59:19Z

Summary

This PR records the post-merge handoff after the v18 release-prep branch landed on main, then sets the next goalpost without widening the v18.0.0 release promise.

It adds design records for slices 103 through 112 covering:

post-merge v18.0.0 release handoff;
tag and publish gates from aligned main;
release evidence archive expectations;
post-v18 storage retirement decision surface;
v19 native Continuum witnesshood runway;
v20 end-to-end graph streaming scope;
post-v18 public documentation honesty audit;
next raw content/property residual-boundary retirement decision;
backlog lane cleanup after v18;
next-goalpost replan after the v18 release-prep merge.

It also updates docs/BEARING.md and backlog lane summaries to reflect that PR #107 is merged, 18.0.0 metadata is on main, and the remaining public v18 operation is tag/publish from aligned main.

Verification

npx markdownlint $(git diff --name-only origin/main...HEAD -- '*.md')
git diff --check origin/main...HEAD
Pre-push IRONCLAD M9 static gates
Pre-push unit suite: 521 test files, 7,126 tests

Notes

This branch does not tag or publish v18.0.0. It keeps that as a release operation from aligned main.

Summary by CodeRabbit

Documentation
- Updated v18 release-prep and post-merge handoff docs; added tag/publish gate, release-evidence archive, post-release audit, and retirement/replan design docs
- Revised BEARING, ROADMAP, and backlog READMEs; expanded release checklists and blocker/watch items; clarified v19/v20 planning and next-goalpost guidance
Tests
- Adjusted unit test asserting updated roadmap/release-status wording

coderabbitai · 2026-05-25T20:59:32Z

Warning

Review limit reached

@flyingrobots, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 16 minutes and 32 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a216da9a-2a27-467e-b288-78158b649c2e

📥 Commits

Reviewing files that changed from the base of the PR and between db2c433 and 44ef0ab.

📒 Files selected for processing (1)

docs/design/0257-post-v18-public-doc-honesty-audit/post-v18-public-doc-honesty-audit.md

📝 Walkthrough

Walkthrough

After PR #107 merged to main, this PR advances v18 release-boundary docs, adds nine design documents for post-merge tag/publish/evidence/audit and forward v19/v20 planning, updates backlog/ROADMAP wording, and adjusts a unit test to match the new public-release narrative.

Changes

V18 Post-Merge Release Handoff and Forward Planning

Layer / File(s)	Summary
BEARING document and backlog README updates `docs/BEARING.md`, `docs/method/backlog/v18.0.0/README.md`, `docs/method/backlog/v18.0.0/RELEASE_v18-public-release-blockers.md`, `docs/method/backlog/v19.0.0/README.md`, `docs/method/backlog/v20.0.0/README.md`, `docs/ROADMAP.md`, `docs/method/backlog/README.md`	BEARING moved to post-PR `#107` state with post-merge checklist items 103–112; next actions split (cut/publish v18.0.0 from aligned main, retire one residual boundary, start v19 runway). Release blockers narrowed to post-merge tag/publish evidence from aligned main; backlog READMEs and ROADMAP wording updated to reflect public v17.0.0 vs source-only 17.0.1 repair.
Post-merge release operation design specs `docs/design/0251-v18-post-merge-release-handoff/...`, `docs/design/0252-v18-tag-publish-gate/...`, `docs/design/0253-v18-release-evidence-archive/...`	Three new design docs specifying post-merge handoff states, tag-and-publish gate requirements (preflight on main, origin/main match, multi-system version agreement), and release evidence archive contents/test plan.
Post-v18 audits and next-boundary decisions `docs/design/0254-post-v18-storage-retirement-decision/...`, `docs/design/0257-post-v18-public-doc-honesty-audit/...`, `docs/design/0258-v18-residual-boundary-next-retirement/...`, `docs/design/0259-backlog-lane-cleanup-after-v18/...`, `docs/design/0260-next-goalpost-replan-after-v18-merge/...`	Five new design docs for post-release audits and decisions: storage-retirement decision framework with closeout audit guard, public-doc honesty audit, residual-boundary retirement criteria and test plan, backlog lane cleanup rules, and next-goalpost replan tied to BEARING slices 103–112.
V19 and V20 scope definition `docs/design/0255-v19-native-continuum-witnesshood-runway/...`, `docs/design/0256-v20-streaming-reads-writes-scope/...`	Two design docs establishing v19 native Continuum witnesshood runway and v20 streaming reads/writes scope, including v19 prerequisites (bounded support, causal-index, support-fragment contracts) required before v20 can claim end-to-end streaming.
Test expectation updates `test/unit/scripts/release-policy-shape.test.ts`	Unit test updated to assert the roadmap/BEARING header now shows the public package/tag `v17.0.0`, next intended `v18.0.0`, and a `v17.0.1` repair note present only in docs (no public tag/npm evidence).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

git-stunts/git-warp#93: Related changes to release metadata and roadmap/tests that this PR builds upon.
git-stunts/git-warp#100: Prior BEARING updates that move the v18 bearing checkpoint; this PR advances the post-merge state.
git-stunts/git-warp#107: Directly related PR referenced in the updated BEARING and backlog materials; this PR records the post-merge handoff after #107 merged.

Poem

🐰 I hopped through docs after merge was done,

nine new plans shining like morning sun.
Tags and archives, audits to chart,
v18 set sail — v19 readies to start.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely captures the main objective: planning the post-v18 release handoff and setting the next goalpost after v18 prep merged.
Description check	✅ Passed	The description provides a clear summary of changes, references specific design records (slices 103–112), documents verification steps, and includes proper structure with summary and notes sections.
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-103-112

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

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

github-actions · 2026-05-25T21:03:39Z

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 · 2026-05-25T21:05:24Z

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

Severity	File/Lines	Type	Finding	Recommended mitigation prompt
P2 Major	`docs/BEARING.md:46-47`; related context at `docs/BEARING.md:30`	Release-state correctness	The branch updates post-merge release handoff state but repeats `17.0.1` as the latest released package line. Live evidence does not support a public `17.0.1` package/tag/release: `npm view @git-stunts/git-warp version --json` returns `"17.0.0"`; `npm view @git-stunts/git-warp versions --json` has no `17.0.1`; `git ls-remote --tags origin 'refs/tags/v17.0.1*'` returns no refs; `gh release view v17.0.1` returns `release not found`. For a PR whose purpose is release handoff, this baseline must not be wrong or ambiguous.	`Update docs/BEARING.md to distinguish the latest public package/tag line from any internal v17.0.1 repair wording. If no public v17.0.1 artifact exists, set the latest released package line to 17.0.0 and revise the “v17.0.1 release repair” sentence so it does not imply a published package/tag.`

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

npm view @git-stunts/git-warp version --json
# "17.0.0"

npm view @git-stunts/git-warp versions --json
# latest listed version is "17.0.0"; no "17.0.1"

git ls-remote --tags origin 'refs/tags/v17.0.1*'
# no output

gh release view v17.0.1 --json tagName,isDraft,isPrerelease,publishedAt,url
# release not found

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/design/0257-post-v18-public-doc-honesty-audit/post-v18-public-doc-honesty-audit.md`:
- Line 43: The test plan uses the raw command `npx markdownlint`; update it to
use the repository's canonical markdown lint script `npm run lint:md` instead.
Locate the occurrence of `npx markdownlint` in the post-v18 public doc honesty
audit test plan and replace it with `npm run lint:md` so the lint step uses the
package.json configuration (`lint:md`) and respects repo-wide ignore rules and
settings.

🪄 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: ad56441e-c0ed-48ef-8c55-ab5cdcce5c6c

📥 Commits

Reviewing files that changed from the base of the PR and between fdcb5da and 5b5d408.

📒 Files selected for processing (15)

docs/BEARING.md
docs/design/0251-v18-post-merge-release-handoff/v18-post-merge-release-handoff.md
docs/design/0252-v18-tag-publish-gate/v18-tag-publish-gate.md
docs/design/0253-v18-release-evidence-archive/v18-release-evidence-archive.md
docs/design/0254-post-v18-storage-retirement-decision/post-v18-storage-retirement-decision.md
docs/design/0255-v19-native-continuum-witnesshood-runway/v19-native-continuum-witnesshood-runway.md
docs/design/0256-v20-streaming-reads-writes-scope/v20-streaming-reads-writes-scope.md
docs/design/0257-post-v18-public-doc-honesty-audit/post-v18-public-doc-honesty-audit.md
docs/design/0258-v18-residual-boundary-next-retirement/v18-residual-boundary-next-retirement.md
docs/design/0259-backlog-lane-cleanup-after-v18/backlog-lane-cleanup-after-v18.md
docs/design/0260-next-goalpost-replan-after-v18-merge/next-goalpost-replan-after-v18-merge.md
docs/method/backlog/v18.0.0/README.md
docs/method/backlog/v18.0.0/RELEASE_v18-public-release-blockers.md
docs/method/backlog/v19.0.0/README.md
docs/method/backlog/v20.0.0/README.md

flyingrobots · 2026-05-25T21:12:37Z

Resolved the self-review finding in e8edb90b (docs: Clarify latest public release line).

Finding	Outcome	Commit
`docs/BEARING.md` implied `17.0.1` was the latest public package/tag line despite npm/tag/release evidence showing only `17.0.0`	Updated BEARING to distinguish the public `17.0.0` package/tag line from the source-recorded `17.0.1` repair entry, which currently lacks public npm/tag evidence.	`e8edb90b`

Verification:

npx markdownlint docs/BEARING.md
# passed

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

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

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

github-actions · 2026-05-25T21:16:47Z

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 · 2026-05-25T23:26:09Z

@codex Self-review findings for PR #108 after e8edb90b. Please confirm before merge.

Severity	File/Lines	Type	Finding	Recommended mitigation prompt
P2 Major	`docs/ROADMAP.md:7`; compare `docs/BEARING.md:30-31`, `docs/BEARING.md:47-50`, and `docs/design/0257-post-v18-public-doc-honesty-audit/post-v18-public-doc-honesty-audit.md:32`	Release-state documentation consistency	The PR now correctly distinguishes the public `v17.0.0` package/tag line from the source-recorded `17.0.1` repair entry in BEARING, but `docs/ROADMAP.md` still states “Current release on `main`: v17.0.1”. That contradicts the new BEARING wording and the new public-doc honesty acceptance criterion that public docs agree on package line and release status. Even though ROADMAP is marked reference-only, this line is explicit current release metadata and will mislead release handoff readers.	`Update docs/ROADMAP.md so its current-release line matches the public package/tag evidence: use v17.0.0 as the current public release and describe v17.0.1 as a source-recorded repair entry without public npm/tag evidence, matching docs/BEARING.md.`

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

npm view @git-stunts/git-warp version --json
# "17.0.0"

git ls-remote --tags origin 'refs/tags/v18.0.0*'
# no output

rg -n 'Current release on `main`|Latest released package line|17\.0\.1|17\.0\.0|package/tag' docs/ROADMAP.md docs/BEARING.md docs/design/0257-post-v18-public-doc-honesty-audit/post-v18-public-doc-honesty-audit.md
# docs/ROADMAP.md:7 still says v17.0.1 while BEARING now says public v17.0.0 package/tag line

flyingrobots · 2026-05-25T23:36:11Z

Resolved the second self-review finding in two commits:

Finding	Outcome	Commit
`docs/ROADMAP.md` still said the current release on `main` was `v17.0.1`, contradicting the corrected public package/tag evidence in BEARING	Updated ROADMAP to say the current public package/tag release is `v17.0.0`, while `17.0.1` repair work is source-recorded without public npm/tag evidence. Also aligned the backlog index wording that still implied `17.0.1` had shipped publicly.	`3800ed2f`
Release-policy shape test still asserted the old ROADMAP header	Updated `test/unit/scripts/release-policy-shape.test.ts` to assert the new public package/tag release wording and source-recorded repair-entry wording.	`db2c433f`

Verification:

npx markdownlint docs/ROADMAP.md docs/method/backlog/README.md docs/BEARING.md
# passed

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

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

npm exec vitest run test/unit/scripts/release-policy-shape.test.ts
# 1 file passed, 8 tests passed

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

github-actions · 2026-05-25T23:40:22Z

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 · 2026-05-26T00:19:39Z

Resolved CodeRabbit's actionable feedback in 44ef0ab4 (docs: Use canonical markdown lint command).

Feedback	Outcome	Commit
In `docs/design/0257-post-v18-public-doc-honesty-audit/...`, replace raw `npx markdownlint` in the test plan with the repo's canonical `npm run lint:md` command.	Updated the test plan to use `npm run lint:md` so it reflects the package script and repo-wide markdown configuration.	`44ef0ab4`

Verification:

npm run lint:md -- docs/design/0257-post-v18-public-doc-honesty-audit/post-v18-public-doc-honesty-audit.md
# passed

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

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

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

github-actions · 2026-05-26T00:23:49Z

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 added 11 commits May 25, 2026 13:50

docs: Record v18 post-merge release handoff

8fa36ae

docs: Define v18 tag publish gate

5304dd1

docs: Define v18 release evidence archive

9f39726

docs: Frame post-v18 storage retirement decision

fcf4657

docs: Frame v19 Continuum witnesshood runway

243a0bb

docs: Scope v20 graph streaming goal

508ba24

docs: Define post-v18 doc honesty audit

9006d72

docs: Pick next residual boundary decision

9bf7045

docs: Plan backlog lane cleanup after v18

f42eb54

docs: Replan after v18 release-prep merge

c31d206

docs: Update bearing after v18 release-prep merge

5b5d408

coderabbitai Bot reviewed May 25, 2026

View reviewed changes

Comment thread docs/design/0257-post-v18-public-doc-honesty-audit/post-v18-public-doc-honesty-audit.md Outdated

docs: Clarify latest public release line

e8edb90

flyingrobots added 2 commits May 25, 2026 16:32

docs: Align v17 public release references

3800ed2

test: Update release policy roadmap expectation

db2c433

docs: Use canonical markdown lint command

44ef0ab

flyingrobots merged commit 59beefe into main May 26, 2026
16 checks passed

flyingrobots deleted the v18-release-prep-slices-103-112 branch May 26, 2026 00:24

coderabbitai Bot mentioned this pull request May 26, 2026

Rotate completed BEARING history #109

Merged

Conversation

flyingrobots commented May 25, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Verification

Notes

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented May 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Poem

Uh oh!

github-actions Bot commented May 25, 2026

Release Preflight

Uh oh!

flyingrobots commented May 25, 2026

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

flyingrobots commented May 25, 2026

Uh oh!

github-actions Bot commented May 25, 2026

Release Preflight

Uh oh!

flyingrobots commented May 25, 2026

Uh oh!

flyingrobots commented May 25, 2026

Uh oh!

github-actions Bot commented May 25, 2026

Release Preflight

Uh oh!

flyingrobots commented May 26, 2026

Uh oh!

github-actions Bot commented May 26, 2026

Release Preflight

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

flyingrobots commented May 25, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented May 25, 2026 •

edited

Loading