@event4u/agent-config 2.26.0 → 3.1.0

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

@@ -9,7 +9,19 @@ disable-model-invocation: true
 suggestion:
   eligible: true
   trigger_description: "document this part of the codebase, create a context doc for X"
-  trigger_context: "working in a module without an agents/contexts/ doc"
+  trigger_context: "working in a module without an agents/settings/contexts/ doc"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /context create
@@ -37,17 +49,17 @@ Check if `app/Modules/` exists. If yes, ask:
 ```
 Should the context be created in a module or in the project root?
 
-1. 📦 In a module → app/Modules/{Module}/agents/contexts/
-2. 🌐 Project root → agents/contexts/
+1. 📦 In a module → app/Modules/{Module}/agents/settings/contexts/
+2. 🌐 Project root → agents/settings/contexts/
 ```
 
 If module:
 - List available modules and ask which one.
-- Target: `app/Modules/{Module}/agents/contexts/`
+- Target: `app/Modules/{Module}/agents/settings/contexts/`
 - Create directory if it doesn't exist.
 
 If project-wide:
-- Target: `agents/contexts/`
+- Target: `agents/settings/contexts/`
 
 ### 3. Determine context type
 

package/.agent-src/commands/context/refactor.md

@@ -9,7 +9,19 @@ disable-model-invocation: true
 suggestion:
   eligible: true
   trigger_description: "update the context doc, refresh this context document"
-  trigger_context: "existing agents/contexts/*.md referenced in the prompt"
+  trigger_context: "existing agents/settings/contexts/*.md referenced in the prompt"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /context refactor
@@ -17,8 +29,8 @@ suggestion:
 
 ### 1. Find the context
 
-- List all context documents in `agents/contexts/`.
-- Also check module-level `app/Modules/*/agents/contexts/`.
+- List all context documents in `agents/settings/contexts/`.
+- Also check module-level `app/Modules/*/agents/settings/contexts/`.
 
 If only one context exists, ask if that's the one to refactor.
 If the user has a context file open in their editor, use that one.

package/.agent-src/commands/context.md

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "create a context document, update an existing context, refactor a context file"
   trigger_context: "user wants to author or restructure a context document"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /context

package/.agent-src/commands/cost-report.md

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "check this session's token cost, see budget utilization, surface 50/75/90/100% alert ladder"
   trigger_context: "user wants to know how expensive the active Claude Code session is or whether it crosses a budget threshold"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 <!-- cloud_safe: noop -->

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

@@ -9,7 +9,19 @@ disable-model-invocation: true
 suggestion:
   eligible: true
   trigger_description: "council on this analysis, critique the project-analyze output, second opinion on the audit findings, turn analysis into roadmap"
-  trigger_context: "user has a local analysis artefact (agents/analysis/*.md|json) and wants an external critique of the analysis quality + roadmap-ready follow-ups"
+  trigger_context: "user has a local analysis artefact (agents/evidence/analysis/*.md|json) and wants an external critique of the analysis quality + roadmap-ready follow-ups"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /council analysis
@@ -17,7 +29,7 @@ suggestion:
 ## Instructions
 
 Specialised council mode for **local analysis artefacts** — `/project-analyze`
-output, audit reports, codebase scans under `agents/analysis/`. Wraps
+output, audit reports, codebase scans under `agents/evidence/analysis/`. Wraps
 `/council default files:<path>` with the `analysis` neutrality preamble that
 focuses members on **critiquing the analysis itself** (dedup, evidence
 quality, roadmap-readiness) rather than re-reviewing the underlying code.
@@ -34,7 +46,7 @@ no path was supplied, ask (one question per turn, per
 
 > Which analysis artefact should the council review?
 >
-> 1. A file path under `agents/analysis/` (`.md` or `.json`)
+> 1. A file path under `agents/evidence/analysis/` (`.md` or `.json`)
 > 2. Multiple files (one analysis split across sections)
 > 3. Free-form analysis text in the chat — paste it now
 

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "council debate on X, multi-round rebuttal, escalate council to debate mode, push the council to argue not synthesize"
   trigger_context: "user wants real pushback — initial positions plus explicit rebuttals across rounds, with progressive cost confirmation between rounds"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /council debate
@@ -46,7 +58,7 @@ the agent's framing.
 ### 2. Decide round count + auto-continue
 
 Default: 2 rounds (initial position + one rebuttal). Cap: the value of
-`defaults.debate_max_rounds` in [`agents/.ai-council.yml`](../../../agents/.ai-council.yml)
+`defaults.debate_max_rounds` in [`agents/settings/.ai-council.yml`](../../../agents/settings/.ai-council.yml)
 (default 4). `--rounds N` overrides the default; values above the cap
 are rejected by the CLI.
 
@@ -82,7 +94,7 @@ to abort.
 
 ```bash
 python3 scripts/council_cli.py debate <topic-path> \
-  --output agents/council-sessions/<date>-<slug>/ \
+  --output agents/runtime/council/sessions/<date>-<slug>/ \
   --confirm \
   --rounds <N> \
   [--auto-continue] \
@@ -90,7 +102,7 @@ python3 scripts/council_cli.py debate <topic-path> \
   --original-ask "<verbatim topic>"
 ```
 
-Session directory shape: `agents/council-sessions/<YYYY-MM-DD>-debate-<slug>/`
+Session directory shape: `agents/runtime/council/sessions/<YYYY-MM-DD>-debate-<slug>/`
 with `debate-round-1.json`, `debate-round-2.json`, … written incrementally.
 An interrupted debate leaves every completed round on disk.
 
@@ -108,7 +120,7 @@ After all rounds complete, render the last round's JSON via
 `/council` render flow:
 
 ```bash
-python3 scripts/council_cli.py render agents/council-sessions/<dir>/debate-round-<N>.json
+python3 scripts/council_cli.py render agents/runtime/council/sessions/<dir>/debate-round-<N>.json
 ```
 
 The debate mode uses the structured decision-lens template (Karpathy
@@ -124,6 +136,6 @@ session directory is the canonical audit trail.
 
 If `DebateCapExceeded` fires, the CLI exits with code 3 and the partial
 debate is persisted. Surface the partial-debate path to the user and
-ask whether to (a) raise the cap in `agents/.ai-council.yml` and rerun,
+ask whether to (a) raise the cap in `agents/settings/.ai-council.yml` and rerun,
 (b) stop here and render the partial result, or (c) start a new debate
 with a smaller scope.

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

@@ -9,6 +9,18 @@ disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Default lens — invoked via /council dispatcher; no direct trigger."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /council default
@@ -94,7 +106,7 @@ Read `.agent-settings.yml` → `ai_council`:
   to env vars. Ever.
 
 Load the price table via `scripts.ai_council.pricing.load_prices()`
-(auto-bootstraps `agents/.agent-prices.md` from defaults if missing). Run
+(auto-bootstraps `agents/runtime/.agent-prices.md` from defaults if missing). Run
 `pricing.is_stale(table)` and, if stale, surface the staleness gate
 from the `ai-council` skill (§ Stale price-table gate) before
 continuing.
@@ -153,11 +165,11 @@ Wait for the user's pick. `1` proceeds; anything else aborts.
 ### 4. Run the CLI
 
 Once the user picks `1`, invoke the same arguments with `run` plus
-`--confirm` and an output path under `agents/council-sessions/`:
+`--confirm` and an output path under `agents/runtime/council/sessions/`:
 
 ```bash
 ./agent-config council:run <question-file> \
-    --output agents/council-sessions/<UTC-timestamp>.json \
+    --output agents/runtime/council/sessions/<UTC-timestamp>.json \
     --confirm \
     [--rounds 1|2|3] \
     [--depth standard|deep] \
@@ -240,7 +252,7 @@ include "discard council input" as an option.
 - Open, comment on, or merge any PR.
 - Run `git` commands beyond `git diff` (read-only).
 
-The CLI persists the responses JSON under `agents/council-sessions/`
+The CLI persists the responses JSON under `agents/runtime/council/sessions/`
 for traceability, but the agent never edits other project files on
 the user's behalf. The neutrality framing loses meaning if the
 council can act on the project directly.
@@ -268,7 +280,7 @@ council can act on the project directly.
 - **Stale price table, refresher fails (offline)** → state the
   failure, re-offer "continue with stale table / cancel", do not
   proceed silently.
-- **`agents/.agent-prices.md` corrupt (missing frontmatter or columns)** →
+- **`agents/runtime/.agent-prices.md` corrupt (missing frontmatter or columns)** →
   surface the parse error, suggest deleting the file to bootstrap
   fresh from defaults; never silently fall back.
 - **All members error (CLI exit 1)** → render the errors via

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "council on this design, second opinion on the ADR, external review of architecture proposal"
   trigger_context: "user has a design doc / ADR / architecture proposal and wants an external review before commitment"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /council design

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "council on this perf hot path, second opinion on this optimization, external review of /optimize output"
   trigger_context: "user has an optimization target (code path, query, profile result, /optimize-* output) and wants a ranked external opinion"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /council optimize

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "council on PR #N, external review of pull request, second opinion on a PR"
   trigger_context: "user has a PR number / URL and wants an external review before approve/merge"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /council pr

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "external second opinion, cross-AI review, devil's advocate on a plan/roadmap/diff, council on PR/design/optimize, polling another model"
   trigger_context: "user wants an outside critique on an artefact (roadmap, diff, prompt, files, PR, design doc, optimization target) without polluting the reviewer with the host agent's framing"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /council
@@ -66,7 +78,7 @@ Sub-command names match the locked contract in
 ## Advisor mode (replace-mode personas)
 
 Any sub-command above can run in **advisor mode** by enabling one or
-more advisors in `agents/.ai-council.yml` under `advisors:` (Contrarian,
+more advisors in `agents/settings/.ai-council.yml` under `advisors:` (Contrarian,
 First-Principles, Expansionist, Outsider, Executor). An enabled advisor
 swaps its bound member's plain call for the same provider running the
 advisor persona — **same call count, same budget**. `council:estimate`

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "write a PR description, draft the PR text"
   trigger_context: "PR exists or branch ready for review without description"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /create-pr:description-only

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "open a PR, create a pull request, make a PR for this branch"
   trigger_context: "branch is ahead of base and not yet on a PR"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /create-pr
@@ -44,6 +56,33 @@ Uses `/create-pr:description-only` to generate the PR content, then creates the
 - Run `git log origin/{default}..HEAD --oneline` to verify there are commits to push.
 - If the branch has not been pushed yet, ask the user (in their language) whether to push.
 
+### 1b. Freshness gate — MANDATORY before opening any PR
+
+The branch may have diverged from its target base while you were
+working. A PR opened against a stale base creates merge conflicts the
+moment another PR lands first — the exact failure that motivates this
+gate.
+
+Run, in order:
+
+1. `git fetch origin {target-base} --quiet` (default: `main`).
+2. `git rev-list --count HEAD..origin/{target-base}` — number of
+   commits HEAD is **behind** the base.
+3. `gh pr list --state open --base {target-base} --limit 20 --json number,headRefName,files`
+   — open PRs targeting the same base.
+
+**Decision matrix:**
+
+| Behind | Overlapping open PR touches same files? | Action |
+|---|---|---|
+| `0` | — | Proceed to Step 2 |
+| `1–N` | No | Surface the count, ask: rebase / merge-main / proceed-anyway / cancel |
+| `1–N` | **Yes** | STOP — surface the overlapping PR number, ask: stack on top of it / wait for it to land / proceed-anyway-and-accept-conflicts / cancel |
+
+Never improvise the base or silently proceed when the branch is behind
+and overlap exists. The 10-second fetch beats hours of rebase
+reconciliation after the parent PR lands.
+
 ### 2. Generate PR content
 
 Run `/create-pr:description-only` Steps 1–4 to generate the PR title and body.

package/.agent-src/commands/e2e-heal.md

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "fix the failing E2E tests, playwright tests are red"
   trigger_context: "failing test output from tests/e2e/"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # e2e-heal

package/.agent-src/commands/e2e-plan.md

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "plan E2E tests for this feature, what should we cover in playwright"
   trigger_context: "new feature or page added without tests/e2e/ coverage"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # e2e-plan

package/.agent-src/commands/estimate-ticket.md

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "how big is this ticket, estimate PROJ-123, should we split this"
   trigger_context: "ticket key matching [A-Z]+-[0-9]+ in the prompt and no plan yet"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # estimate-ticket

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "build this feature end-to-end, run the full feature workflow"
   trigger_context: "long-form feature description spanning multiple components"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /feature:dev
@@ -48,7 +60,7 @@ Do NOT use for single-line fixes, trivial changes, or urgent hotfixes.
    - Key files, services, models, routes involved
 2. Read identified files to build deep understanding.
 3. Check module docs (`app/Modules/*/agents/`) if applicable.
-4. Check existing contexts (`agents/contexts/`) for the affected area.
+4. Check existing contexts (`agents/settings/contexts/`) for the affected area.
 5. Present findings with file references.
 
 ### Phase 3: Clarifying Questions

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "brainstorm this idea, explore this feature concept"
   trigger_context: "open-ended feature idea without acceptance criteria"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /feature explore

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "plan this feature, create a feature spec for X"
   trigger_context: "feature idea referenced and no plan doc exists"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /feature plan
@@ -134,8 +146,8 @@ I analyzed the code. Here's what I found:
 ### 5a. Check for existing context
 
 Check if a context document exists for the affected area:
-- `agents/contexts/` for project-wide contexts
-- `app/Modules/{Module}/agents/contexts/` if a module is involved
+- `agents/settings/contexts/` for project-wide contexts
+- `app/Modules/{Module}/agents/settings/contexts/` if a module is involved
 
 If a context exists:
 ```

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "update the feature plan, refine the feature spec"
   trigger_context: "existing agents/features/*.md referenced in the prompt"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /feature refactor

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "turn this feature into a roadmap, generate the implementation roadmap"
   trigger_context: "existing feature plan without linked roadmap"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /feature roadmap

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "explore feature idea, plan a feature, refactor feature plan, roadmap a feature, full feature dev"
   trigger_context: "user starting or iterating on a feature workflow"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /feature

package/.agent-src/commands/fix/ci.md

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "CI is failing, fix the GitHub Actions errors, the pipeline is red"
   trigger_context: "open PR with failing checks"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /fix ci

package/.agent-src/commands/fix/portability.md

@@ -8,6 +8,18 @@ disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Package-internal — only the event4u/agent-config repo runs this."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /fix portability