feat: add generated scene skill platform hardening
This commit is contained in:
@@ -0,0 +1,71 @@
|
||||
# 102 Final Coverage Status Rollup Design
|
||||
|
||||
> Date: 2026-04-19
|
||||
> Parent Framework: `2026-04-19-scene-skill-102-full-coverage-framework-design.md`
|
||||
> Parent Layer: `Layer E`
|
||||
> Status: Active
|
||||
|
||||
## Intent
|
||||
|
||||
Publish a final, policy-governed coverage rollup after the residual 13 closure sequence.
|
||||
|
||||
This design consolidates the latest full-coverage reconciliation candidate view with the residual 13 follow-up reconciliation result. It does not update the official execution board.
|
||||
|
||||
## Inputs
|
||||
|
||||
1. `tests/fixtures/generated_scene/full_coverage_reconciliation_candidates_2026-04-19.json`
|
||||
2. `tests/fixtures/generated_scene/residual_13_reconciliation_candidates_2026-04-19.json`
|
||||
3. `tests/fixtures/generated_scene/boundary_residual_hold_decision_2026-04-19.json`
|
||||
4. `tests/fixtures/generated_scene/bootstrap_target_residual_isolation_2026-04-19.json`
|
||||
5. `tests/fixtures/generated_scene/promotion_board_reconciliation_policy_2026-04-19.json`
|
||||
|
||||
## Output
|
||||
|
||||
1. `tests/fixtures/generated_scene/final_coverage_status_rollup_2026-04-19.json`
|
||||
2. `docs/superpowers/reports/2026-04-19-102-final-coverage-status-rollup-report.md`
|
||||
|
||||
## Rollup Rule
|
||||
|
||||
Start from the 102-scene full coverage reconciliation candidates.
|
||||
|
||||
For every scene present in the residual 13 reconciliation result, replace its previous candidate status with the residual follow-up candidate status.
|
||||
|
||||
## Status Model
|
||||
|
||||
1. `framework-auto-pass-candidate`
|
||||
2. `framework-structured-fail-closed`
|
||||
3. `framework-valid-host-bridge`
|
||||
4. `source-unreadable`
|
||||
5. `unsupported-family`
|
||||
6. `misclassified-unresolved`
|
||||
7. `missing-source`
|
||||
|
||||
## Expected Final Shape
|
||||
|
||||
After residual closure:
|
||||
|
||||
1. `95` framework auto-pass candidates
|
||||
2. `7` structured fail-closed / hold / isolation candidates
|
||||
3. `0` unresolved states
|
||||
4. `0` source-unreadable states
|
||||
5. `0` unsupported-family states
|
||||
6. `0` misclassified-unresolved states
|
||||
|
||||
## Boundary
|
||||
|
||||
This design must not:
|
||||
|
||||
1. update `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`;
|
||||
2. modify `src/generated_scene/analyzer.rs`;
|
||||
3. modify `src/generated_scene/generator.rs`;
|
||||
4. promote scenes to official board state;
|
||||
5. rerun the 102 sweep;
|
||||
6. add a family.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
1. The rollup contains exactly `102` scenes.
|
||||
2. Residual 13 updates are applied.
|
||||
3. The rollup summary matches the final expected shape.
|
||||
4. The official execution board remains untouched.
|
||||
5. The report states whether official board reconciliation should be the next step.
|
||||
Reference in New Issue
Block a user