@event4u/agent-config 1.20.0 → 1.22.0

package/.agent-src/rules/augment-portability.md

@@ -3,69 +3,21 @@ type: "auto"
 tier: "mechanical-already"
 description: "Editing or creating files inside .augment/ directory — skills, rules, commands, templates, contexts must be project-agnostic"
 source: package
-load_context:
-  - .agent-src.uncompressed/contexts/communication/rules-auto/augment-portability-mechanics.md
+triggers:
+  - path_prefix: ".augment/"
+  - path_prefix: ".agent-src.uncompressed/"
+  - keyword: "portable"
+routes_to:
+  - "guideline:augment-portability-patterns"
+validator_ignore:
+  - type: "substring"
+    pattern: ".agent-src.uncompressed/"
+    reason: "Rule scopes the portability gate to the uncompressed authoring tree."
 ---
 
-# Package Portability
+# Augment Portability
 
-Everything that ships with the `event4u/agent-config` package MUST be
-**project-agnostic**. That includes:
+**Iron Law.** Files inside `.augment/` and `.agent-src.uncompressed/` MUST stay project-agnostic — no project names, domains, stacks.
 
-- Everything inside `.augment/` (skills, rules, commands, guidelines,
-  templates, contexts)
-- The package repo's own root `AGENTS.md`
-- The package repo's own `.github/copilot-instructions.md`
-
-All three are either installed into consumer projects (`.augment/` via
-`install.sh`) or read by AI tools when working on the package itself
-(`AGENTS.md`, `copilot-instructions.md`). Leaking consumer-specific
-content into any of them pollutes downstream projects or misleads agents.
-
-## Rules
-
-- NEVER reference a specific consumer project, repo name, domain, or tech
-  stack directly. The package repo itself (`event4u/agent-config`) MAY be
-  named inside its own root `AGENTS.md` and `copilot-instructions.md` —
-  that is meta about the package, not a leak.
-- NEVER hardcode consumer-project paths, class names, or conventions.
-- Write content so it works as a **reusable package** across any project.
-- Project-specific behavior belongs in the **consumer's** `.agent-settings.yml`,
-  `AGENTS.md`, or `agents/` — never in files shipped by this package.
-- If a skill or rule needs project-specific input, read it from
-  `.agent-settings.yml` or accept it as a parameter.
-- When reviewing or editing package files, always ask: "Would this still
-  make sense in a completely different project?"
-
-## Runtime invocations — no `task` commands
-
-Skills, rules, commands, guidelines, personas, and context docs run in
-**consumer projects**, which may not have Task installed. **Never**
-reference a `task <something>` invocation inside any artefact file
-under `.agent-src.uncompressed/{skills,rules,commands,guidelines,personas,contexts}/`
-(and therefore also not in the compressed mirror under `.agent-src/`).
-Use direct script invocations instead.
-
-## Consumer CLI — `./agent-config`
-
-A subset of package scripts is exposed through a project-local CLI
-wrapper `./agent-config` (written into the project root by the
-installer, gitignored). Artefacts MUST prefer the CLI over raw
-`python3 scripts/…` paths for every command the CLI already covers.
-
-## Translation tables — see mechanics
-
-The full `task`-to-script translation table, the `./agent-config`
-CLI mapping, and the rationale (Task absence on consumers,
-maintainer-vs-artefact split) all live in
-[`contexts/communication/rules-auto/augment-portability-mechanics.md`](../contexts/communication/rules-auto/augment-portability-mechanics.md).
-Pull it whenever an artefact is about to mention a runtime
-invocation.
-
-## Enforcement
-
-`scripts/check_portability.py` scans `.augment/`, `.agent-src.uncompressed/`,
-and the package repo's root `AGENTS.md` + `.github/copilot-instructions.md`
-for forbidden identifiers, for any `task <name>` invocation inside
-artefact files, and for direct script invocations that bypass the
-`./agent-config` CLI. It runs in CI and must pass before any PR.
+Body migrated to `guideline:augment-portability-patterns` (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/augment-source-of-truth.md

@@ -4,7 +4,16 @@ tier: "1"
 description: "Creating, editing, or modifying files inside .agent-src/ or .augment/ — the source of truth is .agent-src.uncompressed/, never edit the generated directories directly"
 source: package
 load_context:
-  - .agent-src.uncompressed/contexts/communication/rules-auto/augment-source-of-truth-mechanics.md
+  - ../contexts/communication/rules-auto/augment-source-of-truth-mechanics.md
+triggers:
+  - path_prefix: ".agent-src/"
+  - path_prefix: ".augment/"
+  - path_prefix: ".claude/"
+  - path_prefix: ".cursor/"
+validator_ignore:
+  - type: "substring"
+    pattern: ".agent-src.uncompressed/"
+    reason: "Rule documents the source-of-truth boundary; mentioning the path is its purpose."
 ---
 
 # Source of Truth

package/.agent-src/rules/autonomous-execution.md

@@ -5,119 +5,38 @@ description: "Deciding whether to ask the user or just act on a workflow step
 alwaysApply: false
 source: package
 load_context:
-  - .agent-src.uncompressed/contexts/execution/autonomy-detection.md
-  - .agent-src.uncompressed/contexts/execution/autonomy-mechanics.md
-  - .agent-src.uncompressed/contexts/execution/autonomy-examples.md
+  - ../contexts/execution/autonomy-detection.md
+  - ../contexts/execution/autonomy-mechanics.md
+  - ../contexts/execution/autonomy-examples.md
+triggers:
+  - intent: "trivial workflow question"
+  - intent: "autonomy mode"
+  - keyword: "personal.autonomy"
 ---
 
 # Autonomous Execution
 
-User's time is the scarce resource. Trivial workflow questions are
-noise. This rule defines **trivial** (just act), **blocking** (still
-ask), the **hard floor** (always ask, no override), and the **commit
-default** (never commit, never ask — review-first by design).
+User's time is the scarce resource. Trivial workflow questions are noise. This rule defines **trivial** (just act), **blocking** (still ask), the **hard floor** (always ask, no override), and the **commit default** (never commit, never ask — review-first by design).
 
 ## Hard Floor — see [`non-destructive-by-default`](non-destructive-by-default.md)
 
-The universal safety floor (production-branch merges, deploys, pushes,
-prod data/infra, whimsical bulk deletions, and commits containing
-bulk deletions or infra changes) is governed by the canonical
-[`non-destructive-by-default`](non-destructive-by-default.md) rule.
-It applies regardless of `personal.autonomy`, a standing autonomy
-directive, or any roadmap authorization. Nothing in **this** rule
-lifts it. If a trigger fires, stop and ask — every other section
-below assumes the floor has already been cleared.
+The universal safety floor (production-branch merges, deploys, pushes, prod data/infra, whimsical bulk deletions, and commits containing bulk deletions or infra changes) is governed by the canonical [`non-destructive-by-default`](non-destructive-by-default.md) rule. It applies regardless of `personal.autonomy`, a standing autonomy directive, or any roadmap authorization. Nothing in **this** rule lifts it. If a trigger fires, stop and ask — every other section below assumes the floor has already been cleared.
 
 ## Setting — `personal.autonomy`
 
-Three values: `on` (suppress trivial questions), `off` (ask trivial
-questions too), `auto` (default — same as `off` until the user opts
-in via a standing autonomy directive). Read once on the first turn
-(per [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules))
-and cache. Missing key → treat as `on`. Full table, semantics, and
-cloud behavior:
-[`contexts/execution/autonomy-mechanics.md`](../contexts/execution/autonomy-mechanics.md).
+Three values: `on` (suppress trivial questions), `off` (ask trivial questions too), `auto` (default — same as `off` until the user opts in via a standing autonomy directive). Read once on the first turn and cache. Missing key → treat as `on`. Full table, semantics, and cloud behavior: [`contexts/execution/autonomy-mechanics.md`](../contexts/execution/autonomy-mechanics.md).
 
 ## Opt-in detection — match by intent, not exact string
 
-In `auto` mode, flip to `on` for the rest of the conversation when
-the user expresses **"stop asking on trivial steps, just work"**.
-Recognize **intent**, not the literal substring. Opt-out (same intent,
-reversed) flips back to `off`. Both directions are
-**speech-act-checked**: the phrase must be a meta-instruction to the
-agent, not content / quote / subject / code / third-party reference /
-hypothetical. In doubt → keep current mode, no speculative flips.
+In `auto` mode, flip to `on` for the rest of the conversation when the user expresses **"stop asking on trivial steps, just work"**. Recognize **intent**, not the literal substring. Opt-out (same intent, reversed) flips back to `off`. Both directions are **speech-act-checked**: the phrase must be a meta-instruction to the agent, not content / quote / subject / code / third-party reference / hypothetical. In doubt → keep current mode, no speculative flips.
 
-Algorithm and speech-act heuristic:
-[`contexts/execution/autonomy-detection.md`](../contexts/execution/autonomy-detection.md).
-Anchor phrases (DE+EN), no-flip patterns, counter-examples:
-[`contexts/execution/autonomy-examples.md`](../contexts/execution/autonomy-examples.md).
-
-## Trivial — JUST ACT, do not ask
-
-In `personal.autonomy: on` or `auto`-after-opt-in, do not ask
-trivial workflow questions — pick the obvious next step and proceed.
-In `personal.autonomy: off`, ask them. Worked cases:
-[`contexts/execution/autonomy-examples.md`](../contexts/execution/autonomy-examples.md).
-
-## Blocking — STILL ASK regardless of `personal.autonomy`
-
-Beyond the Hard Floor above, the autonomy setting also never
-overrides:
-
-- **Vague-request triggers** in [`ask-when-uncertain`](ask-when-uncertain.md)
-  — ambiguous requirements stay ambiguous; pick-one-and-pray is wrong.
-- **Architectural / structural choices** that the codebase doesn't
-  already settle (multi-stack picks, library introductions).
-- **Security-sensitive paths** — see [`security-sensitive-stop`](security-sensitive-stop.md).
-- **Scope expansion** beyond the stated task — see [`scope-control`](scope-control.md).
-- **Remote-state operations** — push, merge, rebase, force-push,
-  branch create/delete/switch, PR create/close/retarget, tag/release.
-  Permission-gated by [`scope-control`](scope-control.md); the
-  prod-trunk and deploy-tied subset is governed by
-  [`non-destructive-by-default`](non-destructive-by-default.md).
-- **Destructive ops** — see [`non-destructive-by-default`](non-destructive-by-default.md)
-  for the full taxonomy (whimsical bulk deletions, content
-  destruction, commits containing bulk deletions or infra changes).
-
-When in doubt whether something is trivial or blocking → it is
-blocking. Ask.
-
-## Commit policy — see [`commit-policy`](commit-policy.md)
-
-Committing is governed by the canonical [`commit-policy`](commit-policy.md)
-rule, which applies regardless of `personal.autonomy`. Summary:
-
-- NEVER commit unless user said so this turn, a commit command was
-  invoked, a standing instruction is active, or the roadmap authorizes it.
-- NEVER ask about committing. The user invokes a command or says so.
-- In autonomous mode, the **only** permitted commit-related question is
-  the one-shot pre-scan ask at the start of roadmap execution.
-
-Push, merge, rebase, branch creation, PR operations, and tags remain
-permission-gated by [`scope-control`](scope-control.md#git-operations--permission-gated).
-
-## Failure modes
-
-Autonomy-side wrong-behavior patterns (sequencing-only asks, CI-run
-asks, commit asks, no-trade-off option blocks, re-asking after a
-standing opt-in):
-[`contexts/execution/autonomy-examples.md`](../contexts/execution/autonomy-examples.md).
-For Hard-Floor failure modes see
-[`non-destructive-by-default`](non-destructive-by-default.md#failure-modes).
+Algorithm and speech-act heuristic: [`contexts/execution/autonomy-detection.md`](../contexts/execution/autonomy-detection.md). Anchor phrases (DE+EN), no-flip patterns, counter-examples, trivial-vs-blocking taxonomy, commit-policy summary, and named failure modes: [`contexts/execution/autonomy-mechanics.md`](../contexts/execution/autonomy-mechanics.md) + [`contexts/execution/autonomy-examples.md`](../contexts/execution/autonomy-examples.md).
 
 ## See also
 
-- [`non-destructive-by-default`](non-destructive-by-default.md) —
-  universal safety floor; never overridden by autonomy
+- [`non-destructive-by-default`](non-destructive-by-default.md) — universal safety floor; never overridden by autonomy
 - [`scope-control`](scope-control.md) — git-ops permission gate
-  (push/merge/branch/PR/tag stays explicit)
-- [`ask-when-uncertain`](ask-when-uncertain.md) — vague-request
-  triggers that always require asking
-- [`no-cheap-questions`](no-cheap-questions.md) — mode-independent
-  floor against context-derived, sequencing-only, and
-  Iron-Law-violating asks (applies in `off` and pre-opt-in `auto` too)
-- [`direct-answers`](direct-answers.md) — Iron Laws on brevity and
-  no-flattery (this rule extends to no-trivial-questions)
-- [`/commit-in-chunks`](../commands/commit-in-chunks.md) — auto-split and commit without confirmation
-- [`/commit`](../commands/commit.md) — split and commit with confirmation
+- [`ask-when-uncertain`](ask-when-uncertain.md) — vague-request triggers that always require asking
+- [`no-cheap-questions`](no-cheap-questions.md) — mode-independent floor against context-derived asks
+- [`commit-policy`](commit-policy.md) — never-commit / never-ask Iron Law
+- [`/commit:in-chunks`](../commands/commit/in-chunks.md), [`/commit`](../commands/commit.md)

package/.agent-src/rules/capture-learnings.md

@@ -2,89 +2,18 @@
 type: "auto"
 tier: "2a"
 description: "After completing a task where a repeated mistake or successful pattern appeared — capture as rule or skill"
-alwaysApply: false
 source: package
+triggers:
+  - phrase: "after completing a task"
+  - keyword: "learning"
+  - keyword: "lesson"
+routes_to:
+  - "skill:learning-to-rule-or-skill"
 ---
 
 # Capture Learnings
 
-When a repeated mistake, successful pattern, or new constraint appears,
-evaluate whether to capture as **rule** or **skill**.
+**Iron Law.** After a task, capture repeated mistakes / successful patterns as a rule or skill — never lose the learning.
 
-## Promotion Gate
-
-A learning may be promoted to rule/skill ONLY if ALL gates pass:
-
-| Gate | Question | Must be YES |
-|---|---|---|
-| Repetition | Occurred at least twice OR clearly generalizable? | ✅ |
-| Impact | Improves correctness, reliability, or consistency? | ✅ |
-| Failure pattern | Prevents a real, observed failure? | ✅ |
-| Non-duplication | No existing rule/skill/guideline covers this? | ✅ |
-| Scope fit | Fits rule (constraint), skill (workflow), or guideline (convention)? | ✅ |
-| Minimal | Update existing preferred over creation? | Checked |
-
-**Reject immediately if:**
-- Occurred only once and is not clearly generalizable
-- Similar guidance already exists (update instead)
-- Baseline model knowledge or standard tool usage
-- Vague frustration without concrete failure pattern
-
-## Triggers
-
-- Mistake that happened 2+ times
-- Pattern that improved outcome and should be reused
-- Missing constraint that caused issues
-- **User frustration or complaint** — extract the underlying failure pattern, don't ignore or defend
-- **New skill/rule/guideline created** — evaluate if it should be contributed upstream (→ `upstream-proposal` rule)
-- **Significant improvement to existing skill/rule** — consider upstream contribution
-
-## Do NOT capture
-
-- One-off problems
-- Vague frustrations without concrete consequence
-- Content already covered by existing guidance
-
-## Rule vs Skill
-
-- **Rule** → always-apply constraint ("never X", "always Y")
-- **Skill** → repeatable workflow with steps ("when X, do 1-5")
-- **Update** → existing guidance covers topic → extend, don't duplicate
-
-## How
-
-- Smallest effective change
-- Update existing over creating duplicates
-- Full workflow: `learning-to-rule-or-skill` skill
-
-## Where learnings are written
-
-Captured learnings live in the **consumer project's** `agents/learnings/`
-directory, one file per learning:
-
-```
-agents/learnings/<YYYY-MM-DD>-<kebab-slug>.md
-```
-
-Minimum fields (markdown with a small YAML frontmatter):
-
-```yaml
----
-slug: <same as filename>
-captured: <ISO date>
-occurrences: <integer, ≥2 or note "one-off, clearly generalizable">
-type_hint: rule | skill | guideline | update
-scope_hint: project | package
----
-```
-
-Body: 1-paragraph **pattern** (not anecdote) + 1 concrete example.
-
-A learning file is the input to `learning-to-rule-or-skill`, which
-produces a proposal draft under `agents/proposals/`. The proposal is
-then gated by `scripts/check_proposal.py`; see
-[`self-improvement-pipeline`](../../docs/guidelines/agent-infra/self-improvement-pipeline.md).
-
-The `agents/learnings/` and `agents/proposals/` directories are
-consumer-owned — the package ships templates and schemas, never the
-data.
+Body migrated to `skill:learning-to-rule-or-skill` (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/cli-output-handling.md

@@ -1,51 +1,21 @@
 ---
 type: "auto"
 tier: "2a"
-alwaysApply: false
 description: "Running CLI commands that produce verbose output — git, tests, linters, docker, build tools, artisan, npm, composer. Wrap with rtk when installed; tail/grep is fallback."
 source: package
-load_context:
-  - .agent-src.uncompressed/contexts/communication/rules-auto/cli-output-handling-mechanics.md
+triggers:
+  - keyword: "git"
+  - keyword: "phpstan"
+  - keyword: "rector"
+  - keyword: "phpunit"
+  - keyword: "composer"
+routes_to:
+  - "skill:rtk-output-filtering"
 ---
 
-# Development Efficiency
+# Cli Output Handling
 
-Loaded for code, tests, quality tools, CLI, analysis. Communication / response style → always-loaded `token-efficiency`.
+**Iron Law.** Wrap verbose CLI output with `rtk` when installed; fall back to `tail`/`grep` only when missing.
 
-## Iron Law — rtk first, tail/grep fallback
-
-```
-IF `rtk` IS INSTALLED, WRAP VERBOSE COMMANDS WITH rtk.
-USE tail / grep / cat ONLY AS FALLBACK WHEN rtk HAS NO MATCHING SUBCOMMAND.
-NEVER PIPE A STILL-RUNNING LONG COMMAND THROUGH tail — IT BUFFERS TO EOF.
-```
-
-Detection: `rtk_installed: true` in `.agent-settings.yml`, or `which rtk`
-exits 0. Caching the result for the session is fine.
-
-| Verbose command | Use | Fallback (no rtk) |
-|---|---|---|
-| CI-style suites, full test runs | `rtk err <cmd>` — only errors/warnings | redirect → tail → grep |
-| Unit tests | `rtk test <cmd>` — only failures | redirect → tail → grep |
-| `git status`/`log`/`diff` | `rtk git <subcmd>` | plain |
-| `gh pr list`, `gh run view` | `rtk gh <subcmd>` | plain |
-| Generic noisy command | `rtk summary <cmd>` or `rtk err <cmd>` | redirect → tail |
-
-For the full rtk subcommand catalog and project-local filter setup → see
-the `rtk-output-filtering` skill.
-
-## Lookup material — see mechanics
-
-Codebase-navigation tips, the redirect-summarize-target fallback
-pattern (with the three-step `tail`/`grep` recipe), the general rules
-(exit code first, summary line, targeted `grep`, read-once-act-move-on,
-iterative fixing), and the CLI-over-MCP catalog all live in
-[`contexts/communication/rules-auto/cli-output-handling-mechanics.md`](../contexts/communication/rules-auto/cli-output-handling-mechanics.md).
-Pull it whenever a verbose command is about to run without an `rtk`
-match.
-
-## Exceptions
-
-- **Small output** (< 30 lines): Read directly, no redirect needed.
-- **Debugging**: OK to read more context around the specific error.
-- **User asks** for full output: Show it.
+Body migrated to `skill:rtk-output-filtering` (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/command-suggestion-policy.md

@@ -2,28 +2,22 @@
 type: "auto"
 tier: "mechanical-already"
 description: "User prompt without /command but matching an eligible slash command — surface matches as numbered options with as-is escape hatch; never auto-executes, user always picks"
-alwaysApply: false
 source: package
+triggers:
+  - phrase: "free-form prompt"
+  - phrase: "command suggestion"
+routes_to:
+  - "contract:command-suggestion-flow"
 load_context:
-  - .agent-src.uncompressed/contexts/communication/rules-auto/command-suggestion-policy-mechanics.md
+  - "../contexts/contracts/command-suggestion-flow.md"
 ---
 
-# Command Suggestion
+# Command Suggestion Policy
 
-When the user's prompt matches an eligible slash command, surface it
-as a **numbered option** alongside an "as-is" escape hatch — the
-"run prompt as-is" option is **always last** and **always present**,
-never omitted. The user always picks. **Nothing auto-executes.** The
-suggestion layer is a read-only shortcut *finder*, not an invocation
-path.
-
-The deterministic engine lives in `scripts/command_suggester/`. The
-locked eligibility table lives in
-[`agents/contexts/command-suggestion-eligibility.md`](../../agents/contexts/command-suggestion-eligibility.md).
-The scoring contract and hardening list live in
-[`docs/contracts/adr-command-suggestion.md`](../../docs/contracts/adr-command-suggestion.md)
-and
-[`docs/contracts/command-suggestion-flow.md`](../../docs/contracts/command-suggestion-flow.md).
+When the user's prompt matches an eligible slash command, surface it as a
+**numbered option** alongside an "as-is" escape hatch. The user always
+picks. **Nothing auto-executes.** Flow contract + senior-gate map:
+[`contexts/contracts/command-suggestion-flow.md`](../contexts/contracts/command-suggestion-flow.md).
 
 ## Iron Law — never auto-execute
 
@@ -31,64 +25,22 @@ and
 SUGGEST. NEVER INVOKE. THE USER PICKS, ALWAYS.
 ```
 
-A suggestion block emits options. It does **not** start a command
-flow. The user picking option N triggers `slash-command-routing-policy` on the
-**next** turn — with all the command's own halts intact.
-
-## When to fire
-
-On a user turn that matches **all** of the following:
-
-1. The message does **not** start with an explicit `/command` (those
-   bypass suggestion entirely — see `slash-command-routing-policy`).
-2. `commands.suggestion.enabled` is `true` (default).
-3. The user has not issued `/command-suggestion-off` in this conversation.
-4. No clarification is owed for the same turn (per
-   `ask-when-uncertain` — clarification wins; suggestion can fire next turn).
-5. No active engine flow is mid-halt (e.g. an `/implement-ticket`
-   step waiting on the user — the active flow has the floor).
-6. The matcher returns at least one match above the effective
-   `confidence_floor` after rank + cooldown + anti-noise.
-
-When all six hold, the suggestion block is the **first and only**
-thing the agent emits that turn. No tools, no edits, no other prose.
+A suggestion block emits options. It does **not** start a command flow.
+The "run as-is" option is **always present**, **always last**, never
+removed.
 
 ## Subordination — when to stay silent
 
 The suggestion rule is **junior** to:
 
-- `scope-control` — never surfaces a git-op command behind a
-  permission gate the user already declined this turn.
-- `ask-when-uncertain` — if a clarification is owed, the
-  clarification is the only question; suggestion suppresses for
-  that turn.
-- `verify-before-complete` — suggestion does not interrupt an
-  evidence-gate verification that's already running.
-- Any active role-mode contract (`role-mode-adherence`).
-- Any active engine halt (`/implement-ticket`, `/work`, etc.).
-
-On any conflict → suggestion stays silent. Zero output. The user's
-prompt is processed as it would be without this rule.
-
-## Cloud Behavior
-
-On cloud surfaces (Claude.ai Web, Skills API) the rule is **inert**
-unless the suggester package is shipped in the bundle. Treat
-`commands.suggestion.enabled` as `false` when the engine is not
-available — degrade silently, never crash the turn.
-
-## Mechanics — output format, anti-noise, what this rule does NOT do
-
-The exact rendered options block, the `Recommendation:` rules, the
-`max_options` cap, the `rank.py` anti-noise filters, and the
-"what this rule does NOT do" catalog live in
-[`contexts/communication/rules-auto/command-suggestion-policy-mechanics.md`](../contexts/communication/rules-auto/command-suggestion-policy-mechanics.md).
-
-## Interactions
-
-- [`slash-command-routing-policy`](slash-command-routing-policy.md) — explicit `/command` skips suggestion entirely.
-- [`user-interaction`](user-interaction.md) — numbered-options Iron Law and single-source recommendation.
-- [`ask-when-uncertain`](ask-when-uncertain.md) — clarification wins on conflict.
-- [`scope-control`](scope-control.md) — git-op gates outrank suggestion.
-- [`role-mode-adherence`](role-mode-adherence.md) — active mode contract outranks suggestion.
-- [`agents/contexts/command-suggestion-eligibility.md`](../../agents/contexts/command-suggestion-eligibility.md) — locked eligibility table.
+- [`scope-control`](scope-control.md) — never surfaces a git-op command
+  behind a permission gate the user already declined.
+- [`ask-when-uncertain`](ask-when-uncertain.md) — clarification wins on
+  conflict; suggestion suppresses for that turn.
+- [`verify-before-complete`](verify-before-complete.md) — suggestion does
+  not interrupt an evidence-gate verification.
+- [`role-mode-adherence`](role-mode-adherence.md) — active role-mode
+  contract outranks suggestion.
+- Any active engine halt (`/implement-ticket`, `/work`).
+
+On any conflict → suggestion stays silent.

package/.agent-src/rules/commit-conventions.md

@@ -1,68 +1,19 @@
 ---
 type: "auto"
 tier: "2a"
-alwaysApply: false
 description: "Git commit message format, branch naming, conventional commits, committing, pushing, or creating pull requests"
 source: package
+triggers:
+  - keyword: "commit"
+  - keyword: "branch"
+  - phrase: "conventional commits"
+routes_to:
+  - "skill:conventional-commits-writing"
 ---
 
 # Commit Conventions
 
-All commit messages and squash/merge titles must follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
+**Iron Law.** Use Conventional Commits (`feat:`, `fix:`, `chore:` …); branches `<type>/<short-slug>`; never invent your own format.
 
-## Format
-
-- With scope: `<type>(<scope>): <description>`
-- Without scope: `<type>: <description>` (omit parentheses when no scope)
-- **Always English** — regardless of user's language.
-- **Imperative mood** ("add feature", not "added feature").
-- **First line max 72 characters.**
-
-## Types
-
-| Type | When |
-|---|---|
-| `feat` | New user-facing functionality |
-| `fix` | Bug fix |
-| `refactor` | Code/structure change, no behavior change |
-| `docs` | Documentation only |
-| `test` | Tests only |
-| `chore` | Maintenance (deps, configs, tooling, cleanup) |
-| `ci` | CI/CD and workflow changes |
-| `style` | Code style (formatting, no logic change) |
-| `perf` | Performance improvement |
-| `build` | Build tooling / packaging changes |
-
-## Scope
-
-- Use the **Jira ticket ID** as scope when the branch contains one (e.g. `DEV-1234`).
-- Otherwise use a short module or area name (e.g. `api`, `auth`, `skills`).
-- Scope is optional — only add when it improves clarity.
-
-## Breaking changes
-
-Mark explicitly with `!` after type/scope or `BREAKING CHANGE:` in footer:
-
-```
-feat(api)!: rename invoice status values
-refactor(auth)!: remove legacy session flow
-```
-
-## Commit splitting
-
-If a change mixes unrelated concerns, split into multiple commits.
-Do NOT hide bug fixes, CI work, docs, and refactors in one commit.
-
-## Examples
-
-```
-feat(DEV-1234): add absence type filter to working time report
-fix(DEV-1234): handle null value in equipment import
-test(DEV-1234): add component test for working time controller
-refactor: extract user sync logic into dedicated service
-chore: update PHP quality package to 2.1.0
-ci(lint): add skill-lint workflow
-docs(roadmap): add phase 3 implementation plan
-```
-
-→ Full type selection rules and anti-patterns: see guideline `docs/guidelines/php/git.md`.
+Body migrated to `skill:conventional-commits-writing` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.