---
phase: 57-control-plane-docs-doctor-parity-and-regression-closure
plan: 01
type: execute
wave: 1
depends_on:
  - 54-control-plane-ontology-freeze-and-runtime-contracts
  - 55-paired-backend-alignment-and-drift-audit
  - 56-h-plane-steering-and-approval-surface-consolidation
files_modified:
  - research/knowledge-hub/knowledge_hub/frontdoor_support.py
  - research/knowledge-hub/tests/test_aitp_service.py
  - research/knowledge-hub/tests/test_agent_bootstrap_assets.py
  - README.md
  - research/knowledge-hub/README.md
  - docs/INSTALL_CODEX.md
  - docs/INSTALL_CLAUDE_CODE.md
  - docs/INSTALL_OPENCODE.md
  - research/knowledge-hub/runtime/scripts/run_scrpa_control_plane_acceptance.py
autonomous: true
requirements:
  - REQ-CTRL-01
  - REQ-CTRL-02
  - REQ-BACKEND-01
  - REQ-BACKEND-02
  - REQ-HPLANE-02
  - REQ-VERIFY-01
must_haves:
  truths:
    - doctor must expose the control-plane governance surface explicitly
    - public docs must name the new audit entrypoints directly
    - milestone closure requires one non-mocked real-topic verification path
---

<objective>
Close `v1.43` with doctor parity, public-doc parity, and one real-topic
control-plane / paired-backend verification flow.
</objective>

<execution_context>
@D:/BaiduSyncdisk/Theoretical-Physics/.codex-home/get-shit-done/workflows/execute-plan.md
@D:/BaiduSyncdisk/Theoretical-Physics/.codex-home/get-shit-done/templates/summary.md
</execution_context>

<context>
@.planning/phases/57-control-plane-docs-doctor-parity-and-regression-closure/57-CONTEXT.md
@.planning/REQUIREMENTS.md
@README.md
@research/knowledge-hub/README.md
@docs/INSTALL_CODEX.md
@docs/INSTALL_CLAUDE_CODE.md
@docs/INSTALL_OPENCODE.md
@research/knowledge-hub/knowledge_hub/frontdoor_support.py
@research/knowledge-hub/knowledge_hub/aitp_service.py
@research/knowledge-hub/knowledge_hub/aitp_cli.py
</context>

<tasks>

<task type="auto">
  <name>Task 1: Add failing tests for doctor governance parity and public docs parity</name>
  <files>research/knowledge-hub/tests/test_aitp_service.py, research/knowledge-hub/tests/test_agent_bootstrap_assets.py</files>
  <read_first>research/knowledge-hub/tests/test_aitp_service.py, research/knowledge-hub/tests/test_agent_bootstrap_assets.py, research/knowledge-hub/knowledge_hub/frontdoor_support.py, README.md, research/knowledge-hub/README.md</read_first>
  <action>Add failing tests that require `aitp doctor --json` to expose explicit control-plane governance contracts and audit commands, and require the public docs to name `aitp capability-audit`, `aitp paired-backend-audit`, and `aitp h-plane-audit`.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_aitp_service.py research/knowledge-hub/tests/test_agent_bootstrap_assets.py -q</verify>
  <acceptance_criteria>
    - tests fail before implementation
    - failures prove the doctor payload or docs are missing the new governance surface
  </acceptance_criteria>
  <done>A real red contract exists for Phase `57`.</done>
</task>

<task type="auto">
  <name>Task 2: Implement doctor control-plane governance parity</name>
  <files>research/knowledge-hub/knowledge_hub/frontdoor_support.py, research/knowledge-hub/tests/test_aitp_service.py</files>
  <read_first>research/knowledge-hub/knowledge_hub/frontdoor_support.py, research/knowledge-hub/knowledge_hub/aitp_service.py, research/knowledge-hub/tests/test_aitp_service.py</read_first>
  <action>Add explicit doctor payload sections that surface the control-plane architecture/paired-backend contracts and the CLI audit/status entrypoints operators should use to inspect them.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_aitp_service.py -q</verify>
  <acceptance_criteria>
    - `ensure_cli_installed()` returns explicit control-plane governance docs and commands
    - the returned section includes both contract paths and audit/status commands
  </acceptance_criteria>
  <done>Doctor can explain the control-plane governance surface without doc hunting.</done>
</task>

<task type="auto">
  <name>Task 3: Update public docs and kernel docs for control-plane closure</name>
  <files>README.md, research/knowledge-hub/README.md, docs/INSTALL_CODEX.md, docs/INSTALL_CLAUDE_CODE.md, docs/INSTALL_OPENCODE.md, research/knowledge-hub/tests/test_agent_bootstrap_assets.py</files>
  <read_first>README.md, research/knowledge-hub/README.md, docs/INSTALL_CODEX.md, docs/INSTALL_CLAUDE_CODE.md, docs/INSTALL_OPENCODE.md, research/knowledge-hub/tests/test_agent_bootstrap_assets.py</read_first>
  <action>Update the main usage docs so operators see the control-plane audit path in the normal command flow and know that `aitp doctor --json` now exposes governance docs plus audit/status entrypoints.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_agent_bootstrap_assets.py -q</verify>
  <acceptance_criteria>
    - root README names the new audit commands
    - kernel README names the new audit commands and extracted support modules
    - install docs explain that `doctor --json` exposes control-plane governance
  </acceptance_criteria>
  <done>Docs and install guides match the production control-plane surface.</done>
</task>

<task type="auto">
  <name>Task 4: Add a real-topic control-plane and paired-backend acceptance flow</name>
  <files>research/knowledge-hub/runtime/scripts/run_scrpa_control_plane_acceptance.py</files>
  <read_first>research/knowledge-hub/runtime/scripts/run_scrpa_thesis_topic_acceptance.py, research/knowledge-hub/runtime/scripts/run_tfim_benchmark_code_method_acceptance.py, research/knowledge-hub/knowledge_hub/aitp_service.py, research/knowledge-hub/knowledge_hub/aitp_cli.py</read_first>
  <action>Create a non-mocked real-topic acceptance script around the scRPA thesis anchor that opens a real topic, materializes steering and paired-backend runtime state, runs production `doctor`, `status`, `capability-audit`, `paired-backend-audit`, and `h-plane-audit` surfaces, and verifies their durable artifacts.</action>
  <verify>python research/knowledge-hub/runtime/scripts/run_scrpa_control_plane_acceptance.py --json</verify>
  <acceptance_criteria>
    - the acceptance script exits 0 on a real topic
    - it proves doctor/status/audit surfaces through production code
    - it writes durable audit artifacts under the topic runtime root
  </acceptance_criteria>
  <done>Phase `57` has a non-mocked real-topic verification path.</done>
</task>

<task type="auto">
  <name>Task 5: Re-run the integrated slice and full suite</name>
  <files>research/knowledge-hub/tests/test_aitp_service.py, research/knowledge-hub/tests/test_agent_bootstrap_assets.py</files>
  <read_first>.planning/REQUIREMENTS.md</read_first>
  <action>Re-run the doctor/docs slice, the real-topic acceptance, and the full knowledge-hub suite to close `v1.43` on a green baseline.</action>
  <verify>python -m pytest research/knowledge-hub/tests -q</verify>
  <acceptance_criteria>
    - targeted tests exit 0
    - the real-topic acceptance exits 0
    - the full knowledge-hub suite exits 0
  </acceptance_criteria>
  <done>`v1.43` lands on a verified green baseline.</done>
</task>

</tasks>
