Record successful PromptKit cache recovery

docs/roadmap/promptkit-bug-report.md

@@ -1,7 +1,7 @@
 # PromptKit Bug Report: v0.2.0 Module Checksum Mismatch
 
 **Status:** Stale local module metadata confirmed; test isolation fixed.
-Shared-cache recovery and PromptKit's adoption retry remain pending.
+Shared-cache recovery and PromptKit's Stage 1 adoption retry succeeded.
 
 ## Summary
 
@@ -90,7 +90,8 @@ The exact command that created the stale metadata remains unknown.
 
 These results support continued use of the published v0.2.0 version. The
 investigation left the affected shared cache and repository contents unchanged.
-Recovery was verified in a copied cache; PromptKit's adoption retry remains pending.
+Recovery was initially verified in a copied cache. The subsequent shared-cache
+recovery and consumer retry are recorded below.
 
 ### Related Test-Isolation Defect
 
@@ -124,3 +125,26 @@ before the fix and passed afterward. All Woodpecker workflow tests passed.
 2. Record the actual cache recovery and consumer retry outcomes here. Preserve
    the published v0.2.0 tag and checksums; this incident requires no replacement
    release.
+
+## Consumer Recovery Outcome
+
+On 2026-10-08, PromptKit quarantined only the stale shared-cache
+`v0.2.0.mod`. The original 58-byte file is retained at
+`/home/eric/releasekit-cache-quarantine-WtdracPk/v0.2.0.mod`; no archive,
+extracted module, or unrelated cache entry was removed.
+
+The retry used Go 1.26.8 with `GOTOOLCHAIN=local`, `GOWORK=off`,
+`GOSUMDB=sum.golang.org`, and cleared `GONOSUMDB`/`GOPRIVATE` bypass settings.
+`go mod download -json gitea.maximumdirect.net/eric/ReleaseKit@v0.2.0`
+succeeded and returned the published commit and expected checksums:
+
+- Commit: `e030794969fb7787e647a90bbc4eb81bd0610f07`.
+- Archive: `h1:EACELngRel4RiulR+Ors56nMZ5fA9orJDyhPxn6UVe4=`.
+- `go.mod`: `h1:xN8w1OWjhCwtDxyHVFbKxFWowuEPbMTCZrf0JIIm9pE=`.
+
+PromptKit then successfully added the v0.2.0 Go tool dependency and prepared
+its module dependencies with checksum verification enabled. Its readonly,
+offline `go test ./...` run passed under the selected local Go installation;
+the root package's runtime dependency list contains no ReleaseKit import.
+This completes the previously blocked Stage 1. The remaining adoption stages
+are still to be implemented. The published v0.2.0 tag remains unchanged.