feat: 불확정 모델 호출의 명시적 오프라인 복구 - #65
Merged
Merged
Conversation
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
Expose the existing
AgentLoop::abandon_model_callsafely through an offline public CLI command. No Core, protocol, SQLite schema, dependency, default resume, or possible-send budget changes.Abandoned/RecoveryDiscardedsettlement using Core.Verification
recover; implemented public CLI suite: 10 passed (four new recovery tests).cargo test --workspace --locked: PASS using an isolated tmpfs test directory and fixed debug binary.cargo fmt --all -- --check: PASS.cargo clippy --workspace --all-targets -- -D warnings: PASS.cargo run --locked --quiet -p xgeny-cli -- protocol check: PASS (9 schemas, 28 fixtures, 26 semantic checks).cargo build --workspace --release --locked: PASS (Rust 1.98.0, Linux x86_64).One earlier full-suite attempt overlapped a debug rebuild and failed the executable-material integrity test; the final fixed-binary run passed it unchanged. No guard or timeout was weakened.
Limits / rollout
No live model call, ML training, production rollout or actual failed-project continuation in this PR. macOS/Windows and remote PR CI remain separate gates. Discard does not prove provider non-delivery/non-billing. External harnesses must retain the original workspace and record scoped recovery authority before integrating this command; it must not become an unconditional timeout retry handler.