98 lines
2.8 KiB
Markdown
98 lines
2.8 KiB
Markdown
# Scene Skill 102 Pseudo-Production Batch Selection Design
|
|
|
|
> Date: 2026-04-20
|
|
> Parent: `2026-04-20-scene-skill-102-static-mock-pseudoprod-validation-plan.md`
|
|
> Upstream: `2026-04-20-sweep-015-direct-mock-partial-closure-plan.md`
|
|
|
|
## Intent
|
|
|
|
Select the first bounded pseudo-production validation batch after all 102 generated skills have passed local full direct mock execution.
|
|
|
|
This design does not execute pseudo-production. It only defines the candidate selection rules, batch composition, evidence requirements, and stop conditions for the next execution stage.
|
|
|
|
## Current Baseline
|
|
|
|
1. Final materialized skills: `102 / 102`
|
|
2. Deterministic invocation readiness: `102 / 102`
|
|
3. Static validation: `102 / 102`
|
|
4. Dispatch dry-run: `102 / 102`
|
|
5. Full direct mock execution: `102 / 102`
|
|
6. Pseudo-production readiness:
|
|
- `pseudo-prod-ready`: `70`
|
|
- `real-env-required`: `32`
|
|
|
|
## Selection Principle
|
|
|
|
The first pseudo-production batch should be small, balanced, and low-risk.
|
|
|
|
It should include only scenes that are:
|
|
|
|
1. materialized
|
|
2. deterministic dispatch ready
|
|
3. static validated
|
|
4. direct mock pass
|
|
5. pseudo-prod-ready
|
|
|
|
It should not include scenes that require host-bridge runtime, local-doc runtime, document export runtime, or other real-environment-only dependencies in the first batch.
|
|
|
|
## Batch Shape
|
|
|
|
The first batch should contain `10` scenes:
|
|
|
|
1. `paginated_enrichment`: 4
|
|
2. `multi_mode_request`: 2
|
|
3. `single_request_enrichment`: 2
|
|
4. `multi_endpoint_inventory`: 1
|
|
5. `page_state_eval`: 1
|
|
|
|
`host_bridge_workflow` and `local_doc_pipeline` are explicitly excluded from the first pseudo-production batch because their readiness records require real environment dependencies.
|
|
|
|
## Required Evidence Per Scene
|
|
|
|
Each selected scene must produce or collect:
|
|
|
|
1. console log
|
|
2. network log or request summary
|
|
3. screenshot if browser target page is required
|
|
4. exported file if an artifact is produced
|
|
5. generation report reference
|
|
6. deterministic invocation input used
|
|
7. final execution classification
|
|
|
|
## Failure Taxonomy
|
|
|
|
Pseudo-production execution results must classify failures as one of:
|
|
|
|
1. `login-blocked`
|
|
2. `network-blocked`
|
|
3. `host-bridge-blocked`
|
|
4. `local-doc-runtime-blocked`
|
|
5. `data-mismatch`
|
|
6. `artifact-mismatch`
|
|
7. `environment-unavailable`
|
|
8. `runtime-error`
|
|
|
|
## Forbidden Scope
|
|
|
|
This design does not allow:
|
|
|
|
1. executing browser automation
|
|
2. accessing production credentials
|
|
3. accessing real business systems
|
|
4. modifying generated skill packages
|
|
5. modifying `analyzer.rs`, `generator.rs`, or runtime dispatch
|
|
6. updating official board status
|
|
7. claiming production pass
|
|
|
|
## Expected Output
|
|
|
|
The output is a pseudo-production batch plan asset that names:
|
|
|
|
1. selected scenes
|
|
2. deferred scenes
|
|
3. selection reasons
|
|
4. execution prerequisites
|
|
5. required evidence checklist
|
|
6. next execution plan input
|
|
|