base-layer/releasekit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

Keep recovery handoffs available after publication cancellation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-03 00:12:30 +00:00
parent cd08a2892a
commit dfaa652098
9 changed files with 284 additions and 68 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/roadmap/implementation.md
View File

@@ -465,9 +465,15 @@ failures without additional consumer release infrastructure.
cold Go-tool executable's removal and launcher-owned metadata cleanup.
Explain how to use another selected supported CLI if an entry point becomes
unavailable.
5. Prepare the command after publication using a separate bounded context so
publication cancellation leaves handoff construction available. Report
module-preparation failures separately and retain a persistent native
executable fallback. Recognized temporary Go-build executables provide no
durable native fallback. Keep publication's original status/error and
immediate reconciliation context unchanged.
**R14 follow-up completed:** API-only recovery uses an independent private module
root. R15 tracks cancellation and preparation-failure handling separately.
**R14/R15 follow-ups completed:** API-only recovery uses an independent private
module root; post-failure preparation handles cancellation and native fallback.
**Verification:** Extend existing publication CLI tests for the default, override,
recording warning with successful status, and original failed/unknown status.
@@ -479,6 +485,10 @@ Include an API-only consumer that vendors the library without declaring the CLI
tool; execute its handoff and verify source/vendor contents remain unchanged.
Exercise relative local replacements, versioned replacements, and ReleaseKit's
own source-module recovery entry point.
Coordinate cancellation at the recorded push boundary for native, cold
registered-tool, and temporary-launcher invocations. Execute the resulting
handoff after driver/launcher cleanup and verify retained publication diagnostics
and recovery statuses. Exercise native fallback after module-preparation failure.
## Stage 8: Finish assembled coverage and canonical documentation
@@ -495,6 +505,8 @@ contracts and a short consumer recovery workflow.
before later recovery. Cover root/nested tags and original-record selection.
Retain the assembled vendored API-only handoff coverage added for R14,
alongside cold registered-tool and temporary-launcher recovery.
R15 adds canceled publication and preparation-failure handoff cases using
explicit push readiness and fresh later invocations.
2. Establish read-only behavior through resulting refs, worktree/branch state,
saved records, and controlled observations of candidate/hosted boundaries.
Reuse lower-level classification and codec tests. Tests use local remotes,