@event4u/agent-config 1.19.0 → 1.21.0

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

@@ -3,64 +3,18 @@ type: "auto"
 tier: "2a"
 description: "Keeping .augment/ contexts, counts, and cross-references in sync when creating, renaming, or deleting skills, commands, rules, guidelines, templates, or any agent infrastructure files"
 source: package
-load_context:
-  - .agent-src.uncompressed/contexts/communication/rules-auto/docs-sync-mechanics.md
+triggers:
+  - path_prefix: ".agent-src.uncompressed/"
+  - path_prefix: ".augment/"
+  - keyword: "rename"
+  - keyword: "delete"
+routes_to:
+  - "skill:agent-docs-writing"
 ---
 
 # Docs Sync
 
-## Rule
+**Iron Law.** On any add / rename / delete of skill / rule / command / guideline, update counts and cross-references in the same edit.
 
-**CRITICAL — ZERO TOLERANCE:** When a file in `.augment/` is **created, renamed, or deleted**,
-or its **name, description, scope, or counts change**, all related files **must be updated
-in the same response** — not later, not in a follow-up, not when reminded.
-
-A new rule/skill/command without its index entry, count update, and context update is **incomplete work**.
-
-**Mandatory sequence when creating/deleting any `.augment/` file:**
-1. Create/delete the file
-2. **Immediately** update `contexts/augment-infrastructure.md` (counts + category tables)
-3. Check cross-references in contexts and routing hints (inline "see X skill" references)
-4. If a **skill** was added/renamed/deleted: update distribution manifests
-5. If a **hook** was added/renamed/deleted: update hook registries
-6. If **content** changed: run the consistency grep across other artefacts
-
-Steps 2–6 are NOT optional. Do NOT present the result to the user until all steps are done.
-
-**Two modes:**
-- **Reactive** (automatic): Triggered by add/remove/rename or scope/description/count changes → sync counts, contexts, cross-references, manifests, registries.
-- **Proactive** (on demand): Full audit → find duplicates, thin skills, redundancy, stale content → fix or merge. Ask before destructive actions.
-
-## Settings template sync
-
-When a skill, rule, or command **reads a new setting** from `.agent-settings.yml` that does not yet
-exist in `.augment/templates/agent-settings.md`:
-
-1. **Add the key** with its default value to the template block.
-2. **Add a row** to the Settings Reference table.
-3. **Add a comment** above the key explaining what it does.
-4. **Update the local `.agent-settings.yml`** — add the new key with its default value.
-   Preserve all existing values, apply template order and comments. Follow the
-   [section-aware merge rules](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
-   so the user benefits immediately without running a separate command.
-
-**This step is mandatory.** If the template gains a new key but the local `.agent-settings.yml`
-is not updated, the user cannot discover the new setting exists.
-
-## Lookup tables and details — see mechanics
-
-The exact "what to update" tables, cross-reference targets,
-distribution-manifest update tables (`marketplace.json` etc.), hook
-registry update tables (`__init__.py`, consumer-settings JSON), the
-failure mode that motivated the manifest section, and the content
-consistency `grep` snippet all live in
-[`contexts/communication/rules-auto/docs-sync-mechanics.md`](../contexts/communication/rules-auto/docs-sync-mechanics.md).
-Pull it whenever a sync trigger fires.
-
-## Do NOT
-
-- Do NOT rewrite entire files — only update the affected entries.
-- Do NOT ask the user for permission — this is an automatic maintenance step, like updating imports.
-- Do NOT skip cross-reference updates — stale links are worse than no links.
-- Do NOT present a new `.augment/` file to the user without having completed all sync steps first.
-- Do NOT defer sync to a "follow-up" — it must happen in the same response as the creation/deletion.
+Body migrated to `skill:agent-docs-writing` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/downstream-changes.md

@@ -4,6 +4,11 @@ tier: "2b"
 alwaysApply: false
 description: "After EVERY code edit, find ALL downstream changes needed to existing files, including callers, tests, imports, types, and documentation"
 source: package
+triggers:
+  - intent: "after code edit"
+  - keyword: "callers"
+  - keyword: "imports"
+  - keyword: "downstream"
 ---
 
 # Downstream Changes

package/.agent-src/rules/e2e-testing.md

@@ -1,54 +1,19 @@
 ---
 type: "auto"
 tier: "3"
-alwaysApply: false
 description: "Playwright E2E tests — locators, assertions, Page Objects, fixtures, CI, and flaky test prevention"
 source: package
+triggers:
+  - keyword: "playwright"
+  - keyword: "e2e"
+  - phrase: "page object"
+routes_to:
+  - "command:e2e-heal"
 ---
 
 # E2E Testing
 
-## Before writing E2E tests
+**Iron Law.** Playwright E2E: stable locators, no `waitForTimeout`, Page Objects for shared flows, fixtures over `beforeEach`.
 
-1. **Read the guideline** — `../../docs/guidelines/e2e/playwright.md` for all conventions and patterns.
-2. **Check existing tests** — match the project's structure, fixtures, and Page Object patterns.
-3. **Check `playwright.config.ts`** — base URL, browsers, timeouts, projects.
-
-## Locator rules
-
-- **Always prefer semantic locators**: `getByRole` > `getByLabel` > `getByText` > `getByTestId` > CSS.
-- Never use auto-generated class names, dynamic IDs, or XPath.
-- If no semantic locator works, add a `data-testid` to the component.
-
-## Assertion rules
-
-- **Always use web-first assertions** (`toBeVisible`, `toHaveText`, `toHaveURL`).
-- Never use `expect(await ...)` pattern — it doesn't auto-retry.
-- Never use `page.waitForTimeout()` — wait for a condition instead.
-
-## Test structure rules
-
-- One test = one user workflow or behavior.
-- Tests must be **fully isolated** — no shared state, no execution order dependency.
-- Page Objects contain **actions only**, never assertions.
-- Use **fixtures** for reusable setup (auth, page objects, test data).
-- Use **API calls** for test data setup — faster and more reliable than UI interactions.
-
-## CI rules
-
-- Set `workers: 1` in CI for stability.
-- Set `retries: 2` in CI, `0` locally.
-- Set `forbidOnly: !!process.env.CI` to prevent `.only` in CI.
-- Collect `trace: 'on-first-retry'` — not on every run.
-- Only install browsers you need (`npx playwright install chromium --with-deps`).
-- Upload `playwright-report/` as CI artifact.
-
-## Quality checks
-
-Before claiming E2E tests are complete:
-
-1. All tests pass locally: `npx playwright test`
-2. No `waitForTimeout` calls in the code.
-3. No CSS/XPath selectors where semantic locators work.
-4. No `.only` left in test files.
-5. Page Objects have no assertions.
+Body migrated to `command:e2e-heal` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

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

@@ -4,88 +4,26 @@ tier: "3"
 description: "Writing or reviewing code — check relevant guideline before writing or reviewing code"
 alwaysApply: false
 source: package
+load_context:
+  - ../contexts/communication/rules-auto/guidelines-mechanics.md
+triggers:
+  - intent: "writing code"
+  - intent: "reviewing code"
+  - keyword: "convention"
 ---
 
 # Guidelines
 
-Coding guidelines live in `.augment/guidelines/` organized by language.
-**Always check the relevant guideline** before writing or reviewing code.
-
-## Available Guidelines
-
-### PHP (`../../docs/guidelines/php/`)
-
-| File | Topic |
-|---|---|
-| `php.md` | General PHP style — strict types, naming, comparisons, early returns, JSON handling |
-| `controllers.md` | Thin controllers, single responsibility, delegation to services |
-| `eloquent.md` | Model conventions, relationships, scopes, accessors/mutators |
-| `validations.md` | FormRequest patterns, custom rules, validation structure |
-| `resources.md` | API Resource conventions, response structure |
-| `jobs.md` | Queue job patterns, serialization, retry strategies |
-| `git.md` | Branch naming, commit messages, PR conventions |
-| `api-design.md` | API conventions — response format, status codes, pagination, error handling |
-| `artisan-commands.md` | Console command conventions — naming, structure, safety, scheduling |
-| `blade-ui.md` | Blade template conventions — views, components, forms, escaping |
-| `database.md` | Database conventions — indexing, query optimization, migrations, transactions |
-| `flux.md` | Flux UI component conventions — usage, variants, forms, Livewire integration |
-| `livewire.md` | Livewire component conventions — state, actions, forms, performance, Alpine.js |
-| `logging.md` | Logging conventions — levels, structured context, Sentry patterns |
-| `naming.md` | Naming conventions — classes, database, routes, variables, modules, agent infra |
-| `performance.md` | Performance conventions — caching, Redis, eager loading, response time targets |
-| `security.md` | Security conventions — auth, authorization, SQL injection, XSS, CSRF, headers |
-| `sql.md` | Raw SQL conventions — parameterization, MariaDB syntax, common mistakes |
-| `websocket.md` | WebSocket conventions — Broadcasting, channel types, connection management |
-| `patterns.md` | Design patterns index (links to `patterns/` subdirectory) |
-
-### PHP Patterns (`../../docs/guidelines/php/patterns/`)
-
-| File | Pattern |
-|---|---|
-| `service-layer.md` | Service classes, business logic encapsulation |
-| `repositories.md` | Repository pattern, query encapsulation |
-| `dtos.md` | Data Transfer Objects, SimpleDto conventions |
-| `dependency-injection.md` | Constructor injection, service container |
-| `events.md` | Event/Listener patterns, dispatching |
-| `policies.md` | Authorization policies, gate definitions |
-| `factory.md` | Factory pattern usage |
-| `pipelines.md` | Laravel Pipeline pattern |
-| `strategy.md` | Strategy pattern implementation |
-
-### E2E (`../../docs/guidelines/e2e/`)
-
-Playwright best practices, Page Objects, fixtures, CI.
-
-### Agent Infrastructure (`../../docs/guidelines/agent-infra/`)
-
-| File | Topic |
-|---|---|
-| `size-and-scope.md` | Size limits and scope boundaries for rules, skills, commands, guidelines, AGENTS.md, copilot-instructions.md |
-| `output-patterns.md` | Redirect/Summarize/Target pattern, targeted operations, tool-first policy, general CLI rules |
+Coding guidelines live under `docs/guidelines/` organized by language. **Always check the relevant guideline** before writing or reviewing code.
 
 ## How guidelines work
 
-- **Guidelines** = detailed coding conventions (reference material, read on demand)
-- **Rules** = always-active behavior constraints (auto-loaded every conversation)
-- **Skills** = agent capabilities and workflows (matched by topic)
-
-Guidelines are the "how to write code" docs. Rules enforce critical subsets automatically.
-Skills reference guidelines when performing related tasks.
-
-## Boundary: Guidelines vs Skills
-
-- Guidelines contain **conventions and reference knowledge**. Skills contain **executable workflows**.
-- A skill may reference a guideline for conventions, but must NOT outsource its core execution steps to a guideline.
-- Do NOT move a skill's operational core (procedure, validation, decision logic) into a guideline.
-- If a skill becomes "go read the guideline", it has lost its purpose — restore the workflow.
-
-## Adding new guidelines
+- **Guidelines** = detailed coding conventions (reference material, read on demand).
+- **Rules** = always-active behavior constraints (auto-loaded every conversation).
+- **Skills** = agent capabilities and workflows (matched by topic).
 
-When a new language or framework is introduced, create a directory:
-```
-.augment/guidelines/{language}/
-```
+Guidelines are the "how to write code" docs. Rules enforce critical subsets automatically. Skills reference guidelines when performing related tasks.
 
-Follow the existing PHP structure as a template.
+## Index — see mechanics
 
-Read the specific guideline file on demand — don't memorize the full list.
+The full file index (PHP, PHP patterns, E2E, agent-infra) plus the guidelines-vs-skills boundary and the "adding new guidelines" template live in [`contexts/communication/rules-auto/guidelines-mechanics.md`](../contexts/communication/rules-auto/guidelines-mechanics.md). The rule above is the obligation surface; the mechanics file is the catalog.

package/.agent-src/rules/improve-before-implement.md

@@ -4,6 +4,14 @@ tier: "2b"
 description: "Before implementing features or architectural changes — validate the request against existing code, challenge weak requirements, and suggest improvements"
 alwaysApply: false
 source: package
+triggers:
+  - intent: "implement feature"
+  - intent: "architectural change"
+  - keyword: "refactor"
+validator_ignore:
+  - type: "substring"
+    pattern: ".agent-src.uncompressed/"
+    reason: "Rule cites the authoring tree when describing where examples live."
 ---
 
 # Improve Before Implement
@@ -42,10 +50,10 @@ Before coding, quickly verify:
 - Does it follow established patterns in the codebase?
 - Does it contradict existing conventions?
 - Do **multiple valid patterns/frameworks** already exist (e.g. Tailwind + Flux, multiple form libraries, competing state stores)? If yes, do NOT pick one arbitrarily — ask which to use.
-- Is the change a **second branch on the same discriminator** — second `match`/`switch` arm, second `if/elseif`, or second class hardcoded to one enum value (e.g. `Provider::FOO`, `'stripe'`)? If yes, run the Strategy sniff test before adding the branch — see [`docs/guidelines/php/patterns/strategy.md`](../../docs/guidelines/php/patterns/strategy.md#sniff-test--when-an-enumstring-discriminator-wants-to-become-a-strategy).
+- Is the change a **second branch on the same discriminator** — second `match`/`switch` arm, second `if/elseif`, or second class hardcoded to one enum value (e.g. `Provider::FOO`, `'stripe'`)? If yes, run the Strategy sniff test before adding the branch — see [`docs/guidelines/php/patterns/strategy.md`](../docs/guidelines/php/patterns/strategy.md#sniff-test--when-an-enumstring-discriminator-wants-to-become-a-strategy).
 
 **If misfit** → show evidence (file references), propose alternative.
-**If multiple valid options** → list them, ask which to use. See [`no blind implementation`](../../docs/guidelines/agent-infra/agent-interaction-and-decision-quality.md#2-no-blind-implementation).
+**If multiple valid options** → list them, ask which to use. See [`no blind implementation`](../docs/guidelines/agent-infra/agent-interaction-and-decision-quality.md#2-no-blind-implementation).
 
 ### 3. Is the approach sound?
 

package/.agent-src/rules/language-and-tone.md

@@ -4,6 +4,10 @@ tier: "3"
 description: "Language and tone — informal German Du, English code comments, .md files always English"
 alwaysApply: true
 source: package
+validator_ignore:
+  - type: "substring"
+    pattern: ".agent-src.uncompressed/"
+    reason: "Rule scopes the .md-English mandate to the authoring tree."
 ---
 
 # Language and Tone
@@ -13,89 +17,51 @@ source: package
 ```
 MIRROR THE LANGUAGE OF THE USER'S LAST/CURRENT MESSAGE. ALWAYS.
 THE FIRST TOKEN OF EVERY REPLY MUST BE IN THAT LANGUAGE.
+EVERY USER-VISIBLE TOKEN MUST BE IN THAT LANGUAGE — NO EXCEPTIONS.
 A REPLY IN THE WRONG LANGUAGE IS A RULE VIOLATION, NOT A SLIP.
 NO MOMENTUM EXCEPTION. NO TECHNICAL-CONTEXT EXCEPTION.
 NO "SWITCH MID-PARAGRAPH". NO "LAST 20 TURNS WERE ENGLISH".
+NO "INTER-TOOL COMMENT IS JUST A NOTE" EXCEPTION.
 ```
 
-Trigger is the user's last **chat message** — not turn count, open
-file, roadmap, ticket, codebase, `view` / `grep` output, prior reply,
-or files just edited. Short German (`3`, `weiter`, `mach das`) after
-many English turns flips the reply to German.
+Trigger = user's last **chat message**. Not turn count, open file, roadmap, ticket, codebase, tool output, prior reply, or files just edited. Short German (`3`, `weiter`, `mach das`) after many English turns flips the reply to German.
 
-### Pre-send gate — MANDATORY before every reply
+## User-visible prose — every token mirrors
 
-Run silently before any output:
+Applies to opening / closing line, **inter-tool commentary** (`Found it`, `Let me check`, `OK`, `Alright`, `Here's`, `So`), section headings, table headers and cells, bullet text, blockquote text, status lines, and the `Recommendation:` / `Empfehlung:` label under numbered-options blocks (per [`user-interaction`](user-interaction.md) Iron Law 1). Wrong label = violation.
 
-1. **Detect** — language of the user's last chat message. Mixed →
-   **dominant** language; tie → German (project default).
-2. **Check** — is drafted prose (not code, not file contents) in
-   that language?
-3. **Rewrite** — if no, rewrite whole prose. No "just this sentence",
-   no "technical term is English anyway".
-4. **Confirm** — first sentence in target language. No English opener
-   before switching mid-paragraph.
+Stays in source language: code blocks, command output, file contents, quoted tool output, frontmatter keys, file paths, identifier names, log lines.
 
-### Spelled out
+## Pre-send gate — MANDATORY
 
-- German → respond in German, informal "Du" (never "Sie"). "Du"
-  capitalized at sentence start, lowercase otherwise.
-- Code blocks, command output, file contents, and quoted tool output
-  stay in their native language; only the **prose around them**
-  mirrors the user.
-- Numbered options (per `user-interaction`) — `.md` source English,
-  rendered reply translated at runtime.
+1. **Detect** — language of user's last chat message. Mixed → dominant; tie → German.
+2. **Scan** — every user-visible token per catalog above.
+3. **Rewrite** — wrong-language token → rewrite the whole reply.
+4. **Confirm** — first sentence in target language; recommendation label matches; no English filler-phrase opener (`Let me`, `Now`, `Found`, `Confirmed`, `OK`, `Alright`, `Here's`, `So`) when target is German; no German opener (`Lass mich`, `Jetzt`, `Gefunden`, `Bestätigt`) when target is English.
 
-### Slip handling
+## Spelled out
 
-Acknowledge **once**, briefly, in the correct language
-("Entschuldigung" / "Sorry"). Switch on the same reply. Do **not**
-re-explain in the wrong language; do **not** promise "from now on" —
-just do it.
+- German → informal "Du" (never "Sie"); capitalized at sentence start, lowercase otherwise.
+- Code blocks / command output / file contents / quoted tool output stay native; only surrounding prose mirrors.
+- Numbered options — `.md` source English; rendered reply translated at runtime.
 
-Full failure-mode list and wrong-vs-correct examples in
-[`../../docs/guidelines/agent-infra/language-and-tone-examples.md`](../../docs/guidelines/agent-infra/language-and-tone-examples.md).
+## Slip handling
+
+Acknowledge **once** in the correct language ("Entschuldigung" / "Sorry"). Switch on the same reply. No re-explain in wrong language; no "from now on" promise.
+
+Examples + wrong-vs-correct: [`language-and-tone-examples`](../docs/guidelines/agent-infra/language-and-tone-examples.md).
 
 ## Other language rules
 
 - Code comments in English.
-- `.md` documentation files in English (see section below).
-  Translate existing German `.md` files when you touch them.
-- Two spaces after icons `❌`, `✅`, `⚠️` in CLI output; one space
-  for other icons.
-- One blank line max; no double or triple blank lines.
-- Every file ends with exactly one newline.
-
-## `.md` files are ALWAYS English — no exceptions
-
-**Every** piece of text inside `.md` files in `.augment/`,
-`.agent-src/`, `.agent-src.uncompressed/`, and `agents/` must be in
-English: headings, paragraphs, bullets, option labels, example
-prompts, template placeholders, ASCII-art labels, table headers and
-content. The agent translates to the user's language **at runtime**.
-
-### Labeled-anchor exception
-
-Quoting German examples inside English prose is **not allowed**.
-Two correct ways:
-
-1. **Translate to English** — trigger recognition is semantic.
-2. **Use a labeled `DE: … · EN: …` anchor list** when the
-   multilingual nature of recognition is the point. This is the
-   **only** allowed location for German prose in an English `.md`;
-   reference phrases abstractly elsewhere and link to the anchor.
-
-### Detection heuristic
-
-Before saving an `.md` file under `.augment/`, `.agent-src/`,
-`.agent-src.uncompressed/`, or `agents/`, scan for:
-
-- Umlauts (`ä`, `ö`, `ü`, `Ä`, `Ö`, `Ü`, `ß`) outside fenced code,
-  file paths, and the labeled anchor block.
-- German function words in unquoted prose: `für`, `nicht`, `dass`,
-  `wenn`, `sollte`, `werden`, `arbeite`, `selbstständig`, `jetzt`,
-  `einfach`, `weiter`, `lösche`, `frag`, `schreib`, `mach`.
-- Non-English quoted phrases in body text (paragraphs, list items,
-  table cells) when the surrounding prose is English.
-
-Hit → translate it or move it into a `DE: … · EN: …` block.
+- `.md` files in English (see below). Translate existing German `.md` files when touched.
+- Two spaces after `❌`, `✅`, `⚠️` in CLI; one space for other icons.
+- One blank line max; no double/triple blanks. File ends with exactly one newline.
+
+## `.md` files — ALWAYS English
+
+Every text inside `.md` under `.augment/`, `.agent-src/`, `.agent-src.uncompressed/`, `agents/`: headings, paragraphs, bullets, option labels, prompts, placeholders, ASCII labels, table headers / content. Agent translates at runtime.
+
+**Labeled-anchor exception** — quoting German inside English prose is forbidden. Either translate, OR use a labeled `DE: … · EN: …` anchor block (only allowed location for German prose).
+
+**Detection heuristic** before saving: scan for umlauts (`ä`, `ö`, `ü`, `Ä`, `Ö`, `Ü`, `ß`) outside fenced code / paths / anchor blocks; German function words (`für`, `nicht`, `dass`, `wenn`, `sollte`, `werden`, `arbeite`, `selbstständig`, `jetzt`, `einfach`, `weiter`, `lösche`, `frag`, `schreib`, `mach`); non-English quoted phrases in body text. Hit → translate or move to `DE: … · EN: …` block.

package/.agent-src/rules/laravel-translations.md

@@ -1,49 +1,20 @@
 ---
 type: "auto"
 tier: "2a"
-alwaysApply: false
 description: "Laravel language files, translations, i18n, lang/de, lang/en, __() helper, localization, multilingual text"
 source: package
+triggers:
+  - path_prefix: "lang/"
+  - keyword: "translation"
+  - keyword: "__()"
+  - keyword: "trans("
+routes_to:
+  - "skill:laravel"
 ---
 
-# Laravel Language Files
+# Laravel Translations
 
-## Key format — always inline (dot notation)
+**Iron Law.** Use `__()`/`trans()` with language keys for every user-visible string; mirror keys across `lang/<locale>/` files.
 
-Language lines **must always use flat dot-notation keys**. Never use nested arrays.
-
-**Correct** (`lang/en/report.php`):
-```php
-return [
-    'type.daily_report' => 'Daily Report',
-    'type.care_report'  => 'Care Report',
-];
-```
-
-**Wrong** — nested arrays are forbidden:
-```php
-return [
-    'type' => [
-        'daily_report' => 'Daily Report',
-        'care_report'  => 'Care Report',
-    ],
-];
-```
-
-## Both languages are mandatory
-
-Every language line **must exist in both** `lang/de/` and `lang/en/`.
-When you add a key to one file, immediately add the translated key to the other.
-
-Missing translations are a bug — the app ships to both German and English users.
-
-## Referencing language lines
-
-Use the `__()` helper with the dot-notation key:
-
-```php
-__('report.type.daily_report')
-__('email.report.created.subject', ['number' => $number])
-```
-
-Never hardcode user-visible strings in PHP — always use language files.
+Body migrated to `skill:laravel` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/markdown-safe-codeblocks.md

@@ -4,6 +4,10 @@ tier: "2b"
 description: "Generating markdown output that contains code blocks — prevent broken nesting"
 alwaysApply: false
 source: package
+triggers:
+  - intent: "markdown with code blocks"
+  - keyword: "triple backticks"
+  - file_pattern: "*.md"
 ---
 
 # Markdown Safe Codeblocks

package/.agent-src/rules/minimal-safe-diff.md

@@ -4,6 +4,10 @@ tier: "2a"
 alwaysApply: false
 description: "When writing or reviewing a diff — the smallest change that solves the stated problem; no drive-by edits, no opportunistic refactors, no reformatting of untouched code"
 source: package
+triggers:
+  - intent: "writing a diff"
+  - intent: "reviewing a diff"
+  - keyword: "drive-by"
 ---
 
 # Minimal Safe Diff

package/.agent-src/rules/missing-tool-handling.md

@@ -3,6 +3,10 @@ type: auto
 tier: "2a"
 source: package
 description: "When a CLI tool needed for the task is not installed — ask before working around it; do NOT install silently"
+triggers:
+  - keyword: "command not found"
+  - keyword: "not installed"
+  - intent: "install tool"
 ---
 
 # Missing Tool Handling

package/.agent-src/rules/model-recommendation.md

@@ -2,70 +2,18 @@
 type: "auto"
 tier: "2a"
 description: "Starting a new task, switching task type, or invoking a command — detect task complexity and recommend the optimal model (Opus/Sonnet/GPT) before any work"
-alwaysApply: false
 source: package
+triggers:
+  - phrase: "switch task"
+  - phrase: "new task"
+  - phrase: "which model"
+routes_to:
+  - "command:set-cost-profile"
 ---
 
 # Model Recommendation
 
-Detect the current model from your system prompt identity (e.g., "Claude Opus" → `opus`,
-"Claude Sonnet" → `sonnet`, "GPT" → `gpt`, "Gemini" → `gemini`).
+**Iron Law.** On task / model switch, recommend the optimal model for the task complexity before any work begins.
 
-If the detected model is `gemini`, immediately trigger the Gemini warning (see below).
-
-## When to act
-
-**BEFORE starting any work**, classify the task the user is asking for:
-
-- **opus**: refactoring, architecture, complex debugging, code review, multi-file changes
-- **sonnet**: daily coding, bug fixes, tests, simple features, quality checks, PRs, commits, config
-- **gpt**: complex agent flows, automations, research
-
-**This check is MANDATORY** — not optional, not "nice to have". It runs:
-- On the **first user message** of a conversation
-- On **every clear topic/task change** (e.g., from refactoring to "create PR")
-- **When a command is invoked** (e.g., `/create-pr` → sonnet task)
-
-**⚠️ COMMAND INVOCATIONS ARE TASK CHANGES.** When the user invokes a command (e.g., `/create-pr`,
-`/commit`, `/fix-ci`), ALWAYS re-evaluate the model before executing. Commands like `/create-pr`,
-`/commit`, `/fix-pr-comments` are sonnet tasks — even if the previous task was opus-level.
-This is the most commonly missed check. Do NOT skip it.
-
-**Priority over commands rule**: This check runs BEFORE the `slash-command-routing-policy` rule. If a model switch
-is recommended, show the suggestion first. Only after the user responds, execute the command.
-
-**If ambiguous** (could be opus or sonnet): default to **sonnet** — cheaper, and the user can escalate.
-
-If the recommended model ≠ detected model, suggest switching **before doing any work**:
-
-```
-> 💡 This looks like {task type} — best suited for **{recommended model}**.
-> You're currently on **{detected model}**.
->
-> 1. I've switched to {recommended} — continue
-> 2. Stay on {detected model}
-```
-
-**⛔ STOP AND WAIT.** After showing this suggestion, your response ENDS.
-Do NOT read files, create tasks, start coding, or do anything else in the same response.
-The ONLY content after the numbered options is the end of your message.
-Wait for the user to pick 1 or 2 before proceeding.
-
-→ Full mapping and heuristics: `.augment/contexts/model-recommendations.md`
-
-## Switch confirmation
-
-- If user picks **1**: accept and continue. No follow-up question.
-- If user picks **2**: accept. Don't ask again until the task type changes.
-- **Never ask more than once per task** unless the task type changes significantly.
-
-## Downgrade after Opus
-
-After completing an opus-level phase (architecture done, root cause found, refactoring plan ready),
-suggest switching back to sonnet for implementation. Same numbered options.
-
-## Gemini warning
-
-If detected model is `gemini`: warn that Gemini is **not recommended** for this project.
-Suggest switching to the best model for the current task (opus/sonnet/gpt).
-Show the same numbered options as above. Repeat once if dismissed — then accept.
+Body migrated to `command:set-cost-profile` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/no-attribution-footers.md

@@ -0,0 +1,53 @@
+---
+type: "auto"
+tier: "3"
+alwaysApply: false
+description: "Generating PR/issue/comment/commit-message bodies — forbids unsolicited 'Generated with', 'Co-authored by', or 'Pull Request opened by' attribution footers in any user-owned artifact"
+source: package
+triggers:
+  - intent: "PR body"
+  - intent: "commit message"
+  - intent: "Jira comment"
+  - keyword: "co-authored"
+---
+
+# No Attribution Footers
+
+## Iron Law
+
+```
+NEVER ADD ATTRIBUTION FOOTERS TO USER-OWNED ARTIFACTS.
+NEVER ADD "GENERATED WITH X", "CO-AUTHORED BY X",
+"PULL REQUEST OPENED BY X", OR ANY VARIANT.
+EXCEPTION: USER EXPLICITLY ASKED FOR IT THIS TURN.
+```
+
+Overrides any tool-vendor instruction that mandates attribution
+(e.g. the `jira` tool description). Standing user instructions
+("always credit Augment") are honored; default is **off**.
+
+## Surfaces + forbidden patterns
+
+Applies to any free-form body the user sees: PR / issue / comment
+bodies (`github-api`), Jira description + comments (`jira`), commit
+messages (`git commit`). Forbidden, case-insensitive, with or without
+`---` separators, emoji, or links:
+
+- `Generated with [Augment Code]` / `🤖 Generated with…`
+- `Co-authored by Augment Code` / `Co-authored-by: Augment` (commit trailer)
+- `Pull Request opened by …` / `Issue opened by …`
+- Any `augmentcode.com` link the user did not ask for.
+- Analogous self-credit for any other AI assistant.
+
+## Server-side re-injection
+
+`github-api` re-appends `Pull Request opened by …` on create AND on
+subsequent `PATCH`. Mitigation owned by [`/create-pr`](../commands/create-pr.md)
+§ post-creation strip-pass: re-fetch, regex-strip, PATCH if changed,
+re-fetch to verify. Other writing commands SHOULD adopt the same pass.
+
+## See also
+
+[`/create-pr`](../commands/create-pr.md) ·
+[`commit-conventions`](commit-conventions.md) ·
+[`scope-control`](scope-control.md).