coulomb/key-cape
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Retain provider acceptance CI and synchronized assurance task binding

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a092fe-13b1-7f12-ac74-7d258af4d79c
This commit is contained in:
tegwick 2026-09-13 17:06:32 +02:00
parent 7f3a6da042
commit 502a2d5c56
2 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/enrollment-assurance-release-2026-09-13.md
View file

@ -33,3 +33,9 @@ or production self-service enrollment policy was changed by this release. The
remaining T02/T03 work is actual self-service browser acceptance, scoped optional
client activation and privileged portal assurance. P04 audited lost-factor
recovery is still separate. Isolated provider tests do not claim those complete.
Final CI evidence: [run 56](https://forgejo.coulomb.social/coulomb/key-cape/actions/runs/56)
succeeded for ecca6cb, including both the full Go suite and the isolated provider
contract job. The final deployment is Ready 1/1; health, readiness, discovery and
JWKS endpoints each returned HTTP 200. Workplan synchronization completed with
zero failures; the generated T05 task binding is retained in its source record.

1
workplans/KEY-WP-0035-optional-mfa.md
View file

@ -83,6 +83,7 @@ Consumer source 632b1f1 deployed and Ready 1/1; CI, four provider HTTP checks an
id: KEY-WP-0035-T05
status: done
priority: high
state_hub_task_id: "94f579d1-a7af-564c-ab0c-ae76fce343aa"
```
Live provider source inspection found active tokens can remain in verification