Repository navigation
Complete managed browser workflows with native human handoff - #212
Merged
Merged
Conversation
Publish prepared P220 consumer implementation and P223 bounded recovery, disposable routing and isolated diagnostics repairs. Refs #202.
… handoffs Preserve native ownership and positive-absence fencing; qualify the isolated installed workflow and retain failed observations.
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.
Normal browser work can use an existing, managed persistent or disposable profile, hand the same browser to a person through native Remote View, and continue automation. Ordinary commands now recover a retained browser after physical idle cleanup before selecting its new physical tab. Closed and expired handoffs return actionable HTTP 410 explanations instead of a generic temporary outage. Explicit profile selection survives the shared-host boundary; unprofiled work admits disposable sessions. Isolated install diagnostics inspect the selected binary, launcher, dashboard and native provider inventory.
References #202 and P223 revision 6. Provider dependency CochranResearchGroup/remote-view#310 is merged. Native Remote View retains viewer and authentication ownership. No production publication, release, authentication change or additional viewer-grant ceremony.
Validation: final consumer tests pass all 29 cases, including restart/idle recovery and refusal before launch when absence is unproven. Format, strict workspace Clippy, client contracts, dashboard type/behavior checks, docs build and policy/archive checks pass. Earlier batch coverage retains the comprehensive run's corrected status-fixture failure alongside all 599 passing service tests; Service Model coverage includes the other 326 tests and corrected recovery case. The previous unchanged routing/core surface passed 1,111 tests with one ignored. All 864 recorded compile inputs match commit
e496cd8e76fc08ff54a148f28c77c4109f8e0448.Installed p221 evidence binds binary SHA256
42b6b0df8ac69165544895148316ace96e526853a8ea7c7f8b273ac21e71efa0: install doctor, three disposable launch/read/close/residue cycles, ordinary cold recovery without opening the handoff first, visible native keyboard input and continued automation in the same new PID. Seven checked peer process identities are unchanged. The first cold read refused unproven absence without launching; fresh full census and the OS guard test passed before one successful retry. That refusal and its unproven transient cause remain recorded. The original link expired during the pause and remains HTTP 410; application authentication is unverified at its interstitial. Earlier disposable native viewing and exact stop/peer-preserving cleanup remain qualified within their recorded scope.Prepared P211 source follows the frozen P220/P219 file-disposition audit; older draft #191 remains intact. P207 tab-refresh behavior is outside this candidate and draft #184 remains intact. RUNBOOK owns current acceptance limits; source merge does not itself close P223.