Keep computer goals executable through scoped recovery and cleanup - #52
Closed
ChesterHsu wants to merge 13 commits into
Closed
ChesterHsu wants to merge 13 commits into
ChesterHsu wants to merge 13 commits into
Conversation
ChesterHsu
enabled auto-merge
September 6, 2026 02:58
auto-merge was automatically disabled
September 7, 2026 02:49
Pull request was closed
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.
AI Space could lose execution authority during goal correction, reuse another caller's browser, or mistake a redirected observation for an executed action. This preserves the nine runtime commits while consolidating caller-owned browser cleanup, trusted same-goal continuation and retained middleware state, unresolved-parameter refusal, canonical argument recovery, private audit metadata, Traditional Chinese action admission and workspace-scoped file permissions. No blanket privilege increase is introduced.
The scope/validation helpers are extracted without changing public Agent methods or the Core dispatch facade. Existing line budgets and monkeypatch contracts remain enforced. The SDK remains unreleased 0.20.1; its exact Core source dependency is reviewed separately in flytohub/flyto-core#88. No package, tag or deployment is published here.
Validation at 6759bf8:
Local verification is recorded separately: an initial full run had 4,371 passes, 17 skips and one missing Core API extra; that source semantic contract passed after installing the declared dev extras. One local rerun hit the tight connector-readiness timing fixture; both complete remote matrices include and pass that case, and no deadline was relaxed.
Live authenticated goal acceptance belongs to Flyto2 Cloud and is not replaced by these deterministic checks. Normal merge still requires the repository's independent approval.