# Local-Doc Runtime Roadmap Report

> Date: 2026-04-19
> Plan: `2026-04-19-local-doc-runtime-roadmap-plan.md`
> Parent decision: `2026-04-19-residual-runtime-roadmap-prioritization-plan.md`
> Scope: fixed five `local_doc_pipeline` residuals only

## Boundary

This roadmap consumed only the five residuals selected for local-doc runtime closure:

1. `sweep-033-scene`
2. `sweep-034-scene`
3. `sweep-042-scene`
4. `sweep-051-scene`
5. `sweep-074-scene`

The plan did not update the official execution board, did not start host-bridge runtime work, did not start bootstrap normalization, and did not add a new family.

## Implementation Slice

The bounded implementation changed the minimal G8 contract in `src/generated_scene/generator.rs`.

Before this slice, the five scenes already had local-doc runtime evidence, document export evidence, and localhost dependencies, but the G8 contract did not accept `selectData` / `configServices/selectData` as the local document query leg. They therefore stayed at structured fail-closed.

The new bounded rule accepts local-doc query steps when a `local_doc_pipeline` workflow step has an entry matching one of:

- `selectData`
- `definedSqlQuery`
- `configServices/selectData`
- `configServices/exeSql`

The contract still requires `doc_export` and localhost runtime evidence. This keeps the change scoped to local-doc pipelines and does not relax unrelated archetypes.

## Follow-Up Result

Follow-up asset:

- `tests/fixtures/generated_scene/local_doc_runtime_roadmap_followup_2026-04-19.json`

| Scene id | Scene name | Archetype | Readiness | Result |
| --- | --- | --- | --- | --- |
| `sweep-033-scene` | `供电可靠率指标统计表` | `local_doc_pipeline` | `A` | `auto-pass` |
| `sweep-034-scene` | `供电可靠性数据质量自查报告月报` | `local_doc_pipeline` | `A` | `auto-pass` |
| `sweep-042-scene` | `国网金昌供电公司营商环境周例会报告` | `local_doc_pipeline` | `A` | `auto-pass` |
| `sweep-051-scene` | `嘉峪关可靠性分析报告` | `local_doc_pipeline` | `A` | `auto-pass` |
| `sweep-074-scene` | `同兴智能安全督查日报` | `local_doc_pipeline` | `A` | `auto-pass` |

Summary:

- `totalScenes`: 5
- `autoPass`: 5
- `failClosedKnown`: 0
- `sourceUnreadable`: 0
- `unknown`: 0

## Reconciliation Candidates

Candidate asset:

- `tests/fixtures/generated_scene/local_doc_runtime_reconciliation_candidates_2026-04-19.json`

All five scenes are now `framework-auto-pass-candidate`.

The official board was not updated by this roadmap. Per the promotion and board reconciliation policy, a later dedicated board reconciliation plan must consume this candidate asset.

## Asset Note

The current official board contains legacy scene names for the same fixed sweep ids that differ from the source directories used by this local-doc roadmap. This roadmap intentionally uses the fixed sweep ids from the residual runtime prioritization decision and the concrete plan target source names. It does not correct board naming; that belongs to a dedicated board reconciliation or board hygiene plan.

## Verification

Executed checks:

```powershell
cargo test --test scene_generator_test generator_accepts_g8_local_doc_select_data_contract -- --nocapture
cargo test --test scene_generator_test generator_blocks_incomplete_g8_local_doc_pipeline_contract -- --nocapture
cargo test --test scene_generator_canonical_test -- --nocapture
```

All checks passed.

## Closure

This roadmap is complete. The fixed five local-doc residuals have moved from `framework-structured-fail-closed` to `framework-auto-pass-candidate` in the local-doc follow-up and candidate assets. The next step is a dedicated official board reconciliation plan that decides whether and how to update `scene_execution_board_2026-04-18.json`.