@event4u/agent-config 9.5.0 → 9.7.0

package/README.md

@@ -14,7 +14,7 @@
 
 **Every public claim in this README is machine-checked — [verify it yourself](docs/proof.md).** In a market that runs on unbacked headline numbers, this one binds each claim to resolvable evidence or fails its own build.
 
-**A deep library of skills, commands, and governed rules** — plus a capability router that loads the right skill on intent, and multi-agent orchestration with consensus review. The whole layer is compiled into 7+ host agents (Claude Code, Cursor, Augment, Cline, Windsurf, Copilot, Gemini) with **zero runtime daemon**.<!-- claim:no-runtime-daemon --> Six role-shaped entry paths sit on top, so any host becomes a reliable team member — without locking you to a single model or vendor.
+**A deep library of skills, commands and governed rules** — plus a capability router that loads the right skill on intent and multi-agent orchestration with consensus review. The whole layer is compiled into 7+ host agents (Claude Code, Cursor, Augment, Cline, Windsurf, Copilot, Gemini) with **zero runtime daemon**.<!-- claim:no-runtime-daemon --> Six role-shaped entry paths sit on top, so any host becomes a reliable team member — without locking you to a single model or vendor.
 
 ### What's different
 
@@ -27,13 +27,13 @@ It is both deep **and** disciplined — and honest about what it deliberately is
 
 **What it deliberately is *not*** — a content + governance layer, not a runtime: **no background daemon, no separate state database, no self-rewriting memory, no auto-build pipeline.** The host agent runs the loop; every learned change is human-reviewed; the same layer stays portable across tools. Capability without a process to babysit.
 
-> **Where this comes from (honest provenance).** The skills, rules, and personas
+> **Where this comes from (honest provenance).** The skills, rules and personas
 > are distilled from real production work on TypeScript and PHP codebases. The
 > governance mechanics are stack-agnostic, but the domain heuristics are richest
 > where they were forged — treat coverage on other stacks as promising, not
-> proven, and tell us where it falls short.
+> proven and tell us where it falls short.
 
-See exactly [what works on which host](docs/capability-matrix.md), or jump to [things you can do in a minute](docs/cookbook.md).
+See exactly [what works on which host](docs/capability-matrix.md) or jump to [things you can do in a minute](docs/cookbook.md).
 
 ### Pick your profile — six entry paths
 
@@ -100,14 +100,14 @@ is platform operation, not a user-work flow.)
 
 > **Creative Pack — cinematic AI video.** script → character-locked image → motion+audio prompt → provider render → stitched clip, with `AIV_DRYRUN=true` as the cost-safety default. A first-class capability inside the **content / creator** experience — no longer the package's headline. See [`/video:from-script`](.augment/commands/video/from-script.md).
 
-> **Legal Pack — not legal advice.** The EU/DE legal pack (contract/NDA/DPA review, triage) is a **research-and-drafting aid only** — it does not provide legal advice, does not replace a qualified lawyer, and must not be relied on for any concrete matter. It produces general information and general templates, never individual-case examination. Read [`LEGAL_NOTICE.md`](LEGAL_NOTICE.md) before use.
+> **Legal Pack — not legal advice.** The EU/DE legal pack (contract/NDA/DPA review, triage) is a **research-and-drafting aid only** — it does not provide legal advice, does not replace a qualified lawyer and must not be relied on for any concrete matter. It produces general information and general templates, never individual-case examination. Read [`LEGAL_NOTICE.md`](LEGAL_NOTICE.md) before use.
 
 > Full catalog — every skill, rule, command, guideline: [`docs/catalog.md`](docs/catalog.md). The headline is the **experience** (profile + packs) **and** the depth behind it.
 
 ## Use it in your project
 
 Run from a consumer repo — bootstrap via `npx`, the agent picks up
-your stack, and you ship work end-to-end. New install? Start with the
+your stack and you ship work end-to-end. New install? Start with the
 [Quickstart](#quickstart). Already installed? [Supported tools](#supported-tools)
 shows the wired AIs; [`docs/featured-commands.md`](docs/featured-commands.md)
 lists the end-to-end workflows (`/implement-ticket`, `/work`,
@@ -119,8 +119,8 @@ lists the end-to-end workflows (`/implement-ticket`, `/work`,
 
 Don't take the claims on trust — **verify them.** [`docs/proof.md`](docs/proof.md)
 is generated from source: a claim→evidence table (every public claim binds to a
-resolvable pointer, or CI fails), honest-null benchmarks *including the runs where
-the package changed nothing*, and a "verify it yourself" block you run on a fresh
+resolvable pointer or CI fails), honest-null benchmarks *including the runs where
+the package changed nothing* and a "verify it yourself" block you run on a fresh
 checkout. The proof page fails CI if it drifts from its sources — reproducibility
 is the proof. Browse it on the deployed docs site — the proof page is the primary entry:
 [event4u-app.github.io/agent-config/proof/](https://event4u-app.github.io/agent-config/proof/).
@@ -132,7 +132,7 @@ find-replace re-skin PRs here runs on your catalog too —
 [`docs/anti-reskin-gate.md`](docs/anti-reskin-gate.md).
 
 Audit-disciplined by construction — every memory consult, decision
-key, and hook concern lands in `agents/runtime/state/` so you can replay it.
+key and hook concern lands in `agents/runtime/state/` so you can replay it.
 [Core principles](#core-principles) names the four invariants;
 [What `agent-config` is — and what it isn't](#what-agent-config-is--and-what-it-isnt)
 draws the scope boundary.
@@ -207,7 +207,7 @@ Migrating from a v1.x install? `npx @event4u/agent-config migrate` — full note
 
 A **content layer** — skills, rules, commands, guidelines, personas — distributed via npm and projected into every supported AI tool's native config format. It follows the [Agent Skills open standard](https://agentskills.io).
 
-It is **not** an agent runtime. The agent loop, the LLM dispatcher, and tool orchestration stay with the host tool (Claude Code, Augment, Cursor, Cline, Windsurf, Gemini CLI, Copilot). Think of it as a playbook and style guide for those tools — not a replacement.
+It is **not** an agent runtime. The agent loop, the LLM dispatcher and tool orchestration stay with the host tool (Claude Code, Augment, Cursor, Cline, Windsurf, Gemini CLI, Copilot). Think of it as a playbook and style guide for those tools — not a replacement.
 
 | In scope | Out of scope |
 |---|---|
@@ -254,7 +254,7 @@ refine → memory → analyze → plan → implement → test → verify → rep
 - **Reviews** the diff through four judges (bugs, security, tests, code quality).
 - **Reports** changes, verdicts, follow-ups — then stops. `/commit` and `/pr:create` are suggestions, never auto-run.
 
-Any ambiguity halts the flow with numbered options — never a silent guess. Persona comes from `.agent-settings.yml` (`roles.active_role`): `senior-engineer` (default), `qa`, or `advisory` (plan-only).
+Any ambiguity halts the flow with numbered options — never a silent guess. Persona comes from `.agent-settings.yml` (`roles.active_role`): `senior-engineer` (default), `qa` or `advisory` (plan-only).
 
 → [Command reference](dist/agent-src/commands/implement-ticket.md) · [Flow contract](docs/contracts/implement-ticket-flow.md)
 
@@ -316,7 +316,7 @@ Create the user file interactively: `/agents user init` ([schema](docs/contracts
 
 ### Self-hosted MCP on Cloudflare — zero local install
 
-Skills, commands, rules, and guidelines can be served as an MCP endpoint from your own Cloudflare Worker — any MCP client (Claude Desktop, Claude Code, Cursor, Zed, Continue, hosted agents) talks to it over HTTP. Two auth modes: `public` (default, OSS read-only deploys) and `bearer-auth` (operator opt-in, `MCP-Token` Wrangler secret).
+Skills, commands, rules and guidelines can be served as an MCP endpoint from your own Cloudflare Worker — any MCP client (Claude Desktop, Claude Code, Cursor, Zed, Continue, hosted agents) talks to it over HTTP. Two auth modes: `public` (default, OSS read-only deploys) and `bearer-auth` (operator opt-in, `MCP-Token` Wrangler secret).
 
 ```bash
 task mcp:cloud:login         # one-time, opens browser
@@ -340,13 +340,13 @@ task mcp:cloud:secret-put    # opt in to bearer-auth (recommended for private de
 
 The Hard Floor on organization-mode features (SSO, central policy, OAuth connectors, team-context) is preserved by design — they stay cancelled until a real first customer + funded security audit lifts them. The small-team recipe is the supported path in the meantime.
 
-> *The 9.3/10 feedback round (2026-05-25) re-asked for OAuth knowledge connectors, IAM / org governance, and organization-shared memory. Each is a stable cancellation row in [`team-deployment-posture`](docs/deploy/team-deployment-posture.md) under the same three release gates — recruited team customer · funded audit · maintainer ADR.*
+> *The 9.3/10 feedback round (2026-05-25) re-asked for OAuth knowledge connectors, IAM / org governance and organization-shared memory. Each is a stable cancellation row in [`team-deployment-posture`](docs/deploy/team-deployment-posture.md) under the same three release gates — recruited team customer · funded audit · maintainer ADR.*
 
 ---
 
 ## Harness expectations
 
-Three classes of install/runtime behaviour look like package bugs but are host-harness behaviour the package cannot control — sibling-plugin namespaces (`codex:*`, `cc-gemini-plugin:*`), deferred tools surfaced via `ToolSearch`, and cross-scope skill drift (real bug, fixed in the distribution-channels track). Diagnostics + the package's response: [`docs/contracts/harness-expectations.md`](docs/contracts/harness-expectations.md). First step when a skill appears twice: `task probe:skills`.
+Three classes of install/runtime behaviour look like package bugs but are host-harness behaviour the package cannot control — sibling-plugin namespaces (`codex:*`, `cc-gemini-plugin:*`), deferred tools surfaced via `ToolSearch` and cross-scope skill drift (real bug, fixed in the distribution-channels track). Diagnostics + the package's response: [`docs/contracts/harness-expectations.md`](docs/contracts/harness-expectations.md). First step when a skill appears twice: `task probe:skills`.
 
 ## Supported tools
 
@@ -477,7 +477,7 @@ Browse content: [all commands](dist/agent-src/commands/) · [skills catalog](doc
 ## Troubleshooting
 
 First stop for any install problem: `agent-config doctor` — it flags a
-missing-from-`PATH` binary, binary↔plugin version drift, stale orphans, and
+missing-from-`PATH` binary, binary↔plugin version drift, stale orphans and
 manifest issues, each with a one-line fix hint.
 
 ### A new command / skill is missing in Claude Code after an upgrade
@@ -486,7 +486,7 @@ Under the single-surface model, `agent-config upgrade` refreshes the
 `~/.claude/` file projection — that IS the content surface, so a fresh
 session picks the new commands up directly. If commands are still missing,
 the usual cause is a leftover **marketplace plugin**: it is a git-SHA
-snapshot that never moves with the npm upgrade, and it shadows nothing —
+snapshot that never moves with the npm upgrade and it shadows nothing —
 it just lists everything twice while lagging behind. Remove it:
 
 ```bash
@@ -521,7 +521,7 @@ Only the initial `npm install -g` hard-aborts an upgrade. Every later step
 (global re-deploy with hook registration, settings sync, wrapper + git-hook
 refresh) runs independently — a single failed step is reported in the
 end-of-run summary instead of silently skipping the rest. Re-run
-`agent-config upgrade` to converge, and use `agent-config doctor` to name
+`agent-config upgrade` to converge and use `agent-config doctor` to name
 anything left in a mixed state.
 
 ### `agent-config: command not found` / hooks stopped firing

package/dist/agent-src/README.md

@@ -1,8 +1,8 @@
 # Agent Infrastructure
 
 > **⚠️ DO NOT edit files in `dist/agent-src/` or `.augment/` directly.**
-> The source of truth is `.agent-src.uncondensed/`. Edit there, then run `task sync`.
-> See `.agent-src.uncondensed/commands/condense.md` for the full workflow.
+> The source of truth is `src/` (`src/skills/`, `src/rules/`, `src/agent-src/`). Edit there, then run `task sync`.
+> See the `source-of-truth` rule and the `/condense` command for the full workflow.
 
 This directory contains the shared agent infrastructure: skills, commands, rules, guidelines,
 templates, and contexts that power the AI coding assistant across all projects.

package/dist/agent-src/commands/agents/audit.md

@@ -9,9 +9,8 @@ sub: audit
 description: Audit agent infrastructure — token overhead, rule triggers, AGENTS.md health, Capability-over-Structure adherence, stale references. Read-only, suggest-only, never auto-apply.
 skills: [copilot-agents-optimization, agents-audit, agent-docs-writing, agents-md-thin-root, quality-tools]
 suggestion:
-  eligible: true
-  trigger_description: "audit agent infrastructure, check rule triggers, verify AGENTS.md health, agent-layer health-check"
-  trigger_context: "maintainer working on .augment/ files, AGENTS.md, or planning a refactor"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/agents/optimize.md

@@ -10,9 +10,8 @@ description: Refactor AGENTS.md to the Thin-Root contract (caps, pointer ratio,
 argument-hint: "[path-to-AGENTS.md]"
 skills: [agents-md-thin-root, copilot-agents-optimization, copilot-config, agent-docs-writing]
 suggestion:
-  eligible: true
-  trigger_description: "refactor AGENTS.md, shrink AGENTS.md, capability bullets, thin-root, optimize agent layer"
-  trigger_context: "maintainer working on AGENTS.md (root or consumer template) or its tool stubs"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/agents/user/review.md

@@ -9,9 +9,8 @@ sub: user
 skills: [agents]
 description: List buffered observations from .agent-user.observations.jsonl with numbered options to inspect or accept individually.
 suggestion:
-  eligible: true
-  trigger_description: "review user observations, see what the agent learned about me, list buffered persona updates"
-  trigger_context: "user wants to see what the agent has buffered about their preferences before applying changes"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:
@@ -86,7 +85,7 @@ One question per turn. Wait for the user's number.
 ### 4. Privacy-floor verify
 
 Before printing any observation's `evidence` text, scan it for the
-[exclusions list](../../../../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
+[exclusions list](../../../../../../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
 Match → replace the offending substring with `[redacted]` in the
 rendered output.
 
@@ -109,6 +108,6 @@ turn.
 
 ## See also
 
-- Schema + buffer contract: [`agent-user-schema § Observation buffer`](../../../../../../docs/contracts/agent-user-schema.md#observation-buffer).
+- Schema + buffer contract: [`agent-user-schema § Observation buffer`](../../../../../../../../docs/contracts/agent-user-schema.md#observation-buffer).
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user accept`](accept.md), [`/agents user update`](update.md).

package/dist/agent-src/commands/agents/user/show.md

@@ -9,9 +9,8 @@ sub: user
 skills: [agents]
 description: Read-only render of .agent-user.md — prints the persona summary the host agent loads at session start.
 suggestion:
-  eligible: true
-  trigger_description: "show user persona, render .agent-user.md, print who the user is"
-  trigger_context: "user wants to see what's currently in .agent-user.md without editing"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:
@@ -21,7 +20,7 @@ packs:
 # /agents user show
 
 Read-only render of the project-root `.agent-user.md` per
-[`docs/contracts/agent-user-schema.md`](../../../../../../../../../docs/contracts/agent-user-schema.md).
+[`docs/contracts/agent-user-schema.md`](../../../../../../../../../../../docs/contracts/agent-user-schema.md).
 
 Use when:
 
@@ -111,6 +110,6 @@ Do NOT chain to other `/agents user *` commands. Do NOT commit.
 
 ## See also
 
-- Schema: [`agent-user-schema`](../../../../../../../../../docs/contracts/agent-user-schema.md).
+- Schema: [`agent-user-schema`](../../../../../../../../../../../docs/contracts/agent-user-schema.md).
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user init`](init.md), [`/agents user update`](update.md).

package/dist/agent-src/commands/agents/user/update.md

@@ -9,9 +9,8 @@ sub: user
 description: Open .agent-user.md in the user's IDE for manual edit; validates schema and 100-line cap on save.
 argument-hint: "[--validate]"
 suggestion:
-  eligible: true
-  trigger_description: "edit user persona, update .agent-user.md, change nickname, change language, refresh voice sample"
-  trigger_context: "user wants to manually edit the persona file rather than answer interview questions"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:
@@ -62,7 +61,7 @@ When called with `--validate` (or after the user confirms "done"):
 
 1. Read `.agent-user.md`.
 2. Parse frontmatter; check every required field per
-   [`agent-user-schema § Field reference`](../../../../../docs/contracts/agent-user-schema.md#field-reference).
+   [`agent-user-schema § Field reference`](../../../../../../../docs/contracts/agent-user-schema.md#field-reference).
 3. Check file size ≤100 lines.
 4. Run the privacy-floor scan (same as `init` step 4): credentials,
    third-party PII, financial figures, health/legal status.
@@ -100,6 +99,6 @@ Do NOT commit. Do NOT chain to another `/agents user *` command.
 
 ## See also
 
-- Schema: [`agent-user-schema`](../../../../../docs/contracts/agent-user-schema.md).
+- Schema: [`agent-user-schema`](../../../../../../../docs/contracts/agent-user-schema.md).
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user init`](init.md), [`/agents user show`](show.md), [`/agents user review`](review.md).

package/dist/agent-src/commands/agents/user.md

@@ -10,9 +10,8 @@ description: User-persona file (.agent-user.md) — interview, render, and maint
 argument-hint: "[init|show|review|accept|update] [args]"
 type: orchestrator
 suggestion:
-  eligible: true
-  trigger_description: "create user persona, render .agent-user.md, review observations, accept observations, edit user file"
-  trigger_context: "user wants to bootstrap or maintain the .agent-user.md persona file (name, language, role, style, voice sample)"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/analytics/prune.md

@@ -9,9 +9,8 @@ sub: prune
 description: Drop events older than the 90-day retention window from the local analytics log. Atomic and idempotent.
 skills: [file-editor]
 suggestion:
-  eligible: true
-  trigger_description: "prune the analytics log, drop old events, clean up events.jsonl"
-  trigger_context: "user wants to manually advance the rolling retention window"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/analytics/show.md

@@ -10,9 +10,8 @@ description: Render top prompts, launcher → completion rate per role, average
 argument-hint: "[--window 24h|7d|30d] [--event <name>] [--role <slug>] [--format markdown|csv|json]"
 skills: [file-editor]
 suggestion:
-  eligible: true
-  trigger_description: "show analytics, top prompts last 30 days, which role launched what, completion rate per role"
-  trigger_context: "user wants a human-readable report from the local workspace event log"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/analyze/decision.md

@@ -10,9 +10,8 @@ skills: [decision-review]
 description: Audit a past architectural decision — restate what was chosen and why, compare original assumptions against reality now, produce a verdict (still valid / needs amendment / superseded).
 argument-hint: "[adr-id | path | decision-name]"
 suggestion:
-  eligible: true
-  trigger_description: "decision review, ADR review, did this hold up, rückblick Architektur, past decision"
-  trigger_context: "user wants to audit a past architectural decision or ADR for continued validity"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - engineering
 packs:

package/dist/agent-src/commands/analyze/incident.md

@@ -10,9 +10,8 @@ skills: [incident-commander, root-cause-frameworks, blameless-post-mortem]
 description: Full incident flow — incident-commander coordination, then RCA via root-cause-frameworks, then a blame-free write-up via blameless-post-mortem, ending with an incident-learnings candidate.
 argument-hint: "[incident-description]"
 suggestion:
-  eligible: true
-  trigger_description: "production is down, active incident, Vorfall, Prod ist down, full incident analysis"
-  trigger_context: "user is managing or reviewing a production incident end-to-end"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - engineering
 packs:

package/dist/agent-src/commands/analyze/near-miss.md

@@ -10,9 +10,8 @@ skills: [blameless-post-mortem]
 description: Blame-free near-miss analysis — same post-mortem flow as analyze:postmortem but framed around a close call that did not result in a production incident.
 argument-hint: "[event-description]"
 suggestion:
-  eligible: true
-  trigger_description: "near-miss, almost failed, beinahe-Vorfall, close call, we almost had an outage"
-  trigger_context: "user wants to analyse a close call or near-miss event that did not produce a full incident"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - engineering
 packs:

package/dist/agent-src/commands/analyze/postmortem.md

@@ -10,9 +10,8 @@ skills: [blameless-post-mortem, root-cause-frameworks]
 description: Blame-free post-mortem after a resolved incident — consume the incident-commander skeleton, derive root cause, write corrective actions, draft an incident-learnings memory candidate.
 argument-hint: "[incident-description]"
 suggestion:
-  eligible: true
-  trigger_description: "post-mortem, Nachbesprechung, incident review, was ist schiefgelaufen"
-  trigger_context: "incident or outage is resolved and a structured write-up is needed"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - engineering
 packs:

package/dist/agent-src/commands/analyze/premortem.md

@@ -10,9 +10,8 @@ skills: [premortem]
 description: Forward-looking imagined-failure analysis before committing to a heavy or irreversible plan — enumerate failure stories, score each mode, derive early-warning signals and guardrails.
 argument-hint: "[plan-summary]"
 suggestion:
-  eligible: true
-  trigger_description: "premortem, what if this fails, imagine failure, stress-test this plan, what could go wrong"
-  trigger_context: "user wants to anticipate failure modes before committing to a plan"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - engineering
 packs:

package/dist/agent-src/commands/analyze/reference-repo.md

@@ -10,9 +10,8 @@ skills: [project-analyzer, learning-to-rule-or-skill]
 description: Analyze an external reference repository (competitor, inspiration, peer) and produce a structured comparison + adoption plan for this project.
 argument-hint: "<repo-url | owner/repo | archive-url> [--focus=<area>] [--no-roadmap]"
 suggestion:
-  eligible: true
-  trigger_description: "look at how X does this, compare with that other repo, study this competitor's approach"
-  trigger_context: "external repo URL or path mentioned in the prompt"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/brand/identity.md

@@ -10,9 +10,8 @@ skills: [brand-identity]
 description: Define the brand identity — logo direction, colour story, type story, imagery direction — and the token constraints downstream generation consumes.
 argument-hint: "<strategy-ref | brief>"
 suggestion:
-  eligible: true
-  trigger_description: "define our brand identity, logo and colour direction, type story, visual identity system"
-  trigger_context: "user has a brand strategy and wants the identity system (logo/colour/type/imagery)"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - small-business
 packs:

package/dist/agent-src/commands/brand/review.md

@@ -10,9 +10,8 @@ skills: [brand-audit]
 description: Audit emitted UI, copy, and assets against the active brand tokens and voice profile — flag any value not traceable to a brand token or voice rule.
 argument-hint: "<artifact-path | description>"
 suggestion:
-  eligible: true
-  trigger_description: "audit our brand consistency, is this on-brand, check this UI/copy against the brand, brand review"
-  trigger_context: "user has emitted UI/copy/assets and wants an on-brand consistency check against tokens + voice"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - small-business
 packs:

package/dist/agent-src/commands/brand/strategy.md

@@ -10,9 +10,8 @@ skills: [brand-strategy]
 description: Define brand positioning, archetype, voice, tone, and messaging over the brand-grounding corpus — the strategy that bounds identity and UI.
 argument-hint: "<brief>"
 suggestion:
-  eligible: true
-  trigger_description: "define our brand strategy, what's our brand archetype, positioning and messaging, brand voice direction"
-  trigger_context: "user wants brand positioning/archetype/voice/messaging before identity or UI work"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - small-business
 packs:

package/dist/agent-src/commands/brand/tokens.md

@@ -10,9 +10,8 @@ skills: [brand-to-tokens]
 description: Derive a DTCG .tokens.json source of truth from brand decisions, then emit CSS vars + Tailwind via the no-Node token generator.
 argument-hint: "<identity-ref>"
 suggestion:
-  eligible: true
-  trigger_description: "derive brand tokens, turn our brand into design tokens, generate a .tokens.json from the brand"
-  trigger_context: "user has brand identity decisions and wants a DTCG token source of truth + CSS/Tailwind output"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - small-business
 packs:

package/dist/agent-src/commands/brand/voice.md

@@ -10,9 +10,8 @@ skills: [voice-and-tone-design]
 description: Define the brand voice-and-tone profile — register, do/don't lexicon, and tone shifts by context — the profile the brand-consistency gate checks copy against.
 argument-hint: "<brand-ref | strategy-ref>"
 suggestion:
-  eligible: true
-  trigger_description: "define our brand voice, voice and tone guide, how should our copy sound, tone of voice profile"
-  trigger_context: "user wants a documented voice-and-tone profile for the brand to govern copy"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - small-business
 packs:

package/dist/agent-src/commands/bug/fix.md

@@ -11,9 +11,8 @@ description: Plan and implement a bug fix — based on investigation, with quali
 argument-hint: "[bug-description]"
 council_depth: deep
 suggestion:
-  eligible: true
-  trigger_description: "fix this bug, patch the issue, resolve this error"
-  trigger_context: "branch name matches fix/* or bug/*"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 framework: laravel
 workspaces:
   - agent-config-maintainer

package/dist/agent-src/commands/bug/investigate.md

@@ -11,9 +11,8 @@ description: Investigate a bug — auto-detect ticket from branch, gather Jira/S
 argument-hint: "[ticket-key | sentry-url | error-message | description]"
 council_depth: deep
 suggestion:
-  eligible: true
-  trigger_description: "why is this broken, investigate this error, trace the root cause"
-  trigger_context: "Sentry URL, Jira bug ticket key, or stack trace pasted in the prompt"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/challenge-me/vision.md

@@ -9,9 +9,8 @@ sub: vision
 description: "Stress-test a plan or idea by one-question-at-a-time interview until 95% confidence — emits a copyable Markdown vision pitch for tickets, roadmaps, or fresh-chat handoff."
 argument-hint: "[--until=N] [--keep-going] [seed]"
 suggestion:
-  eligible: true
-  trigger_description: "challenge me on this plan, grill me, grill me on this, grill me on the vision, grill me on the idea, grill me until it's clear, grill me hard, frag mich durch, dreh mich durch die Mangel"
-  trigger_context: "user has a fuzzy plan/idea/feature draft and wants it sharpened interactively rather than reconstructed in one shot"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/challenge-me/with-docs.md

@@ -9,9 +9,8 @@ sub: with-docs
 description: "Doc-aware /challenge-me — 95%-confidence interview with session glossary vs CONTEXT.md, load-bearing claim-vs-code verification, optional CONTEXT.md patch + ADR candidates in the pitch."
 argument-hint: "[--until=N] [--keep-going] [seed]"
 suggestion:
-  eligible: true
-  trigger_description: "challenge me against the docs, grill me with our context, grill me against the docs, grill me against CONTEXT.md, grill me with the project context, frag mich durch und prüf gegen CONTEXT.md, challenge plan with domain docs"
-  trigger_context: "user wants the seed challenged against existing project glossary, CONTEXT.md, or ADRs — not a greenfield interview"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/chat-history/import.md

@@ -8,9 +8,8 @@ cluster: chat-history
 sub: import
 description: Surface prior chat-history sessions as a numbered table, let the user pick one, read it silently, and emit a short summary plus a resume offer — selective, user-driven cross-session import
 suggestion:
-  eligible: true
-  trigger_description: "import a past session into the current chat, pull a prior session into context, pick a session to read"
-  trigger_context: "user wants to selectively pull a prior session's context into the current one as a short summary"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/commit/in-chunks.md

@@ -10,9 +10,8 @@ sub: in-chunks
 skills: [git-workflow]
 description: Stage and commit all uncommitted changes in logical chunks WITHOUT confirmation — sibling of /commit for autonomous flows
 suggestion:
-  eligible: true
-  trigger_description: "commit everything autonomously, split and commit without confirmation"
-  trigger_context: "autonomous mode active and uncommitted changes present"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/context/create.md

@@ -10,9 +10,8 @@ skills: [agent-docs-writing]
 description: Analyze a codebase area and create a structured context document
 argument-hint: "[topic]"
 suggestion:
-  eligible: true
-  trigger_description: "document this part of the codebase, create a context doc for X"
-  trigger_context: "working in a module without an agents/settings/contexts/ doc"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/context/refactor.md

@@ -9,9 +9,8 @@ sub: refactor
 skills: [agent-docs-writing]
 description: Analyze, update, and extend an existing context document
 suggestion:
-  eligible: true
-  trigger_description: "update the context doc, refresh this context document"
-  trigger_context: "existing agents/settings/contexts/*.md referenced in the prompt"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/cost/report.md

@@ -9,9 +9,8 @@ cluster: cost
 description: Capture token cost from the active Claude Code session, append to the local sessions store, and surface the 50/75/90/100% budget alert ladder with cost-profile suggestions.
 skills: [file-editor]
 suggestion:
-  eligible: true
-  trigger_description: "check this session's token cost, see budget utilization, surface 50/75/90/100% alert ladder"
-  trigger_context: "user wants to know how expensive the active Claude Code session is or whether it crosses a budget threshold"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/council/analysis.md

@@ -10,9 +10,8 @@ skills: [ai-council]
 description: Run the council on a local analysis output (project-analyze, audit script, codebase scan) — critiques the analysis itself for dedup, evidence quality, and roadmap-readiness.
 argument-hint: "[path] [question]"
 suggestion:
-  eligible: true
-  trigger_description: "council on this analysis, critique the project-analyze output, second opinion on the audit findings, turn analysis into roadmap"
-  trigger_context: "user has a local analysis artefact (agents/evidence/analysis/*.md|json) and wants an external critique of the analysis quality + roadmap-ready follow-ups"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs:

package/dist/agent-src/commands/council/debate.md

@@ -10,9 +10,8 @@ skills: [ai-council]
 description: Multi-round council debate with progressive cost disclosure — each member produces a position, then rebuts the strongest opposing position in subsequent rounds. User confirms spend between rounds.
 argument-hint: "[topic | path] [--rounds N] [--auto-continue]"
 suggestion:
-  eligible: true
-  trigger_description: "council debate on X, multi-round rebuttal, escalate council to debate mode, push the council to argue not synthesize"
-  trigger_context: "user wants real pushback — initial positions plus explicit rebuttals across rounds, with progressive cost confirmation between rounds"
+  eligible: false
+  rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
 workspaces:
   - agent-config-maintainer
 packs: