Summary

Fix gateway /kanban create auto-subscribe when the command uses the global --board flag.

Before this change, a command like:

/kanban --board projx create "hello" --assignee alice

would create the task on projx, but the gateway would fail to auto-subscribe the originating chat to task notifications. The handler only detected create when it was the first token, and the follow-up subscription write did not carry the explicit board through to the DB connection.

Root cause

GatewayRunner._handle_kanban_command() used a naive first-token check:

• text.split(None, 1)[:1] == ["create"]

That breaks as soon as --board appears before the subcommand.

The auto-subscribe path also opened a plain kanban connection without the explicit board override, so even if create detection had succeeded, the subscription write could drift to the ambient/current board instead of the requested one.

Fix

• Parse the slash command tokens with shlex
• Skip the global --board flag when determining the actual subcommand
• Capture the requested board slug and use it when opening the DB connection for the auto-subscribe write

This keeps the patch local to the gateway handler and avoids broader parser refactors.

Tests

Added a regression test covering:

• /kanban --board projx create ... from the gateway surface
• task creation on the named board
• auto-subscription stored on that same board
• no subscription leak into default

Test run:

• python -m pytest -o "addopts=" tests/hermes_cli/test_kanban_notify.py -q