@event4u/agent-config 1.22.0 → 1.23.0

package/.agent-src/commands/agents/cleanup.md

@@ -145,30 +145,44 @@ After each action:
 
 Progress Phase {n}: [{completed}/{total}]
 ██████████░░░░░░ 60%
-
-> 1. Continue with next action
-> 2. Stop here
 ```
 
-### 5. Summary
+Per `verbosity.routine_confirmations` (default `false`):
 
-After completing a phase or all actions:
+- `false` → continue to the next action silently. User can interrupt
+  any time; "continue" is dominant once cleanup is in flight.
+- `true` → ask:
+  ```
+  > 1. Continue with next action
+  > 2. Stop here
+  ```
 
-```
-═══════════════════════════════════════════════
-  ✅  CLEANUP SUMMARY
-═══════════════════════════════════════════════
+### 5. Summary (verbosity-gated)
 
-  📁 Moved:     {count} files
-  🔗 Merged:    {count} files
-  🗑️  Deleted:   {count} files
-  ✏️  Updated:   {count} files
-  📄 Created:   {count} contexts
+After completing a phase or all actions, read
+`verbosity.post_action_reports` from `.agent-settings.yml` (default
+`minimal`).
 
-  Remaining:        {count} actions in {phases} phases
+- `off` → emit nothing on success; surface errors only.
+- `minimal` (default) → one line:
+  `→ Cleanup: {moved} moved · {deleted} deleted · {updated} updated · {remaining} remaining`.
+- `full` → multi-line block:
 
-═══════════════════════════════════════════════
-```
+  ```
+  ═══════════════════════════════════════════════
+    ✅  CLEANUP SUMMARY
+  ═══════════════════════════════════════════════
+
+    📁 Moved:     {count} files
+    🔗 Merged:    {count} files
+    🗑️  Deleted:   {count} files
+    ✏️  Updated:   {count} files
+    📄 Created:   {count} contexts
+
+    Remaining:        {count} actions in {phases} phases
+
+  ═══════════════════════════════════════════════
+  ```
 
 ### Rules
 

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

@@ -63,7 +63,16 @@ Splitting rules:
 
 Generate commit messages per [`commit-conventions`](../../rules/commit-conventions.md).
 
-### 4. Commit immediately
+### 4. Validate, then commit immediately
+
+Before staging anything, run the same `preview-on-error` validator as
+[`/commit`](../commit.md) step 5. Each generated message must match
+`^(feat|fix|chore|docs|refactor|test|perf|style|build|ci|revert)(\([^)]+\))?!?: .+`.
+
+- **All valid** → proceed silently.
+- **Any invalid** → stop, print the failed message(s) + the regex,
+  hand back to the user. Do **not** auto-commit broken messages even
+  though confirmation is otherwise suppressed.
 
 For each planned commit in order:
 
@@ -75,18 +84,29 @@ git commit -m "{message}"
 No "looks good?" prompt. No confirmation step. The user invoked this
 command knowing the plan would be executed.
 
-### 5. Report
+### 5. Report (verbosity-gated)
 
-Show a summary:
+Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
+`minimal`). Same contract as [`/commit`](../commit.md) step 7.
 
-```
-Created N commits:
-1. {sha1}  feat(DEV-1234): {summary}
-2. {sha2}  test(DEV-1234): {summary}
-3. {sha3}  chore: {summary}
-```
+- `off` → emit nothing (still run `git log --oneline -N` silently for
+  the agent's own verification).
+- `minimal` (default) → one line:
+
+  ```
+  → N commits created
+  ```
+
+- `full` → full summary:
+
+  ```
+  Created N commits:
+  1. {sha1}  feat(DEV-1234): {summary}
+  2. {sha2}  test(DEV-1234): {summary}
+  3. {sha3}  chore: {summary}
+  ```
 
-Include `git log --oneline -N` output for verification.
+  Include `git log --oneline -N` output for verification.
 
 ## Rules
 

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

@@ -79,7 +79,33 @@ Rules for splitting:
 - **Style-only changes** (ECS/Rector formatting) may get their own `style:` or `chore:` commit
   if they are large and mixed with logic changes.
 
-### 5. Present the commit plan
+### 5. Present the commit plan (verbosity-gated)
+
+Read `verbosity.preview_artifacts` and `verbosity.routine_confirmations`
+from `.agent-settings.yml`. Both default to `false`.
+
+**Terse path** — `preview_artifacts: false` AND `routine_confirmations: false`:
+
+1. Validate every generated commit message against the
+   conventional-commits regex
+   `^(feat|fix|chore|docs|refactor|test|perf|style|build|ci|revert)(\([^)]+\))?!?: .+`.
+2. **All messages valid** → skip the preview block and the confirmation
+   prompt. Print one line summarising the plan and proceed to step 6:
+
+   ```
+   → 3 commits planned: feat, test, chore (scope: DEV-1234)
+   ```
+
+3. **Any message invalid** → `preview-on-error` safety net fires:
+   force the full preview block below + the numbered confirm prompt,
+   regardless of the two flags. The user must approve before step 6.
+4. **Hard-Floor diff** (bulk deletion ≥5 unrelated files, infra changes
+   touching Terraform / Pulumi / k8s / Ansible / cloud-config) →
+   ALWAYS preview + confirm regardless of flags, per
+   [`non-destructive-by-default`](../rules/non-destructive-by-default.md).
+
+**Preview path** — `preview_artifacts: true` OR `routine_confirmations: true`
+(or `preview-on-error` triggered):
 
 Show the proposed commits as a numbered list, including which files go into each:
 
@@ -107,19 +133,33 @@ Then ask:
 
 Wait for the user's response before doing anything.
 
+**Override:** the user may force the preview at any time with
+*"show me the commit plan first"* / *"preview commits"* — treat as a
+one-shot `preview_artifacts: true` for this invocation.
+
 ### 6. Commit
 
-Only after the user confirms (option 1):
+On the **terse path** proceed directly. On the **preview path** only after
+the user confirms (option 1).
 
 For each planned commit in order:
 1. Stage only the files for that commit: `git add {files...}`
 2. Commit: `git commit -m "{message}"`
 
-### 7. Report
+### 7. Report (verbosity-gated)
+
+Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
+`minimal`).
+
+- `off` → emit nothing.
+- `minimal` (default) → one line:
+
+  ```
+  → 3 commits created
+  ```
 
-Show a summary:
-- Number of commits created
-- Commit messages (one per line)
+- `full` → multi-line summary: number of commits + commit messages
+  (one per line).
 
 ## Rules
 

package/.agent-src/commands/compress.md

@@ -50,18 +50,18 @@ For each changed `.md` file:
      pleasantries, hedging, connective fluff (however, furthermore, additionally),
      redundant wording, obvious framework knowledge, repeated explanations, decorative prose
    - **Shorten:** "in order to" → "to", "make sure to" → "ensure", use short synonyms
-   - **Abbreviate** common terms when context unambiguous: `DB`, `auth`,
-     `config`, `req`, `res`, `fn`, `impl`, `env`, `deps`, `ctx`. Skip on
-     first occurrence of the concept in the file, or when the
-     abbreviation collides with a domain term (`auth` stays
-     `authentication` inside an auth-module file). Never abbreviate
-     inside code blocks, frontmatter, file paths, command strings, or
-     Iron Law fenced blocks.
+   - **Abbreviate** common terms when context is unambiguous: `DB`, `auth`,
+     `config`, `req`, `res`, `fn`, `impl`, `env`, `deps`, `ctx`. Skip if it
+     would be the first occurrence of the concept in the file, or if the
+     abbreviation collides with a domain term (e.g. `auth` stays
+     `authentication` inside an auth-module file). Never abbreviate inside
+     code blocks, frontmatter, file paths, command strings, or Iron Law
+     fenced blocks.
    - **Arrows for causality:** `X causes Y` / `X leads to Y` / `X, then Y`
-     → `X → Y`. Keep arrows out of code blocks, frontmatter, and Iron
-     Law fenced blocks; surrounding prose only. (Example phrases
-     backticked on purpose — inline-code protection skips them; never
-     strip the backticks.)
+     → `X → Y`. Keep arrows out of code blocks, frontmatter, and Iron Law
+     fenced blocks; only the surrounding prose uses them. (The example
+     phrases here are intentionally backticked so the inline-code
+     protection skips them — never strip those backticks.)
    - **Fragments OK:** "Run tests before commit" not "You should always run tests before committing"
    - **Drop:** "you should", "make sure to", "remember to" — state action directly
    - **Merge** redundant bullets that say the same thing differently
@@ -142,9 +142,15 @@ python3 scripts/check_compression.py
 Must show **zero 🔴 errors**. Warnings (🟡) are acceptable.
 If any 🔴 errors remain: go back and fix those files before finishing.
 
-## Step 5: Summary
+## Step 5: Summary (verbosity-gated)
 
-Show a summary table with per-category stats (files compressed, avg savings).
+Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
+`minimal`).
+
+- `off` → emit nothing on success; surface errors only.
+- `minimal` (default) → one line: `→ N files compressed (avg X% savings)`.
+- `full` → multi-line table with per-category stats (files compressed,
+  avg savings).
 
 ## Hash management
 

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/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

@@ -55,94 +55,109 @@ fallback structure defined in `/create-pr:description-only`. NEVER invent a cust
 **Preview gate** — read `commands.create_pr.preview_description` from
 `.agent-settings.yml` (default `false` when unset):
 
-- `false` (default): skip Steps 5–6 of `/create-pr:description-only` (preview + adjust loop). Use the generated title and body directly in Step 3. Saves tokens; user can still edit in the GitHub UI after creation.
-- `true`: run Steps 5–6 — present title and body as copyable blocks and ask for adjustments before proceeding.
-
-### 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}
-  ```
+- `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.
 
-### 4. After creation
+### 2b. Council review — explicitly excluded
 
-#### 4a. Strip attribution footers (mandatory)
+`/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.
 
-`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**:
+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.
 
-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").
+### 3. Create the PR (draft-vs-ready, verbosity-gated)
 
-#### 4b. Show the PR URL
+- **Head branch**: EXACT output of `git branch --show-current` from step 1.
+- **Base branch**: default branch (`main` / `master`).
 
-#### 4c. Jira transition
+**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).
 
-If a Jira ticket was linked, ask:
-```
-> Transition Jira ticket {TICKET-ID} to "In Review"?
->
-> 1. Yes — update status
-> 2. No — leave as-is
+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.
-- **Preview before creating is opt-in** — controlled by `commands.create_pr.preview_description` in `.agent-settings.yml` (default `false`). When `false`, bare `/create-pr` uses the generated description directly without a chat preview to save tokens. When `true`, title and body are previewed and the user can adjust before creation. `/create-pr:description-only` always previews — that is its sole purpose.
-- **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/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