Summary

Read-only /operational-state admin panel shipped against a hardcoded stub endpoint. Pairs with CC#1's KR-P2-I-skeleton (R4.1 §9.1 state machine) and goes in ahead of the runtime wire-in so the UI is ready when KR-P2-I-integration lands.

Endpoint (kora_cli/web_server.py)

GET /api/operational-state — returns the v1 stub:

{
  "primary_state": "ready",
  "claim_permission": "normal",
  "degradation_reasons": [],
  "is_degraded": false,
  "transition_history": [{ "timestamp": "...", "from_state": "booting", "to_state": "ready", "trigger": "..." }],
  "valid_next_states": [{ "to_state": "active", "trigger": "..." }, ...],
  "stub": true
}

Enum value strings pinned verbatim to R4.1 §9.1:

• primary_state ∈ {booting, ready, active, paused, stopped}
• claim_permission ∈ {none, critical_only, normal}
• degradation_reason ∈ {cost, auth, dispatch, substrate, migration, operator, token_expiring, retry_ceiling}

No write-side endpoints — state mutations belong to kora_control (KR-P2-J), not this panel.

Frontend (web/)

• pages/OperationalStatePage.tsx — primary-state badge with tone per state, claim-permission pill, degradation chips with hover blurbs (rendered only when present), transition-history table, valid-next-states list. STUB banner renders only when stub: true so a real outage never gets masked as "stub data".
• lib/api.ts — typed enums + OperationalStateResponse so a future Python-side enum drift surfaces as a TS error.
• App.tsx — /operational-state route + nav entry (Activity icon) inserted between /sessions and /analytics per spec §3.

Flip-over plan

When KR-P2-I-integration lands, swap the get_operational_state body to project from the real OperationalState singleton and drop the stub: True field. Frontend continues to work unchanged; the stub banner disappears the moment the flag goes away.

Test plan

• tests/kora_cli/test_web_server_operational_state.py — 8/8 green, covers all five §5 scenarios + READY-exits guard + enum-subset guard
• test_web_server_{cron_profiles,host_header,mcp,gateway_identity}.py — 39/39 still green (regression sanity, 47 total in suite)
• npx tsc -b on web/ — clean
• npx vite build on web/ — clean
• §8 grep checks: STUB banner present, endpoint registered, zero write-side routes leaked
• Manual smoke: navigate to /operational-state, verify STUB banner renders, verify READY badge + transition row + three valid next-states list render

Dependency notes

• R4.1 §9.1 is the contract this stub is built against.
• KR-P2-I-skeleton (CC#1) lands the Python dataclass + enum + transition table. This PR's TypeScript enum value strings match §9.1 verbatim; if CC#1 deviates, we update here.
• KR-P2-I-integration (post-substrate-round Bucket C) flips the stub → real read.

🤖 Generated with Claude Code