chore: close out v1.19 planning artifacts

Author: szTheory

.planning/REQUIREMENTS.md

@@ -11,24 +11,24 @@
 ### INTEG — Adapter contracts and host wiring
 
 - [x] **INTEG-01**: Threadline publishes one stable adapter contract for actor extraction, additive context overrides, optional dependency behavior, and operator-surface composition across `Threadline.Plug`, `Threadline.Job`, and `Threadline.Integrations.*`.
-- [ ] **INTEG-02**: At least one first-party breadth path ships as a reusable `Threadline.Integrations.*` reference integration that materially reduces host glue while keeping the host framework as a soft dependency.
-- [ ] **INTEG-03**: The operator surface has a documented and tested host-owned access pattern for router pipeline checks, LiveView mount checks, and optional scoped investigation queries, without introducing a Threadline-owned user or role model.
+- [x] **INTEG-02**: At least one first-party breadth path ships as a reusable `Threadline.Integrations.*` reference integration that materially reduces host glue while keeping the host framework as a soft dependency.
+- [x] **INTEG-03**: The operator surface has a documented and tested host-owned access pattern for router pipeline checks, LiveView mount checks, and optional scoped investigation queries, without introducing a Threadline-owned user or role model.
 
 ### COMPAT — Support matrix and verification honesty
 
 - [x] **COMPAT-01**: Threadline documents a narrow support matrix that names only proven combinations for Plug-only installs, Phoenix operator-surface installs, and the current Sigra-backed reference path.
 - [x] **COMPAT-02**: Verification and CI entrypoints exercise the claimed breadth story, including compile-without-optional-deps and the named surface/reference-path combinations, so docs do not promise ranges that the repo does not prove.
-- [ ] **COMPAT-03**: Example-app and guide dependency pins, install steps, and compatibility wording are refreshed to the currently supported Phoenix/Sigra lines with explicit caveats where support differs by host stack.
+- [x] **COMPAT-03**: Example-app and guide dependency pins, install steps, and compatibility wording are refreshed to the currently supported Phoenix/Sigra lines with explicit caveats where support differs by host stack.
 
 ### ADOPT — Mount recipes and runbooks
 
-- [ ] **ADOPT-08**: Threadline ships canonical mount recipes for secure admin and support-read-only operator-surface installs, including router placement, `live_session` / mount-auth expectations, and first verification steps.
-- [ ] **ADOPT-09**: The canonical reference path is proven end to end in docs and the example app, and every recommended surface-first workflow names the equivalent Mix-task or CLI fallback for capture-only adopters.
+- [x] **ADOPT-08**: Threadline ships canonical mount recipes for secure admin and support-read-only operator-surface installs, including router placement, `live_session` / mount-auth expectations, and first verification steps.
+- [x] **ADOPT-09**: The canonical reference path is proven end to end in docs and the example app, and every recommended surface-first workflow names the equivalent Mix-task or CLI fallback for capture-only adopters.
 
 ### PKG — Packaging-boundary decision
 
-- [ ] **PKG-01**: Threadline defines an explicit `threadline_web` extraction-readiness scorecard based on objective triggers such as version-matrix pressure, release-cadence divergence, and repeated adopter glue.
-- [ ] **PKG-02**: v1.19 closes with a documented package-boundary decision — expected default: stay in-tree for now — with README, guides, module-grouping/package contracts, and migration-path wording aligned to that decision.
+- [x] **PKG-01**: Threadline defines an explicit `threadline_web` extraction-readiness scorecard based on objective triggers such as version-matrix pressure, release-cadence divergence, and repeated adopter glue.
+- [x] **PKG-02**: v1.19 closes with a documented package-boundary decision — expected default: stay in-tree for now — with README, guides, module-grouping/package contracts, and migration-path wording aligned to that decision.
 
 ## Future Requirements
 
@@ -55,14 +55,14 @@
 |-------------|-------|--------|
 | INTEG-01 | Phase 69 | Complete |
 | COMPAT-01 | Phase 69 | Complete |
-| COMPAT-02 | Phase 69 | Complete |
-| INTEG-02 | Phase 70 | Pending |
-| COMPAT-03 | Phase 70 | Pending |
-| ADOPT-09 | Phase 70 | Pending |
-| INTEG-03 | Phase 71 | Pending |
-| ADOPT-08 | Phase 71 | Pending |
-| PKG-01 | Phase 72 | Pending |
-| PKG-02 | Phase 72 | Pending |
+| COMPAT-02 | Phase 73 | Complete |
+| INTEG-02 | Phase 70 | Complete |
+| COMPAT-03 | Phase 73 | Complete |
+| ADOPT-09 | Phase 73 | Complete |
+| INTEG-03 | Phase 73 | Complete |
+| ADOPT-08 | Phase 73 | Complete |
+| PKG-01 | Phase 74 | Complete |
+| PKG-02 | Phase 74 | Complete |
 
 **Coverage at roadmap open:**
 - v1.19 requirements: 10 total

.planning/ROADMAP.md

@@ -4,8 +4,8 @@
 
 ### v1.19 — Integration Breadth
 
-**Status:** In progress
-**Phases:** 69-72 (continuing from v1.18's last phase, no `--reset-phase-numbers`)
+**Status:** Gap closure in progress
+**Phases:** 69-74 (continuing from v1.18's last phase, no `--reset-phase-numbers`)
 **Granularity:** coarse (per `.planning/config.json`)
 **Coverage:** 10/10 v1.19 requirements mapped
 
@@ -14,9 +14,11 @@
 #### Phases
 
 - [x] **Phase 69: Integration Contracts & Support Matrix** — Freeze the reusable adapter contract, define the named support matrix, and wire verification/CI expectations so Threadline only claims combinations the repo actually proves
-- [ ] **Phase 70: Sigra/Phoenix Reference Integration Refresh** — Refresh the current Sigra-backed reference path and example/docs/package wording to match the supported Phoenix/Sigra lines while keeping Sigra a soft dependency
-- [ ] **Phase 71: Mount Recipes & Access Tiers** — Ship canonical admin and support-read-only mount/runbook patterns for the operator surface, including router/live-session/auth-hook placement and CLI fallback parity
-- [ ] **Phase 72: Packaging Boundary Scorecard & Closeout** — Define objective `threadline_web` extraction triggers, align package/docs/module-group contracts, and close the milestone with an explicit stay-in-tree or extract-later decision
+- [x] **Phase 70: Sigra/Phoenix Reference Integration Refresh** — Refresh the current Sigra-backed reference path and example/docs/package wording to match the supported Phoenix/Sigra lines while keeping Sigra a soft dependency
+- [x] **Phase 71: Mount Recipes & Access Tiers** — Ship canonical admin and support-read-only mount/runbook patterns for the operator surface, including router/live-session/auth-hook placement and CLI fallback parity
+- [x] **Phase 72: Packaging Boundary Scorecard & Closeout** — Define objective `threadline_web` extraction triggers, align package/docs/module-group contracts, and close the milestone with an explicit stay-in-tree or extract-later decision
+- [x] **Phase 73: Authorization Contract Repair & Scoped Access Enforcement** — Repair the shared `authorize_fn` example, enforce documented support-read-only scope behavior across operator flows, and regenerate the missing Phase 71 proof artifacts
+- [x] **Phase 74: Nyquist Closeout & Requirement Tracking Repair** — Restore Phase 72 validation and summary bookkeeping so the packaging-closeout evidence meets the milestone's traceability standards
 
 #### Phase Details
 
@@ -47,6 +49,11 @@
 **Goal**: Adopters can copy one secure pattern for admin access and one secure pattern for support-read-only access without Threadline owning auth or roles.
 **Depends on**: Phase 69 (contract/matrix) and Phase 70 (reference-path refresh)
 **Requirements**: INTEG-03, ADOPT-08
+**Plans:** 3 plans
+Plans:
+- [x] `71-01-PLAN.md` — Canonical admin/support mount contract docs
+- [x] `71-02-PLAN.md` — Quickstart and runnable reference-path alignment
+- [x] `71-03-PLAN.md` — Contract and auth proof lock
 **Success Criteria**:
 1. The operator surface has a documented and tested host-owned access pattern for router pipeline checks, LiveView mount checks, and optional scoped investigation queries, without introducing a Threadline-owned user or role model.
 2. Threadline ships canonical mount recipes for secure admin and support-read-only installs, including router placement, `live_session` / mount-auth expectations, and first verification steps.
@@ -58,23 +65,53 @@
 **Goal**: Close v1.19 with an evidence-based package-boundary decision and aligned docs/package contracts instead of speculative extraction pressure.
 **Depends on**: Phases 69-71
 **Requirements**: PKG-01, PKG-02
+**Plans:** 2 plans
+Plans:
+- [x] `72-01-PLAN.md` — Scorecard & Closeout Docs
+- [x] `72-02-PLAN.md` — Module Grouping Alignment
 **Success Criteria**:
 1. Threadline defines an explicit `threadline_web` extraction-readiness scorecard based on objective triggers such as version-matrix pressure, release-cadence divergence, and repeated adopter glue.
 2. README, guides, module groups, release/package contracts, and migration-path wording all align to the closeout decision — expected default: stay in-tree for now.
 3. The milestone closes with a clear recorded answer to "why not split yet?" or, if evidence unexpectedly justifies it, a concrete follow-on extraction milestone instead of an ad-hoc package move.
 **UI hint**: no
 
+##### Phase 73: Authorization Contract Repair & Scoped Access Enforcement
+
+**Goal**: Restore one fail-closed authorization contract across docs, example code, and operator flows while making the documented support-read-only behavior real and provable.
+**Depends on**: Phases 69-72
+**Requirements**: COMPAT-02, COMPAT-03, ADOPT-09, INTEG-03, ADOPT-08
+**Gap Closure**: Closes the Phase 71 authorization drift, scoped-access enforcement gap, missing `71-VERIFICATION.md`, and unfinished `71-VALIDATION.md` flagged by the v1.19 audit.
+**Success Criteria**:
+1. The canonical example `authorize_fn` demonstrates the same host-owned policy contract across LiveView and export fallback, without relying on divergent transport-specific semantics.
+2. The documented support-read-only scope is either enforced consistently across timeline, actor, transaction, and export behavior or the docs are deliberately narrowed to the supported behavior with matching tests.
+3. Phase 71 closes with complete verification and validation artifacts, and the proof surface would fail fast if the shared authorization contract drifts again.
+**UI hint**: no
+
+##### Phase 74: Nyquist Closeout & Requirement Tracking Repair
+
+**Goal**: Finish the packaging-closeout evidence chain so v1.19 can be re-audited on complete Nyquist and requirement-tracking artifacts rather than partial bookkeeping.
+**Depends on**: Phase 73
+**Requirements**: PKG-01, PKG-02
+**Gap Closure**: Closes the missing `72-VALIDATION.md` artifact and incomplete Phase 72 requirement-tracking summaries flagged by the v1.19 audit.
+**Success Criteria**:
+1. Phase 72 has a complete validation artifact that records the final packaging-boundary proof and marks Nyquist closeout status explicitly.
+2. Phase 72 summaries and requirement traceability carry the expected requirement-tracking metadata so milestone evidence does not depend on ad hoc reconstruction.
+3. The active milestone planning state no longer claims closeout readiness until the repaired proof artifacts are present and a fresh audit passes.
+**UI hint**: no
+
 #### v1.19 Sequencing Rationale
 
 - **Phase 69 must come first** because Threadline should not broaden its host story before freezing the contract and compatibility language that every later phase depends on.
 - **Phase 70 follows immediately** because the current Sigra/Phoenix path is the highest-leverage real host integration already near the codebase; refreshing it against the contract is the fastest way to prove the breadth story with honest caveats.
 - **Phase 71 comes after the reference refresh** so mount recipes and access-tier runbooks are written from a proven path instead of speculative patterns.
 - **Phase 72 closes the milestone** because the `threadline_web` decision only becomes credible after the adapter contract, reference integration, and mount/runbook burden are visible in one milestone's worth of evidence.
+- **Phase 73 reopens the milestone closeout path** because the audit found that the Phase 71 auth contract and support-read-only story drifted from the live proof surface.
+- **Phase 74 finishes closeout bookkeeping last** because Nyquist and traceability repairs should capture the final post-fix state, not a stale pre-repair snapshot.
 - **The optional-deps posture remains a release gate throughout** — every breadth change must preserve compile-without-optional-deps and avoid introducing new hard runtime dependencies.
 
 ## Milestones
 
-- 📋 **v1.19 — Integration Breadth** — Phases 69-72 (active) — [requirements](REQUIREMENTS.md)
+- 📋 **v1.19 — Integration Breadth** — Phases 69-74 (gap closure in progress) — [requirements](REQUIREMENTS.md)
 - ✅ **v1.18 — Adoption and Policy Hardening** — Phases 64-68 (shipped 2026-05-07) — [requirements](milestones/v1.18-REQUIREMENTS.md) · [audit](milestones/v1.18-MILESTONE-AUDIT.md) · [archive](milestones/v1.18-ROADMAP.md)
 - ✅ **v1.17 — Operator Surface Foundation** — Phases 57-63 (shipped 2026-05-06) — [requirements](milestones/v1.17-REQUIREMENTS.md) · [archive](milestones/v1.17-ROADMAP.md)
 - ✅ **v1.16 — Investigation Table Stakes** — Phases 53-56 (shipped 2026-05-06) — [requirements](milestones/v1.16-REQUIREMENTS.md) · [archive](milestones/v1.16-ROADMAP.md)
@@ -88,8 +125,10 @@
 | Phase | Plans Complete | Status | Completed |
 |-------|----------------|--------|-----------|
 | 69. Integration Contracts & Support Matrix | 3/3 | Complete | 2026-05-07 |
-| 70. Sigra/Phoenix Reference Integration Refresh | 0/0 | Pending | — |
-| 71. Mount Recipes & Access Tiers | 0/0 | Pending | — |
-| 72. Packaging Boundary Scorecard & Closeout | 0/0 | Pending | — |
+| 70. Sigra/Phoenix Reference Integration Refresh | 3/3 | Complete | 2026-05-08 |
+| 71. Mount Recipes & Access Tiers | 3/3 | Complete | 2026-05-08 |
+| 72. Packaging Boundary Scorecard & Closeout | 2/2 | Complete | 2026-05-08 |
+| 73. Authorization Contract Repair & Scoped Access Enforcement | 3/3 | Complete | 2026-05-08 |
+| 74. Nyquist Closeout & Requirement Tracking Repair | 2/2 | Complete | 2026-05-08 |
 
 See `.planning/MILESTONE-ARC.md` for the forward-looking ranked recommendation order beyond the active milestone.