check-issue-refs: blanket-ban tracker tags in markdown too, no exceptions
This commit is contained in:
parent
786ab304d6
commit
e1e913015d
24 changed files with 81 additions and 89 deletions
|
|
@ -222,7 +222,7 @@ operator-driven `hivectl choom` session — which passes neither `--tools`
|
|||
nor `--allowedTools` — gets claude's built-in synchronous `Bash` tool
|
||||
(inline, human-approved). That sidesteps the async `mcp__bash__run`
|
||||
completion wake landing in the wrong session (the harness inbox) for a
|
||||
choom-started task (#2356); `choom` is an operator (root) action, so
|
||||
choom-started task (`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/2356`); `choom` is an operator (root) action, so
|
||||
built-in shell there stays within the existing trust boundary. The bash MCP server
|
||||
(`run` / `status` / `kill`) uses `allowedTools = ["*"]` so all
|
||||
`mcp__bash__*` tools are always available regardless of tool groups.
|
||||
|
|
|
|||
Loading…
Reference in a new issue