fix(rules): handle retired worktrees and pasted command output - #134
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
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.
What changed, and why
Historical worktrees that no longer exist caused standing-rule commands to
report a consented project as unconsented. Resolve those stored paths through
their existing physical ancestor while retaining denial and symlink checks.
Pasted multiline
elepha:output could also trigger an unwanted help injection.Ignore it before opening the database and keep internal wrapper markers out of
verbatim replies. Both user-visible fixes have patch changesets.
How it was verified
git diff --checkpassed.npm testand reported a pass.returns
not_command.receipts. The user also confirmed Claude behavior; a matching local
SessionStart receipt was not captured.
Before merging