fix: warn when a :* tool rule follows a slash or equals sign

[rmnvg]

Summary

Refs #1823.

In Claude Code, a :* suffix means the same as a trailing *, so Bash(prefix:*) only matches when the command continues with a space (permissions docs). #1823 used this rule:

Bash(gh api --method PATCH repos/<owner>/<repo>/issues/comments/:*)

The command it was meant to allow puts the comment ID directly after the slash (.../comments/12345), so the rule never matches and the edit is denied every time. The create path (gh pr comment 5 ...) has a space after the prefix, which is why it worked. The action passes the rule through unchanged, so parsing isn't the problem. The rule is just easy to get wrong, and nothing tells you.

Changes

• parseSdkOptions logs core.warning for any allowedTools / disallowedTools rule ending in /:* or =:*, and suggests the prefix* form. The rule is still passed through unchanged, so this can't break an existing workflow.
• The check only covers / and =, which are almost always followed directly by more text. Rules like Bash(git -C .:*) or Bash(gh pr comment:*) can legitimately be followed by a space, so they don't warn.
• Adds a short note to docs/configuration.md explaining the rule with the comment-ID example.

Testing

• 3 new tests in base-action/test/parse-sdk-options.test.ts: warns for /:* in allowedTools, warns for =:* in disallowedTools, no warning for the rule shapes used in the docs and examples.
• bun test (969 pass), bun run typecheck, bun run format:check all pass.

🤖 Generated with Claude Code