@event4u/agent-config 1.18.0 → 1.20.0

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

@@ -28,8 +28,7 @@ The user invoked `/council default` on exactly one input mode:
 - `files:<path>,<path>` — a comma-separated file list
 
 Optional invocation flag: `mode:api|manual` overrides the per-member
-and global mode for this call only (see Step 2.5). `mode:playwright`
-is reserved for Phase 2c — refuse politely if invoked.
+and global mode for this call only (see Step 2.5).
 
 Optional **rounds**: `rounds:N` (1-3) enables multi-round debate. Round
 1 sees the artefact alone. Round 2+ sees the artefact plus anonymised
@@ -71,7 +70,7 @@ Read `.agent-settings.yml` → `ai_council`:
   to env vars. Ever.
 
 Load the price table via `scripts.ai_council.pricing.load_prices()`
-(auto-bootstraps `.agent-prices.md` from defaults if missing). Run
+(auto-bootstraps `agents/.agent-prices.md` from defaults if missing). Run
 `pricing.is_stale(table)` and, if stale, surface the staleness gate
 from the `ai-council` skill (§ Stale price-table gate) before
 continuing.
@@ -81,15 +80,13 @@ continuing.
 For each enabled member, resolve its mode via
 `scripts.ai_council.modes.resolve_mode(name, invocation_mode,
 member_settings, global_mode)`. Precedence: invocation flag >
-per-member setting > global setting > default (`api`).
+per-member setting > global setting > default (`manual`).
 
 Construct each member from the resolved mode:
 
 - `api` → `AnthropicClient` / `OpenAIClient` (billable, cost-gated).
 - `manual` → `ManualClient` from `scripts.ai_council.clients`
   (`billable=False`, no API key, no SDK call).
-- `playwright` → reserved for Phase 2c. If a settings/invocation
-  resolves to it, refuse with a one-line note.
 
 ### 3. Cost confirmation — ALWAYS ASK for billable members
 
@@ -97,71 +94,65 @@ Council calls to billable members spend money. Even under
 `personal.autonomy: on`, the agent **must** ask before invoking any
 billable member.
 
-Compute `orchestrator.estimate(question, members, table)` over the
-**billable** subset only (`getattr(m, "billable", True)`). Manual
-members contribute `$0` and skip the estimate.
+Run the CLI in **estimate** mode first — it bundles the artefact, runs
+redaction, and prints the per-member preview without spending:
 
-Render the cost-confirmation numbered-options block per the
-`ai-council` skill (§ Pre-call estimate format) — per-member tokens
-+ USD, projected total, budget caps, then `1. Run / 2. Cancel`. If
-the resolved member set is **all-manual**, skip the gate entirely
-(spend = $0) and proceed directly to Step 4.
-
-Wait for the user's pick. `1` proceeds; anything else aborts.
-
-### 4. Bundle the context
-
-Use `scripts.ai_council.bundler`:
+```bash
+./agent-config council:estimate <question-file> \
+    [--input-mode prompt|roadmap] \
+    [--max-tokens N] \
+    [--mode-override api|manual] \
+    [--original-ask "<framing sentence>"]
+```
 
-- `prompt` mode → `bundle_prompt(text)`
-- `roadmap` mode → `bundle_roadmap(path)`
-- `diff` mode → `bundle_diff(base, head)`
-- `files` mode → `bundle_files(paths)`
+For `prompt:"<text>"` mode, write the text to a temp file first
+(`mktemp` is fine) and pass that path. For `roadmap:<path>`, pass the
+roadmap file with `--input-mode roadmap`. `diff` and `files` modes
+remain Phase 4 — for now ask the user to convert into a `prompt`.
 
-The bundler runs redaction + size guard. If `BundleTooLarge` raises,
-surface the byte count and ask the user to narrow scope. Do **not**
-truncate silently.
+The CLI prints a `council:estimate · members=N (billable=M)` line
+followed by per-member projected USD and a TOTAL. Render that to the
+user inside the cost-confirmation numbered-options block per the
+`ai-council` skill (§ Pre-call estimate format) — then `1. Run /
+2. Cancel`. If the billable count is `0`, skip the gate entirely
+(spend = $0) and proceed directly to Step 4.
 
-Print the manifest (what was included) and the excluded list before
-sending — gives the user a chance to abort if scope is wrong.
+Wait for the user's pick. `1` proceeds; anything else aborts.
 
-### 5. Run the orchestrator
+### 4. Run the CLI
 
-Members are constructed from the settings file plus
-`load_anthropic_key()` / `load_openai_key()`. Cost budget comes from
-`ai_council.cost_budget`.
+Once the user picks `1`, invoke the same arguments with `run` plus
+`--confirm` and an output path under `agents/council-sessions/`:
 
-Detect project context once via
-`scripts.ai_council.project_context.detect_project_context()` (reads
-`composer.json`, `package.json`, root `README.md` — never raises;
-empty-fields fall back to bare neutrality preamble).
+```bash
+./agent-config council:run <question-file> \
+    --output agents/council-sessions/<UTC-timestamp>.json \
+    --confirm \
+    [--rounds 1|2|3] \
+    [--input-mode …] [--max-tokens …] [--mode-override …] \
+    [--original-ask "<framing sentence>"]
+```
 
-Call:
+The CLI:
 
-```python
-consult(
-    members, question, budget,
-    table=table,
-    on_overrun=_handle_overrun,
-    project=project,
-    original_ask=original_ask,
-    rounds=rounds,  # 1 by default; 2-3 enables multi-round debate
-)
-```
+- 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),
+- detects project context via `detect_project_context()`,
+- calls `orchestrator.consult(...)` with the `cost_budget` from
+  settings,
+- writes the responses JSON to `--output`.
 
-`project` + `original_ask` flow into `handoff_preamble()` so each
-member receives a neutral context-handoff alongside the artefact
-(see `ai-council` skill § Neutrality — context-handoff). Members run
-**sequentially**; per-member errors are normalised — one failure
-does not abort the others. Define `_handle_overrun(event)` per the
-`ai-council` skill (§ Mid-flow overrun callback) to surface the user
-prompt before each breaching member.
+Per-member errors are normalised — one failure does not abort the
+others. Exit code `1` means **all** members errored; `0` means at
+least one succeeded; `2` means the gate refused before any spend.
 
-### 6. Render the report
+### 5. Render the report
 
-Use `scripts.ai_council.orchestrator.render(responses)` for the
-per-member sections (stacked, not side-by-side — narrow terminals).
-Then write the **Convergence / Divergence** section yourself:
+Use `./agent-config council:render <output.json>` for the per-member
+sections (stacked, not side-by-side — narrow terminals). Then write
+the **Convergence / Divergence** section yourself:
 
 - **Agreements** — points all members made (or did not contradict).
 - **Disagreements** — points where members took opposing positions.
@@ -173,49 +164,53 @@ End with a numbered-options block asking the user how to proceed
 (e.g. update the roadmap, request a second round, ignore the
 critique).
 
-### 7. Hard floor — text only
+### 6. Hard floor — text only
 
 `/council` produces **text**. It does **NOT**:
 
 - Edit any file in the project.
 - Open, comment on, or merge any PR.
 - Run `git` commands beyond `git diff` (read-only).
-- Persist API responses outside the current chat unless the user
-  explicitly asks (Phase 4 — out of scope for v1).
 
-This is restated in step 7 deliberately. The neutrality framing
-loses meaning if the council can act on the project directly.
+The CLI persists the responses JSON under `agents/council-sessions/`
+for traceability, but the agent never edits other project files on
+the user's behalf. The neutrality framing loses meaning if the
+council can act on the project directly.
 
 ## Failure modes
 
-- **Member SDK not installed** → tell the user exactly which `pip
-  install` runs (`pip install anthropic` / `pip install openai`).
-  Do not fall back to mocks.
-- **Key file mode drift** → refuse and point at the install script.
+- **CLI exits 2, "ai_council.enabled is false"** → tell the user how
+  to flip it on; 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.
+- **CLI raises `BundleTooLarge`** → surface the byte count and ask the
+  user to narrow scope. Do not truncate silently.
+- **Member SDK not installed** → CLI prints the missing-package
+  message; tell the user exactly which `pip install` runs
+  (`pip install anthropic` / `pip install openai`). Do not fall back
+  to mocks.
+- **Key file mode drift** → CLI refuses; point at the install script.
   The 0600 contract is non-negotiable.
-- **Manual mode + non-interactive stdin** → `ManualClient` reads
-  pasted replies from stdin terminated by a line containing only
-  `END`. If stdin is closed before any reply lands, the member
-  returns empty text with `error="manual_aborted"`; render the
-  partial result and ask the user.
-- **Invalid mode value** → `resolve_mode()` raises
-  `InvalidModeError` with the exact settings path. Surface verbatim
-  and stop.
-- **Cost budget exceeded mid-fan-out** → render the partial
-  responses and clearly mark the unfinished members with their
-  `cost_budget_exceeded` error. Do not silently retry.
+- **Invalid mode value** → CLI surfaces `InvalidModeError` with the
+  exact settings path. Surface verbatim and stop.
+- **Cost budget exceeded mid-fan-out** → render the partial responses
+  and clearly mark unfinished members with `cost_budget_exceeded`. Do
+  not silently retry.
 - **Stale price table, refresher fails (offline)** → state the
   failure, re-offer "continue with stale table / cancel", do not
   proceed silently.
-- **`.agent-prices.md` corrupt (missing frontmatter or columns)** →
+- **`agents/.agent-prices.md` corrupt (missing frontmatter or columns)** →
   surface the parse error, suggest deleting the file to bootstrap
   fresh from defaults; never silently fall back.
-- **All members error** → render the errors and ask the user
-  whether to fix and retry, or abort.
+- **All members error (CLI exit 1)** → render the errors via
+  `council:render` and ask the user whether to fix and retry, or
+  abort.
 
 ## See also
 
 - `/council` — cluster dispatcher.
 - `ai-council` skill — neutrality guidelines, anti-patterns, redaction expectations.
 - `subagent-orchestration` skill — internal multi-agent variant (no network calls).
+- `scripts/council_cli.py` — the CLI entry point this command wraps.
 - `docs/customization.md` § Available settings → `ai_council.*`.

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

@@ -106,19 +106,39 @@ Once the user approves the content from step 2:
 
 ### 4. After creation
 
-- Show the PR URL.
-- If a Jira ticket was linked, ask:
-  ```
-  > Transition Jira ticket {TICKET-ID} to "In Review"?
-  >
-  > 1. Yes — update status
-  > 2. No — leave as-is
-  ```
+#### 4a. Strip attribution footers (mandatory)
+
+`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**:
+
+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").
+
+#### 4b. Show the PR URL
+
+#### 4c. Jira transition
+
+If a Jira ticket was linked, ask:
+```
+> Transition Jira ticket {TICKET-ID} to "In Review"?
+>
+> 1. Yes — update status
+> 2. No — leave as-is
+```
 
 ### 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.

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

@@ -111,6 +111,28 @@ For each roadmap, work through the phases interactively:
 - Single: `agents/roadmaps/{feature-name}.md`
 - Multiple: `agents/roadmaps/{feature-name}-{aspect}.md`
 
+**Collision check before writing.** For each planned filename, scan
+the entire roadmap namespace — active, `archive/`, `skipped/`, and
+nested subdirs:
+
+```bash
+find agents/roadmaps -type f -iname "{feature-name}.md" 2>/dev/null
+# Module-scoped:
+find app/Modules/{Module}/agents/roadmaps -type f -iname "{feature-name}.md" 2>/dev/null
+```
+
+If any planned name already exists anywhere under the namespace,
+**STOP** and ask (in the user's language):
+
+> Filename `{feature-name}.md` already exists at `<path>` (archived/skipped/active).
+>
+> 1. Pick a different name — suggest `{feature-name}-v2` or `{feature-name}-{scope}`
+> 2. Open the existing roadmap first — revival or extension may fit
+> 3. Abort
+
+Re-run the check after a rename. Never silently overwrite, never
+auto-suffix without the user's pick.
+
 ### 5. Link roadmaps in the feature plan
 
 Update the feature file's `## Roadmaps` section:

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

@@ -92,8 +92,40 @@ Show the complete roadmap to the user and ask (in their language) if anything sh
 ### 6. Save the file
 
 - Generate a filename from the title: kebab-case, e.g. `optimize-webhook-jobs.md`.
-- Save to the chosen location.
-- Show the final path.
+
+**Before saving, check for filename collisions across the entire
+roadmap namespace** — active, `archive/`, `skipped/`, and any nested
+subdirs (e.g. `agent-memory/`). A new roadmap that shadows an
+archived or skipped one silently buries history; never overwrite,
+never auto-suffix without the user's pick.
+
+```bash
+NAME="<kebab-case-name>.md"
+# Project-root roadmaps:
+find agents/roadmaps -type f -iname "$NAME" 2>/dev/null
+# Module-scoped roadmaps (only if step 1 picked a module):
+find app/Modules/<Module>/agents/roadmaps -type f -iname "$NAME" 2>/dev/null
+```
+
+Use `-iname` (case-insensitive) so case-only differences still count
+as a collision on case-sensitive filesystems.
+
+If the search returns one or more hits → **STOP**. Show the matches
+and ask (in the user's language):
+
+> Found N existing roadmap(s) with this name:
+>   - `agents/roadmaps/archive/<file>.md` (archived)
+>   - `agents/roadmaps/skipped/<file>.md` (skipped)
+>
+> 1. Pick a different name — suggest `<name>-v2`, `<name>-<scope>`, or `<name>-<YYYY-MM>`
+> 2. Open the existing file first — revival or extension may be the right move
+> 3. Abort creation
+
+- **1** → re-prompt for name, re-run the collision check, repeat until clean.
+- **2** → read the existing roadmap, summarize state, hand back to the user.
+- **3** → stop without writing anything.
+
+Only when the search is empty: save to the chosen location and show the final path.
 
 ### 7. Update the progress dashboard
 
@@ -150,12 +182,12 @@ If yes → switch to the `roadmap-execute` command workflow with the newly creat
   violates [`roadmap-progress-sync`](../rules/roadmap-progress-sync.md)
   Iron Law #2.
 - **Status is binary: `ready` (default) or `draft`.** Create new
-  roadmaps as **ready** — no `status:` field needed, ready is
-  implicit. Only mark `status: draft` (in YAML frontmatter) when the
+  roadmaps as **ready** — no `status:` field needed.
+  Only mark `status: draft` (in YAML frontmatter) when the
   user explicitly says it should be hidden from the dashboard (still
   being authored, awaiting upstream decisions, capture-only synthesis
   without executable phases). If the user wants draft, ask once at
   step 3 — do not infer it.
-- **Write the roadmap in English** (per project convention for `.md` files).
-- Follow the roadmap template from `.augment/templates/roadmaps.md`.
+- Follow the roadmap template from `.augment/templates/roadmaps.md`; write in English (project convention).
 - Keep the file focused: 500–1000 lines max. If larger, suggest splitting.
+- **Never overwrite an existing roadmap.** Step 6 scans `active/`, `archive/`, `skipped/` (+ subdirs); on collision → STOP, present rename / open / abort. Auto-suffix requires explicit pick.

package/.agent-src/commands/roadmap/execute.md

@@ -33,7 +33,26 @@ suggestion:
   > "Phase 2: {name} — noch nicht begonnen"
   > "Next open step: {step description}"
 
-### 3. Execute step by step
+### 3. Resolve quality cadence (read once, before any step runs)
+
+Read `roadmap.quality_cadence` from `.agent-settings.yml`:
+
+| Value | When the project's quality pipeline runs |
+|---|---|
+| `end_of_roadmap` (default) | Once, in step 7 — before archiving |
+| `per_phase` | Once after every completed phase, plus step 7 |
+| `per_step` | After every completed step, plus step 7 (legacy verbose) |
+
+Missing key, unreadable file, or unknown value → fall back to `end_of_roadmap`.
+Cite the resolved cadence once in step 2's summary so the user can override it.
+
+The Iron Law `verify-before-complete` still applies — fresh quality
+output is mandatory before any "roadmap complete" claim, regardless of
+cadence. Step checkboxes and `agents/roadmaps-progress.md` are ALWAYS
+updated in the same response per `roadmap-progress-sync`; cadence only
+gates the *quality pipeline*, not progress tracking.
+
+### 4. Execute step by step
 
 For each open step:
 
@@ -41,28 +60,35 @@ For each open step:
 2. **Analyze** the codebase to understand what's needed for this step.
 3. **Present a plan** — what files to change, what approach to take.
 4. **Ask for confirmation**: "Should I implement this step?"
-   - If yes → implement, run quality checks, mark step as done in the roadmap file.
+   - If yes → implement, mark the step `[x]` in the roadmap file.
    - If no / skip → move to the next step.
    - If the user wants to stop → stop and summarize progress.
 
-### 4. After each step
+### 5. After each step
 
-- Update the roadmap file: mark the completed step (e.g. `[x]` or add a completion note).
-- Run quality tools if code was changed (PHPStan at minimum).
+- Update the roadmap file: mark the completed step `[x]` (or `[~]` / `[-]`).
 - Regenerate `agents/roadmaps-progress.md` — `./agent-config roadmap:progress`.
+- **Quality pipeline** — run only when `quality_cadence: per_step`.
+  Otherwise skip and proceed.
 - Ask: "Continue with the next step?"
 
-### 5. After all steps in a phase
+### 6. After all steps in a phase
 
 - Summarize what was accomplished in the phase.
+- **Quality pipeline** — run when `quality_cadence: per_phase` (or `per_step`).
+  Skip when `end_of_roadmap`.
 - Ask: "Phase {N} complete. Continue with Phase {N+1}?"
 
-### 6. When done (or stopped)
+### 7. When done (or stopped)
 
 - Summarize total progress: steps completed, steps remaining.
 - Update the roadmap file with the current status.
 - Regenerate the dashboard one last time so it matches the final state.
-- **If ALL steps are done** → trigger the completion & archiving workflow from the `roadmap-management` skill.
+- **If ALL steps are done** → run the project's quality pipeline now
+  (this is the `verify-before-complete` evidence gate; required for
+  every cadence value, including `end_of_roadmap`). On green, trigger
+  the completion & archiving workflow from the `roadmap-management`
+  skill. On red, stop, surface the failures, do not archive.
 
 ### Rules
 
@@ -77,6 +103,7 @@ For each open step:
       to execute the listed commit steps, then proceed silently per the answer.
 - **Push, merge, branch, PR, tag** stay permission-gated by [`scope-control`](../rules/scope-control.md#git-operations--permission-gated).
 - **Always ask before implementing** a step — never auto-execute.
-- **Run quality checks** after each code change.
+- **Quality cadence** is set by `roadmap.quality_cadence` (see step 3).
+  Step 7 always runs the pipeline before archival regardless of cadence.
 - If a step is unclear or too large, suggest breaking it down further.
 - If a step reveals a problem not covered in the roadmap, flag it to the user.

package/.agent-src/commands/sync-gitignore.md

@@ -11,7 +11,7 @@ suggestion:
 
 Ensures the consumer project's `.gitignore` contains every entry the
 package expects to be ignored (symlinked `.augment/` subdirectories,
-`/agent-config` CLI wrapper, `.agent-settings*`, `.agent-chat-history*`).
+`/agent-config` CLI wrapper, `.agent-settings*`, `agents/.agent-chat-history*`).
 Canonical list lives in `config/gitignore-block.txt`; the same file
 drives the installer, so the two cannot drift.
 

package/.agent-src/contexts/communication/rules-auto/skill-quality-mechanics.md

@@ -60,3 +60,79 @@ Compression may remove:
 - Verbose explanations
 - Redundant examples (keep the strongest)
 - Commentary that doesn't affect execution
+
+## Senior-tier patterns
+
+Detail spec for the four blocks the [`skill-quality`](../../../rules/skill-quality.md)
+rule requires on `tier: senior` skills. Each block ≤ 6-line spec + 1
+reference pattern. Forward-only — applies to new senior-tier skills,
+no retrofit on existing Wing-1 skills.
+
+### 1. Context-First lead (description)
+
+Two-sentence frontmatter `description`. First sentence: cognition
+cluster anchor — name the domain + the senior role's stance. Second
+sentence: the trigger — what the user types that should fire this.
+
+Pattern:
+
+```
+description: "Use when {trigger paraphrase}. {Domain} cognition for the
+{senior role} — produces {artifact name}."
+```
+
+Anti-pattern: leading with the artifact ("Produces a DCF model …") —
+buries the cognition cluster, undertriggers on cluster-shaped prompts.
+
+### 2. Related Skills (`## Related Skills`)
+
+Two named lists, no ambiguity:
+
+```markdown
+## Related Skills
+
+**WHEN to use this**
+- {situation A this skill resolves better than {peer-1}}
+- {situation B}
+
+**WHEN NOT to use this**
+- {situation C} — route to [`{peer-1}`](../{peer-1}/SKILL.md)
+- {situation D} — route to [`{peer-2}`](../{peer-2}/SKILL.md)
+```
+
+WHEN-NOT entries MUST name the peer and link it. Naming without a
+link drifts the moment the peer renames.
+
+### 3. Proactive Triggers (`## When the agent should load this`)
+
+3–5 concrete user-prompt patterns the agent watches for. Concrete =
+phrases users actually type, not abstract categories.
+
+```markdown
+## When the agent should load this
+
+- "should we build feature X or Y first" → opportunity-tree shaped
+- "what's the ICE / RICE on this backlog" → prioritization shaped
+- "how do I split this epic into shippable slices" → INVEST shaped
+```
+
+Anti-pattern: abstract categories ("prioritization questions",
+"product-shaped requests") — the routing layer matches phrases, not
+taxonomies.
+
+### 4. Output Artifacts (`## Output`)
+
+1–4 named artifacts with concrete shape. Each entry: name +
+shape-hint the orchestrator can cite by name in a handoff.
+
+```markdown
+## Output
+
+1. **opportunity-tree.md** — markdown tree, root = north-star metric,
+   leaves = candidate solutions with hypothesis + evidence rank
+2. **prioritization-table.md** — markdown table, columns =
+   {opportunity, ICE score, evidence-grade, owner, next-step}
+```
+
+Anti-pattern: prose summary ("a doc explaining the prioritization") —
+no orchestrator-citable identifier, no shape contract.

package/.agent-src/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md

@@ -15,7 +15,7 @@ this file mirrors that contract for runtime lookup. Linter:
 | `/fix` | 1 | `ci` · `pr` · `pr-bots` · `pr-developers` · `portability` · `refs` · `seeder` | `/fix-ci` · `/fix-pr-comments` · `/fix-pr-bot-comments` · `/fix-pr-developer-comments` · `/fix-portability` · `/fix-references` · `/fix-seeder` |
 | `/optimize` | 1 | `agents` · `augmentignore` · `rtk` · `skills` | `/optimize-agents` · `/optimize-augmentignore` · `/optimize-rtk-filters` · `/optimize-skills` |
 | `/feature` | 1 | `explore` · `plan` · `refactor` · `roadmap` | `/feature-explore` · `/feature-plan` · `/feature-refactor` · `/feature-roadmap` |
-| `/chat-history` | 2 | `show` · `resume` · `clear` · `checkpoint` | `/chat-history` (legacy status) · `/chat-history-resume` · `/chat-history-clear` · `/chat-history-checkpoint` |
+| `/chat-history` | 2 | `show` | `/chat-history` (legacy status) — `resume` / `clear` / `checkpoint` removed in `road-to-chat-history-hook-only` |
 | `/agents` | 2 | `audit` · `cleanup` · `prepare` | `/agents-audit` · `/agents-cleanup` · `/agents-prepare` |
 | `/memory` | 2 | `add` · `load` · `promote` · `propose` | `/memory-add` · `/memory-full` · `/memory-promote` · `/propose-memory` |
 | `/roadmap` | 2 | `create` · `execute` | `/roadmap-create` · `/roadmap-execute` |
@@ -25,8 +25,8 @@ this file mirrors that contract for runtime lookup. Linter:
 | `/override` | 2 | `create` · `manage` | `/override-create` · `/override-manage` |
 | `/copilot-agents` | 2 | `init` · `optimize` | `/copilot-agents-init` · `/copilot-agents-optimize` |
 | `/judge` | 2 | `solo` · `on-diff` · `steps` | `/judge` (legacy standalone) · `/do-and-judge` · `/do-in-steps` |
-| `/commit` | 2 | flag: `--in-chunks` | `/commit-in-chunks` |
-| `/create-pr` | 2 | flag: `--description-only` | `/create-pr-description` |
+| `/commit` | 2 | flag: `--in-chunks` | `/commit:in-chunks` |
+| `/create-pr` | 2 | flag: `--description-only` | `/create-pr:description-only` |
 
 ## Routing semantics
 

package/.agent-src/contexts/communication/rules-auto/user-interaction-mechanics.md

@@ -1,17 +1,10 @@
 # User Interaction — mechanics
 
-Format examples, common failure modes, progress indicators, and
-summary patterns for the [`user-interaction`](../../../rules/user-interaction.md)
-rule. Iron Law 1 (single-source recommendation) and Iron Law 2
-(pre-send self-check) live in the rule; this file is the lookup
-material for the format details.
-
-## Common failure modes — known, named, no excuses
-
-- **End-of-turn menu skipped.** Reply answers the question fine, then ends with `> 1. Foo > 2. Bar > 3. Stop` and no `Empfehlung:`. Iron Law 1 was violated — these are numbered options, position is irrelevant.
-- **"Genuinely no preference" hedge.** Pick anyway. The agent has more context than the user on the trade-off; refusing to pick dumps the work back. Pick the safest option, name the flip-condition.
-- **"User knows the project better" hedge.** Same failure mode, different costume. The user asked for an opinion by virtue of accepting the options block; deliver it.
-- **Multi-block reply with one recommendation.** Two options blocks but only one `Empfehlung:` line — the second block is unguarded. Rule 5 of Iron Law 2 closes this.
+Format examples, progress indicators, and summary patterns for the
+[`user-interaction`](../../../rules/user-interaction.md) rule. Iron
+Law 1 (single-source recommendation), Iron Law 2 (pre-send
+self-check), and the named failure-mode catalog live in the rule
+itself; this file is the lookup material for the format details.
 
 ## Examples
 

package/.agent-src/rules/agent-authority.md

@@ -1,5 +1,6 @@
 ---
 type: "always"
+tier: "3"
 description: "Priority Index for the four authority rules — Hard Floor → Permission Gate → Commit Default → Trivial-vs-Blocking; read first, route to canonical rule"
 alwaysApply: true
 source: package

package/.agent-src/rules/agent-docs.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 description: "Reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md"
 source: package
 ---

package/.agent-src/rules/analysis-skill-routing.md

@@ -1,5 +1,6 @@
 ---
 type: auto
+tier: "3"
 description: "When choosing an analysis skill, route to the narrowest matching skill instead of defaulting to broad analysis"
 source: package
 ---

package/.agent-src/rules/architecture.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "3"
 alwaysApply: false
 description: "Architecture rules for creating new files, classes, controllers, modules, or making structural decisions about project organization"
 source: package

package/.agent-src/rules/artifact-drafting-protocol.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "2a"
 alwaysApply: false
 description: "Creating a new skill, rule, command, or guideline, or significantly rewriting one — runs a mandatory Understand → Research → Draft sequence before any artifact content is written."
 source: package

package/.agent-src/rules/artifact-engagement-recording.md

@@ -1,5 +1,6 @@
 ---
 type: "auto"
+tier: "mechanical-already"
 alwaysApply: false
 description: "After a /implement-ticket or /work phase-step (refine/memory/analyze/plan/implement/test/verify/report) or full task — emit one telemetry:record call with consulted+applied ids when enabled"
 source: package

package/.agent-src/rules/ask-when-uncertain.md

@@ -1,5 +1,6 @@
 ---
 type: "always"
+tier: "3"
 description: "Ask when uncertain — don't guess, assume, or improvise"
 alwaysApply: true
 source: package