claw/docs/superpowers/specs/2026-04-20-scene-skill-102-pseudoprod-batch-execution-design.md

Scene Skill 102 Pseudo-Production Batch Execution Design

Date: 2026-04-20 Parent: 2026-04-20-scene-skill-102-pseudoprod-batch-execution-preparation-plan.md

Intent

Execute the prepared 10-scene pseudo-production batch in an operator-provided quasi-production or production-like environment and collect structured evidence.

This design defines execution boundaries and result recording. It does not embed credentials or require credentials to be stored in the repository.

Fixed Inputs

1. tests/fixtures/generated_scene/scene_skill_102_pseudoprod_execution_handoff_2026-04-20.json
2. tests/fixtures/generated_scene/scene_skill_102_pseudoprod_evidence_checklist_2026-04-20.json
3. tests/fixtures/generated_scene/scene_skill_102_pseudoprod_execution_record_template_2026-04-20.json
4. final materialized skill directory: examples/scene_skill_102_final_materialization_2026-04-19/skills

Execution Boundary

Pseudo-production execution may only run in an operator-approved environment where the operator has provided:

1. browser or sgClaw runtime access
2. required network access
3. valid session state outside the repository
4. a local evidence output directory
5. approval to capture redacted logs/screenshots/artifacts

Credential Rule

Never store these in the repository:

1. passwords
2. cookies
3. access tokens
4. Authorization headers
5. private keys
6. VPN secrets
7. internal session dumps

Execution records may reference that an operator-provided session was used, but must not include the session material.

Execution Result States

Each selected scene must resolve to exactly one:

1. pseudo-prod-pass
2. login-blocked
3. network-blocked
4. host-bridge-blocked
5. local-doc-runtime-blocked
6. data-mismatch
7. artifact-mismatch
8. environment-unavailable
9. runtime-error

Evidence Requirements

Each selected scene must collect:

1. execution-record.json
2. console log
3. network summary
4. screenshot when browser target page is required
5. exported artifact if produced
6. notes

All evidence must be redacted before committing any summary to the repository.

Repository Outputs

The repository should receive only redacted and structured execution summaries:

1. tests/fixtures/generated_scene/scene_skill_102_pseudoprod_batch_execution_results_2026-04-20.json
2. docs/superpowers/reports/2026-04-20-scene-skill-102-pseudoprod-batch-execution-report.md

Raw evidence may remain outside the repository unless explicitly redacted.

Forbidden Scope

This design does not allow:

1. committing credentials
2. modifying generated skill packages
3. modifying analyzer/generator/runtime code
4. updating official board status
5. expanding beyond the selected 10 scenes
6. treating pseudo-production pass as full production certification