48 lines
1.5 KiB
Markdown
48 lines
1.5 KiB
Markdown
# Generated Scene Resolver Request Mapping Hardening Plan
|
|
|
|
> Date: 2026-04-20
|
|
> Status: Draft
|
|
> Parent route:
|
|
> - `resolver_request_mapping_hardening`
|
|
> Parent ledger:
|
|
> - `tests/fixtures/generated_scene/generated_scene_source_first_runtime_semantics_ledger_2026-04-20.json`
|
|
|
|
## Plan Intent
|
|
|
|
Implement the first reusable mapping slice for request-field recovery.
|
|
|
|
## Fixed Input Bucket
|
|
|
|
Use the bounded bucket:
|
|
|
|
1. scenes with explicit `org` and/or `period` params
|
|
2. scenes whose source evidence shows request-field tokens like `orgno`, `fdate`, `weekSfdate`, `weekEfdate`
|
|
3. scenes currently lacking explicit generated request-mapping metadata
|
|
|
|
This first slice is expected to center on the parameterized `multi_mode_request` family and adjacent structured-request scenes.
|
|
|
|
## Allowed Files
|
|
|
|
1. `src/generated_scene/analyzer.rs`
|
|
2. `src/generated_scene/generator.rs`
|
|
3. `src/generated_scene/ir.rs`
|
|
4. route-local generator tests
|
|
|
|
## Forbidden Files
|
|
|
|
1. no edits to final materialized skill bundle
|
|
2. no execution-board assets
|
|
3. no runtime / browser callback host
|
|
4. no service console assets
|
|
|
|
## Expected Coverage Delta
|
|
|
|
1. introduce reusable request-field mapping metadata rather than scene-name patches
|
|
2. reduce `resolver_to_request_mapping_gap` in the highest-signal parameterized bucket
|
|
|
|
## Stop Statement
|
|
|
|
Stop after the first reusable mapping slice is implemented and route-local follow-up assets are published.
|
|
|
|
Do not yet attempt full 102-scene closure inside this route plan.
|