fix(cli): follow the selected release on foreground restart #288
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/restart-selected-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #287: Node resolves the launcher's module URL to its original immutable release. Deriving cli.js from that URL would pin later /restart calls to the old release after a current-directory selector is updated. Resolve executable shims while preserving symlinked parent directories, then reuse that selected entrypoint path for each new child. No writers overlap.
Regression test creates old/new releases, starts through an executable shim/current selector, switches current before exit 75, and proves the replacement runs new rather than old. Typecheck and full final suite 1560/1560 passed, no skips; focused subprocess suite 6/6. One initial test launch failed before execution due to a transient network timeout downloading locked plugin sources; the complete rerun passed.
Actual model-protocol smoke test against the local configured gateway also proves the #287 behavior: initial Sonnet HTTP 400; resource-only reload does not read the model config; explicit model reload fixes the SAME session/model to return valid JSON through openai-completions. No productive tools or external state changes.