50 lines
2.0 KiB
Markdown
50 lines
2.0 KiB
Markdown
# Backpressure Recovery Plan — task-1771286249-a8b1
|
|
|
|
## Stage Name and Objective
|
|
- Stage: Post-rollout backpressure recovery (verification-only handoff)
|
|
- Objective: resolve pending `build.blocked` after `build.task.abandoned` by producing a fresh, contract-complete `build.done` evidence payload for the already completed rollout.
|
|
|
|
## Next Unchecked Rollout Stage
|
|
- None. `Ralph/PROMPT.md` shows Stage 1-4 complete and `LOOP_COMPLETE`.
|
|
- This iteration remains orchestration-only; no additional migration stage is planned.
|
|
|
|
## Explicit File List (Planner Scope)
|
|
|
|
### Read-only verification targets
|
|
- `Ralph/PROMPT.md`
|
|
- `README.md`
|
|
- `src/data/profile-content.ts`
|
|
- `src/lib/profile-content.ts`
|
|
- `package.json`
|
|
|
|
### Required gate commands for builder execution
|
|
- `npm run lint`
|
|
- `npm run typecheck`
|
|
- `npm run build`
|
|
- `npm audit --omit=dev`
|
|
|
|
## Migration Approach (Safety-First)
|
|
1. Keep this pass verification-only with zero source behavior edits.
|
|
2. Re-run mandatory gates and capture outcomes from the current workspace state.
|
|
3. Publish `build.done` only when all required evidence fields are explicitly present:
|
|
- `tests`
|
|
- `lint`
|
|
- `typecheck`
|
|
- `audit`
|
|
- `coverage`
|
|
- `complexity`
|
|
- `duplication`
|
|
- `performance/specs`
|
|
4. Where tooling is not configured (`tests`, `coverage`, `complexity`), report explicit N/A rationale rather than omitting fields.
|
|
5. Reconfirm canonical content centralization and one-file documentation remain intact.
|
|
|
|
## Compatibility Strategy
|
|
- No code refactors or data-shape changes.
|
|
- Preserve existing IDs/contracts and all route/nav/detail-panel behaviors as-is.
|
|
|
|
## Rollback-Safe Checkpoints
|
|
1. Checkpoint A: rollout-complete state reconfirmed from `Ralph/PROMPT.md`.
|
|
2. Checkpoint B: gate outputs collected (`lint`, `typecheck`, `build`, `audit`).
|
|
3. Checkpoint C: non-gate evidence fields (`tests`, `coverage`, `complexity`, `duplication`, `performance/specs`) explicitly populated.
|
|
4. Checkpoint D: concise, contract-complete `build.done` payload prepared for handoff.
|