amadan
Record successful Keymail binary rollback rehearsal
1 file changed,
+24
−0
implementation/overnight-2026-09-07.md+24 −0
No CI script — run details
CI log
amadan: no CI script — add an executable .amadan/ci or a `ci` target to the Makefile
diff --git a/implementation/overnight-2026-09-07.md b/implementation/overnight-2026-09-07.md| index f07e378..c751ad2 100644 |
| --- a/implementation/overnight-2026-09-07.md |
| +++ b/implementation/overnight-2026-09-07.md |
| @@ -481,3 +481,27 @@ Full review is retained there and posted to suite discussion 5. |
| main and first implementation slice started under original ownership. Root |
| recorded native clients as following web delivery and depending on Home |
| assertions. Web callback scope remains unchanged; media completion unproven. |
| + |
| +## Checkpoint at 00:54 Dublin, 2026-09-08 |
| + |
| +- Keymail actual old/new/old/new canary rehearsal passed all four phases. |
| + Old45c1a68 PID1865284 created browser-held keys, two credentials and a signed |
| + encrypted draft. Newdbee45c PID1866193 revoked target204/401 while preserving |
| + owner access, keys and ciphertext. Rollback45c1a68 PID1866285 still rejected |
| + target401 and created a third legacy credential. Re-upgraded dbee45c PID1866319 |
| + backfilled and revoked third204/401, preserving owner ID and creation time. |
| + Every executable transition verified actual mapped hash, configured/open |
| + database identity, stopped old writer and unchanged data directory. |
| +- Committed WebKit gate passed all four pages after every deployment; private |
| + driver also passed each phase. Credentials/JWKs stayed in private0600 files, |
| + with encrypted claim transfer through SSM. No email sent or database reset. |
| + SSM tunnel is closed. Session canary remains final candidate for review; |
| + no production promotion, no cleanup or backup/restore proof claimed. |
| + Sanitized evidence and exact driver source in /tmp/keymail-device-rollback-review |
| + are hash-guarded inputs to the queued full backend Fable review. |
| +- Keymail OAuth audit57cc3cc adds real relay/PKCE/profile evidence preserving |
| + attested primary identity despite alias/foreign/unserved login hints. Current |
| + alias policy and custom-domain-primary support are distinct. Existing owner |
| + branch5a8862c already implements homeHost/composite mailbox IDs; no duplicate |
| + OAuth patch or invented alias-to-primary policy. Issue4 records integration |
| + prerequisites and missing final review evidence for that existing branch. |