fix: harden Cursor sessions and retained work ownership - #1
Merged
Merged
Conversation
showxu
marked this pull request as ready for review
September 29, 2026 05:38
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
1 participant
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.
Cursor sessions preserve native errors, bound protocol input and output, and retain host-visible ownership through background prompts, interactive requests and confirmed process cleanup. Continuations keep their original acquisition references; safe release cannot evict unresolved work. The patch candidate is 0.1.1; published 0.1.0 remains immutable.
Release workflows use the pinned central catalog notification action; configuring receiver-scoped dispatch authority remains a deployment prerequisite.
Validation: 68 Python tests, native version/help verification, Python 3.13/3.14 CI and byte-identical local/CI archives. The exact archive passes isolated Computer MCP 1.3.0 build40 fixture checks for permissions, retained provider work, cleanup and wrong-host-version rejection. The validator requires an explicit reviewed host version.
Live ACP initialization passed, but existing-auth authentication timed out before any model prompt. Authenticated model acceptance and public patch delivery remain open; no production App was replaced or activated.