Harden production authorization and service auth

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0217e-8c4c-7383-be6b-f50a6e485306

README.md

@@ -57,6 +57,7 @@ SECRETS_ENGINE_HUB_URL="" bash scripts/demo-e2e.sh
 - ops-warden routing contract: [docs/ops-warden-routing-contract.md](docs/ops-warden-routing-contract.md)
 - Hardening backlog (exit bootstrap mode): [docs/hardening-backlog.md](docs/hardening-backlog.md)
 - Existing-lane catalog admission: [docs/catalog-admission.md](docs/catalog-admission.md)
+- KeyCape service-auth consumer boundary: [docs/service-auth.md](docs/service-auth.md)
 
 The implementation is a Python package (`src/secrets_engine/`). OpenBao is
 reached only through the `bao` CLI adapter (`openbao.py`); the rest of the code
@@ -68,7 +69,8 @@ speaks in lanes and guarded plans.
   workplans, or normal logs.
 - OpenBao is the backend custody and audit authority.
 - Build, test, and production have separate policy boundaries.
-- Production actions require approved decisions except explicit break-glass
-  flows.
+- Production live actions fail closed until the durable State Hub
+  action-authorization endpoint is available; local approval mirrors are
+  throwaway-demo material only.
 - Temporary bootstrap OpenBao credentials must live outside repos, use mode
   0600, be revocable, and be removed after narrower auth is working.