# Roadmap: v1.85 Hypothesis Route Transition Escalation Surface

## Result

`v1.85` is complete.

## Overview

`v1.85` closed the next post-`v1.84` research-control gap around
hypothesis-aware route transition escalation. It derived one bounded
`route_transition_escalation` summary from the current route transition repair
plus operator-checkpoint context, surfaced the bounded escalation state through
runtime status and replay, and proved the bounded coexistence path with a
dedicated isolated acceptance lane.

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

## Phase Details

### Phase 159: Hypothesis Route Transition Escalation Surface

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

**Plans:** 1 plan

Plans:

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

**Outcome:**

- landed `route_transition_escalation` payload construction and rendering on
  the runtime/read-path layer
- surfaced `none`, `checkpoint_recommended`, and `checkpoint_active`
  escalation state through runtime status, the runtime protocol note, and
  replay
- aligned schema, docs, and isolated acceptance coverage for the bounded route
  transition-escalation path

## Milestone Summary

**Key Accomplishments:**

- route transition repair and operator-checkpoint context now join into one
  explicit bounded escalation surface
- runtime status and replay now keep checkpoint recommendation versus active
  checkpoint state visible without replacing transition repair or helper
  mechanisms
- one isolated acceptance lane now proves bounded transition-escalation
  visibility stays declarative and does not widen into fresh runtime mutation

**Issues Resolved:**

- closed the gap where operators could see repair but still had to infer when
  that repair should become a human checkpoint
- closed the gap where route-transition repair still had no explicit escalation
  surface

**Issues Deferred:**

- explicit route-transition clearance after checkpoint lifecycle changes
- automatic route commit and follow-up runtime mutation
- automatic branch spawning and multi-branch scheduling

**Technical Debt / Honest Gaps:**

- the first slice makes route-transition escalation visible, but it does not
  yet surface one explicit clearance lane for when an active or answered
  checkpoint releases the bounded transition back into follow-through

---

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