feat: escalate chat approvals through inbox

packages/casan-control-panel/README.md

@@ -53,10 +53,11 @@ Approval inbox / HITL:
 - `GET /api/v1/approvals?status=pending` — list proposals and oversight tail.
 - `POST /api/v1/approvals/submit` — submit a governed proposal; delegation is resolved
   by harness `approval-inbox.py` + `delegation-policy.yaml`.
-- `POST /api/v1/approvals/decide` — approve/reject with SoD and reason; approved
+- `POST /api/v1/approvals/decide` — approve/reject with SoD and reason; strict mode
+  or supplied `approvalJwt` is verified by harness `approval-verify.sh`; approved
   settings proposals apply through `control-plane-settings.py`.
 
-Governed Chat (Plan-18 MVP-0/1 + MVP-2 Track 4, Operator Track 5/6, and Track 8.1-8.3):
+Governed Chat (Plan-18 MVP-0/1 + MVP-2 Track 4, Operator Track 5/6, and Track 8.1-8.4):
 
 - `POST /api/v1/chat/ask` — Ask CASAN endpoint. The API only wraps harness
   `chat-turn.py`; router verdicts, H4 input/output scan, action-gate decisions,
@@ -73,12 +74,15 @@ Governed Chat (Plan-18 MVP-0/1 + MVP-2 Track 4, Operator Track 5/6, and Track 8.
   `chat-replay.py`.
 - `GET /api/v1/command` — includes the `chat_loop` Command Center widget backed
   by chat audit/replay evidence, loop ticker rows, and token budget gauge.
+- Delegation escalation returns `ESCALATED` and creates a pending `chat.escalate`
+  proposal in the approval inbox.
 - `/chat` UI shows actor/role scope, `mode/risk/decision` badges, certified answer,
   evidence sources, registered operator actions, agent binding, loop certification,
   action-gate status, router details, and audit hash. Side-effect requests outside
   registered actions return governed `BLOCK` or `NOT_SUPPORTED` responses; operator
   side effects are held until the loop draft is certified.
 - `/command` UI renders the Chat/Loop widget in the existing evidence drawer flow.
+- `/approvals` UI accepts an approval JWT for strict reviewer identity checks.
 
 FinOps/SLO: