141 lines
3.9 KiB
Markdown
141 lines
3.9 KiB
Markdown
# 102 Sweep Status Reconciliation Plan
|
|
|
|
> Date: 2026-04-19
|
|
> Status: Draft
|
|
> Upstream Spec: `docs/superpowers/specs/2026-04-19-102-sweep-status-reconciliation-design.md`
|
|
|
|
## Plan Intent
|
|
|
|
Reconcile the follow-up `102` sweep result with the final route-conflict decisions so the next roadmap uses a trustworthy status baseline.
|
|
|
|
This plan is a status reconciliation plan, not an implementation plan.
|
|
|
|
## Scope Guardrails
|
|
|
|
1. do not modify `src/generated_scene/analyzer.rs`
|
|
2. do not modify `src/generated_scene/generator.rs`
|
|
3. do not modify `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
|
|
4. do not promote any scene
|
|
5. do not add or modify family baselines
|
|
6. do not rerun the `102` sweep
|
|
7. do not implement fixes for fail-closed or timeout records
|
|
|
|
## Phase 0: Freeze Inputs
|
|
|
|
### Objective
|
|
|
|
Freeze the exact reconciliation inputs.
|
|
|
|
### Tasks
|
|
|
|
1. read `full_sweep_improvement_followup_2026-04-19.json`
|
|
2. read `remaining_route_conflict_decisions_2026-04-19.json`
|
|
3. verify follow-up sweep scene count is `102`
|
|
4. verify route-decision conflict count is `4`
|
|
|
|
### Deliverables
|
|
|
|
1. input validation summary
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. reconciliation does not proceed if follow-up scene count is not `102`
|
|
2. reconciliation does not proceed if route-decision count is not `4`
|
|
|
|
## Phase 1: Merge Route Decisions
|
|
|
|
### Objective
|
|
|
|
Apply route-conflict decisions as a reconciliation overlay without changing raw sweep status.
|
|
|
|
### Tasks
|
|
|
|
1. match route decisions by `sceneId`
|
|
2. for each matching scene, keep `dryRunStatus = misclassified`
|
|
3. add `routeDecision = valid-host-bridge-workflow`
|
|
4. set `reconciledStatus = adjudicated-valid-host-bridge`
|
|
5. preserve decision reason and evidence summary
|
|
|
|
### Deliverables
|
|
|
|
1. route-decision overlay records
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. all `4` route decisions match a follow-up scene
|
|
2. all `4` are reconciled to `adjudicated-valid-host-bridge`
|
|
3. no broad status rewrite is performed
|
|
|
|
## Phase 2: Build Reconciled Status Counts
|
|
|
|
### Objective
|
|
|
|
Build the reconciled status summary for all `102` scenes.
|
|
|
|
### Tasks
|
|
|
|
1. copy all follow-up scene records into a new reconciliation asset
|
|
2. assign `reconciledStatus` for every scene
|
|
3. count statuses:
|
|
- `auto-pass`
|
|
- `fail-closed-known`
|
|
- `adjudicated-valid-host-bridge`
|
|
- `source-unreadable`
|
|
- `missing-source`
|
|
- `unsupported-family`
|
|
- `misclassified-unresolved`
|
|
4. summarize fail-closed records by archetype and reason
|
|
5. preserve remaining timeout records as unresolved timeout inputs
|
|
|
|
### Deliverables
|
|
|
|
1. `tests/fixtures/generated_scene/full_sweep_status_reconciliation_2026-04-19.json`
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. total scene count is `102`
|
|
2. reconciled status count total is `102`
|
|
3. unresolved misclassification count is `0`
|
|
4. timeout count remains `2`
|
|
|
|
## Phase 3: Publish Reconciliation Report
|
|
|
|
### Objective
|
|
|
|
Make the reconciled state readable and actionable.
|
|
|
|
### Tasks
|
|
|
|
1. summarize raw follow-up counts
|
|
2. summarize reconciled counts
|
|
3. list `4` valid-host-bridge adjudications
|
|
4. list `2` remaining timeout inputs
|
|
5. summarize `48` fail-closed-known records as the next implementation-analysis candidate
|
|
6. state explicitly that the execution board was not changed
|
|
|
|
### Deliverables
|
|
|
|
1. `docs/superpowers/reports/2026-04-19-102-sweep-status-reconciliation-report.md`
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. report explains why raw `misclassified = 4` no longer means unresolved route bugs
|
|
2. report identifies the next likely roadmap input without starting it
|
|
3. report confirms no code or execution-board changes
|
|
|
|
## Completion Criteria
|
|
|
|
This plan is complete when:
|
|
|
|
1. reconciliation JSON exists
|
|
2. reconciliation report exists
|
|
3. all `4` route conflicts are represented as adjudicated valid host-bridge workflows
|
|
4. no unresolved misclassification remains
|
|
5. `2` timeouts and `48` fail-closed records remain visible as separate future inputs
|
|
|
|
## Stop Statement
|
|
|
|
Stop after publishing the reconciliation JSON and report.
|
|
|
|
Do not start the next roadmap in this plan.
|