# Phase 165.2-01 Summary

Status: implemented in working tree

## Goal

Make runtime bundle generation actually obey the selected operating mode
(`discussion`, `explore`, `verify`, `promote`) instead of treating mode as
decorative metadata, and make the human-control / bounded-autonomy contract
visible in the generated runtime surfaces.

## What Landed

- mode contract selection now accepts `human_request` and derives
  `active_submode` through `build_runtime_mode_contract()` in:
  - `research/knowledge-hub/knowledge_hub/mode_envelope_support.py`
- runtime bundle generation now does a mode-aware context refocus pass for all
  major modes, not just literature intake:
  - `discussion` foregrounds checkpoint / idea-packet / minimal route context
  - `explore` keeps candidate-formation context light and defers validation /
    promotion surfaces
  - `verify` foregrounds validation bundle + validation contract + selected
    route / execution surfaces
  - `promote` foregrounds readiness + gate surfaces and defers unrelated topic
    history
- mode-scoped trigger sensitivity now suppresses out-of-mode escalation
  triggers before the final runtime bundle is materialized:
  - `research/knowledge-hub/knowledge_hub/mode_envelope_support.py`
  - `research/knowledge-hub/knowledge_hub/runtime_bundle_support.py`
- plain-language human interaction posture and bounded-autonomy posture are now
  top-level runtime/session surfaces instead of hidden secondary context

## Verification

- `python -m pytest research/knowledge-hub/tests/test_runtime_profiles_and_projections.py -q`
- `python -m pytest research/knowledge-hub/tests/test_runtime_scripts.py -q`
- `python -m pytest research/knowledge-hub/tests/test_aitp_service.py -q -k "test_execute_auto_actions_appends_and_runs_literature_intake_stage or test_execute_auto_actions_skips_literature_intake_stage_outside_literature_submode or test_execute_auto_actions_stops_on_backedge_transition_contract or test_execute_auto_actions_stops_when_operator_checkpoint_is_requested or continuous_iterative_verify"`

## Outcome

Plan `165.2-01` is closed as a runtime-envelope enforcement slice.

- mode selection now changes the actual read path instead of only changing
  explanatory text
- verify and promote bundles now expose the right foreground surfaces for the
  bounded task at hand
- trigger activation is no longer allowed to stay globally active when the
  current mode should suppress it
- the generated runtime bundle now exposes whether AITP should wait for the
  human or continue bounded work autonomously
