# Roadmap: v1.84 Hypothesis Route Transition Repair Surface

## Result

`v1.84` is complete.

## Overview

`v1.84` closed the next post-`v1.83` research-control gap around
hypothesis-aware route transition repair. It derived one bounded
`route_transition_repair` summary from the current route transition discrepancy
plus current route artifacts, surfaced the bounded repair plan through runtime
status and replay, and proved the bounded coexistence path with a dedicated
isolated acceptance lane.

**Phases:** 158
**Total Plans:** 1
**Total Tasks:** 2
**Shipped:** 2026-04-12

## Phase Details

### Phase 158: Hypothesis Route Transition Repair Surface

**Goal:** Add one durable route transition-repair summary for the current
handoff mismatch and expose it through runtime/read-path/replay flows without
widening into fresh runtime mutation.

**Plans:** 1 plan

Plans:

- [x] `158-01`: add route transition-repair summary to runtime/replay surfaces
  and isolated acceptance

**Outcome:**

- landed `route_transition_repair` payload construction and rendering on the
  runtime/read-path layer
- surfaced `recommended` versus `none_required` repair state through runtime
  status, the runtime protocol note, and replay
- aligned schema, docs, and isolated acceptance coverage for the bounded route
  transition-repair path

## Milestone Summary

**Key Accomplishments:**

- route transition discrepancy and current route artifacts now join into one
  explicit bounded repair plan
- runtime status and replay now keep the next repair step visible without
  replacing discrepancy or helper mechanisms
- one isolated acceptance lane now proves bounded transition-repair visibility
  stays declarative and does not widen into fresh runtime mutation

**Issues Resolved:**

- closed the gap where operators could see discrepancy but still had to infer
  what bounded repair action should happen next
- closed the gap where route-transition mismatch still had no explicit repair
  surface

**Issues Deferred:**

- explicit route-transition escalation into operator checkpoint when repair
  remains unresolved
- automatic candidate reactivation and parent-topic reintegration mutation
- automatic branch spawning and multi-branch scheduling

**Technical Debt / Honest Gaps:**

- the first slice makes route-transition repair visible, but it does not yet
  surface one explicit escalation lane for when discrepancy should become a
  human checkpoint

---

For current planning state after `v1.84`, continue from the next fresh
milestone definition.
