---
phase: 74-collaborator-profile-and-session-continuity
plan: 01
type: execute
wave: 1
depends_on:
  - 73-docs-acceptance-and-regression-closure
files_modified:
  - research/knowledge-hub/knowledge_hub/collaborator_profile_support.py
  - research/knowledge-hub/knowledge_hub/runtime_bundle_support.py
  - research/knowledge-hub/knowledge_hub/aitp_service.py
  - research/knowledge-hub/knowledge_hub/kernel_markdown_renderers.py
  - research/knowledge-hub/runtime/schemas/progressive-disclosure-runtime-bundle.schema.json
  - research/knowledge-hub/tests/test_aitp_service.py
  - research/knowledge-hub/tests/test_schema_contracts.py
autonomous: true
requirements:
  - REQ-CPROF-01
  - REQ-CPROF-02
must_haves:
  truths:
    - collaborator profile must be a real durable runtime surface, not only raw collaborator-memory rows
    - continuity surfaces must expose collaborator-profile paths and summary through production code
    - watchlisted hotspot budgets must remain green after the wiring lands
---

<objective>
Open `v1.48` by making collaborator-profile continuity explicit across runtime
bundle, status, session-start, and current-topic memory.
</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/74-collaborator-profile-and-session-continuity/74-CONTEXT.md
@.planning/REQUIREMENTS.md
@research/knowledge-hub/knowledge_hub/collaborator_profile_support.py
@research/knowledge-hub/tests/test_aitp_service.py
</context>

<tasks>

<task type="auto">
  <name>Task 1: Add failing collaborator-profile surface tests</name>
  <files>research/knowledge-hub/tests/test_aitp_service.py, research/knowledge-hub/tests/test_schema_contracts.py</files>
  <read_first>research/knowledge-hub/knowledge_hub/topic_shell_support.py</read_first>
  <action>Add red tests that require collaborator profile to appear in topic status, current-topic memory, session-start artifacts, and the runtime-bundle schema.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_aitp_service.py -k "collaborator_profile or current_topic_memory_payload_includes_collaborator_profile_when_present or start_chat_session_materializes_current_topic_route" -q</verify>
  <acceptance_criteria>
    - tests fail before production wiring
    - failures prove collaborator-profile continuity is still missing from real surfaces
  </acceptance_criteria>
  <done>A red contract exists for collaborator-profile continuity.</done>
</task>

<task type="auto">
  <name>Task 2: Wire collaborator profile through runtime surfaces</name>
  <files>research/knowledge-hub/knowledge_hub/collaborator_profile_support.py, research/knowledge-hub/knowledge_hub/runtime_bundle_support.py, research/knowledge-hub/knowledge_hub/aitp_service.py, research/knowledge-hub/knowledge_hub/kernel_markdown_renderers.py, research/knowledge-hub/runtime/schemas/progressive-disclosure-runtime-bundle.schema.json</files>
  <read_first>research/knowledge-hub/knowledge_hub/research_judgment_runtime_support.py</read_first>
  <action>Normalize collaborator profile into the runtime bundle, status, current-topic memory, and session-start artifacts without regrowing hotspot files past watch budgets.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_aitp_service.py research/knowledge-hub/tests/test_schema_contracts.py -q</verify>
  <acceptance_criteria>
    - collaborator-profile red tests turn green
    - runtime bundle schema exposes a stable collaborator-profile contract
    - current-topic and session-start surfaces carry collaborator-profile paths
  </acceptance_criteria>
  <done>Phase `74` has real collaborator-profile continuity surfaces.</done>
</task>

<task type="auto">
  <name>Task 3: Re-run budgets and the full suite</name>
  <files>research/knowledge-hub/tests/test_maintainability_budgets.py, research/knowledge-hub/tests</files>
  <read_first>.planning/REQUIREMENTS.md</read_first>
  <action>Re-run targeted tests, watch budgets, and the full knowledge-hub suite to open `v1.48` on a green baseline.</action>
  <verify>python -m pytest research/knowledge-hub/tests -q</verify>
  <acceptance_criteria>
    - collaborator-profile slice exits 0
    - maintainability watch budgets stay green
    - full suite exits 0
  </acceptance_criteria>
  <done>Phase `74` is ready to hand off and Phase `75` can start from a green baseline.</done>
</task>

</tasks>
