Preserve shared native names and session settings across hosts - #357
Merged
Merged
Conversation
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.
Web-created session names must remain visible in CLI listing and resume, and a later runtime save must not restore an old name after another host renames it. Use Foundation's native metadata field updates and canonical naming API; preserve unknown metadata and provider context at checkpoints. Bind the native session settings scope before resolving resume configuration and applying configurator settings.
Foundation #401 is merged. The dependency tracks
main; the lockfile records the tested resolved revision52dec7e276db62f720448c8e2ec176b9cbffde2d. Names and descriptions remain inmetadata.json, and generic settings merging is shared with Unified. Existing standalone execution ownership is unchanged.Validation: focused native rename/checkpoint tests pass. A separately installed CLI/Unified integration environment verifies web creation, CLI JSON listing, native resume reads, CLI rename, subsequent checkpoints, and Unified refresh while retaining transcript and event bytes. The same installed apps resolve all four settings scopes identically. Full local CLI suite: 2,392 passed, 45 skipped, 13 integration tests deselected, one expected failure; the two added native metadata regressions also pass. All eight GitHub Linux/macOS/Windows and POSIX integration checks pass, plus CLA.
Updated hosts cooperate through the short metadata lock; older running processes retain their prior save behavior until restarted. Web-only pending operations and private runtime-control files are not part of this change.