@event4u/agent-config 1.24.0 → 1.26.0

package/.agent-src/commands/review-routing.md

@@ -1,6 +1,6 @@
 ---
 name: review-routing
-skills: [review-routing, reviewer-awareness, review-routing-awareness]
+skills: [review-routing, reviewer-awareness]
 description: Compute reviewer roles and matched historical bug patterns for the current diff, using project-local ownership-map.yml and historical-bug-patterns.yml
 disable-model-invocation: true
 suggestion:
@@ -18,10 +18,9 @@ reviewer roles plus any matched historical bug patterns — so the author
 knows *who* to request and *what* to test before opening a PR.
 
 Dispatches to [`review-routing`](../skills/review-routing/SKILL.md) for
-the core resolution logic. The rules
-[`reviewer-awareness`](../rules/reviewer-awareness.md) and
-[`review-routing-awareness`](../rules/review-routing-awareness.md) govern
-the output format and data handling.
+the core resolution logic. The rule
+[`reviewer-awareness`](../rules/reviewer-awareness.md) governs reviewer
+choice, routing, and data handling.
 
 ### 1. Gather the diff
 
@@ -73,7 +72,7 @@ After the block, ask:
 ```
 
 - On **1**: hand off to
-  [`create-pr-description`](../skills/create-pr-description/SKILL.md).
+  [`create-pr-description`](../skills/create-pr:description-only/SKILL.md).
 - On **2**: respect CODEOWNERS — request the *roles* resolved to people
   by the consumer's own mapping, never invent usernames.
 - On **3**: the user wants to curate the map first. Stop.
@@ -104,12 +103,10 @@ After the block, ask:
 ## See also
 
 - [`review-routing`](../skills/review-routing/SKILL.md) — the resolver
-- [`reviewer-awareness`](../rules/reviewer-awareness.md) — role vocabulary
-- [`review-routing-awareness`](../rules/review-routing-awareness.md) —
-  data-source rules
+- [`reviewer-awareness`](../rules/reviewer-awareness.md) — role vocabulary + data-source rules
 - [`review-routing-data-format`](../docs/guidelines/agent-infra/review-routing-data-format.md)
   — YAML schemas
-- [`create-pr-description`](../skills/create-pr-description/SKILL.md) —
+- [`create-pr-description`](../skills/create-pr:description-only/SKILL.md) —
   consumes the routing block
 - [`verify-before-complete`](../rules/verify-before-complete.md) —
   consumes the `required_test` list

package/.agent-src/contexts/authority/kernel-rule-edits.md

@@ -0,0 +1,48 @@
+# Kernel-Rule Edits — Slow-Rollout Guarantee
+
+Loaded by [`scope-control`](../../rules/scope-control.md). Codifies the
+soak-time guarantee for edits to always-loaded (kernel) rules under
+`.agent-src.uncompressed/rules/`.
+
+**Size budget:** ≤ 1,500 chars.
+
+## The guarantee
+
+Each kernel-rule edit ships in **its own PR**, with **≥ 24 h between
+merges** of consecutive kernel-rule PRs. Autonomous mandate, roadmap
+authorization, and standing "just keep going" directives **do not lift
+this** — it is a behaviour-soak guarantee, not a governance preference.
+
+The 24 h window exists so that a regression introduced by the first
+edit (a rule that stops firing, an Iron Law that loses rhetorical
+weight, a trigger that swallows a sibling rule's domain) surfaces in
+real interactions before the second edit lands and confounds the
+diagnosis.
+
+## Trigger
+
+A PR is a "kernel-rule edit" iff it modifies any file in
+`.agent-src.uncompressed/rules/` that is in the locked kernel set
+(see [`docs/contracts/kernel-membership.md`](../../../docs/contracts/kernel-membership.md)).
+
+The CI guard (Phase 4.2 of the always-budget-relief roadmap) fails
+any PR that touches **> 1** kernel rule in the same diff. Override is
+a single PR label: `bundled-always-rules-acknowledged` — the maintainer
+records why the bundle is necessary in the PR body.
+
+## Out of scope
+
+- Auto-tier rules. Auto rules load on demand; the soak rationale does
+  not apply with the same force.
+- Context files cited by kernel rules. Context edits are reversible
+  cheaply and do not change rule firing surface.
+- Whitespace / typo / link fixes inside a single kernel rule. Same-rule
+  cosmetic edits are not subject to the 24 h window — they ship as a
+  normal PR.
+
+## Source
+
+- Roadmap Phase 4: always-budget-relief roadmap § Phase 4 (transient — see `agents/roadmaps/archive/`).
+- Lesson: PR #36 (2026-05-04) compressed the rollout schedule under
+  autonomous mandate; the slow-rollout note was deferred until this
+  ADR pass.

package/.agent-src/contexts/authority/scope-mechanics.md

@@ -58,6 +58,21 @@ Then present numbered options (`user-interaction`) with "stay on the
 current branch" as the default. The user decides. Do not branch
 first and explain later.
 
+## Branch-base inventory — ALWAYS before starting work
+
+Before the first commit on related work, scan: `git branch --show-current` (is this branch shaped for the task?), `gh pr list --state open --limit 10` (overlapping open PR?), `git branch --sort=-committerdate | head -10` (in-flight branch to extend?).
+
+A plausible base beyond the current branch exists → STOP and ask with numbered options:
+
+1. Branch off the **current branch** — stacked PR.
+2. Branch off **`main`** — independent PR.
+3. **Continue on the current branch** — extend the in-flight PR.
+4. **Cancel**.
+
+User decides. Default: **3** when the current branch's name and scope match the task; otherwise **2**. Never improvise the base.
+
+**Failure mode — diverging stacked PRs.** Skipping the inventory and committing to the wrong base creates two PRs that should have been one stack: merge conflicts when the parent lands, rebase / force-push churn, duplicate review effort. The 30-second inventory cost up front beats hours of rebase reconciliation later.
+
 ## Decline = silence — context
 
 The right moment to ask is **before** the work starts (writing the

package/.agent-src/contexts/contracts/consumer-agents-md-guide.md

@@ -0,0 +1,127 @@
+# Consumer `AGENTS.md` — fill-out guide
+
+> Outboard target for the placeholder sections that used to live verbatim
+> in the consumer-template `AGENTS.md`. The template is now Thin-Root; this
+> guide carries the prose / examples / `<!-- … -->` hints that the
+> consumer copies in only when they need them.
+
+After installing `event4u/agent-config`, the consumer project gets:
+
+- `AGENTS.md` at project root — Thin-Root, points here.
+- `.augment/`, `.agent-src/`, `.claude/`, `.cursor/`, `.clinerules/`,
+  `.windsurfrules` — installed artifacts, never hand-edited.
+- `agents/` — project docs / roadmaps / sessions / overrides.
+- `.agent-settings.yml` — project config consumed by skills.
+
+## Recommended `AGENTS.md` shape
+
+The installed Thin-Root carries: project name + description, layer table,
+five-question emergency triage block, pointers to this guide. Copy any of
+the sections below into AGENTS.md only when the project actually needs
+the content there (e.g. an unusual stack note that no `agents/` doc
+covers). Default: leave AGENTS.md thin and put detail under `agents/`.
+
+## Tech-stack section (optional copy-in)
+
+```markdown
+## Tech Stack
+
+- **Language:** {{primary_language}}
+- **Framework:** {{framework}}        # Laravel 11 / Next.js 15 / Rails 7 / Django 5
+- **Database:** {{database}}          # PostgreSQL / MySQL / MariaDB / SQLite
+- **Testing:** {{test_framework}}     # Pest / PHPUnit / Jest / Vitest / pytest
+- **Code style:** {{code_style_tool}} # ECS / PHPStan / Ruff / ESLint
+```
+
+## Development-setup section (optional copy-in)
+
+```markdown
+## Development Setup
+
+​```bash
+{{dev_start_command}}    # make start / docker compose up / npm run dev / php artisan serve
+{{dev_test_command}}     # make test / docker compose exec app bash / npm test / php artisan test
+​```
+
+### Environment files
+
+| File | Purpose |
+|---|---|
+| `.env` | Main environment |
+| `.env.local` | Local overrides |
+| `.env.testing` | Testing environment |
+```
+
+## Project-structure section (optional copy-in)
+
+```markdown
+## Project Structure
+
+{{project_structure_notes}}   # Where new features go, module/component
+                              # boundaries, namespace conventions.
+```
+
+## Testing section (optional copy-in)
+
+```markdown
+## Testing
+
+{{testing_notes}}             # Framework quirks, how to run all/targeted
+                              # tests, test data strategy (seeders /
+                              # factories / fixtures), performance-critical
+                              # suites.
+```
+
+## Quality-tools section (optional copy-in)
+
+```markdown
+## Quality Tools
+
+{{quality_tools_notes}}       # Which linters/formatters run, whether
+                              # they auto-fix or report only, CI
+                              # enforcement level.
+```
+
+## Recommended entry flow
+
+Two entrypoints share the same engine and Option-A loop; pick by input shape:
+
+| You have | Command | Envelope |
+|---|---|---|
+| Ticket id, URL, or pasted ticket payload | [`/implement-ticket`](.augment/commands/implement-ticket.md) | `input.kind="ticket"` |
+| Free-form goal, no ticket | [`/work`](.augment/commands/work.md) | `input.kind="prompt"` |
+
+Both drive the linear flow `refine → memory → analyze → plan → implement
+→ test → verify → report` with block-on-ambiguity semantics and no
+auto-git.
+
+`/work` adds a confidence-band gate at `refine`: the
+[`refine-prompt`](.augment/skills/refine-prompt/SKILL.md) skill scores
+the prompt on five dimensions and the engine proceeds **silently** on
+`high`, halts with an **assumptions report** on `medium`, or halts with
+**one clarifying question** on `low` (per the `ask-when-uncertain` Iron
+Law). UI-shaped prompts route through the product UI track (`directive_set`
+`ui` / `ui-trivial` / `mixed`) — `audit → design → apply → review →
+polish` with a hard audit gate before any `apply`.
+
+Persona comes from `.agent-settings.yml` (`roles.active_role`). Use
+`/commit` and `/create-pr` explicitly after the delivery report. The
+two flows are mutually exclusive at the state-file level: one
+`.work-state.json` carries one envelope at a time; the engine refuses to
+switch mid-flight.
+
+## Multi-agent support
+
+| Tool | Rules | Skills | How |
+|---|---|---|---|
+| **Augment Code** | `.augment/rules/` | `.augment/skills/` | Native (source) |
+| **Claude Code** | `.claude/rules/` | `.claude/skills/` | Symlinks + Agent Skills standard |
+| **Cursor** | `.cursor/rules/` | — | Symlinks |
+| **Cline** | `.clinerules/` | — | Symlinks |
+| **Windsurf** | `.windsurfrules` | — | Concatenated file |
+| **Gemini CLI** | `GEMINI.md` | — | Symlink → AGENTS.md |
+
+Reinstall agent-config: `composer update event4u/agent-config` (PHP) or
+`npm update @event4u/agent-config` (JS). Don't run package-internal
+`task` commands from a consumer project; they only work in the
+agent-config repo itself.

package/.agent-src/contexts/contracts/emergency-triage-block.md

@@ -0,0 +1,53 @@
+# Emergency Triage Block — canonical source
+
+> Canonical content of the **Emergency Triage** block referenced by the
+> `agents-md-thin-root` skill. Both the package-root `AGENTS.md` and
+> `.agent-src.uncompressed/templates/AGENTS.md` (consumer template)
+> embed this block verbatim. Drift is caught by the `lint-agents-md`
+> task in the package's CI pipeline.
+
+The block exists so a host agent can answer five basic questions from
+the root file alone when network access, context-engine retrieval, or
+linked-file fetches are degraded. Each answer fits on one line.
+
+## Package-root variant
+
+Use this variant in `AGENTS.md` at the package root.
+
+```
+## Emergency triage — read this when nothing else is reachable
+
+1. **What is this repo?** — `event4u/agent-config`, a governed skill / rule / command suite for AI coding tools (no application runtime).
+2. **What language?** — All `.md` content is English; agents mirror the user's language at runtime.
+3. **Where do I edit?** — `.agent-src.uncompressed/` only. Never `.agent-src/`, `.augment/`, `.claude/`, `.cursor/`, `.clinerules/`, `.windsurfrules`.
+4. **Lint / test / sync entry point?** — `task ci` (full pipeline). Subsets: `task sync`, `task generate-tools`, `task lint-skills`, `task test`.
+5. **Where do the always-active rules live?** — `.agent-src/rules/` (kernel = 9 Iron-Law rules; tier-1 / tier-2 routed via `.agent-src/router.json`).
+```
+
+## Consumer-template variant
+
+Use this variant in `.agent-src.uncompressed/templates/AGENTS.md`. The
+consumer's `AGENTS.md` lands at the consumer-project root after install.
+
+```
+## Emergency triage — read this when nothing else is reachable
+
+1. **What is this repo?** — Consumer project; agent-config is installed as a shared skill / rule / command suite at `.augment/` and `.agent-src/`.
+2. **What language?** — Project-specific; agents mirror the user's language at runtime.
+3. **Where do I edit agent-config?** — Do not edit `.augment/` or `.agent-src/` here; they are installed artifacts. Project edits live in `agents/` and project source.
+4. **Lint / test / sync entry point?** — Project-specific (see project README); agent-config itself reinstalls via `composer update event4u/agent-config` or `npm update @event4u/agent-config`.
+5. **Where do the always-active rules live?** — `.agent-src/rules/` (kernel = 9 Iron-Law rules; tier-1 / tier-2 routed via `.agent-src/router.json`).
+```
+
+## Why two variants
+
+The package-root and the consumer template answer the same five
+questions but in different repos:
+
+- The package-root variant points at this repo's authoring layer
+  (`.agent-src.uncompressed/`) and the package's CI entry point.
+- The consumer variant tells the agent it is in a **consumer** project
+  where `.augment/` is an installed artifact and editing it is wrong.
+
+The questions stay identical so a host agent can recognise the block
+visually regardless of which repo it landed in.

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

@@ -1,5 +1,5 @@
 ---
-type: "auto"
+type: "manual"
 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/artifact-drafting-protocol.md

@@ -2,7 +2,7 @@
 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."
+description: "Creating a new skill, rule, command, or guideline, or significantly rewriting one — runs mandatory Understand → Research → Draft before drafting"
 source: package
 triggers:
   - intent: "create new skill"

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

@@ -2,7 +2,7 @@
 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"
+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"
 source: package
 triggers:
   - phrase: "/implement-ticket"

package/.agent-src/rules/augment-source-of-truth.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 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"
+description: "Creating, editing, or modifying files in .agent-src/ or .augment/ — source of truth is .agent-src.uncompressed/, never edit generated dirs directly"
 source: package
 load_context:
   - ../contexts/communication/rules-auto/augment-source-of-truth-mechanics.md

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

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "3"
-description: "Deciding whether to ask the user or just act on a workflow step — trivial-vs-blocking classification, autonomy opt-in detection, commit default; defers to non-destructive-by-default for the Hard Floor"
+description: "Whether to ask or act on a workflow step — trivial-vs-blocking, autonomy opt-in, commit default; Hard Floor in non-destructive-by-default"
 alwaysApply: false
 source: package
 load_context:

package/.agent-src/rules/caveman-speak.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "1"
-description: "When caveman.speak_scope != off — compress reply prose to caveman grammar with byte-for-byte carve-outs for numbered options, Iron-Law literals, code, paths, and error markers."
+description: "When caveman.speak_scope != off — compress reply prose to caveman grammar with carve-outs for numbered options, Iron-Law, code, paths, error markers"
 source: package
 triggers:
   - intent: "any reply"

package/.agent-src/rules/cli-output-handling.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-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."
+description: "Running CLI commands that produce verbose output — git, tests, linters, docker, build tools, artisan, npm, composer. Wrap with rtk; tail/grep fallback"
 source: package
 triggers:
   - keyword: "git"

package/.agent-src/rules/command-suggestion-policy.md

@@ -1,7 +1,7 @@
 ---
 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"
+description: "User prompt without /command matching an eligible slash command — surface matches as numbered options with as-is escape; never auto-executes"
 source: package
 triggers:
   - phrase: "free-form prompt"

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

@@ -1,7 +1,7 @@
 ---
 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"
+description: "Keeping .augment/ contexts, counts, cross-references in sync when creating, renaming, or deleting skills, rules, commands, templates, agent infra"
 source: package
 triggers:
   - path_prefix: ".agent-src.uncompressed/"

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

@@ -1,5 +1,5 @@
 ---
-type: "auto"
+type: "manual"
 tier: "3"
 description: "Writing or reviewing code — check relevant guideline before writing or reviewing code"
 alwaysApply: false

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

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2b"
-description: "Before implementing features or architectural changes — validate the request against existing code, challenge weak requirements, and suggest improvements"
+description: "Before implementing features or architectural changes — validate the request against existing code, challenge weak requirements, suggest improvements"
 alwaysApply: false
 source: package
 council_depth: deep

package/.agent-src/rules/invite-challenge.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2b"
-description: "Before executing a complex plan or non-trivial design — proactively ask 'am I solving the right problem?' and pause for user confirmation, even when no ambiguity is detected"
+description: "Before executing a complex plan or non-trivial design — ask 'am I solving the right problem?' and pause for user confirmation, even when no ambiguity"
 alwaysApply: false
 source: package
 council_depth: deep

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

@@ -2,7 +2,7 @@
 type: "auto"
 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"
+description: "When writing or reviewing a diff — the smallest change that solves the stated problem; no drive-by edits, opportunistic refactors, or reformatting"
 source: package
 triggers:
   - intent: "writing a diff"

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

@@ -1,7 +1,7 @@
 ---
 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"
+description: "Starting a new task, switching task type, or invoking a command — detect complexity and recommend optimal model (Opus/Sonnet/GPT) before work"
 source: package
 triggers:
   - phrase: "switch task"

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

@@ -2,7 +2,7 @@
 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"
+description: "Generating PR/issue/comment/commit-message bodies — forbids 'Generated with', 'Co-authored by', or 'Pull Request opened by' attribution footers"
 source: package
 triggers:
   - intent: "PR body"

package/.agent-src/rules/no-roadmap-references.md

@@ -1,31 +1,49 @@
 ---
 type: "auto"
 tier: "mechanical-already"
-description: "Adding a link to a specific file in agents/roadmaps/ from any stable artifact (rule, skill, command, context, guideline) — roadmaps are transient; promote durable findings to agents/contexts/ instead"
+description: "Linking transient files (agents/roadmaps/, agents/council-{questions,responses,sessions}/) from a stable artifact — both layers expire; promote findings"
 alwaysApply: false
 source: package
 triggers:
   - path_prefix: "agents/roadmaps/"
+  - path_prefix: "agents/council-questions/"
+  - path_prefix: "agents/council-responses/"
+  - path_prefix: "agents/council-sessions/"
   - intent: "link from stable artifact"
+  - intent: "link to council artefact"
+routes_to:
+  - "skill:ai-council"
 validator_ignore:
   - type: "substring"
     pattern: ".agent-src.uncompressed/"
-    reason: "Rule contrasts the authoring tree with transient roadmap files."
+    reason: "Rule contrasts the authoring tree with transient layers."
 ---
 
-# No Roadmap References from Stable Artifacts
+# No Transient References from Stable Artifacts
 
-Roadmaps in `agents/roadmaps/` are **transient** — archived, skipped,
-or deleted as work completes. Stable artifacts (rules, skills,
-commands, contexts, guidelines, AGENTS.md, README) outlive them. A
-stable artifact citing a specific roadmap file becomes a broken
-reference the moment that roadmap is deleted.
+Two transient layers under `agents/` outlive nothing: roadmaps in
+`agents/roadmaps/` are archived, skipped, or deleted as work
+completes; council artefacts in `agents/council-{questions,responses,
+sessions}/` are **gitignored, local-only, and auto-pruned** after
+`ai_council.session_retention_days` (default 7). Stable artifacts
+(rules, skills, commands, contexts, guidelines, AGENTS.md, README,
+copilot-instructions) outlive both. A stable artifact citing a
+specific transient file becomes a broken reference the moment that
+file is deleted or pruned.
+
+Council links rot three ways: gitignored (not in cloned repo),
+pruned after retention window (gone even locally), and the installed
+`.augment/` projection cannot follow a path that does not exist in
+the consumer.
 
 ## The Iron Law
 
 ```
-NEVER LINK TO A SPECIFIC FILE IN agents/roadmaps/ FROM A STABLE ARTIFACT.
+NEVER LINK TO A SPECIFIC FILE IN agents/roadmaps/
+OR IN agents/council-{questions,responses,sessions}/
+FROM A STABLE ARTIFACT.
 PROMOTE DURABLE CONCLUSIONS TO agents/contexts/ AND CITE THAT INSTEAD.
+INLINE COUNCIL CONVERGENCE WITH DATE + MEMBERS, NEVER THE PATH.
 ```
 
 Stable artifact = anything that is **not** a roadmap, council
@@ -37,6 +55,9 @@ These paths must not appear inside a stable artifact:
 
 - `agents/roadmaps/<file>.md`, `agents/roadmaps/archive/<file>.md`,
   `agents/roadmaps/skipped/<file>.md`
+- `agents/council-questions/<file>.md`,
+  `agents/council-responses/<file>.json`,
+  `agents/council-sessions/<file>.json` or `<timestamp>/...`
 
 Stable artifact = any file under `.agent-src.uncompressed/{rules,
 skills,commands,contexts,templates,personas}/`, `agents/contexts/`,
@@ -44,38 +65,53 @@ skills,commands,contexts,templates,personas}/`, `agents/contexts/`,
 `docs/customization.md`, `docs/getting-started.md`, `docs/catalog.md`,
 `AGENTS.md`, `README.md`, `copilot-instructions.md`.
 
-CI enforcement: `scripts/check_no_roadmap_refs.py` (companion linter
-— fails the build on any new violation).
+CI enforcement: `scripts/check_no_roadmap_refs.py` (roadmap layer)
+and `scripts/check_council_references.py` (council layer) — both
+fail the build on any new violation.
 
 ## Allowed patterns
 
-- `agents/roadmaps/` and its subdirectories as directory mentions
+- `agents/roadmaps/` and `agents/council-*/` as **directory** mentions
   (talking about the layer, not a specific file)
 - Roadmap → roadmap references (siblings within the transient layer)
+- The `ai-council` skill and `/council:*` commands documenting the
+  output path schema
+- Inline council convergence summary — e.g. *"Council
+  (claude-sonnet-4-5 + gpt-4o, 2026-05-06) converged on …"* with
+  date + members, no filepath
 - Council sessions, `agents/.agent-chat-history`, commit messages, PR
   descriptions — transient by construction, not part of the package
   surface
 
 ## What to do instead
 
-When a stable artifact needs to cite a roadmap finding:
+When a stable artifact needs to cite a transient finding:
 
 1. Identify the durable conclusion — decision, contract, lesson,
    mechanic.
 2. Promote it to a context file under `agents/contexts/` (ADR,
-   mechanics doc, locked decision). The roadmap can then point at
-   the context, not the other way around.
+   mechanics doc, locked decision). The roadmap or council session
+   can then point at the context, not the other way around.
 3. Reference the context from the stable artifact.
+4. For council convergences specifically: inline a convergence-summary
+   block (members, date, cost if relevant — see `ai-council`
+   § Output format) instead of linking the session JSON.
+
+Failure modes:
 
-Failure mode: *"I'll just link to the roadmap, it's evidence."* The
-roadmap gets archived, then deleted, then the link rots. **Promote
-first, link second.**
+- *"I'll just link to the roadmap, it's evidence."* The roadmap
+  gets archived, then deleted, then the link rots. **Promote first,
+  link second.**
+- *"I'll just link to the session JSON, it's evidence."* The session
+  is gone in 7 days. **Inline first, link never.**
 
 ## See also
 
 - [`docs-sync`](docs-sync.md) — cross-reference sync after rename / delete
 - [`agent-docs`](agent-docs.md) — roadmap layer conventions
-- [`roadmap-progress-sync`](roadmap-progress-sync.md) — sync dashboard on
-  roadmap touch
+- [`roadmap-progress-sync`](roadmap-progress-sync.md) — sync dashboard
+  on roadmap touch
 - [`augment-source-of-truth`](augment-source-of-truth.md) — edit
   `.agent-src.uncompressed/`
+- [`ai-council`](../skills/ai-council/SKILL.md) — output path
+  convention and convergence-summary format

package/.agent-src/rules/onboarding-gate.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "1"
-description: "First turn of a conversation on a project — check onboarding.onboarded in .agent-settings.yml; when false, prompt the user to run /onboard before executing any other request"
+description: "First turn of a conversation on a project — check onboarding.onboarded in .agent-settings.yml; when false, prompt to run /onboard before any request"
 source: package
 triggers:
   - phrase: "first turn"

package/.agent-src/rules/package-ci-checks.md

@@ -1,5 +1,5 @@
 ---
-type: "auto"
+type: "manual"
 tier: "mechanical-already"
 description: "Before pushing to remote or creating a PR in the agent-config package — run all CI checks locally first"
 source: package

package/.agent-src/rules/reviewer-awareness.md

@@ -1,18 +1,25 @@
 ---
 type: "auto"
 tier: "2a"
-description: "When suggesting reviewers for a change — anchor the choice in paths and risk, never prestige or seniority; require primary + secondary role for medium/high risk"
+description: "When suggesting reviewers or flagging risk hotspots — anchor in paths/risk + ownership-map + bug-patterns; medium/high needs primary + secondary"
 source: package
 triggers:
   - keyword: "reviewer"
   - phrase: "suggest reviewers"
+  - phrase: "risk hotspot"
+  - phrase: "ownership map"
 routes_to:
   - "skill:review-routing"
 ---
 
 # Reviewer Awareness
 
-**Iron Law.** Anchor reviewer choice in paths and risk, never seniority; medium / high risk requires primary + secondary role.
+**Iron Law (reviewer choice).** Anchor reviewer choice in paths and risk, never seniority; medium / high risk requires primary + secondary role.
+
+**Iron Law (routing / risk).** Consult ownership-map and historical-bug-patterns before suggesting reviewers or claiming a change is safe.
 
 Body migrated to `skill:review-routing` (per P4 of `road-to-kernel-and-router.md`).
 Trigger-set above activates this routing under the `balanced` and `full` profiles.
+
+Consolidates the former review-routing-awareness rule per the
+package's adr-auto-rule-consolidation decision.

package/.agent-src/rules/roadmap-progress-sync.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "1"
-description: "Any roadmap touch (file move, checkbox flip, phase change) regens dashboard same response; archive at 0 open. Autonomous runs flip each checkbox the SAME reply, never batched at the end."
+description: "Any roadmap touch (file move, checkbox flip, phase change) regens dashboard same response; archive at 0 open. Autonomous runs flip checkboxes inline"
 source: package
 triggers:
   - path_prefix: "agents/roadmaps/"