# 102 Sweep Status Reconciliation Report

> Date: 2026-04-19
> Plan: `docs/superpowers/plans/2026-04-19-102-sweep-status-reconciliation-plan.md`
> Reconciliation Asset: `tests/fixtures/generated_scene/full_sweep_status_reconciliation_2026-04-19.json`

## Input Validation

The reconciliation used only the frozen inputs required by the plan:

| Input | Count |
| --- | ---: |
| Follow-up sweep scenes | 102 |
| Route-conflict decisions | 4 |

All `4` route-conflict decisions matched a follow-up `sceneId`, and each matched record kept raw `dryRunStatus = misclassified`. No `102` sweep rerun was performed.

## Raw Follow-Up Counts

| Raw dry-run status | Count |
| --- | ---: |
| `auto-pass` | 48 |
| `fail-closed-known` | 48 |
| `misclassified` | 4 |
| `source-unreadable` | 2 |
| `missing-source` | 0 |
| `unsupported-family` | 0 |

The raw follow-up asset still reports `misclassified = 4` because it is the original sweep measurement. Those `4` records are not rewritten in place.

## Reconciled Counts

| Reconciled status | Count |
| --- | ---: |
| `auto-pass` | 48 |
| `fail-closed-known` | 48 |
| `adjudicated-valid-host-bridge` | 4 |
| `source-unreadable` | 2 |
| `missing-source` | 0 |
| `unsupported-family` | 0 |
| `misclassified-unresolved` | 0 |
| Total | 102 |

The raw `misclassified = 4` has been fully adjudicated by `remaining_route_conflict_decisions_2026-04-19.json`. In the reconciled view, these no longer represent unresolved route bugs; they are valid host-bridge workflows whose prior group expectations did not close the G2/G3 contracts.

## Valid Host-Bridge Adjudications

| Scene ID | Scene | Raw status | Route decision | Reconciled status |
| --- | --- | --- | --- | --- |
| `sweep-007-95598` | 95598报修工单日管控 | `misclassified` | `valid-host-bridge-workflow` | `adjudicated-valid-host-bridge` |
| `sweep-009-95598` | 95598重要服务事项报备统计表 | `misclassified` | `valid-host-bridge-workflow` | `adjudicated-valid-host-bridge` |
| `sweep-029-scene` | 台区线损台区月度高负损预测 | `misclassified` | `valid-host-bridge-workflow` | `adjudicated-valid-host-bridge` |
| `sweep-093-95598` | 配网支撑月报(95598抢修统计报表) | `misclassified` | `valid-host-bridge-workflow` | `adjudicated-valid-host-bridge` |

Each adjudicated record preserves `decisionReason` and `evidenceSummary` in the reconciliation JSON.

## Remaining Timeout Inputs

| Scene ID | Scene | Raw status | Reason |
| --- | --- | --- | --- |
| `sweep-015-scene` | 任务报表 | `source-unreadable` | generator timeout after 45s |
| `sweep-025-scene` | 力禾动环系统巡视记录 | `source-unreadable` | generator timeout after 45s |

These `2` records remain future timeout/source-scale diagnostic inputs.

After route adjudication, the remaining future inputs are exactly these `2` timeout records and the `48` structured fail-closed records summarized below.

## Fail-Closed Known Summary

| Inferred archetype | Reason | Count |
| --- | --- | ---: |
| `paginated_enrichment` | workflow evidence is incomplete before package generation | 35 |
| `local_doc_pipeline` | workflow evidence is incomplete before package generation | 5 |
| `multi_mode_request` | workflow evidence is incomplete before package generation | 4 |
| `single_request_enrichment` | workflow evidence is incomplete before package generation | 2 |
| `host_bridge_workflow` | workflow evidence is incomplete before package generation | 1 |
| `page_state_eval` | bootstrap_target | 1 |

The remaining structured future inputs are `48` `fail-closed-known` records. They are visible as workflow-evidence or contract-completion analysis candidates, but this plan does not start that roadmap or implement fixes.

## Scope Confirmation

No execution-board status was changed. No scene was promoted. No family baseline was added or modified. `src/generated_scene/analyzer.rs`, `src/generated_scene/generator.rs`, and `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json` were not modified by this reconciliation.