@event4u/agent-config 1.21.0 → 1.23.0

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

@@ -0,0 +1,120 @@
+---
+name: cost-report
+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]
+disable-model-invocation: true
+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"
+---
+
+<!-- cloud_safe: noop -->
+
+# /cost:report
+
+Records the current Claude Code session's token usage and checks it against
+the configured budget. Local-only: writes to
+`agents/cost-tracking/sessions.jsonl` (no MCP / external services).
+
+## Steps
+
+### 1. Capture the active session
+
+```bash
+node scripts/cost/track.mjs
+```
+
+Emits a Markdown summary of the session (model breakdown, per-tier cost,
+total USD) and appends a JSON record to
+`agents/cost-tracking/sessions.jsonl`.
+
+If `track.mjs` exits 2 with `no Claude Code project dir`, the user is not in
+a Claude Code session — surface that and stop.
+
+### 2. Check the budget
+
+```bash
+node scripts/cost/budget.mjs check
+```
+
+Reads the runtime budget config under `agents/cost-tracking/` (set via step 4
+if missing) and the JSONL store, computes utilization, and prints the alert
+level.
+
+### 3. Surface the alert ladder
+
+The check output already includes the level. Translate it into a
+profile recommendation per the table:
+
+| Level | Utilization | Recommendation |
+|---|---|---|
+| 🟢 OK | < 50% | within budget — no action |
+| 🟡 INFO | ≥ 50% | log notification, no UX disruption |
+| 🟠 WARNING | ≥ 75% | suggest [`/set-cost-profile balanced→minimal`](set-cost-profile.md) |
+| 🔴 CRITICAL | ≥ 90% | recommend model downgrades, consider [`/set-cost-profile minimal`](set-cost-profile.md) |
+| 🛑 HARD_STOP | ≥ 100% | halt non-essential work; review before continuing (`budget.mjs check` exits 1) |
+
+If `level` ≥ WARNING and the current `cost_profile` in `.agent-settings.yml`
+is not already `minimal`, add an explicit suggestion sentence:
+
+> Run [`/set-cost-profile`](set-cost-profile.md) to switch from your
+> current profile to a leaner one.
+
+### 4. First-run: prompt to set a budget
+
+If `budget.mjs check` reports `no budget configured`, ask the user (one
+question per turn — see [`ask-when-uncertain`](../rules/ask-when-uncertain.md)):
+
+> No budget set yet. What monthly USD cap do you want to track against?
+> (e.g. 25, 50, 200)
+
+On reply, run:
+
+```bash
+node scripts/cost/budget.mjs set <usd>
+```
+
+Then re-run step 2.
+
+### 5. Period filter (optional)
+
+If the user asks for spend in a specific window — "this week", "today",
+"this month" — re-run with `BUDGET_PERIOD`:
+
+```bash
+BUDGET_PERIOD=week node scripts/cost/budget.mjs check
+```
+
+Allowed values: `today`, `week`, `month`, `all` (default).
+
+## Rules
+
+- **Local-only.** Never persist cost data to remote stores. The
+  JSONL store and the `budget.json` config both live inside `agents/`,
+  which is gitignored by default in consumer projects.
+- **Don't auto-switch profiles.** This command surfaces a recommendation;
+  the user runs [`/set-cost-profile`](set-cost-profile.md) themselves.
+  Auto-mutation of `.agent-settings.yml` would breach
+  [`commit-policy`](../rules/commit-policy.md) and
+  [`scope-control`](../rules/scope-control.md).
+- **Honor HARD_STOP.** When `budget.mjs check` exits 1, surface the alert
+  prominently and stop the current task — do not keep working through the
+  cap silently.
+
+## See also
+
+- [`/set-cost-profile`](set-cost-profile.md) — change `cost_profile` in
+  `.agent-settings.yml`.
+- [`/agent-status`](agent-status.md) — per-conversation token estimate
+  (different scope: in-flight estimate, not historical actuals).
+- [`scripts/cost/track.mjs`](../../scripts/cost/track.mjs) — tracker source.
+- [`scripts/cost/budget.mjs`](../../scripts/cost/budget.mjs) — budget source.
+
+## Attribution
+
+Forked from
+[`ruvnet/ruflo`](https://github.com/ruvnet/ruflo)
+`plugins/ruflo-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/.agent-src/commands/council/default.md

@@ -30,17 +30,34 @@ The user invoked `/council default` on exactly one input mode:
 Optional invocation flag: `mode:api|manual` overrides the per-member
 and global mode for this call only (see Step 2.5).
 
-Optional **rounds**: `rounds:N` (1-3) overrides the multi-round debate
-count. Round 1 sees the artefact alone. Round 2+ sees the artefact plus
-anonymised critiques from the previous round (provider/model identity
-stripped). Total spend = N × single-round cost; surface in cost gate.
-
-Default comes from `ai_council.min_rounds` in `.agent-settings.yml`
-(default `2` so members critique each other at least once before
-convergence). **Do NOT ask "how many rounds?"** when `rounds:N` is
-unset or `N <= min_rounds` — proceed with the settings default. Ask
-only when the artefact is genuinely complex; surface as a numbered
-choice with the cost delta.
+Optional **rounds**: `rounds:N` (1-3) overrides the multi-round
+debate count. Round 1 sees the artefact alone. Round 2+ sees the
+artefact plus anonymised critiques from the previous round
+(provider/model identity stripped). Total spend = N × single-round
+cost; surface this in the cost gate.
+
+Optional **depth**: `depth:deep` raises the round floor to
+`ai_council.deep_min_rounds` (default `3`, max'd with `min_rounds`)
+for architecture, refactoring, or bug-diagnosis artefacts. Set
+explicitly by the user, or derived from `council_depth: deep`
+declared in the frontmatter of the active rule, skill, or command —
+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
+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
+complex and you want more depth than `min_rounds` provides; surface
+the proposal as a numbered choice (per `ask-when-uncertain`) with
+the cost delta.
+
+Resolution chain (highest priority first):
+1. `rounds:N` / `--rounds N` — explicit user override.
+2. `depth:deep` / `--depth deep` — floors at `max(deep_min_rounds, min_rounds)`.
+3. `ai_council.min_rounds` — default.
 
 Optional **mode_override**: `mode_override=pr|design|optimize` swaps
 the system-prompt addendum for one of the specialised lenses
@@ -135,6 +152,7 @@ Once the user picks `1`, invoke the same arguments with `run` plus
     --output agents/council-sessions/<UTC-timestamp>.json \
     --confirm \
     [--rounds 1|2|3] \
+    [--depth standard|deep] \
     [--input-mode …] [--max-tokens …] [--mode-override …] \
     [--original-ask "<framing sentence>"]
 ```
@@ -143,7 +161,13 @@ Once the user picks `1`, invoke the same arguments with `run` plus
 `.agent-settings.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; settings owner already chose `min_rounds`.
+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
+`3`). If `--rounds N` is also passed, `--rounds` wins.
 
 The CLI:
 
@@ -169,12 +193,35 @@ the **Convergence / Divergence** section yourself:
 - **Agreements** — points all members made (or did not contradict).
 - **Disagreements** — points where members took opposing positions.
 - **Unique insights** — points raised by exactly one member.
-- **Suggested next actions** — translated into concrete options for
-  the user.
 
-End with a numbered-options block asking the user how to proceed
-(e.g. update the roadmap, request a second round, ignore the
-critique).
+### 5a. Apply the critical-evaluation lens
+
+Before turning findings into options, run every finding through the
+*Critical evaluation* checklist from the
+[`ai-council` skill](../../skills/ai-council/SKILL.md#critical-evaluation--convener-skeptic-stance):
+codebase fit · locked-decision conflict · already addressed · cost
+/ benefit · hallucination. Cite host evidence (file:line, ADR,
+contract) for each verdict.
+
+Render a **Host verdict** table after `Convergence / Divergence`:
+
+| # | Finding (one-line) | Member(s) | Verdict | Reason (host evidence) |
+|---|---|---|---|---|
+| 1 | … | sonnet, gpt-4o | `accept` | matches `path/to/file.py:42` |
+| 2 | … | sonnet | `accept-with-modification` | scope creep — narrow to module X |
+| 3 | … | gpt-4o | `reject` | contradicts ADR `docs/decisions/foo.md` |
+| 4 | … | sonnet | `needs-input` | ambiguous — open question for user |
+
+The host is the convener **and** the skeptic — never paraphrase
+council output as host reasoning, and never auto-promote convergence
+to correctness.
+
+### 5b. Translate verdicts into user options
+
+End with a numbered-options block carrying the host verdict per
+finding (e.g. `1. [accept] Apply finding 1 — <patch summary>`,
+`2. [reject] Skip finding 2 — <reason>` — user can override). Always
+include "discard council input" as an option.
 
 ### 6. Hard floor — text only
 

package/.agent-src/commands/create-pr/description-only.md

@@ -13,6 +13,14 @@ suggestion:
 
 # /create-pr:description-only
 
+> **Carve-out:** this command's *purpose* is the copyable preview of
+> the PR description. It therefore **ignores**
+> `verbosity.preview_artifacts` and `commands.create_pr.preview_description`
+> — both flags govern only the bare `/create-pr` flow's preview-and-
+> adjust loop. Removing the preview here would make the command a
+> no-op. Do not "fix" this; the suppression flags only apply when the
+> PR is actually being created.
+
 ## Input
 
 The user may or may not provide a PR URL or branch name.

package/.agent-src/commands/create-pr.md

@@ -45,100 +45,119 @@ Uses `/create-pr:description-only` to generate the PR content, then creates the
 
 ### 2. Generate PR content
 
-Run `/create-pr:description-only` to generate the PR title and body.
+Run `/create-pr:description-only` Steps 1–4 to generate the PR title and body.
 This handles: Jira ticket extraction, diff analysis, commit messages, **PR template filling**.
 
 **CRITICAL**: The PR body MUST use the project's PR template (`.github/pull_request_template.md`).
 Read the template file and fill in its sections. If the template does not exist, use the
 fallback structure defined in `/create-pr:description-only`. NEVER invent a custom body structure.
 
-The user reviews and adjusts the content in that step.
-
-### 2b. Offer council review (B2 hook)
-
-If `.agent-settings.yml` has `ai_council.enabled: true` **and** at least
-one member is enabled, ask (in the user's language):
-
-> 1. Run the council on this diff before opening the PR? (billable)
-> 2. Skip council review
-
-Suppress when `personal.autonomy: on` (council is billable; autonomy
-must not silently spend — see `road-to-ai-council.md` Decision 3).
-
-If picked **1**:
-
-- Compute the diff range — `origin/<default>..HEAD` from step 1.
-- Run `/council diff:<base>..<head>` with `original_ask` set to the
-  PR title from step 2 (the user's framing of the change).
-- Surface findings to the user before step 3. **Do not** auto-edit
-  the PR body or block PR creation — output is advisory.
-- Optional: offer to append a one-paragraph "Council notes" section
-  to the PR description for reviewer transparency. Default: skip.
-
-If picked **2** → continue.
-
-### 3. Create the PR
-
-Once the user approves the content from step 2:
-
-- **Head branch**: Use the EXACT output of `git branch --show-current` from step 1.
-  **NEVER** reuse a branch name from earlier in the conversation — always use the fresh value.
-- **Base branch**: Default branch (`main` / `master`).
-- Ask the user:
-  ```
-  > 1. Create as draft
-  > 2. Create as ready for review
-  ```
-- Create the PR via GitHub API with the approved title and body.
-- **CRITICAL**: Set the `draft` parameter based on the user's choice:
-  - Option 1 → `"draft": true`
-  - Option 2 → `"draft": false`
-  - Do NOT default to draft. The user's choice is the ONLY factor.
-- **After creating with `draft: false`**: The GitHub REST API sometimes ignores
-  `draft: false` and creates a draft anyway. Always verify by running:
-  ```bash
-  gh pr view {number} --json isDraft --jq '.isDraft'
-  ```
-  If it returns `true`, fix it immediately:
-  ```bash
-  gh pr ready {number}
-  ```
+**Preview gate** — read `commands.create_pr.preview_description` from
+`.agent-settings.yml` (default `false` when unset):
 
-### 4. After creation
+- `false` (default): skip Steps 5–6 of `/create-pr:description-only` (the
+  copyable preview block + adjust loop). Use the generated title and body
+  directly in Step 3 below. This saves agent tokens by avoiding a full
+  re-render of the description in chat. The user can still edit the PR
+  body in the GitHub UI after creation.
+- `true`: run Steps 5–6 of `/create-pr:description-only` — present the
+  title and body as copyable blocks and ask for adjustments before
+  proceeding. The user reviews and adjusts the content in that step.
 
-#### 4a. Strip attribution footers (mandatory)
+### 2b. Council review — explicitly excluded
 
-`github-api` may server-side-append attribution after a clean send.
-Per [`no-attribution-footers`](../rules/no-attribution-footers.md),
-re-check the body after creation **and after every body PATCH**:
+`/create-pr` does **not** prompt for council review, even when
+`ai_council.enabled: true`. Invoking the PR command is an explicit
+delivery action; interrupting it with a billable opt-in question is
+out of scope.
 
-1. `GET /repos/{owner}/{repo}/pulls/{number}` — re-fetch body.
-2. Search (case-insensitive) for: `Generated with [Augment Code]`,
-   `🤖 Generated with`, `Pull Request opened by [Augment Code]`,
-   `Co-authored by Augment Code`, unsolicited `augmentcode.com` link.
-3. If any present, strip with surrounding `---` and trailing
-   whitespace, then `PATCH /pulls/{number}` with cleaned body.
-4. Re-fetch to verify. If the pattern reappears, repeat once; if
-   still present, surface to user and stop (no strip/PATCH loop).
-5. Note in the reply how many footers were removed (or "clean").
+Users who want a council pass on the diff run `/council diff:<base>..<head>`
+**before** `/create-pr`. Do not re-add the prompt here without an explicit
+user request.
 
-#### 4b. Show the PR URL
+### 3. Create the PR (draft-vs-ready, verbosity-gated)
 
-#### 4c. Jira transition
+- **Head branch**: EXACT output of `git branch --show-current` from step 1.
+- **Base branch**: default branch (`main` / `master`).
 
-If a Jira ticket was linked, ask:
-```
-> Transition Jira ticket {TICKET-ID} to "In Review"?
->
-> 1. Yes — update status
-> 2. No — leave as-is
+**Behavior change vs. legacy:** with `verbosity.routine_confirmations:
+false` (default), `/create-pr` creates the PR as draft silently. Override
+per-invocation with `:ready` / `:final` / `:draft`. Restore the prompt
+by flipping `routine_confirmations: true`. See
+[`docs/customization.md` § Verbosity](../../docs/customization.md#verbosity).
+
+Resolve `"draft"` (first match wins):
+
+1. `:ready` / `:final` arg → `false`.
+2. `:draft` arg → `true`.
+3. `routine_confirmations: true` → ask `1. draft / 2. ready`.
+4. Default → `true` (silent draft).
+
+Create the PR with the approved title/body and the resolved `draft`.
+
+**Verify after `draft: false`** — the GitHub REST API sometimes ignores
+the flag:
+
+```bash
+gh pr view {number} --json isDraft --jq '.isDraft'
+# returns true → gh pr ready {number}
 ```
 
+**Silent-draft postscript** (rule 4) → see step 4b.
+
+### 4. After creation
+
+#### 4a. Strip attribution footers (mandatory)
+
+Some `github-api` tool surfaces append attribution server-side after
+the agent has sent a clean body. Per
+[`no-attribution-footers`](../rules/no-attribution-footers.md), every
+PR body must be re-checked and stripped after every write.
+
+Run this strip-pass **after PR creation and after every body PATCH**:
+
+1. Re-fetch the PR body:
+   ```
+   GET /repos/{owner}/{repo}/pulls/{number}
+   ```
+2. Search the body (case-insensitive) for any of:
+   - `Generated with [Augment Code]` / `🤖 Generated with`
+   - `Pull Request opened by [Augment Code]`
+   - `Co-authored by Augment Code`
+   - Any `augmentcode.com` link the user did not ask for
+3. If any pattern is present, remove it together with surrounding
+   `---` separators and trailing whitespace, then:
+   ```
+   PATCH /repos/{owner}/{repo}/pulls/{number}
+   { "body": "<cleaned body>" }
+   ```
+4. Re-fetch the body once more to verify the strip stuck. If a
+   pattern reappears (server re-injection), repeat steps 2–4 once;
+   if it still reappears, surface the issue to the user and stop
+   (do not enter a strip/PATCH loop).
+5. Briefly note in the reply how many footers were removed (or
+   "no footers found" if clean).
+
+#### 4b. Show the PR URL (verbosity-gated)
+
+Per `verbosity.post_action_reports` (default `minimal`):
+
+- `off` → nothing.
+- `minimal` → `→ #N opened: <url>`. Append `→ created as draft — run
+  \`gh pr ready N\` to flip` when silent-draft (rule 4); omit on ready.
+- `full` → multi-line: PR number, URL, draft state, base/head, ready-reminder.
+
+#### 4c. Jira transition (only when transitioned)
+
+Linked ticket + `routine_confirmations: true` → ask `1. Yes / 2. No`.
+Default (`false`) → skip silently. **Only emit a transition line when
+an actual Jira API call succeeded** — never announce "skipped".
+
 ### Rules
 
-- **Always use the PR template** from `.github/pull_request_template.md` — read it, fill its sections.
-- **Always show the PR content before creating it** — never create blindly.
-- **Push the branch first** if it hasn't been pushed (with user permission).
-- **Never add attribution footers** — see [`no-attribution-footers`](../rules/no-attribution-footers.md). Strip-pass in 4a defends against tool-injected footers.
-- Only create the PR — never merge it.
-- Only commit or push with explicit user permission.
+- **Always use the PR template** from `.github/pull_request_template.md`.
+- **Preview is opt-in** — `commands.create_pr.preview_description` (default `false`). `/create-pr:description-only` always previews.
+- **Push the branch first** if needed (with permission).
+- **No attribution footers** — see [`no-attribution-footers`](../rules/no-attribution-footers.md); strip-pass at 4a defends against tool injection.
+- Only create the PR — never merge.
+- Only commit or push with explicit permission.

package/.agent-src/commands/feature/plan.md

@@ -209,16 +209,22 @@ Mir sind noch ein paar offene Fragen aufgefallen:
 Hast du dazu schon eine Meinung?
 ```
 
-### 5d. Offer council idea-validation (B4 hook)
+### 5d. Offer council idea-validation (B4 hook, verbosity-gated)
 
-Once the conversation has converged on a problem statement, proposal,
-and rough scope (rounds 1–4), but **before** step 6 writes the file,
-ask (in the user's language):
+Once rounds 1–4 have converged but **before** step 6 writes the file,
+read `verbosity.offer_council_in_delivery` from `.agent-settings.yml`
+(default `false`):
 
-> 1. Run the council on this idea before writing the plan? (billable)
-> 2. Skip — write the plan now
+- `false` (default): skip the prompt silently. When `ai_council.enabled:
+  true`, emit one line: `→ council skipped (set
+  verbosity.offer_council_in_delivery: true to enable, or run
+  /council directly)`. When `ai_council.enabled: false`, emit nothing.
+- `true`: ask (in the user's language):
 
-Suppress when `personal.autonomy: on` (council is billable).
+  > 1. Run the council on this idea before writing the plan? (billable)
+  > 2. Skip — write the plan now
+
+  Also suppress when `personal.autonomy: on` (council is billable).
 
 If picked **1**:
 

package/.agent-src/commands/grill-me.md

@@ -0,0 +1,38 @@
+---
+name: grill-me
+description: Alias for /challenge-me — interactive grill-style interview that sharpens a fuzzy plan/idea into a copyable Markdown pitch
+cluster: challenge-me
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "grill me, grill me on this, grill me on this plan, grill me through this, grill me on the idea, grill me until it's clear, grill me hard"
+  trigger_context: "user has a fuzzy plan/idea/feature draft and wants it sharpened interactively rather than reconstructed in one shot"
+---
+
+# /grill-me
+
+Alias for [`/challenge-me`](challenge-me.md). Identical behaviour,
+sub-commands (`vision`, `with-docs`), and in-interview triggers
+(`!pitch`, `!roadmap`, `!ai`).
+
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/grill-me vision` | `commands/challenge-me/vision.md` | 95%-confidence interview, emits a vision pitch |
+| `/grill-me with-docs` | `commands/challenge-me/with-docs.md` | Same flow plus glossary + claim-vs-code check vs `CONTEXT.md` / ADRs |
+
+## Dispatch
+
+1. Parse: `/grill-me <sub-command> [flags] [seed]`.
+2. Load [`commands/challenge-me.md`](challenge-me.md) and follow its
+   `## Dispatch` verbatim with the same sub-command + flags + seed.
+3. Unknown / missing sub-command → print menu from `challenge-me.md`.
+
+## Rules
+
+- Thin alias — all behaviour, triggers, cost-gate, file-write rules
+  live in [`challenge-me.md`](challenge-me.md) and the routed sub-commands.
+  Do not duplicate them here; edit them there.
+- Suggestion engine surfaces this for free-form "grill me" prompts;
+  `/grill-me` is the direct invocation path.

package/.agent-src/commands/judge/steps.md

@@ -7,7 +7,7 @@ description: Execute an ordered plan step by step with a judge gate between step
 disable-model-invocation: true
 suggestion:
   eligible: false
-  rationale: "Subagent orchestration — overlaps /work and /roadmap-execute; keep explicit."
+  rationale: "Subagent orchestration — overlaps /work and /roadmap:process-*; keep explicit."
 ---
 
 # /judge steps

package/.agent-src/commands/memory/add.md

@@ -115,14 +115,22 @@ link resolves. Broken link → block and ask the user to fix.
 - Duplicate of an existing entry (step 2) — update instead.
 - Missing `source:` — an entry without evidence cannot be reviewed.
 
-## Output format
-
-```
-✅  Added <type>/<id> (confidence: <high|medium|low>)
-   Path: agents/memory/<type>.yml (or agents/memory/<type>/<hash>.yml)
-   Gate: scripts/check_memory.py → PASS
-   Next: commit and link from the relevant skill/command.
-```
+## Output format (verbosity-gated)
+
+Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
+`minimal`).
+
+- `off` → emit nothing on success; surface gate failures only.
+- `minimal` (default) → one line:
+  `✅  Added <type>/<id> (gate: PASS)`.
+- `full` → multi-line block:
+
+  ```
+  ✅  Added <type>/<id> (confidence: <high|medium|low>)
+     Path: agents/memory/<type>.yml (or agents/memory/<type>/<hash>.yml)
+     Gate: scripts/check_memory.py → PASS
+     Next: commit and link from the relevant skill/command.
+  ```
 
 ## See also
 

package/.agent-src/commands/memory/promote.md

@@ -120,15 +120,23 @@ git push -u origin memory/promote-<curated-id>
 # Then route to /create-pr with the memory-promote template hint.
 ```
 
-### 7. Report
-
-```
-> ✅ Promotion drafted.
-> - Signal:   <sig-id>
-> - Curated:  <curated-id> in agents/memory/<type>.yml
-> - PR:       <url or branch name>
-> - Next:     review + merge
-```
+### 7. Report (verbosity-gated)
+
+Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
+`minimal`).
+
+- `off` → emit nothing on success; surface errors only.
+- `minimal` (default) → one line:
+  `→ Promoted <sig-id> → <curated-id> (PR: <url or branch>)`.
+- `full` → multi-line block:
+
+  ```
+  > ✅ Promotion drafted.
+  > - Signal:   <sig-id>
+  > - Curated:  <curated-id> in agents/memory/<type>.yml
+  > - PR:       <url or branch name>
+  > - Next:     review + merge
+  ```
 
 ## Safety
 

package/.agent-src/commands/optimize/rtk.md

@@ -103,17 +103,22 @@ Run a quick test to confirm rtk picks up the filters:
 rtk config 2>&1 | tail -5
 ```
 
-### 7. Present results
-
-Show a summary table:
-
-```
-| # | Filter | Match | Max Lines |
-|---|---|---|---|
-| 1 | phpstan | phpstan\|quality:phpstan\|vendor/bin/phpstan | 80 |
-| 2 | pest | pest\|phpunit\|artisan test | 60 |
-| ... | ... | ... | ... |
-```
+### 7. Present results (verbosity-gated)
+
+Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
+`minimal`).
+
+- `off` → emit nothing on success; surface errors only.
+- `minimal` (default) → one line: `→ N filters configured in .rtk/rtk.toml`.
+- `full` → multi-line summary table:
+
+  ```
+  | # | Filter | Match | Max Lines |
+  |---|---|---|---|
+  | 1 | phpstan | phpstan\|quality:phpstan\|vendor/bin/phpstan | 80 |
+  | 2 | pest | pest\|phpunit\|artisan test | 60 |
+  | ... | ... | ... | ... |
+  ```
 
 ### Rules
 

package/.agent-src/commands/prepare-for-review.md

@@ -80,12 +80,18 @@ Once all merges succeed:
 git checkout {head-branch-of-target-PR}
 ```
 
-### 7. Report
-
-Inform the user:
-- Which branch chain was processed (in order)
-- That the target branch is now checked out and up to date
-- Any warnings (e.g. branch was already up to date)
+### 7. Report (verbosity-gated)
+
+Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
+`minimal`).
+
+- `off` → emit nothing on success; surface warnings/errors only.
+- `minimal` (default) → one line:
+  `→ {branch} ready · {N} branches merged · {warnings or "clean"}`.
+- `full` → multi-line block listing:
+  - Which branch chain was processed (in order)
+  - That the target branch is now checked out and up to date
+  - Any warnings (e.g. branch was already up to date)
 
 ## Rules