fix: constrain profile names to one namespace - #18
Merged
Merged
Conversation
This was referenced Sep 20, 2026
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
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.
Core DataConfig accepted path separators and traversal components in profile names, so derived data_dir and storage_dir could escape the intended data/profiles/ namespace. This adds the same safe profile-name contract already enforced by the MCP adapter and enables assignment validation so post-construction profile changes cannot bypass it. Regression coverage rejects traversal, separators, dot names, empty names, and invalid assignment. Validation: 14 config tests passed; no legacy code, storage schema, or API response changes. Targets main.