Repository navigation
Reconcile a lost first identity after a cold bridgeOS restart - #19
Closed
pablo-ur-fixer wants to merge 2 commits into
Closed
pablo-ur-fixer wants to merge 2 commits into
pablo-ur-fixer wants to merge 2 commits into
Conversation
The enrollment worker logged only the exception class names and an authorization reason, so a Catacomb persistence failure appeared as "classes=...>CatacombBridgeError reason=unclassified" and could not be told apart from the other bridge checks. Add a JSON "detail=" list with the messages of exceptions raised by t2_* modules along the cause chain. Those messages are fixed strings; foreign exceptions are dropped and the text is bounded to printable ASCII, so the line still carries no identifiers or raw bridge replies. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Z5eh7nvcZfcnceC8vskKu
A Linux-only first enrollment can confirm and stage user_<UID>.cat and then stop at the master.cat prepare request with nothing committed on the host (observed on MacBookPro16,3 / bridgeOS 24P6005). The journal stays outcome-unknown and blocks every further enrollment, and no recovery command accepts that shape: recover-outcome refused the staged prepare directory, and even after a cold bridgeOS restart returned the SEP to the pre-enrollment surface the E3 bootstrap rule rejected a zero Catacomb UUID as invalid. Admit the exact returned-to-baseline case. The E3 classifier accepts a bootstrap baseline whose live Catacomb is absent again when no identity remains and nothing else changed. The journal forgets a witnessed identity on a no-change recovery only when its persistence failure left host commit impossible. recover-outcome discards the staged user file only once the fresh inventory already shows the empty baseline, because while bridgeOS is warm that file is the sole durable copy of the fingerprint. Everything else is still left for manual review. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Z5eh7nvcZfcnceC8vskKu
This was referenced Oct 31, 2026
Owner
|
Thanks for this. We're closing it as superseded, along with the rest of the stack: T2Touch is moving its Touch ID support into Omarchy itself. #17 has the details, the answers to your questions, and what we've recorded from these fixes for that work, with credit. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #18 (shares the CHANGELOG entry); only the second commit is new here.
Fixes the recovery gap described in #17.
A first enrollment on bridgeOS 24P6005 confirmed
user_<uid>.catand then stopped at themaster.catprepare with a bareCatacombBridgeError, leaving the journaloutcome-unknownwith the identity still in the SEP and nomaster.catever written to the host. No recovery command applied (recover-observedneeds the terminal stage and the same boot,recover-outcomeneeds an unchanged identity set,recover-localis compat-only), so enrollment was blocked for good.Because the master was never saved, the identity cannot survive a cold bridgeOS restart anyway. After one (shutdown plus 10 s power-button hold) the SEP is back at the bootstrap surface: no identities, Catacomb uuid/hash status 22, master state 1. This lets
recover-outcomeclose that journal as a no-change recovery:E3_RECOVERY_NO_CHANGE_RECONCILEDonly when the persistence failure lefthost_commit_possibleFalse; any other vanished identity still raises.t2-native-enroll: the stageduser_<uid>.catfrom an exact[[user, master], [biolockout]]plan that stopped at the master prepare is discarded only when the live inventory is already empty; warm surfaces keep the file and fail as before.Tests replay the real journal milestone sequence against a cold surface and the warm variants. Verified on the affected machine:
recover-outcomereturnedidentity_count 0, local_prepare_discarded true, and re-enrollment then succeeded. Docs: TROUBLESHOOTING section "First enrollment saved the user Catacomb but not the master".🤖 Generated with Claude Code
https://claude.ai/code/session_013Z5eh5T2UPSQnihyoB12TP