Repository navigation
Conversation
added 2 commits
July 27, 2026 13:28
Distinguish unreadable config from empty values, block repairs with unknown starting state, record partial mutations, and roll back every post-change failure. Co-authored-by: Felirami <feli@arcabot.ai> Signed-off-by: Felirami <feli@arcabot.ai>
Co-authored-by: Felirami <feli@arcabot.ai> Signed-off-by: Felirami <feli@arcabot.ai>
felirami
marked this pull request as ready for review
July 27, 2026 14:15
added 5 commits
August 1, 2026 21:42
Signed-off-by: Cad from Arca <cad@arcabot.ai>
Signed-off-by: Cad from Arca <cad@arcabot.ai>
Signed-off-by: Cad from Arca <cad@arcabot.ai>
Signed-off-by: Cad from Arca <cad@arcabot.ai>
Signed-off-by: Cad from Arca <cad@arcabot.ai>
Merged
Owner
|
Superseded by merged release PR #26, which contains the final repair transaction-safety implementation and release evidence. Do not merge this branch separately. |
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.
Summary
This updates the repair-safety candidate with the remaining fail-closed execution boundaries found during release review.
status === 0null/undefinedfor fail-closed classificationSafety contract
A repair is reported as applied only after an unambiguous successful apply result and post-apply verification. Execution ambiguity is failure, not success. Rollback and result evidence remain bounded and do not expose generated token values.
Validation
Exact candidate head:
34360f6a92242e0feb808006882d509d12da65b2npm audit --omit=dev: 0 vulnerabilitiesb10aea25f19e1ca3fe278bc0a90688924d2d14a8709ec1f6fe007d3b82df0d0a0; cleanup and empty provider inventory were verifiedFresh independent exact-head static review: READY, no findings.
No deployment, merge, npm publication, GitHub release, or production mutation is part of this PR update.