# v2.2 Milestone Audit

Status: passed

## Scope Closed

- Phase `176`: New-Topic Session-Start Routing Hardening
- Phase `176.1`: Windows Source Registration Path And Status Coherence
- Phase `176.2`: Fresh Real-Topic First-Use Replay Proof

## Requirements Coverage

Score: `5/5` requirements satisfied

- `FTF-01` satisfied by Phase `176` through bounded route fixes that recognize
  explicit "from scratch" fresh-topic intent and allocate a new topic instead
  of reopening current-topic memory.
- `FTF-02` satisfied by Phase `176` through durable `start_chat_session()`
  routing receipts that preserve the corrected `request_new_topic` decision.
- `FTF-03` satisfied by Phase `176.1` through short stable source-directory
  slugs that remove long paper-title path segments from Layer 0 registration.
- `FTF-04` satisfied by Phase `176.1` through immediate runtime/status refresh
  when a topic runtime already exists, plus post-registration proof that
  `source_count >= 1` is visible.
- `FTF-05` satisfied by Phase `176.2` through one replayable first-use lane
  from fresh bootstrap through first-source registration and immediate status
  readback.

## Verification Evidence

- Phase `176` front-door routing:
  - `pytest-session-start-routing.txt`: `8 passed, 147 deselected in 1.90s`
- Phase `176.1` source registration:
  - `pytest-source-discovery-contracts.txt`: `15 passed in 1.37s`
  - `pytest-first-run-cli-e2e.txt`: `1 passed, 25 deselected in 3.52s`
  - `run-first-run-after-registration.json`:
    `runtime_status_sync.status = refreshed`, `source_count = 1`
- Phase `176.2` replay closure:
  - `pytest-runtime-script.txt`: `1 passed, 81 deselected in 3.76s`
  - `first-run-replay.json`:
    `status_after_registration.active_research_contract.l1_source_intake.source_count = 1`

## Cross-Phase Integration

- Phase `176` repaired the front-door route decision so the operator can start
  a fresh topic honestly.
- Phase `176.1` repaired the first-source registration path and immediate
  source visibility on that fresh topic.
- Phase `176.2` then replayed the combined route mechanically instead of
  leaving the end-to-end proof implicit.

## Audit Notes

- This milestone follows the same audit convention as `v2.0` and `v2.1`: it is
  audited from phase `SUMMARY.md` files plus fresh replay receipts.
- No unsatisfied requirement remains in the `v2.2` traceability table.
- The milestone stayed honest: it proves bounded first-use reliability only,
  not broader planning or scientific closure.

## Accepted Open Gaps

- Post-registration next-action selection can still retain the earlier L0
  handoff wording even though source-count visibility is now correct.
- This milestone does not yet widen back to new scientific claims or deeper
  multi-lane replay beyond the bounded first-use route.
