@event4u/agent-config 6.0.0 → 7.0.0

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

@@ -3,6 +3,7 @@ model_tier: medium
 name: bug-fix
 pack: engineering-base
 tier: 2
+visibility: internal
 skills: [bug-analyzer, pest-testing]
 description: Plan and implement a bug fix — based on investigation, with quality checks and test verification
 council_depth: deep

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

@@ -3,6 +3,7 @@ model_tier: inherit
 name: bug-investigate
 pack: engineering-base
 tier: 2
+visibility: internal
 skills: [bug-analyzer, sentry-integration]
 description: Investigate a bug — auto-detect ticket from branch, gather Jira/Sentry/description context, trace root cause
 council_depth: deep

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

@@ -1,8 +1,9 @@
 ---
 model_tier: inherit
 name: challenge-me-vision
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 cluster: challenge-me
 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."
@@ -13,7 +14,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /challenge-me vision

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

@@ -1,8 +1,9 @@
 ---
 model_tier: medium
 name: challenge-me-with-docs
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 cluster: challenge-me
 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."
@@ -13,7 +14,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /challenge-me with-docs

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

@@ -1,8 +1,9 @@
 ---
 model_tier: medium
 name: challenge-me
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 description: Challenge-me orchestrator — routes to vision, with-docs
 cluster: challenge-me
 type: orchestrator
@@ -13,7 +14,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /challenge-me

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

@@ -1,8 +1,9 @@
 ---
 model_tier: medium
 name: chat-history-import
-pack: meta
+pack: memory
 tier: 2
+visibility: internal
 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
@@ -13,7 +14,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - memory
 ---
 <!-- cloud_safe: noop -->
 
@@ -31,15 +32,15 @@ This is the opt-in counterpart to the read-path filter (Phase 3 of
 `road-to-chat-history-session-isolation`): default reads stay
 session-scoped; `import` is the explicit surface for crossing the
 session boundary. For project-improving learnings derived from a
-prior session, see [`/chat-history learn`](learn.md).
+prior session, see [`/memory mine-session --mode=proposals`](../memory/mine-session/command.md).
 
 ## When NOT to use
 
-- Inspect the current session — that is the default of
-  `/chat-history show` plus `scripts/chat_history.py read`.
+- Inspect the current session — use the host's native transcript /
+  session view, or `scripts/chat_history.py read`.
 - Generate a learning proposal from a prior session — use
-  [`/chat-history learn`](learn.md), which orchestrates
-  `learning-to-rule-or-skill` on the picked session.
+  [`/memory mine-session --mode=proposals`](../memory/mine-session/command.md),
+  which frames the session's signals and runs `learning-to-rule-or-skill`.
 - Bulk-import all sessions — out of scope for v1. One session per
   invocation; multi-pick is v2.
 - Search prior sessions by content — out of scope for v1; no fuzzy
@@ -164,8 +165,7 @@ instruction.
 
 ## See also
 
-- [`/chat-history learn`](learn.md) — pick a prior session and turn it into a project-improving proposal via `learning-to-rule-or-skill`
-- [`/chat-history show`](show.md) — current-session inspector
+- [`/memory mine-session --mode=proposals`](../memory/mine-session/command.md) — pick a prior session and turn it into a project-improving proposal via `learning-to-rule-or-skill` (the former `/chat-history learn`)
 - [`chat-history-platform-hooks`](../../../agents/settings/contexts/chat-history-platform-hooks.md) — read contract, isolation default, opt-in cross-session path
 - [`scripts/chat_history.py`](../../../scripts/chat_history.py) — `sessions` and `read --session` CLI surface
 - [`user-interaction`](../../rules/user-interaction.md) — numbered-options Iron Law

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

@@ -2,59 +2,61 @@
 model_tier: medium
 name: chat-history
 disable-model-invocation: true
-pack: meta
+pack: memory
 tier: 2
-description: Chat-history orchestrator — routes to show, import, learn
+visibility: internal
+description: Chat-history orchestrator — routes to import (selective cross-session resume). Mining moved to /memory mine-session; raw-log inspection uses the host's native transcript view.
 cluster: chat-history
 type: orchestrator
 suggestion:
   eligible: true
-  trigger_description: "show chat-history status, inspect agents/runtime/.agent-chat-history log, import a prior session into the current chat, mine a prior session for project-improving learnings"
-  trigger_context: "user wants to inspect the persistent agents/runtime/.agent-chat-history log, pull a prior session in verbatim, or extract learnings from a prior session"
+  trigger_description: "import a prior session into the current chat, resume a previous session, pull a prior session in verbatim"
+  trigger_context: "user wants to pull a prior session from the agents/runtime/.agent-chat-history log into the current chat verbatim and optionally resume it"
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - memory
 ---
 
 <!-- cloud_safe: noop -->
 
 # /chat-history
 
-Top-level orchestrator for the `/chat-history` family. After the
-hook-only reduction (`road-to-chat-history-hook-only`) writes and
-overflow handling are driven entirely by platform hooks +
-`scripts/chat_history.py` internals; the surfaced sub-commands are
-read-only on the log itself. Sessions coexist in one log file —
-each entry self-tags via the `s` field — so there is no ownership
-layer to recover from.
+Top-level orchestrator for the `/chat-history` family. Writes and overflow
+handling are driven entirely by platform hooks + `scripts/chat_history.py`
+internals (`road-to-chat-history-hook-only`); the surfaced sub-command is
+read-only on the cross-host log (`agents/runtime/.agent-chat-history`).
+Sessions coexist in one log file — each entry self-tags via the `s` field —
+so there is no ownership layer to recover from.
 
 ## Sub-commands
 
 | Sub-command | Routes to | Purpose |
 |---|---|---|
-| `/chat-history show` | `commands/chat-history/show.md` | Inspect the log — size, entries, header, last entries |
-| `/chat-history import` | `commands/chat-history/import.md` | List prior sessions, pick one, render its entries verbatim — selective cross-session import |
-| `/chat-history learn` | `commands/chat-history/learn.md` | List prior sessions, pick one, mine it for project-improving learnings via `learning-to-rule-or-skill` |
+| `/chat-history import` | `commands/chat-history/import.md` | List prior sessions, pick one, render its entries verbatim — selective cross-session import + resume |
+
+**Consolidated elsewhere** (see `road-to-memory-pipeline-consolidation.md`):
+
+- **Mining a session for learnings** — use
+  [`/memory mine-session --mode=proposals`](../memory/mine-session/command.md)
+  (the former `/chat-history learn`; now the single mining command, reading the
+  same cross-host log).
+- **Inspecting the raw log** (size, entries, header) — use the host's native
+  transcript / session view; the bespoke `/chat-history show` was dropped as
+  redundant.
 
 ## Dispatch
 
 1. Parse the user's argument: `/chat-history <sub-command> [args]`.
-2. Look up the sub-command in the table above.
-3. Load the body of the routed file and follow its `## Steps`
-   section verbatim with the remaining args.
-4. If the sub-command is unknown or missing (including the bare
-   `/chat-history` invocation), route to `show` — the safe,
-   current-session inspector default. `import` and `learn` are
-   opt-in only.
+2. The only sub-command is `import`. Bare `/chat-history` (or an unknown
+   sub-command) → route to `import`.
+3. Load `commands/chat-history/import.md` and follow its `## Steps` verbatim
+   with the remaining args.
 
 ## Rules
 
-- **Do NOT commit, push, or open a PR** — `show` and `import` are
-  read-only; `learn` writes proposal drafts under
-  `agents/proposals/` only and does not commit them.
-- **Do NOT chain sub-commands.** One `/chat-history <sub>` per turn.
-- **`import` and `learn` cross the session boundary** — only run
-  them when the user explicitly asked for cross-session reading.
-  The default read path (filtered to current session) stays in
-  effect for every other tool.
+- **Do NOT commit, push, or open a PR** — `import` is read-only (it renders a
+  prior session into the current chat; it writes nothing).
+- **Do NOT chain sub-commands.** One `/chat-history import` per turn.
+- **`import` crosses the session boundary** — only run it when the user
+  explicitly asked for cross-session reading.

package/dist/agent-src/commands/check-current-md.md

@@ -3,6 +3,7 @@ model_tier: medium
 name: check-current-md
 pack: meta
 tier: 2
+visibility: internal
 description: "Check the open .md file (or a passed path) for German outside DE:/EN: anchor blocks — umlauts, function words, untranslated quotes. Reports and offers fixes."
 suggestion:
   eligible: false
@@ -36,7 +37,7 @@ Stop here.
 ### 2. Run the checker
 
 ```bash
-python3 scripts/check_md_language.py <path> [<path> …] --format json
+./scripts-run src/scripts/check_md_language <path> [<path> …] --format json
 ```
 
 Exit codes:
@@ -104,7 +105,7 @@ Edit only the source-of-truth file:
 After all fixes, re-run:
 
 ```bash
-python3 scripts/check_md_language.py <path> [<path> …]
+./scripts-run src/scripts/check_md_language <path> [<path> …]
 ```
 
 ### 6. Mark hashes (only if `.agent-src.uncondensed/` was edited)
@@ -112,7 +113,7 @@ python3 scripts/check_md_language.py <path> [<path> …]
 For each modified source file:
 
 ```bash
-python3 scripts/condense.py --mark-done "{relative_path}"
+./scripts-run src/scripts/condense --mark-done "{relative_path}"
 ```
 
 This keeps `.condensation-hashes.json` consistent with the new content.

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

@@ -4,6 +4,7 @@ name: git-commit-in-chunks
 pack: git
 replaces: [commit-in-chunks, commit:in-chunks]
 tier: 2
+visibility: internal
 cluster: git-commit
 sub: in-chunks
 skills: [git-workflow]

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

@@ -7,6 +7,7 @@ intent: "Stage and commit changes in logical chunks with a Conventional Commits
 routes_to: [git-workflow, conventional-commits-writing]
 replaces: [commit]
 tier: 0
+visibility: visible
 cluster: git-commit
 skills: [git-workflow]
 description: Stage and commit all uncommitted changes — splits into logical commits following Conventional Commits

package/dist/agent-src/commands/condense.md

@@ -6,6 +6,7 @@ intent: "Condense src/ sources into the shipped dist/agent-src trees"
 routes_to: [skill-management]
 replaces: []
 tier: 1
+visibility: advanced
 skills: []
 description: Condense .md files from src/ into telegraph format and write to dist/agent-src/
 suggestion:
@@ -111,7 +112,7 @@ For each changed `.md` file:
 7. **MANDATORY: Run condensation quality check on this file:**
 
 ```bash
-python3 scripts/check_condensation.py --format text 2>&1 | grep "{path}"
+./scripts-run src/scripts/check_condensation --format text 2>&1 | grep "{path}"
 ```
 
 If the output contains 🔴 (error) for this file: **STOP. Fix the condensed file before continuing.**
@@ -145,7 +146,7 @@ bash scripts/condense.sh --check
 Must show ✅ (hashes in sync).
 
 ```bash
-python3 scripts/check_condensation.py
+./scripts-run src/scripts/check_condensation
 ```
 
 Must show **zero 🔴 errors**. Warnings (🟡) are acceptable.

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

@@ -3,6 +3,7 @@ model_tier: inherit
 name: context-create
 pack: meta
 tier: 2
+visibility: internal
 cluster: context
 sub: create
 skills: [agent-docs-writing]

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

@@ -3,6 +3,7 @@ model_tier: high
 name: context-refactor
 pack: meta
 tier: 2
+visibility: internal
 cluster: context
 sub: refactor
 skills: [agent-docs-writing]

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

@@ -4,6 +4,7 @@ name: context
 disable-model-invocation: true
 pack: meta
 tier: 2
+visibility: internal
 description: Context orchestrator — routes to create, refactor
 cluster: context
 type: orchestrator

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

@@ -1,8 +1,9 @@
 ---
 model_tier: medium
 name: cost-report
-pack: meta
+pack: analytics
 tier: 2
+visibility: internal
 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:
@@ -12,7 +13,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - analytics
 ---
 
 <!-- cloud_safe: noop -->
@@ -125,7 +126,7 @@ Allowed values: `today`, `week`, `month`, `all` (default).
 ## Attribution
 
 Forked from
-[`ruvnet/ruflo`](https://github.com/ruvnet/ruflo)
-`plugins/ruflo-cost-tracker/scripts/{track,budget}.mjs`. The MCP
+an external reference
+`plugins/external-cost-tracker/scripts/{track,budget}.mjs`. The MCP
 `memory_store` dependency was replaced with a local JSONL append; the
 50/75/90/100% alert ladder and pricing tiers are preserved verbatim.

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

@@ -1,8 +1,9 @@
 ---
 model_tier: high
 name: council-analysis
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 cluster: council
 sub: analysis
 skills: [ai-council]
@@ -14,7 +15,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /council analysis

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

@@ -1,8 +1,9 @@
 ---
 model_tier: inherit
 name: council-debate
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 cluster: council
 sub: debate
 skills: [ai-council]
@@ -14,7 +15,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /council debate
@@ -51,7 +52,7 @@ the agent's framing.
 ### 2. Decide round count + auto-continue
 
 Default: 2 rounds (initial position + one rebuttal). Cap: the value of
-`defaults.debate_max_rounds` in [`agents/settings/.ai-council.yml`](../../../agents/settings/.ai-council.yml)
+`defaults.debate_max_rounds` in `~/.event4u/agent-config/settings/.ai-council.yml`
 (default 4). `--rounds N` overrides the default; values above the cap
 are rejected by the CLI.
 
@@ -86,7 +87,7 @@ to abort.
 ### 5. Invoke the CLI
 
 ```bash
-python3 scripts/council_cli.py debate <topic-path> \
+./scripts-run src/scripts/council_cli debate <topic-path> \
   --output agents/runtime/council/sessions/<date>-<slug>/ \
   --confirm \
   --rounds <N> \
@@ -113,7 +114,7 @@ After all rounds complete, render the last round's JSON via
 `/council` render flow:
 
 ```bash
-python3 scripts/council_cli.py render agents/runtime/council/sessions/<dir>/debate-round-<N>.json
+./scripts-run src/scripts/council_cli render agents/runtime/council/sessions/<dir>/debate-round-<N>.json
 ```
 
 The debate mode uses the structured decision-lens template (Karpathy
@@ -129,6 +130,6 @@ session directory is the canonical audit trail.
 
 If `DebateCapExceeded` fires, the CLI exits with code 3 and the partial
 debate is persisted. Surface the partial-debate path to the user and
-ask whether to (a) raise the cap in `agents/settings/.ai-council.yml` and rerun,
+ask whether to (a) raise the cap in `~/.event4u/agent-config/settings/.ai-council.yml` and rerun,
 (b) stop here and render the partial result, or (c) start a new debate
 with a smaller scope.

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

@@ -1,8 +1,9 @@
 ---
 model_tier: inherit
 name: council-default
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 cluster: council
 sub: default
 skills: [ai-council]
@@ -13,7 +14,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /council default
@@ -51,8 +52,8 @@ the host translates that to `--depth deep` on the CLI. If multiple
 active artefacts disagree, **deep wins** (max policy). Explicit
 `rounds:N` overrides depth.
 
-The default comes from `ai_council.min_rounds` in
-`.agent-settings.yml` (default `2` so members critique each other at
+The default comes from `defaults.min_rounds` in the resolved
+`.ai-council.yml` (default `2` so members critique each other at
 least once before convergence). **Do NOT ask the user "how many
 rounds?"** when `rounds:N` is unset or `N <= min_rounds` — proceed
 with the settings default. Ask only when the artefact is genuinely
@@ -87,16 +88,40 @@ Neutrality — context-handoff).
 
 ### 2. Check the council is configured + price table fresh
 
-Read `.agent-settings.yml` → `ai_council`:
+Council config lives in **`.ai-council.yml`**, NOT in `.agent-settings.yml`.
+The CLI (`scripts/ai_council/config.py:resolve_config_path`, per
+[ADR-093](../../../docs/decisions/ADR-093-ai-council-config-user-global.md))
+resolves it — first hit wins:
 
-- If `ai_council.enabled` is false → state that and offer to flip it
-  on. Do not flip it autonomously.
-- If no member has `enabled: true` → list the install commands
-  (`./agent-config keys:install-anthropic`, `./agent-config keys:install-openai`)
-  and stop.
-- If a member is enabled but its `*.key` file is missing or has the
-  wrong mode → tell the user which key to install. Do not fall back
-  to env vars. Ever.
+1. Project-local `<project_root>/agents/settings/.ai-council.yml` (if present).
+2. User-global `~/.event4u/agent-config/settings/.ai-council.yml` — default
+   home; one global config serves every project.
+
+Keys are **top-level** (`enabled`, `defaults:`, `members:`). No `ai_council:`
+parent block; the legacy `ai_council.*` block under `.agent-settings.yml` was
+removed in ADR-093 — never read or recommend that path for council config.
+
+```
+NEVER claim the council "needs `.agent-settings.yml` set up" or an
+`ai_council` block. The CLI's `resolve_config_path` is authoritative:
+run `council:estimate` (Step 3) and read its exit code + message before
+making any "not configured" claim. A user-global `.ai-council.yml` with
+`enabled: true` works from EVERY project, including consumer repos that
+have no project-local config.
+```
+
+CLI is the single source of truth for the configured-check — do not hand-parse
+the YAML to second-guess it. Map its outcomes (Step 4 exit codes + the
+**CLI exits 2** cases below):
+
+- `enabled: false` (top-level in resolved `.ai-council.yml`) → CLI exits 2 with
+  `ai_council.enabled is false`. State that, offer to flip it on. Do not flip
+  it autonomously.
+- No member has `enabled: true` (under top-level `members:`) → list install
+  commands (`./agent-config keys:install-anthropic`,
+  `./agent-config keys:install-openai`) and stop.
+- A member is enabled but its `*.key` file is missing or wrong-mode → tell the
+  user which key to install. Do not fall back to env vars. Ever.
 
 Load the price table via `scripts.ai_council.pricing.load_prices()`
 (auto-bootstraps `agents/runtime/.agent-prices.md` from defaults if missing). Run
@@ -171,8 +196,8 @@ Once the user picks `1`, invoke the same arguments with `run` plus
     [--original-ask "<framing sentence>"]
 ```
 
-`--rounds` defaults to `ai_council.min_rounds` from
-`.agent-settings.yml` (or `2` if unset). Pass `--rounds N` only when
+`--rounds` defaults to `defaults.min_rounds` from the resolved
+`.ai-council.yml` (or `2` if unset). Pass `--rounds N` only when
 the user explicitly asked for a different count or a complex
 artefact justifies more depth — do not pass `--rounds 1` to "save
 money" by default; the settings owner already chose `min_rounds`.
@@ -180,15 +205,15 @@ money" by default; the settings owner already chose `min_rounds`.
 `--depth` defaults to `standard`. Set `--depth deep` when the
 active rule, skill, or command declares `council_depth: deep` in
 its frontmatter; the floor becomes
-`max(ai_council.deep_min_rounds, ai_council.min_rounds)` (default
+`max(defaults.deep_min_rounds, defaults.min_rounds)` (default
 `3`). If `--rounds N` is also passed, `--rounds` wins.
 
 The CLI:
 
 - bundles the artefact via `scripts.ai_council.bundler` (redaction +
   size guard — `BundleTooLarge` exits 2 with the byte count),
-- builds members from `.agent-settings.yml` (refusing if
-  `ai_council.enabled` is false or no member is wired up),
+- builds members from the resolved `.ai-council.yml` (refusing if
+  top-level `enabled` is false or no member is wired up),
 - detects project context via `detect_project_context()`,
 - calls `orchestrator.consult(...)` with the `cost_budget` from
   settings,
@@ -252,8 +277,11 @@ council can act on the project directly.
 
 ## Failure modes
 
-- **CLI exits 2, "ai_council.enabled is false"** → tell the user how
-  to flip it on; do not flip it autonomously.
+- **CLI exits 2, "ai_council.enabled is false"** → tell the user to set
+  top-level `enabled: true` in the resolved `.ai-council.yml` (user-global
+  `~/.event4u/agent-config/settings/.ai-council.yml`, or project-local
+  `<project_root>/agents/settings/.ai-council.yml`) — never in
+  `.agent-settings.yml`. Do not flip it autonomously.
 - **CLI exits 2, "no council member has `enabled: true`"** → list the
   install commands (`./agent-config keys:install-anthropic`,
   `./agent-config keys:install-openai`) and stop.

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

@@ -1,8 +1,9 @@
 ---
 model_tier: inherit
 name: council-design
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 cluster: council
 sub: design
 skills: [ai-council]
@@ -14,7 +15,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /council design

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

@@ -1,8 +1,9 @@
 ---
 model_tier: inherit
 name: council-optimize
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 cluster: council
 sub: optimize
 skills: [ai-council]
@@ -14,7 +15,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /council optimize

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

@@ -1,8 +1,9 @@
 ---
 model_tier: inherit
 name: council-pr
-pack: meta
+pack: product-reasoning
 tier: 2
+visibility: internal
 cluster: council
 sub: pr
 skills: [ai-council]
@@ -14,7 +15,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /council pr

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

@@ -2,11 +2,12 @@
 model_tier: medium
 name: council
 disable-model-invocation: true
-pack: meta
+pack: product-reasoning
 intent: "Poll external AIs for a neutral second opinion (pr/design/optimize/analysis lenses)"
 routes_to: [council-default, council-pr, council-design, council-analysis]
 replaces: []
 tier: 1
+visibility: advanced
 description: Council orchestrator — routes to default, pr, design, optimize, analysis, debate
 cluster: council
 type: orchestrator
@@ -17,7 +18,7 @@ suggestion:
 workspaces:
   - agent-config-maintainer
 packs:
-  - meta
+  - product-reasoning
 ---
 
 # /council
@@ -75,7 +76,7 @@ Sub-command names match the locked contract in
 ## Advisor mode (replace-mode personas)
 
 Any sub-command above can run in **advisor mode** by enabling one or
-more advisors in `agents/settings/.ai-council.yml` under `advisors:` (Contrarian,
+more advisors in `~/.event4u/agent-config/settings/.ai-council.yml` under `advisors:` (Contrarian,
 First-Principles, Expansionist, Outsider, Executor). An enabled advisor
 swaps its bound member's plain call for the same provider running the
 advisor persona — **same call count, same budget**. `council:estimate`