Skip to content

fix: preserve proxy recovery after rollback failure - #58

Merged
kev1n77 merged 1 commit into
mainfrom
codex/proxy-rollback-fault-injection
Jul 18, 2026
Merged

kev1n77 merged 1 commit into
mainfrom
codex/proxy-rollback-fault-injection

Conversation

@kev1n77

@kev1n77 kev1n77 commented Jul 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • keep the recovery journal armed when proxy apply and synchronous rollback both fail
  • trigger and await the independent watchdog recovery path instead of deleting recovery evidence
  • preserve the journal and return all three errors if watchdog recovery also fails
  • add PAC-state fault injection through a real watchdog child process
  • update TST-003 progress

Verification

  • cargo test -p codeischeap-proxy-recovery --all-targets (8 passed, 1 ignored real WinINet test)
  • cargo clippy -p codeischeap-proxy-recovery --all-targets -- -D warnings
  • cargo fmt --all -- --check
  • git diff --check

Local environment note

Full workspace test and Clippy builds are blocked locally because vendored OpenSSL cannot find Perl; CI provides the authoritative cross-platform workspace checks.

@kev1n77
kev1n77 merged commit 09d03b9 into main Jul 18, 2026
9 checks passed
@kev1n77
kev1n77 deleted the codex/proxy-rollback-fault-injection branch July 18, 2026 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant