Skip to content

Serialize Supervisor Player lifecycle operations - #7

Merged
ChenlizheMe merged 2 commits into
mainfrom
lizhechen/player-lifecycle-serialization
Oct 20, 2026
Merged

ChenlizheMe merged 2 commits into
mainfrom
lizhechen/player-lifecycle-serialization

Conversation

@ChenlizheMe

Copy link
Copy Markdown
Collaborator

Concurrent Player launch/stop requests can race on the same Supervisor and start duplicate processes. Serialize operations for each Supervisor owner, synchronize creation in the local registry, and close the parent's log handle once the child inherits it.

Validation: parent engine supervisor regressions passed on Windows (43 tests) and Linux (45 tests plus 7 subtests), including concurrent launch/stop coverage. No package version change.

MCP is user-directed local tooling. Remove the per-user credential, the bearer middleware and the stdio bridge that only existed to carry it; generated client configs point directly at http://127.0.0.1:<port>/mcp again, so existing direct-HTTP configurations keep working. The SDK DNS-rebinding guard (loopback Host allow-list, local-only Origin) stays. The default grant is '*'; projects can still narrow granted_capabilities. Transport contract bumped to 2 so authenticated owners from contract 1 are retired on hot reload.
@ChenlizheMe
ChenlizheMe merged commit c2e88f8 into main Oct 20, 2026
2 checks passed
@ChenlizheMe
ChenlizheMe deleted the lizhechen/player-lifecycle-serialization branch November 15, 2026 12:40
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