chore(ai): forbid Agent/Task/Workflow fan-out tools in .claude settings-template deny (#13698) (#13699)

* chore(ai): forbid Agent/Task/Workflow fan-out tools in .claude settings-template deny (#13698)

Adds Agent/Task/Workflow to permissions.deny + an autoMode.hard_deny NL rule (mirroring the gh-pr-merge dual-guard) so the fan-out forbiddance propagates to every bootstrapped worktree/repo via template hydration. Fan-out spins fresh full-context agents — 100k to millions of tokens for zero value over the V-B-A tools (jq/grep/Read) — negative-ROI, drains the weekly limit. Operator-directed (@tobiu, 2026-06-21).

* chore(ai): name the correct V-B-A tools in the fan-out hard_deny (#13698)

The hard_deny entry mislabeled jq/grep/Read/Bash as THE V-B-A tools. The CORE V-B-A is ask_knowledge_base (the Knowledge Base) + /memory-mining (the Memory Core); neural-link verifies run-time state; jq/Read/grep are the file / use-case layer. Operator correction 2026-06-21.

---------

Co-authored-by: tobiu <tobiasuhlig78@gmail.com>

Author: neo-opus-ada

.claude/settings.template.json

@@ -6,7 +6,10 @@
       "mcp__neo-mjs-knowledge-base__*"
     ],
     "deny": [
-      "Bash(gh pr merge *)"
+      "Bash(gh pr merge *)",
+      "Agent",
+      "Task",
+      "Workflow"
     ]
   },
   "autoMode": {
@@ -26,7 +29,8 @@
       "$defaults",
       "Never run `gh pr merge` or any other pull-request-merge command. Merging is reserved for the human operator (AGENTS.md critical gate #1); no approval signal ('LGTM', 'approved', 'ready to merge') authorizes an agent to merge.",
       "Never push or commit directly to the `main` or `dev` branches. Always branch and open a pull request targeting `dev` (AGENTS.md critical gates #3 and #8). The release pipeline is the only sanctioned exception.",
-      "Never write a client, customer, or partner name — or private business strategy — into any public-facing artifact: public-repo issues, pull requests, discussions, docs, or comments (AGENTS.md critical gate #9)."
+      "Never write a client, customer, or partner name — or private business strategy — into any public-facing artifact: public-repo issues, pull requests, discussions, docs, or comments (AGENTS.md critical gate #9).",
+      "Never spawn subagents or run multi-agent workflows (the Agent / Task / Workflow fan-out tools). Each spawned agent is a fresh full context that re-reads everything — 100k to millions of tokens for zero value. Use the V-B-A tools instead — the CORE two are `ask_knowledge_base` (the Knowledge Base) and `/memory-mining` (the Memory Core); verify run-time state with the neural-link tools, and read files / large saved tool-results with `jq`/`Read`/`grep`. Fan-out is negative-ROI and drains the weekly limit."
     ]
   },
   "hooks": {