[SYMPP-BE79] Stop managed backends after final MCP client - #623
Merged
Pimpmuckl merged 1 commit intoAug 17, 2026
Conversation
Summary: - remove the installed-artifact residency exception from Node and PowerShell last-detach cleanup - apply shutdown-on-idle uniformly and replace resident-PID assertions with zero-listener and PID-rotation proof - keep cold singleton, warm attach, and nested PowerShell coverage intact Rationale: - managed Symphony++ backends must exist only while MCP clients are attached, regardless of source or artifact runtime mode - the existing lease lock remains the shared owner for final cleanup Tests: - pwsh -NoProfile -ExecutionPolicy Bypass -File plugins/symphony-plus-plus-mcp/tests/launcher/run-launcher-tests.ps1 - make -C elixir all Co-authored-by: Codex <codex@openai.com>
Pimpmuckl
merged commit Aug 17, 2026
9c157b6
into
integration/mcp-first-caller-lifecycle
18 checks passed
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.
Context
Managed installed-artifact backends stayed resident after their final MCP client, so later client waves reused the old PID.
TL;DR
Stop every managed S++ backend after the final MCP client and cold-start a new PID for a later wave.
Summary
Alternatives
Test Plan
make -C elixir allmake -C elixir ci-fullwhen release/full validation is required (not required for this launcher-only slice)pwsh -NoProfile -ExecutionPolicy Bypass -File plugins/symphony-plus-plus-mcp/tests/launcher/run-launcher-tests.ps1rvw_fd3fbf60clean on exact head; simplification closure conforms