Restore CPU headroom for identity credential renewal

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a09cbb-87c6-7900-a145-4ce53ba9f1a6
This commit is contained in:
tegwick 2026-09-14 03:46:27 +02:00
parent 65c83dedbf
commit 854affd2ef
3 changed files with 60 additions and 1 deletions

View file

@ -825,3 +825,15 @@ Repeatable contained helper: key-cape/tools/register-informed-decision.py
(default preflight; --apply mutates only a missing exact registration).
Human callback/MFA/token proof and T03 approval entries remain pending. The
previous ready check established service health, not browser login acceptance.
### Credential-renewal scheduling recovery — 2026-09-14
KeyCape returned 503 after repeated 10m factor-renewer Jobs could not schedule
at full cluster CPU requests. The reviewed service used 1m; lowered its request
from 20m to 5m, retaining the 500m limit and memory settings. The next scheduled
renewal completed, self-revoked, and propagated through ESO to KeyCape; all four
readiness checks and both OpenBao reader callback routes passed. Renderer tests:
14 passed. Receipt: docs/evidence/2026-09-14-keycape-renewal-capacity-recovery.json.
Recurring-job scheduling headroom remains with CUST-WP-0071-T01. Human reviews
remain confirmed; service restart does not require their repetition.