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

Verify factor identity again after recovery mutation
All checks were successful
Authentication acceptance / acceptance (push) Successful in 1m6s
Details
Authentication acceptance / provider-contract (push) Successful in 12s
Details

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:30:23 +02:00
parent 3b7df9047e
commit 4d893ed3c2
3 changed files with 10 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
workplans/KEY-WP-0036-platform-factor-recovery.md
View file

@ -29,7 +29,7 @@ state_hub_task_id: "f3287544-8412-5b1f-9d16-9f7b9e895ceb"
requires an operator verification attestation and matching metadata version,
disables one factor with a row lock, requires pre-mutation audit durability,
reads back state, records completion and reconciles retries. Reject changed or
replaced factors and reference conflicts. Eight isolated unit tests pass.
replaced factors and reference conflicts. Nine isolated unit tests pass, including replacement between disable and readback.
The installed-provider Job provider-recovery-contract-02 passed real database
and audit persistence, disable/readback and replay assertions in an isolated
fixture. Acceptance CI includes both suites. No real user's factor was changed.