---
phase: 150-hypothesis-route-reentry-surface
plan: 01
type: execute
wave: 1
depends_on:
  - v1.75-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_reentry_acceptance.py
  - research/knowledge-hub/tests/test_hypothesis_route_reentry_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-HREENTRY-01
  - REQ-HREENTRY-02
  - REQ-HREENTRY-03
  - REQ-VERIFY-01
must_haves:
  truths:
    - extend existing parked-route contracts instead of inventing a disconnected re-entry ledger
    - keep the first slice bounded to declarative re-entry visibility rather than automatic reactivation or parent-topic mutation
    - coexist with the current route_activation surface, deferred reactivation helpers, and follow-up reintegration mechanisms
---

<objective>
Make the concrete re-entry conditions of parked routes explicit on the active
topic surface so operators can see when a parked hypothesis is merely waiting,
when it is re-entry-ready, and what a follow-up child route still owes before
reintegration.
</objective>

<tasks>

<task type="auto">
  <name>Task 1: Add hypothesis route re-entry 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 re-entry summary derived from deferred-buffer reactivation conditions and follow-up return metadata for parked hypotheses.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_hypothesis_route_reentry_contracts.py -q</verify>
  <acceptance_criteria>
    - runtime surfaces expose which parked routes are waiting versus re-entry-ready
    - replay/read paths surface deferred reactivation conditions and follow-up return obligations directly
    - the re-entry surface coexists with the current route_activation, deferred buffer, and follow-up surfaces
  </acceptance_criteria>
  <done>The route re-entry 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_reentry_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_activation_acceptance.py</read_first>
  <action>Add one isolated acceptance lane and align docs so the route re-entry surface is testable and discoverable.</action>
  <verify>python research/knowledge-hub/runtime/scripts/run_hypothesis_route_reentry_acceptance.py --json</verify>
  <acceptance_criteria>
    - docs and runbook reference the route re-entry acceptance lane
    - isolated acceptance proves deferred reactivation conditions and follow-up return readiness on a temp kernel root without automatic reactivation or parent-topic mutation
  </acceptance_criteria>
  <done>Phase `150` is ready to execute and verify.</done>
</task>

</tasks>
