Record live image cdec9dd7 with the sign-in diagnosis page (KEY-WP-0041-T02).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1041694@bnt-lap001
Assistant-Session: 7af0bb68-ac4a-4ce3-8639-24ddd84c0b52
This commit is contained in:
tegwick 2026-10-15 00:09:11 +02:00
parent 8c6c071ad9
commit 3b8d69546b
2 changed files with 18 additions and 9 deletions

View file

@ -186,15 +186,19 @@ workload or customer data, any sign the transcript left the workstation, or a
planned key rotation. The same workplan removes the problem class by giving
agents a cluster identity that cannot read these objects at all.
## Current image (2026-09-26)
## Current image (2026-10-15)
The live issuer is
`sha256:82f1e5ac481e4f963dbd4b05256aee75412c9e9b465d31c9356f5d17f26a6897`,
source `13afaa9`. The sign-out confirmation uses the NetKingdom Identity
page design. Recorded as `ADMINISTER @ realm:kubernetes/railiance01`,
`activation=APPROVED`. The patch replaced only the image. Strategy stayed
Recreate and requests stayed 25m/32Mi. Rollback is
`sha256:8dc35801d1d2b0905a43530c40b1fed0107fc179141fe5b2b614c52c01714fc9`.
`forgejo.coulomb.social/coulomb/key-cape@sha256:cdec9dd7c515f7e0a6169fc3fa560ee2cc47bf40d899755dec808c362f5ce010`,
source `8c6c071`. Over the previous live source `1164f65` it adds the
duplicate-clientId startup check (`c528daa`), the lost-authenticator help link
(`205a1c0`), and the opt-in sign-in diagnosis page with `uid`/`assurance` on
`auth_success` (`af3b1b0`). Founder-run on 2026-10-15: `keycape check-config`
on the live config was valid (13 clients, no errors), `kubectl diff` showed only
the image, server dry-run passed, Recreate rollout succeeded, pod ready with 0
restarts and discovery answering 200. The owner manifest is
`net-kingdom/sso-mfa/k8s/keycape/deployment.yaml`. Rollback is
`sha256:6f79a2af1c695d39480173fad013facd84d21e7732860366af519302a2c496b8`.
## Fail-closed startup changes from source 11ce29a