3.4 KiB
3.4 KiB
Scene Skill 102 Pseudo-Production Batch Execution Plan
Date: 2026-04-20 Status: Draft Upstream Design:
docs/superpowers/specs/2026-04-20-scene-skill-102-pseudoprod-batch-execution-design.md
Plan Intent
Run the prepared 10-scene pseudo-production batch in an operator-provided environment and record structured results.
This plan is bounded to execution and evidence collection for the selected 10 scenes.
Fixed Inputs
tests/fixtures/generated_scene/scene_skill_102_pseudoprod_execution_handoff_2026-04-20.jsontests/fixtures/generated_scene/scene_skill_102_pseudoprod_evidence_checklist_2026-04-20.jsontests/fixtures/generated_scene/scene_skill_102_pseudoprod_execution_record_template_2026-04-20.jsontests/fixtures/generated_scene/scene_skill_102_pseudoprod_batch_selection_2026-04-20.json
Planned Outputs
tests/fixtures/generated_scene/scene_skill_102_pseudoprod_batch_execution_results_2026-04-20.jsondocs/superpowers/reports/2026-04-20-scene-skill-102-pseudoprod-batch-execution-report.md
Allowed Files
- planned execution result JSON
- planned execution report
- redacted evidence summaries if explicitly generated
Forbidden Files
src/generated_scene/analyzer.rssrc/generated_scene/generator.rssrc/generated_scene/ir.rsexamples/scene_skill_102_final_materialization_2026-04-19/skills/**tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json- any credential, token, cookie, or secret file
Phase 0: Confirm Environment Readiness
Tasks
- Confirm operator-provided browser/runtime environment exists.
- Confirm network/session access is provided outside repository.
- Confirm evidence output location.
- Confirm redaction rules.
Acceptance Criteria
- No credentials are stored in repository.
- Execution does not start unless environment readiness is confirmed externally.
Phase 1: Execute Selected Scenes
Tasks
For each selected scene:
- use the deterministic invocation input ending with
。。。 - execute through sgClaw runtime or agreed quasi-production host
- collect console log
- collect network summary
- capture screenshot if target page is required
- capture exported artifact if produced
- record final result state
Acceptance Criteria
- every selected scene has one execution record
- every record has exactly one result state
- failures use the allowed taxonomy
Phase 2: Redact And Normalize Evidence
Tasks
- redact credentials, cookies, tokens, Authorization headers, and private data
- normalize evidence paths
- confirm each evidence checklist item is present or explicitly unavailable
Acceptance Criteria
- no secret material enters repository output
- missing evidence has a reason
Phase 3: Publish Execution Results
Tasks
- write execution results JSON
- write execution report
- summarize pass/blocker/mismatch/runtime-error counts
- list follow-up blockers
Acceptance Criteria
- selected scene count remains 10
- report does not claim full production certification
- official board is not updated under this plan
Completion Criteria
This plan is complete when all 10 selected scenes have structured execution records and a redacted execution report is published.
Stop Statement
Stop after publishing execution results and report.
Do not update official board status under this plan.