Refine %catalog context resolution: strict use(), optional list() path - #57
Merged
Merged
Conversation
use() now only accepts a whole, absolute path and never resolves it against the existing context (previously it accepted dot-optional/`../` relative paths like every other verb) — pointing context somewhere always means saying exactly where. list()'s own path is now optional (defaults to listing the current context itself), and every other single-path verb's bare path now stays absolute instead of getting silently appended to an existing context when it already starts with `catalog`, this deployment's one real root source — previously the only way to mix an absolute path into an already-`use()`d session was to clear context first. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Sep 18, 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.
Summary
use()now only accepts a whole, absolute path and never resolves it against the existing context (previously it accepted dot-optional/../relative paths like every other verb) — pointing context somewhere always means saying exactly where, with the same live existence check as before.list()'s ownpathis now optional — omitted (or""), it lists the current context itself, raisingCatalogSessionErrorif none is set.catalog(this deployment's one real root source) — previously the only way to mix a full absolute path into an already-use()d session was to clear context first.Test plan
pytest— 357 passedruff check/ruff format --check— clean on touched files🤖 Generated with Claude Code