@event4u/agent-config 9.8.0 → 9.10.0

package/docs/customization.md

@@ -1,696 +0,0 @@
-# Customization
-
-## Override System
-
-The project override system allows consumer projects to extend or replace shared skills,
-rules, and commands **without modifying the package**.
-
-```
-agents/overrides/
-├── skills/                  ← Override skill behavior
-│   └── pest-testing/
-│       └── SKILL.md         ← Replaces .augment/skills/pest-testing/SKILL.md
-├── rules/                   ← Override rule behavior
-│   └── php-coding.md        ← Replaces .augment/rules/php-coding.md
-└── commands/                ← Override command behavior
-    └── commit/
-        └── SKILL.md
-```
-
-**Resolution order:** project override → shared package (`.augment/`).
-
-Overrides are project-specific and should be committed to the consumer project.
-Use the `/override-create` command to scaffold a new override.
-
----
-
-## AGENTS.md
-
-Every consumer project should have an `AGENTS.md` at the project root.
-The installer copies a default version if none exists.
-
-`AGENTS.md` provides project-specific context to the agent: tech stack, conventions,
-module structure, test setup, and quality tooling.
-
-It is loaded by Claude Code, Augment Code, and Gemini CLI.
-
----
-
-## Agent Settings
-
-The `.agent-settings.yml` file in the consumer project configures agent behavior.
-It is written as YAML with section-level grouping; dotted keys below reference
-those sections.
-
-### User-global DX-comfort defaults (cross-project)
-
-Six **DX-comfort** keys can be carried across every project that uses
-`event4u/agent-config` by storing them once in a user-global file at:
-
-```
-~/.event4u/agent-config/agent-settings.yml
-```
-
-The path namespaces every event4u-owned user-global artefact under one
-root — same place where `anthropic.key`, `openai.key`, and
-`council-spend.jsonl` now live. Pre-2.4 installs that still keep these
-files under `~/.config/agent-config/` are read as a fallback until the
-namespace migration shim moves them.
-
-**Whitelist (locked, exact dotted paths)** — only these six keys are
-mergeable from the user-global file; every other key is silently ignored:
-
-```
-name
-ide
-rule_loading_tier
-personal.bot_icon
-personal.autonomy
-telegraph.speak_scope
-```
-
-**Merge order** (lowest → highest precedence; every layer optional):
-
-```
-1. Package defaults                                   (shipped by event4u/agent-config)
-2. ~/.event4u/agent-config/agent-settings.yml         (user-global · whitelist-filtered · legacy ~/.config/agent-config/ read as fallback)
-3. <repo-root>/.agent-settings.yml                    (project-wide · all keys)
-4. <intermediate-dir>/.agent-settings.yml             (subsystem-scoped · all keys · optional)
-5. <CWD>/.agent-settings.yml                          (deepest · all keys · wins)
-```
-
-`<repo-root>` is the nearest ancestor of the CWD that contains a `.git`
-directory **or** file (submodule support). The walk stops there — it
-never drifts into a parent repo or `$HOME`. Callers that omit the
-``cwd`` argument get the legacy two-layer behaviour (user-global +
-single project file) — back-compat is hard.
-
-Project-local values **always win** over user-global. The user-global
-file is a fallback, never a lock. Non-whitelisted keys in the
-user-global file are dropped without error — adding `personal.theme`
-there has no effect.
-
-**Whitelist asymmetry.** The six-key whitelist applies **only** to the
-user-global layer. Non-root in-project layers (intermediate +
-``<CWD>``) carry arbitrary keys — they live inside the project
-boundary, are tracked in git, and reviewed in PRs like any other
-config. Use a subdirectory `.agent-settings.yml` to scope a single
-field (e.g. a `rule_loading_tier` override for `services/heavy-ml/`) without
-duplicating the root file.
-
-The user-global file is created **only on explicit opt-in via the
-setup wizard** (`agent-config setup`). The loader at
-[`scripts/_lib/agent_settings.py`](../src/scripts/_lib/agent_settings.py)
-is **read-only** — no script can create or mutate it without explicit
-wizard confirmation. Edit the file by hand for mid-life changes;
-`/sync-agent-settings` stays project-scoped and never touches
-user-global state.
-
-### Agent config version pin
-
-The top-level `agent_config_version` key pins the project to an exact
-release of `@event4u/agent-config`. Under the npx-only distribution
-model (see [`docs/architecture.md`](architecture.md) §
-*"npx-only distribution + version-pin governance"*), there is no
-local `node_modules/` or `vendor/` lockfile to anchor the runtime —
-the pin is the substitute mechanism.
-
-```yaml
-agent_config_version: "2.0.3"   # exact semver, no ranges
-```
-
-Rules:
-
-- **Exact semver only.** Ranges (`^2.0`, `~2.0.3`, `>=2.0`) are
-  rejected — the pin must be reproducible across the team.
-- **Empty string = unpinned.** The resolver picks the latest release
-  on every invocation. Only safe for greenfield projects; production
-  consumers should pin.
-- **Owned by the project, not the developer.** Lives in
-  `.agent-settings.yml` (committed), reviewed in PRs like any other
-  config change. Never merged from `~/.event4u/agent-config/agent-settings.yml`.
-- **Resolver enforcement.** `npx @event4u/agent-config <cmd>`
-  compares the resolved CLI version against the pin; mismatch
-  triggers a re-exec at the pinned version
-  (`npx @event4u/agent-config@<pin> <cmd>`).
-
-### Editing settings
-
-`.agent-settings.yml` has two write surfaces — both share one
-canonical commit path:
-
-#### Via the GUI (recommended)
-
-Run `agent-config setup` for first-run onboarding (cost profile,
-identity, personality, memory, roadmap quality, optional
-`.agent-user.md`) or `agent-config settings` for subsequent edits.
-Both launch the same Fastify server on `127.0.0.1`; the setup
-command lands on `/#/wizard`, the settings command on `/#/settings`.
-Form primitives, JSON schema, and the `commitMulti` 2PC write path
-are shared. See [`docs/wizard.md`](wizard.md) for the step-by-step
-tour.
-
-#### By hand-editing the YAML (advanced)
-
-Open `.agent-settings.yml` in an editor and save. Hand edits skip
-the 2PC marker dance (your editor's atomic save is trusted), but
-you lose the schema validation, optimistic locking, and template
-substitution the GUI surfaces provide. Use this path for quick
-tweaks, comments, or bulk edits across multiple keys.
-
-#### Shared substrate
-
-Both GUI surfaces call `commitMulti` (2PC + intent marker,
-comment-preserving merge via `mergeIntoTemplate`); a crash mid-write
-is recovered on the next server boot.
-
-### Available settings
-
-| Setting | Default | Description |
-|---|---|---|
-| `agent_config_version` | *(empty)* | Exact semver pin of the agent-config release (see above). Empty = unpinned. |
-| `rule_loading_tier` | `balanced` | Token budget (`minimal`, `balanced`, `full`, `custom`) — rationale: [`docs/contracts/cost-profile-defaults.md`](contracts/cost-profile-defaults.md) |
-| `personal.user_name` | *(empty)* | User's first name for personalized responses |
-| `personal.minimal_output` | `true` | Suppress intermediate output |
-| `personal.play_by_play` | `false` | Share intermediate findings during analysis |
-| `personal.open_edited_files` | `false` | Open edited files in IDE |
-| `personal.ide` | *(empty)* | IDE for file opening (`cursor`, `code`, `phpstorm`) |
-| `pipelines.skill_improvement` | `true` | Post-task learning capture. Included in every profile except `custom`. |
-| `chat_history.enabled` | `true` | Persistent JSONL log at `agents/runtime/.agent-chat-history` for crash recovery. |
-| `chat_history.frequency` | per profile | Logging granularity: `per_turn`, `per_phase`, or `per_tool` (see matrix below). |
-| `chat_history.max_size_kb` | per profile | Max file size before overflow handling (see matrix below). |
-| `chat_history.on_overflow` | per profile | `rotate` drops oldest, `condense` marks for summarization (see matrix below). |
-| `onboarding.onboarded` | `false` | Whether the setup wizard has run. The `onboarding-gate` rule prompts for `agent-config setup` while this is `false`. |
-| `ai_council.enabled` | `false` | Master switch for the `/council` command. Even when enabled, every consultation asks before spending tokens. |
-| `ai_council.members.<provider>.enabled` | `false` | Per-provider opt-in (`anthropic`, `openai`). Tokens live in `~/.event4u/agent-config/<provider>.key` (mode 0600), never in this file. Legacy `~/.config/agent-config/<provider>.key` is read as a fallback. |
-| `ai_council.members.<provider>.model` | per provider | Which model the provider sends the query to (e.g. `claude-sonnet-4-5`, `gpt-4o`). |
-| `ai_council.cost_budget.max_input_tokens` | `50000` | Hard cap on summed input tokens per `/council` invocation. |
-| `ai_council.cost_budget.max_output_tokens` | `20000` | Hard cap on summed output tokens per `/council` invocation. |
-| `ai_council.cost_budget.max_calls` | `10` | Maximum council members per invocation. |
-| `ai_council.cost_budget.max_total_usd` | `0.0` | Per-invocation USD ceiling. `0` disables (token caps still apply). |
-| `ai_council.cost_budget.daily_limit_usd` | `0.0` | Rolling 24h USD ceiling across all `/council` calls. `0` disables. Ledger lives at `~/.event4u/agent-config/council-spend.jsonl` (mode 0600). |
-| `ai_council.session_retention_days` | `14` | Auto-prune for `agents/runtime/council/sessions/` audit folders. Older session directories are removed on the next `save()`. `0` disables (keep forever). |
-| `reasoning.enabled` | `true` | Master switch for the Reasoning Discipline Protocol (RDP). `false` = the whole layer is inert (zero overhead). See [`docs/contracts/reasoning-discipline-protocol.md`](contracts/reasoning-discipline-protocol.md). |
-| `reasoning.auto_gate` | `true` | Benefit-gates RDP on table-free signals (task signal + host self-assessment) so it engages only where it pays. `false` = gate on task-signal + toggles only (skip the host self-assessment). |
-| `reasoning.components.<name>` | `true` | Per-component switches — `orchestrator`, `notes_first`, `grounding`, `intent`, `complexity_first`, `verifier_default`, `prediction_tracking`, `decision_ledger`, `uncertainty_budget`. Each fires only when `reasoning.enabled` **and** the `auto_gate` test passes. |
-
-> **Experimental.** AI Council is not yet validated by external users. API costs apply per consultation.
-
-Council API tokens are installed via `./agent-config keys:install-anthropic`
-and `./agent-config keys:install-openai` — they prompt on `/dev/tty`, write to
-`~/.event4u/agent-config/<provider>.key` with mode `0600`, and never accept env
-vars. Pre-2.4 installs at `~/.config/agent-config/<provider>.key` are still
-honoured by the loaders as a fallback. The `/council` command refuses to run
-if the key file's permissions drift.
-
-The `reasoning.*` group controls the **Reasoning Discipline Protocol (RDP)** —
-a cost-gated layer that transplants the *operating discipline* of a frontier
-reasoning model onto any host model (it transfers discipline, never capability).
-For what it does, when it engages, and how to switch it off, see the user-facing
-contract [`docs/contracts/reasoning-discipline-protocol.md`](contracts/reasoning-discipline-protocol.md);
-the sourced rationale lives in the design dossier
-[`docs/guidelines/agent-infra/frontier-reasoning-operating-profile.md`](guidelines/agent-infra/frontier-reasoning-operating-profile.md).
-
-### Cost profiles
-
-> **Four "cost" concepts — don't confuse them.** Several settings sound like
-> they steer spend; only one is the rule-loading footprint:
->
-> | Concept | What it controls | What it's a lever for |
-> |---|---|---|
-> | `rule_loading_tier` *(this setting)* | How many behavioural rule tiers load each session | Token footprint of the rule layer (small, ~once per session) |
-> | `memory.cadence` | Whether the `🧠 Memory: …` visibility line renders (`auto`/`always`/`never`) | Output noise — **not** spend |
-> | `model.auto_switch` + a skill's `model_tier` | Which Claude model runs a skill (lite/medium/high → haiku/sonnet/opus) | The **dominant** per-turn spend lever (~10× delta) |
-> | `/cost:report` + `cost.budgets` | Tracking actual token/USD spend + optional ceilings | Budget enforcement |
->
-> Before the 2026-06-01 untangle, `rule_loading_tier` was named `cost_profile`
-> **and** the same key also carried the `memory.cadence` values — one key, two
-> colliding meanings. The rename split them so each lever owns its name. When
-> a budget is tight, reach for the **model** lever first — lowering the rule
-> tier saves little and drops guardrails.
-
-`rule_loading_tier` is the **legacy** master switch for rule-tier loading; its
-successor is the single runtime knob `discipline_profile: auto | off |
-essential | full` (ADR-110 — when set, it wins; legacy values map
-minimal→off, balanced→essential, full→full). The kernel (always-loaded
-Iron-Law floor, ≤ 26k chars across 9 rules) ships in every profile. Tier-1
-and tier-2 trigger routing stays active under every profile (trigger
-semantics are configuration-independent, ADR-040); the profile names the
-always-honoured surface, resolved at session start from `dist/router.json`
-(compiled by `scripts/compile_router.ts`).
-
-| Profile | Always-honoured surface | Token footprint | Best for |
-|---|---|---|---|
-| `off` (legacy `minimal`) | kernel only | ~1x (lowest) | Hosts with a MEASURED null discipline lift (`src/config/host-capabilities.yml`); cost-sensitive sessions |
-| `essential` | kernel + the lift-carrying rules (`downstream-changes`) | ~3.3x | Day-to-day work — keeps the measured weak-host discipline lift (+0.458, p=0.0135) |
-| `full` | kernel + tier-1 + tier-2 (everything) | ~11.7x (highest) | EXPERIMENTAL opt-in — residual lift over `essential` not established (p=0.37); agent-config development |
-| `auto` | resolved per session: measured-null host → `off`; unmeasured Claude-family → `essential`; unmeasured non-Claude → `off` (P2 verdict, vendor-granular `unknown_defaults`) | varies | The balanced-preset default — lift only where measured |
-| `custom` (legacy) | profile ignored — every matrix value must be set explicitly | varies | Power users with bespoke rule sets |
-
-> **`balanced` was retired 2026-07-07** — the size cut (kernel + tier-1)
-> measured a NULL discipline lift (p=0.81, `docs/benchmark.md § Cost-factor
-> sweep`) because it missed the lift-carrying `downstream-changes`. Existing
-> `rule_loading_tier: balanced` settings keep working and map to `essential`.
-
-The kernel-and-router architecture is documented in
-[`docs/contracts/rule-router.md`](contracts/rule-router.md) and
-[`docs/contracts/kernel-membership.md`](contracts/kernel-membership.md).
-Tier flags live in each rule's frontmatter (`tier: kernel | tier-1 | tier-2`);
-the router compiles them into `dist/router.json` deterministically.
-
-All profiles except `custom` ship with `pipelines.skill_improvement: true`,
-so the agent captures learnings after meaningful tasks by default. Set it
-to `false` in `.agent-settings.yml` to silence post-task analysis without
-changing the profile.
-
-The authoritative matrix of all matrix-controlled settings lives in
-[`src/agent-src/templates/agent-settings.md`](../src/agent-src/templates/agent-settings.md).
-
-### Chat-history defaults per profile
-
-`scripts/install.py` fills these placeholders from
-[`src/config/profiles/*.ini`](../config/profiles) when it writes
-`.agent-settings.yml`. Edit the values afterwards if you want different
-behavior — the per-profile table is just the initial default.
-
-| Setting | `minimal` | `balanced` | `full` |
-|---|---|---|---|
-| `chat_history.enabled` | `true` | `true` | `true` |
-| `chat_history.frequency` | `per_turn` | `per_phase` | `per_tool` |
-| `chat_history.max_size_kb` | `128` | `256` | `512` |
-| `chat_history.on_overflow` | `rotate` | `rotate` | `condense` |
-
-`custom` ignores these defaults — set every value explicitly.
-
-### Verbosity
-
-The `verbosity:` block and `telegraph.speak_scope` control how much narration
-the agent emits around routine actions. Defaults are tuned for token
-frugality — flip values to `true` (or higher tier) to restore legacy verbose
-output. Iron-Law gates (`commit-policy`, `scope-control` git-ops,
-`non-destructive-by-default`) ALWAYS confirm regardless of these flags.
-
-| Setting | Values | Default | Description |
-|---|---|---|---|
-| `verbosity.preview_artifacts` | `true`, `false` | `false` | Show generated commit messages, PR titles/bodies, and branch names before acting. `false` = use the generated content directly. |
-| `verbosity.routine_confirmations` | `true`, `false` | `false` | Confirmation prompts for routine workflow steps when there is one obvious answer ("looks good — commit?"). Iron-Law gates always ask regardless. |
-| `verbosity.offer_council_in_delivery` | `true`, `false` | `false` | Offer "run AI Council on this?" inside delivery commands (`/feature-plan`, `/review-changes`, `/roadmap-create`). The `/council` command itself is unaffected. |
-| `verbosity.post_action_reports` | `off`, `minimal`, `full` | `minimal` | Multi-line status / summary blocks after a successful action. `off` = no report; `minimal` = one-line confirmation; `full` = bullet list. |
-| `verbosity.intent_announcements` | `true`, `false` | `false` | Intent announcements ("Let me check…", "Now I will…", "Found it") in skill bodies. `false` = act and emit the result. |
-| `verbosity.script_output` | `silent`, `minimal`, `verbose` | `minimal` | Stdout chatter from `scripts/*.py`, `scripts/*.sh`, and `.augment/scripts/`. `silent` = stderr only; `minimal` = one summary line per script; `verbose` = pre-Phase-10 per-step prints. Iron-Law surfaces (release confirms, install secrets prompts, error markers) ignore this key. |
-| `verbosity.taskfile_command_echo` | `true`, `false` | `false` | Suppress the `task: [name] cmd...` echo Taskfile prints before each task body. `true` = echoes preserved (legacy behaviour); `false` = `silent: true` is set on every Phase-10 safe task. |
-| `telegraph.speak_scope` | `off`, `prose_only`, `aggressive` | `prose_only` | How widely telegraph-speak grammar applies in chat. `off` = no telegraph; `prose_only` = telegraph in body prose, numbered options + Iron-Law-literal blocks stay full prose; `aggressive` = telegraph everywhere except Iron-Law literals. |
-
-The cross-rule index for these defaults lives in
-[`src/agent-src/contexts/contracts/frugality-charter.md`](../src/agent-src/contexts/contracts/frugality-charter.md).
-Writer skills (`skill-writing`, `rule-writing`, `command-writing`,
-`guideline-writing`, `roadmap-writing`, `persona-writing`,
-`agent-docs-writing`, `context-authoring`, `conventional-commits-writing`,
-`readme-writing`, `readme-writing-package`, `adr-create`) cite the charter
-under their `## Frugality Standards` section.
-
-#### Behavior change vs. legacy — `/create-pr` silent draft default
-
-When `verbosity.routine_confirmations: false` (the new default),
-`/create-pr` creates the PR as a **draft silently** instead of asking
-"draft or ready?". A one-line postscript surfaces the override:
-
-```
-→ #42 opened: https://github.com/org/repo/pull/42
-→ created as draft — run `gh pr ready 42` to flip
-```
-
-Per-invocation overrides (no settings change required):
-
-| You want | Argument |
-|---|---|
-| Ready-for-review immediately | `/create-pr:ready` or `/create-pr:final` |
-| Explicit draft (no postscript change) | `/create-pr:draft` |
-| Numbered prompt restored | set `verbosity.routine_confirmations: true` |
-
-`/create-pr` still skips the AI council prompt unconditionally per the
-existing carve-out — `verbosity.offer_council_in_delivery` does not
-re-enable it. Use `/council diff:<base>..<head>` separately.
-
-#### PR description content — tier + enrichments
-
-The `commands.create_pr.*` block controls how much the generated PR
-**description body** carries. Defaults are tuned for token frugality: the
-description defaults to `min`, and the two enrichments are additive and
-self-limiting (grounded / capability-gated), so `min` stays genuinely
-minimal without ever dropping a critical callout.
-
-| Setting | Values | Default | Description |
-|---|---|---|---|
-| `commands.create_pr.detail_level` | `min`, `med`, `max` | `min` | Verbosity tier of the Description section. `min` = title + 2-3 sentence what/why/impact + linked ticket; `med` = `min` + grouped changes + tests note; `max` = `med` + how-to-test + edge cases + reviewer guidance. Critical info (breaking changes, migrations, security, rollback) is included at **every** tier — the tier governs explanatory depth, never whether a critical callout appears. |
-| `commands.create_pr.api_examples` | `true`, `false` | `true` | Add a fenced JSON request/response example for API-endpoint changes. `true` = include **only** when grounded in a real source (DTO/resource, OpenAPI, test fixture, or an actual probe); otherwise a one-line pointer, never an invented example. `false` = never. |
-| `commands.create_pr.screenshots` | `true`, `false` | `false` | Capture frontend screenshots for UI changes. `false` = never. `true` = attempt when the host has browser/preview tooling and the diff touches a frontend surface; capability-gated (emits a one-line note and leaves the placeholder when tooling is absent, never fails or blocks the PR). Before/after + region-highlighting is best-effort; byte-embedding into the PR body is not possible via the GitHub API (host image-upload or manual attach). |
-| `commands.create_pr.ui_paths` | glob list | `[]` | Optional globs that make frontend detection explicit (e.g. `["resources/views/**", "src/pages/**"]`). Empty = a light path/extension heuristic that fails open. |
-| `commands.create_pr.api_paths` | glob list | `[]` | Optional globs that make API-endpoint detection explicit (e.g. `["app/Http/Controllers/Api/**", "src/pages/api/**"]`). Empty = a light heuristic that fails open. |
-
-These flags are read once at the top of the `/create-pr` run and cached; the
-content flags feed `/create-pr:description-only` generation. `min` is the
-default precisely because a shorter description costs fewer output tokens on
-every PR — turn it up per-project (or per-invocation via the settings file)
-when reviewers want the richer context.
-
-#### Script-output level — env-var overrides
-
-`verbosity.script_output` is read by `scripts/_lib/script_output.py`.
-For incident debugging when editing `.agent-settings.yml` is awkward,
-two env vars override the file for the current process tree:
-
-| Env var | Value | Effect |
-|---|---|---|
-| `AGENT_SCRIPT_VERBOSITY` | `silent`, `minimal`, `verbose` | Authoritative — wins over the settings file |
-| `SCRIPT_OUTPUT_VERBOSE` | `1` | Alias — equivalent to `AGENT_SCRIPT_VERBOSITY=verbose` |
-
-Once the helper resolves the level, it exports the resolved value back
-into `AGENT_SCRIPT_VERBOSITY` so child processes inherit the same level
-without re-reading the settings file. Per-call `--quiet` flags on a
-child script still win at the call site (per-call override > inherited
-level).
-
-Iron-Law surfaces — production-deploy confirmation prompts in
-`scripts/release.py`, secret-installer prompts in `install_*_key.sh`,
-and any output via `error()` — bypass the helper and stay loud at every
-level.
-
----
-
-## Autonomous roadmap execution
-
-Roadmaps can declare how `/roadmap:process-full` / `process-phase`
-should interact, via frontmatter (`/roadmap:create` asks this as one
-question at creation time):
-
-```yaml
-execution:
-  mode: autonomous   # autonomous | phase-checkpoints | interactive
-```
-
-- `interactive` (absent-field default) — every gate fires as today.
-- `phase-checkpoints` — one compact status + continue prompt per phase
-  boundary.
-- `autonomous` — at run start the loop derives an **execution
-  contract** (feature branch, chunked commits, push to that branch
-  only, PR-open — never merge, batched artifact drafting, council
-  auto-enable). ONE acceptance activates all grants for the run; after
-  that the run is uninterrupted except the safety floors (Hard Floor,
-  security-sensitive-stop, N=3 validation budget, context-hygiene
-  aborts, deferred-`[~]` archival gate).
-
-The frontmatter field is a declaration of intent, never a permission
-grant — authorization happens only at the run-start contract, derived
-fresh from the roadmap's current content on every invocation. Details:
-`contexts/execution/roadmap-execution-contract.md`, template rule 18 in
-`templates/roadmaps.md`. Global `roadmap.*` keys in
-`.agent-settings.yml` (quality/dashboard cadence, pre-run gate) keep
-their meaning in every mode.
-
----
-
-## Project documentation
-
-Consumer projects can maintain their own agent documentation:
-
-```
-agents/
-├── overrides/               ← Skill/rule/command overrides (required after migrate)
-├── knowledge/               ← Optional: curated project-specific knowledge pages
-├── memory/                  ← Optional: memory promotion pipeline
-├── roadmaps/                ← Optional: project-local roadmaps
-├── tmp/                     ← Optional: user inbox (gitignored)
-└── tmp.old/                 ← Optional: processed inbox archive (gitignored)
-```
-
-Full classification (git policy, retention, owner) for every allowed entry:
-[`docs/contracts/agents-layout.md`](contracts/agents-layout.md).
-
-#### Environment bootstrap (optional)
-
-If standing up your project takes more than a package install — starting
-services, seeding fixtures, generating config — declare a single **`env-bootstrap`**
-entry in your runner file (a `Taskfile.yml` / `Makefile` target or a
-`package.json` script named `env-bootstrap`). When present, the agent surfaces
-it as the suggested first action at worktree/session stand-up (see the
-`using-git-worktrees` skill § 5) — **suggest-only, never auto-run**. This gives
-long-running work one deterministic stand-up entry instead of re-deriving it
-each session. Purely optional: with no entry, dependency install + a green
-baseline is the whole stand-up.
-
-#### User inbox workflow (`agents/tmp/` → `agents/tmp.old/`)
-
-Drop a note or draft into `agents/tmp/` and point a command at it
-(e.g. "create a roadmap from `agents/tmp/my-idea.md`"). The agent reads
-the file, processes it, and moves it to `agents/tmp.old/` in the same
-reply. The archive decays via a 30-day janitor TTL.
-
-- Both dirs are **gitignored** — they never enter the commit graph.
-- The agent's own scratch goes to `agents/runtime/tmp/` — never into `agents/tmp/`.
-- Run `task janitor` for a dry-run report; `task janitor-apply` to sweep.
-
-#### Keeping your consumer `agents/` clean
-
-Run the sync-gitignore fix command after an install or migration:
-
-```bash
-agent-config sync-gitignore --cleanup-legacy
-# Or via the chat command: /sync-gitignore:fix
-```
-
-This scrubs legacy patterns, syncs the managed block, and reports any
-files that are tracked but now ignored (the `git rm --cached` commands
-to fix them are printed — never run automatically).
-
-Module-level documentation goes into `app/Modules/*/agents/`.
-
-### `agents/` overlay cascade
-
-A subset of `agents/` subdirs participates in the same deepest-wins
-cascade as `.agent-settings.yml` (see *"User-global DX-comfort
-defaults"* above). The cascade is **per-file** by basename — the
-deepest existing `agents/<kind>/<name>.md` wins; the rest are silently
-shadowed.
-
-**One exception, and it is not silent.** Kernel and `tier: safety-floor`
-rules sit outside the cascade: a `Mode: replace` override on one is
-refused and reported, and a `Mode: extend` (a tightening) needs a
-registered entry in `agents/overrides/kernel-exceptions.yml`. See
-[`override-system`](../src/agent-src/contexts/override-system.md)
-§ *The non-overridable class* — including its stated limit, since the
-class is a norm with a partial gate, not a proof.
-
-| Subdir | Cascade? | User-global allowed? | Why |
-|---|---|---|---|
-| `agents/overrides/` | ✅ Yes — deepest wins by basename. | ✅ Yes — weakest layer. | Personal developer overrides. |
-| `agents/settings/contexts/` | ✅ Yes — deepest wins by basename. | ❌ No — project-shaped. | Shared knowledge; would leak across projects. |
-| `agents/decisions/` | ✅ Yes — deepest wins by basename. | ❌ No — project-shaped ADRs. | Decisions are repo-bound. |
-| `agents/roadmaps/` | ❌ No — project-rooted only. | ❌ No. | Active delivery plans. |
-| `agents/runtime/state/`, `agents/memory/`, `agents/work_engine/`, `agents/runtime/.agent-prices.md`, `agents/runtime/council/*/` | ❌ No — stateful / session-scoped. | ❌ No. | Per-session state, not shareable. |
-
-**User-global asymmetry.** `~/.event4u/agent-config/agents/overrides/`
-is the only user-global overlay path consulted by the loader (the
-legacy `~/.config/agent-config/agents/overrides/` tree is read as a
-fallback). Files under `~/.event4u/agent-config/agents/settings/contexts/` or
-`.../agents/decisions/` are silently skipped — these kinds are
-project-shaped and must not leak across projects.
-
-The resolver lives at
-[`scripts/_lib/agents_overlay.ts`](../src/scripts/_lib/agents_overlay.ts)
-and is enforced by
-[`scripts/check_overlay_cascade_subdirs.ts`](../src/scripts/check_overlay_cascade_subdirs.ts)
-— drift between the code constants (`CASCADE_ELIGIBLE_KINDS`,
-`USER_GLOBAL_OVERLAY_KINDS`) and the table above breaks the build.
-(Both were `.py` before the ADR-200 TypeScript port; the old paths were
-cited here long after they were deleted.)
-
----
-
-## Workspaces & packs (discovery)
-
-Every shipped artefact (skill, rule, command, template) carries five
-discovery keys in its frontmatter — `workspaces:`, `packs:`,
-`lifecycle:`, `trust:`, `install:`. The contract is defined in
-[ADR-013](decisions/ADR-013-discovery-frontmatter-contract.md) and the
-closed vocabularies live in
-[`src/config/discovery/workspaces.yml`](../config/discovery/workspaces.yml)
-(9 workspaces) and
-[`src/config/discovery/packs.yml`](../config/discovery/packs.yml) (21
-packs).
-
-At release time, `scripts/build_discovery_manifest.py` walks the source
-trees, validates frontmatter against the vocabularies, and writes
-`dist/discovery/discovery-manifest.json` + the human-readable
-`discovery-manifest.summary.md`. The manifest ships inside the published
-tarball and is the source of truth consumed by:
-
-- `npx @event4u/agent-config workspaces ls` / `packs ls` (CLI)
-- the installer's pack-selection prompts
-- downstream tools that resolve "which skills install for workspace X".
-
-> **Virtual packs and workspaces — a tag, not a directory.** A pack is a
-> label in an artefact's frontmatter, not a folder on disk. A workspace
-> is a label that groups packs, not a git submodule. The discovery
-> scanner emits a JSON catalogue; it does **not** move files, create
-> sub-`package.json` entries, or generate per-pack `node_modules/`.
-> When you read "the Laravel pack", picture a filter over the shared
-> artefact tree — not a separate npm package. The day ADR-011's
-> extraction trigger flips, the same scan output drives the split;
-> until then, every artefact lives under `src/`.
-
-Alongside the JSON manifest, the scanner writes
-`dist/discovery/discovery-manifest.json.sha256` — a sidecar hash that
-lets downstream consumers detect tampering before trusting the
-manifest's `trust.level` claims.
-
-CI gates: `task lint-discovery-vocab` (vocabulary integrity),
-`task lint-discovery-manifest` (manifest validity),
-`task lint-artefact-frontmatter` (per-file frontmatter sanity), and
-`task check-discovery-determinism` (byte-identical re-runs).
-`task check-release-includes-discovery` is the prepublish guard that
-refuses to ship a tarball without the manifest.
-
-Consumer projects do **not** edit these YAMLs directly — they pick
-packs at install time via `npx @event4u/agent-config install` and the
-resulting `.agent-settings.yml` records which packs the project opted
-into.
-
-### Session profiles — surface one audience for the current session
-
-Install every pack once, then **activate a profile per session** so only
-the matching packs' commands/skills are the surfaced set:
-
-- `/profile activate laravel` — surface the Laravel closure
-  (`laravel` + `php` + `engineering-base`) + core artefacts; everything
-  else is hidden from `/help` and the skill surface.
-- `/profile activate po` — switch to the product-owner surface.
-- `/profile show` — active packs + surfaced/hidden counts.
-- `/profile deactivate` — full surface returns.
-
-The activatable name is a session-profile alias
-(`src/config/discovery/session-profiles.yml`: `developer`, `po`, `finance`,
-`gtm`, `content`) or a raw pack id. It is **recommendation-bias only** —
-an inactive-pack command still runs (with a one-line notice); execution is
-never blocked. The choice is **ephemeral**: it writes
-`runtime.active_packs` to the gitignored `agents/settings/.agent-settings.local.yml`,
-never the committed config, and is cleared with `/profile deactivate`.
-A new session emits a staleness reminder if a profile is still active.
-
-This is a runtime view over the existing **pack** axis, not a new axis,
-and is unrelated to the install `--profile=<minimal|balanced|full>` flag
-(which sets `rule_loading_tier`). Full contract:
-[`session-profile-overlay`](contracts/session-profile-overlay.md).
-
----
-
-## Update check
-
-`npx @event4u/agent-config <cmd>` checks the npm registry once per
-24 h for a newer release of the package and, when one is available,
-writes a two-line banner to **stderr** *after* the subcommand has
-finished. There is no prompt — the user updates when they want with
-`npx @event4u/agent-config update` (Phase 3).
-
-```
-ℹ️  agent-config 1.42.0 available (you have 1.38.0).
-    Update: npx @event4u/agent-config update
-```
-
-State is persisted at `~/.event4u/agent-config/update-check.json`
-(mode `0600`; the legacy `~/.config/agent-config/update-check.json`
-is read as a fallback) — sibling of `anthropic.key`,
-`council-spend.jsonl`. The fetch is hard-capped at 1 s and silent on
-any error.
-
-### Suppression matrix
-
-The banner is silently skipped when **any** of the following match:
-
-| Condition | Reason |
-|---|---|
-| `CI=1` / `CI=true` / `GITHUB_ACTIONS=true` | CI noise, breaks log scrapers. |
-| `stdout` is not a TTY | Piped / redirected output must stay clean. |
-| `AGENT_CONFIG_NO_UPDATE_CHECK=1` | Per-invocation escape hatch. |
-| `update_check.enabled: false` in `.agent-settings.yml` | Project / user opt-out. |
-| Registry call exceeds 1 s | Network must never delay `npx`. |
-| Registry call raises any exception | Best-effort — failure is silent. |
-
-`update_check.enabled` is a **project-scoped** key — it is *not* on
-the user-global whitelist (see [§ Agent Settings](#agent-settings)).
-Each project decides; the user-global file cannot flip it on or off
-for unrelated projects.
-
-The decision logic lives at
-[`scripts/_lib/update_check.py`](../src/scripts/_lib/update_check.py); the
-dispatcher integration lives in [`scripts/agent-config`](../src/scripts/agent-config)
-(`run_update_check_banner`).
-
----
-
-## Explainability — `explain last`
-
-`agent-config explain last` reconstructs the execution trace for the
-most recent `/work`, `/implement-ticket`, `/council`, or `/video` run.
-Read-only by construction — never writes back, never opens a network
-socket. Output is the `ExplainTrace` v1 contract
-([`docs/contracts/explain-trace.schema.json`](contracts/explain-trace.schema.json));
-free-form strings pass through the shared PII scrubber before they hit
-your terminal.
-
-```
-agent-config explain last              # Markdown trace
-agent-config explain last --json       # ExplainTrace JSON
-agent-config explain last --quiet      # no trailing tip footer
-```
-
-Sample Markdown output:
-
-```markdown
-# explain last — run PROJ-1234
-
-**Subject:** /implement-ticket · **Started:** 2026-05-19 10:14:22Z
-
-## Why this route?
-- Active rules: architecture, downstream-changes
-- Kernel rules: 9
-- Persona: senior-engineer
-
-## Why this profile / preset?
-| knob | value | source |
-|---|---|---|
-| profile.id | developer | user (.agent-settings.yml) |
-| preset.id  | balanced  | profile.developer |
-
-## Assumptions
-- [x] api-rate-limit-is-100rpm — accepted in step `refine`
-```
-
-Disable for `rule_loading_tier: minimal` CI runs by setting `explain.enable_last: false`
-in `.agent-settings.yml`; the command then exits 0 with a one-line
-notice instead of producing a trace. Exit codes: `0` rendered or
-disabled · `1` no recent run found · `2` invocation error.
-
-## Troubleshooting
-
-### A skill appears twice in my AI tool
-
-Most common cause: cross-scope drift between a user-global install (e.g.
-`~/.claude/skills/`) and a project-local install (e.g. `./.claude/skills/`).
-Run the probe to confirm:
-
-```bash
-task probe:skills
-# or directly: ./scripts-run src/scripts/probe_skill_registration
-```
-
-The probe lists every registration across all six tools and flags
-`DUPLICATE` (same skill in ≥ 2 sources) and `DRIFT` (same skill, different
-descriptions or versions — the actual 2026-05-25 failure mode). To clean a
-stale install at the other scope: `bash scripts/cleanup_other_scope.sh --confirm`.
-Background: [`docs/contracts/skill-distribution-channels.md`](contracts/skill-distribution-channels.md)
-+ [`docs/contracts/install-scopes.md`](contracts/install-scopes.md).
-
----
-
-← [Back to README](../README.md)