101 lines
2.5 KiB
Markdown
101 lines
2.5 KiB
Markdown
# Scene Skill 102 Pseudo-Production Batch Execution Preparation Design
|
|
|
|
> Date: 2026-04-20
|
|
> Parent: `2026-04-20-scene-skill-102-pseudoprod-batch-selection-plan.md`
|
|
|
|
## Intent
|
|
|
|
Prepare the first pseudo-production execution batch without running it.
|
|
|
|
This design defines environment handoff requirements, evidence collection rules, and execution record templates for the 10 selected scenes from the batch selection plan.
|
|
|
|
## Fixed Batch
|
|
|
|
The execution preparation batch is fixed by:
|
|
|
|
- `tests/fixtures/generated_scene/scene_skill_102_pseudoprod_batch_selection_2026-04-20.json`
|
|
|
|
The batch contains 10 scenes across:
|
|
|
|
1. `paginated_enrichment`: 4
|
|
2. `multi_mode_request`: 2
|
|
3. `single_request_enrichment`: 2
|
|
4. `multi_endpoint_inventory`: 1
|
|
5. `page_state_eval`: 1
|
|
|
|
## Preparation Only
|
|
|
|
This design does not allow real execution.
|
|
|
|
It only prepares:
|
|
|
|
1. environment handoff checklist
|
|
2. evidence package layout
|
|
3. per-scene execution record template
|
|
4. failure taxonomy mapping
|
|
5. operator instructions
|
|
|
|
## Environment Handoff Requirements
|
|
|
|
The operator must provide or confirm these outside the repository:
|
|
|
|
1. target browser or quasi-production host
|
|
2. network access to required internal endpoints
|
|
3. valid login/session state where needed
|
|
4. allowed output directory for downloaded/exported artifacts
|
|
5. console log capture method
|
|
6. network log capture method
|
|
7. screenshot capture method
|
|
|
|
No credentials, tokens, cookies, or secrets should be stored in the repository.
|
|
|
|
## Evidence Package Layout
|
|
|
|
Each scene should use a local evidence folder outside tracked credentials:
|
|
|
|
```text
|
|
pseudoprod_evidence/
|
|
<scene-id>/
|
|
execution-record.json
|
|
console.log
|
|
network-summary.json
|
|
screenshot.png
|
|
exported-artifact.*
|
|
notes.md
|
|
```
|
|
|
|
The repository may store templates and redacted summaries, but not sensitive raw credentials or session material.
|
|
|
|
## Execution Result States
|
|
|
|
Each scene must resolve to one of:
|
|
|
|
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`
|
|
|
|
## Forbidden Scope
|
|
|
|
This design does not allow:
|
|
|
|
1. running browser automation
|
|
2. invoking real target systems
|
|
3. storing credentials
|
|
4. modifying generated skills
|
|
5. modifying `analyzer.rs`, `generator.rs`, dispatch, or runtime code
|
|
6. updating official board status
|
|
|
|
## Expected Outputs
|
|
|
|
1. environment handoff checklist JSON
|
|
2. per-scene execution record template JSON
|
|
3. evidence checklist JSON
|
|
4. preparation report
|
|
|