flex-auth

Author	SHA1	Message	Date
tegwick	79582870c0	Pin flex-auth-tenant-engine to the nine-action policy image All checks were successful CI Smoke / container-smoke (push) Successful in 1s Details CI Smoke / host-smoke (push) Successful in 0s Details Build and Publish Container Image / build-and-push (push) Successful in 35s Details CI digest sha256:1bf060e6 (main-f304688) is live. Seven pre-existing actions still allow; guardrail.read/set match the FLEX-WP-0014 split. user-engine pin unchanged. Rollback target is sha256:9320df39.	2026-08-16 09:57:07 +02:00
tegwick	87f114f036	Restore flex-auth-tenant-engine to the seven-action policy image All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Build and Publish Container Image / build-and-push (push) Successful in 32s Details FLEX-WP-0013. Production had been rolled back to sha256:c25fc34a (four actions), so tenant.update / tenant.retire / tenant.reactivate denied unknown_action. Re-pin and apply the previously-live sha256:9320df39 image (`e9911eb`). Live probe after restore: all seven actions allow; misspelled action and unknown subject still deny. user-engine pin unchanged. TEN-WP-0006 guardrail actions not added.	2026-08-16 02:36:56 +02:00
tegwick	1d58f13eb8	Add Railiance staged-promotion overlay for flex-auth All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details FLEX-WP-0011 T01/T02: railiance.app.v1 contract, independently pinned Helm values for tenant-engine and user-engine, isolated canary cycle (deploy/observe/promote/rollback), and emergency kubectl path retained. T03 waits on the custodian drain-plan row.	2026-08-16 01:32:31 +02:00

3 commits