fix: skip full command suggestion when it contains separators

[roomote]

This PR fixes an issue in the CommandPatternSelector component where the full command was being suggested as a pattern even when it contained command separators (&&, ||, ;, |, &).

Problem

When a command like npm install && npm test was executed, the manage command permissions UI would suggest the entire command string as a pattern that could be allowed/denied. This was problematic because:

• It would allow/deny the entire chain of commands at once
• It goes against the principle of managing individual commands separately
• The command validation system already splits commands by separators for individual validation

Solution

Modified the CommandPatternSelector component to check if the command contains separators before adding it as the first pattern. If separators are detected, only the extracted individual command patterns are shown.

Changes

• Updated CommandPatternSelector.tsx to add separator detection logic
• Added comprehensive tests to verify the behavior with various separator types
• Existing functionality for commands without separators remains unchanged

Testing

• All existing tests pass
• Added new test cases specifically for commands with separators
• Verified linting and type checking pass

---

Important

CommandPatternSelector now skips suggesting full commands with separators as patterns, showing only individual commands instead.

• Behavior:
  • CommandPatternSelector now skips suggesting full commands with separators (&&, ||, ;, |, &) as patterns.
  • Only individual command patterns are shown if separators are present.
• Code Changes:
  • Updated CommandPatternSelector.tsx to include separator detection logic.
  • Adjusted logic to only add full command if no separators are present.
• Testing:
  • Added tests in CommandPatternSelector.spec.tsx for commands with and without separators.
  • Verified behavior with various separator types.

^{This description was created by for c2082fd. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

I reviewed my own code and found it surprisingly coherent. Must be a bug in the review system.

[roomote]

Is this regex pattern robust enough? It might miss edge cases with whitespace variations like npm install &&npm test (no space before operator). The command-validation module might handle these cases differently.

Also, since command separators are used in multiple places (I see similar patterns in command-validation.ts), would it make sense to extract this as a shared constant to ensure consistency?

[roomote]

Consider enhancing this comment to explicitly list all the separators being checked: &&, ||, ;, |, &. This would make it immediately clear what patterns trigger the separator detection.

[roomote]

Great test coverage for the main scenarios! Consider adding a few edge case tests:

• Commands with separators but no extracted patterns
• Commands with multiple consecutive separators (e.g., cmd1 && || cmd2)
• Commands with separators at the beginning or end (e.g., && cmd or cmd &&)

These edge cases might not be common, but they could help ensure the component behaves predictably in all situations.