---
phase: 151-hypothesis-route-handoff-surface
plan: 01
type: execute
wave: 1
depends_on:
  - v1.76-closure
files_modified:
  - research/knowledge-hub/knowledge_hub/runtime_read_path_support.py
  - research/knowledge-hub/knowledge_hub/runtime_bundle_support.py
  - research/knowledge-hub/knowledge_hub/topic_replay.py
  - research/knowledge-hub/runtime/schemas/progressive-disclosure-runtime-bundle.schema.json
  - research/knowledge-hub/runtime/scripts/run_hypothesis_route_handoff_acceptance.py
  - research/knowledge-hub/tests/test_hypothesis_route_handoff_contracts.py
  - research/knowledge-hub/tests/test_runtime_scripts.py
  - research/knowledge-hub/tests/test_topic_replay.py
  - research/knowledge-hub/tests/test_schema_contracts.py
  - research/knowledge-hub/README.md
  - research/knowledge-hub/runtime/README.md
  - research/knowledge-hub/runtime/AITP_TEST_RUNBOOK.md
autonomous: true
requirements:
  - REQ-HHANDOFF-01
  - REQ-HHANDOFF-02
  - REQ-HHANDOFF-03
  - REQ-VERIFY-01
must_haves:
  truths:
    - extend existing route activation and re-entry contracts instead of inventing a disconnected handoff ledger
    - keep the first slice bounded to declarative handoff visibility rather than automatic route mutation
    - coexist with the current action queue, route_activation, route_reentry, and helper mechanisms
---

<objective>
Make the concrete handoff implications of re-entry-ready parked routes explicit
on the active topic surface so operators can see which parked route is now a
concrete next-step candidate and which ready parked routes should still remain
parked.
</objective>

<tasks>

<task type="auto">
  <name>Task 1: Add hypothesis route handoff summary to runtime/replay surfaces</name>
  <files>research/knowledge-hub/knowledge_hub/runtime_read_path_support.py, research/knowledge-hub/knowledge_hub/runtime_bundle_support.py, research/knowledge-hub/knowledge_hub/topic_replay.py, research/knowledge-hub/runtime/schemas/progressive-disclosure-runtime-bundle.schema.json</files>
  <read_first>research/knowledge-hub/knowledge_hub/runtime_read_path_support.py</read_first>
  <action>Add one explicit route handoff summary derived from the current local route plus re-entry-ready parked routes.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_hypothesis_route_handoff_contracts.py -q</verify>
  <acceptance_criteria>
    - runtime surfaces expose ready parked-route handoff candidates directly
    - replay/read paths surface keep-parked versus handoff-candidate decisions directly
    - the handoff surface coexists with route activation, route re-entry, and the current helper mechanisms
  </acceptance_criteria>
  <done>The route handoff surface is durable and operator-visible.</done>
</task>

<task type="auto">
  <name>Task 2: Add isolated acceptance and docs</name>
  <files>research/knowledge-hub/runtime/scripts/run_hypothesis_route_handoff_acceptance.py, research/knowledge-hub/tests/test_runtime_scripts.py, research/knowledge-hub/tests/test_topic_replay.py, research/knowledge-hub/tests/test_schema_contracts.py, research/knowledge-hub/README.md, research/knowledge-hub/runtime/README.md, research/knowledge-hub/runtime/AITP_TEST_RUNBOOK.md</files>
  <read_first>research/knowledge-hub/runtime/scripts/run_hypothesis_route_reentry_acceptance.py</read_first>
  <action>Add one isolated acceptance lane and align docs so the route handoff surface is testable and discoverable.</action>
  <verify>python research/knowledge-hub/runtime/scripts/run_hypothesis_route_handoff_acceptance.py --json</verify>
  <acceptance_criteria>
    - docs and runbook reference the route handoff acceptance lane
    - isolated acceptance proves ready parked-route handoff visibility on a temp kernel root without automatic route mutation
  </acceptance_criteria>
  <done>Phase `151` is ready to execute and verify.</done>
</task>

</tasks>
