FLEX-WP-0035-T04 done: readback pin and lifecycle v2 live, verified from outside
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 735967@bnt-lap001
Assistant-Session: 5971967f-77f8-4ced-9e02-c6ef67040ffc
This commit is contained in:
tegwick 2026-10-10 13:09:42 +02:00
parent 82aa2721e0
commit b9836264a9

View file

@ -158,10 +158,8 @@ readback over the shipped files. The live lifecycle pin still runs v1 (image
```task
id: FLEX-WP-0035-T04
status: wait
needs_human: true
status: done
depends_on: [FLEX-WP-0035-T05]
blocking_reason: "Founder go given 2026-10-10; repo side done (bb14ec6). The helm rollout must be run by the operator."
priority: medium
state_hub_task_id: "82a8a7e6-54e9-5262-a271-24ce2f161362"
```
@ -184,5 +182,12 @@ pin moves to `e8c57c18` (`main-b5da745`, v2). Rollback target is `bdac62bc`.
`TestReadbackPinMatchesParticipantPins` checks that the readback pin uses the same
image and package path as each participant's own pin. Rollout order: the lifecycle
pin, then the readback pin.
2026-10-10 done. The founder ran both helm upgrades: the lifecycle pin is at
revision 2 and `flex-auth-application-readback` at revision 1, both on `e8c57c18`.
Verified: both Ready, `/healthz` 200 on both, the readback routes return 401
without a token, `/v1/check` returns 404 on the readback pin, anonymous lifecycle
`/v1/check` returns 401, and ingress admits only `user-engine/user-engine`.
user-engine's live check with its own token is still to come.
The pin ships with the image that contains `serve-readback`. Hand user-engine
the evidence that unblocks `USER-WP-0026-T03`.