Repository navigation
Display Wake controller notifications and model-readable intervention state #403
Description
Parent
What to build
Show clearly identifiable controller policy/action/reason/outcome notifications in modded Codex, expose model-readable state, and integrate the separately owned exact-TUI health capability without changing probe behavior.
Acceptance criteria
- Show clearly identifiable controller policy/action/reason/outcome notifications in modded Codex, expose model-readable state, and integrate the separately owned exact-TUI health capability without changing probe behavior.
- Demonstrate the stated end-to-end behavior through public operations and every capable CLI/API/MCP surface.
- Cover authorized success, stale/unsupported/unauthorized targets and relevant crash/reconnect or uncertain-effect cases.
- Record source/package evidence and preserve existing work, authority and cumulative accounting; production effects need separate authorization.
Existing upgrade reconciliation
Existing #390 exclusively owns exact-loop health implementation. This slice adds clear controller notifications/model-readable status and integrates its health capability without duplicating the native health work.
Delivery boundary
Use public-seam TDD and exact red/green receipts. Source, integration, installed disposable acceptance and production activation are distinct. No provider experiment, credential copying, shared restart, governor activation or resource renewal is implied.
Activity
ecochran76 commentedon Oct 30, 2026
Qualified source 607f1f7 on feat/controller-393-resumed. Evidence: docs/dev/evidence/plan0190/notices403-installed.json and docs/dev/notes/controller-notices403.md. All five installed frontdoors publish original caller-owned actions to actual owned native TUI; rendered text/model context confirmed. Broad grants and revoked tokens denied; lost acknowledgement reads original event without replay; stock unsupported explicit. Local 2 notice,10 runtime,6 health tests pass. No model turn, governor enrollment, health probe, resource renewal, shared restart or production activation; four startup network requests trapped locally. Hosted CI skipped per operator policy. Scheduling/deactivation consumer follows in #404.