@event4u/agent-config 2.26.0 → 3.1.0

package/.agent-src/commands/project-analyze.md

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "analyze the project structure, do a full project audit"
   trigger_context: "new project or after a major refactor"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # project-analyze
@@ -206,7 +218,7 @@ Per `verbosity.routine_confirmations` (default `false`):
   > 2. Skip — continue with next phase
   ```
 
-For each confirmed domain, create `agents/analysis/domains/{domain}.md` using the template
+For each confirmed domain, create `agents/evidence/analysis/domains/{domain}.md` using the template
 from the `project-analyzer` skill.
 
 ### Phase 6: API surface & service map
@@ -243,24 +255,24 @@ Per `verbosity.routine_confirmations` (default `false`):
   ```
 
 Create:
-- `agents/analysis/api/endpoints-v1.md`
-- `agents/analysis/api/endpoints-v2.md`
-- `agents/analysis/api/contracts.md`
-- `agents/analysis/services/service-map.md`
+- `agents/evidence/analysis/api/endpoints-v1.md`
+- `agents/evidence/analysis/api/endpoints-v2.md`
+- `agents/evidence/analysis/api/contracts.md`
+- `agents/evidence/analysis/services/service-map.md`
 
 ### Phase 7: Write analysis files
 
 Write all remaining analysis files that haven't been created yet:
 
-- `agents/analysis/overview.md` — project profile, tech stack summary
-- `agents/analysis/architecture/database.md` — schema, connections, multi-tenancy
-- `agents/analysis/architecture/api.md` — versioning, routes, middleware, auth
-- `agents/analysis/architecture/infrastructure.md` — Docker, CI/CD, deployment
-- `agents/analysis/architecture/patterns.md` — design patterns used
-- `agents/analysis/models/api-database.md` — all api_database models
-- `agents/analysis/models/customer-database.md` — all customer_database models
-- `agents/analysis/modules/{module}.md` — one per module
-- `agents/analysis/testing/test-map.md` — test suites, coverage, strategy
+- `agents/evidence/analysis/overview.md` — project profile, tech stack summary
+- `agents/evidence/analysis/architecture/database.md` — schema, connections, multi-tenancy
+- `agents/evidence/analysis/architecture/api.md` — versioning, routes, middleware, auth
+- `agents/evidence/analysis/architecture/infrastructure.md` — Docker, CI/CD, deployment
+- `agents/evidence/analysis/architecture/patterns.md` — design patterns used
+- `agents/evidence/analysis/models/api-database.md` — all api_database models
+- `agents/evidence/analysis/models/customer-database.md` — all customer_database models
+- `agents/evidence/analysis/modules/{module}.md` — one per module
+- `agents/evidence/analysis/testing/test-map.md` — test suites, coverage, strategy
 
 Per `verbosity.routine_confirmations` (default `false`):
 
@@ -310,7 +322,7 @@ Ask the user (in their language) what they want to do next:
 - **Present findings incrementally** — don't dump everything at once.
 - **Be honest about gaps** — flag missing docs and outdated references.
 - **Respect existing docs** — don't overwrite, offer to update.
-- **Reference existing `agents/docs/` and `agents/contexts/`** — don't duplicate their content
+- **Reference existing `agents/reference/docs/` and `agents/settings/contexts/`** — don't duplicate their content
   in analysis files. Link to them instead.
 - **Analysis files should be self-contained enough to rebuild** — include actual table names,
   column names, class names, method signatures. Not just "see the code".

package/.agent-src/commands/project-health.md

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "check project health, what's the state of my docs and modules"
   trigger_context: "routine health check, no destructive intent"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # project-health
@@ -51,7 +63,7 @@ AGENT DOCS:          {total count}
   📄 Guidelines:       {count} in .augment/guidelines/
   📋 Features:         {count} in agents/features/
   🗺️  Roadmaps:        {count} in agents/roadmaps/
-  📄 Contexts:         {count} in agents/contexts/
+  📄 Contexts:         {count} in agents/settings/contexts/
 
 ───────────────────────────────────────────────
 MODULE:              {total count}

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

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "fix the quality errors — run the project's type-checker / linter / formatter and resolve every issue (PHPStan / tsc / mypy / golangci-lint / clippy / …)"
   trigger_context: "type-checker / linter / formatter output in recent tool results (PHPStan, Rector, ECS, tsc, eslint, prettier, ruff, mypy, golangci-lint, clippy)"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # quality-fix

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

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "refine PROJ-123, tighten the acceptance criteria, is this ticket clear"
   trigger_context: "ticket key in prompt with vague acceptance criteria"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # refine-ticket

package/.agent-src/commands/research/deep.md

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "deep research, populate the research scaffold, fill outline.yaml items"
   trigger_context: "user has run `/research <topic>` and now wants per-item depth"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /research:deep

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "summarise research results, build research report, render outline.yaml results"
   trigger_context: "user has finished `/research:deep` and wants a single markdown summary"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /research:report

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "research a topic, scan competitors, benchmark X, do a tech-selection survey"
   trigger_context: "user names a research topic and wants a structured scaffold (objects + fields), not an immediate answer"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /research

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

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "self-review my changes, judge this diff before PR"
   trigger_context: "uncommitted or staged changes pre-PR"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # review-changes

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

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "who should review this, suggest reviewers for this PR"
   trigger_context: "PR open without assigned reviewers"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # review-routing

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

@@ -11,6 +11,18 @@ suggestion:
   eligible: true
   trigger_description: "council on roadmap, challenge this roadmap, stress-test the plan, refactor roadmap from council findings"
   trigger_context: "existing agents/roadmaps/*.md the user wants reviewed before execution"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /roadmap:ai-council
@@ -48,7 +60,7 @@ Follow [`/council default`](../council/default.md) Steps 2–4
 - `--input-mode roadmap`
 - `--depth deep` (this command declares `council_depth: deep` in
   frontmatter; the host translates it into `--depth deep`)
-- `--output agents/council-responses/<roadmap-stem>-roadmap.json`
+- `--output agents/runtime/council/responses/<roadmap-stem>-roadmap.json`
   (overwrite if it exists; the previous run is the predecessor for
   this iteration)
 - `--original-ask "<captured-ask>"`
@@ -94,7 +106,7 @@ content):
 
 ### Predecessor council trace
 
-`agents/council-responses/<roadmap-stem>-roadmap.json` (this run).
+`agents/runtime/council/responses/<roadmap-stem>-roadmap.json` (this run).
 ```
 
 Run `./agent-config roadmap:progress` after the append. The block
@@ -146,7 +158,7 @@ The user picks one or more numbers (`1,3,5` is allowed). Apply each selected pat
 
 `/roadmap:ai-council` may:
 
-- write `agents/council-responses/<…>.json`
+- write `agents/runtime/council/responses/<…>.json`
 - append the Council review block to the named roadmap
 - apply user-picked patches to the same roadmap
 - regenerate `agents/roadmaps-progress.md`

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "create a roadmap for X, plan this work as a roadmap"
   trigger_context: "multi-phase work without an existing agents/roadmaps/*.md"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /roadmap create
@@ -163,7 +175,7 @@ If the user picks **1**:
   verbatim, see `scripts/ai_council/prompts.py`).
 - Append the council findings as a `## Council review (<UTC date>)`
   section at the bottom of the roadmap. Include the trace path to
-  `agents/council-sessions/<timestamp>/raw-text.md` so future readers
+  `agents/runtime/council/sessions/<timestamp>/raw-text.md` so future readers
   can audit.
 - Do **not** rewrite the roadmap based on the findings — surface them,
   let the user decide what to act on.

package/.agent-src/commands/roadmap/process-full.md

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "process the whole roadmap, finish the roadmap, komplette roadmap abarbeiten"
   trigger_context: "existing agents/roadmaps/*.md and user wants the entire file done end-to-end"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /roadmap:process-full

package/.agent-src/commands/roadmap/process-phase.md

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "process the next phase, finish this phase autonomously, eine phase abarbeiten"
   trigger_context: "existing agents/roadmaps/*.md and user wants the next phase done end-to-end"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /roadmap:process-phase

package/.agent-src/commands/roadmap/process-step.md

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "process the next step, do the next roadmap step, einen schritt abarbeiten"
   trigger_context: "existing agents/roadmaps/*.md and user wants exactly one step done autonomously"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /roadmap:process-step

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "create a roadmap, process a roadmap, work through a roadmap autonomously, plan or abarbeiten"
   trigger_context: "user wants to scaffold or autonomously execute a roadmap under agents/roadmaps/"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /roadmap

package/.agent-src/commands/rule-compliance-audit.md

@@ -7,6 +7,18 @@ suggestion:
   eligible: true
   trigger_description: "audit my rules, check rule trigger quality"
   trigger_context: "maintainer working on .augment/rules/ files"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # rule-compliance-audit

package/.agent-src/commands/set-cost-profile.md

@@ -7,6 +7,18 @@ disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Settings mutation — must be deliberate."
+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/sync-agent-settings.md

@@ -6,6 +6,18 @@ disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Settings sync — must be deliberate."
+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/sync-gitignore/fix.md

@@ -9,22 +9,38 @@ suggestion:
   eligible: true
   trigger_description: "fix .gitignore garbage, clean up legacy agent-config entries, my .gitignore has stale agent entries, /sync-gitignore is not picking up the right paths"
   trigger_context: "consumer project carries pre-/agents/ runtime patterns (.agent-chat-history, .agent-prices.md) at the root from an older install"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /sync-gitignore:fix
 
 Cleanup sibling of [`/sync-gitignore`](../sync-gitignore.md). Strips
-legacy root-level patterns (pre-`/agents/` runtime artefacts —
+legacy patterns (pre-`/agents/` runtime artefacts —
 `.agent-chat-history`, `.agent-chat-history.bak`,
-`.agent-chat-history.*.bak`, `.agent-prices.md`, `.council-tmp/`) from
-**anywhere** in the consumer's `.gitignore` — inside or outside the
-managed block — then re-runs the regular sync so the current canonical
-`/agents/`-prefixed entries land in the block.
+`.agent-chat-history.*.bak`, `.agent-prices.md`, `.council-tmp/` —
+plus the 2.x intermediate `agents/runtime/.agent-prices.md`) from **anywhere**
+in the consumer's `.gitignore` — inside or outside the managed block —
+then re-runs the regular sync so the current canonical entries
+(`/agents/runtime/.agent-chat-history`, `/agents/runtime/.agent-prices.md`,
+`/agents/runtime/council/`) land in the block.
 
 Use when:
 
 - An older installer (pre-May 2026) dropped root-level `.agent-chat-history`
   / `.agent-prices.md` lines that the current scripts no longer recognise.
+- A 2.x install left `/agents/.agent-prices.md` in the block before the
+  cache moved under `/agents/runtime/`.
 - A hand-edit added one of those legacy paths and it now conflicts with
   the managed `/agents/...` entry.
 - `/sync-gitignore` reports "already in sync" but git is still ignoring
@@ -37,7 +53,7 @@ Use when:
   sub-command only touches the legacy pattern list — nothing else.
 - To delete the entire managed block → do it by hand.
 - To migrate runtime files themselves (move `.agent-chat-history` →
-  `agents/.agent-chat-history`) → the installer's
+  `agents/runtime/.agent-chat-history`) → the installer's
   `migrate_legacy_root_infra` step handles that. This sub-command only
   fixes `.gitignore`.
 
@@ -102,15 +118,18 @@ Free-text replies (`"nö"`, `"leave it"`, unrecognized input) count as
 
 ### 4. Suggest the migration check (informational, do NOT auto-run)
 
-If the cleanup removed `.agent-chat-history` or `.agent-prices.md`,
-mention that the **file** at the root (if still present) may need to
-move to `agents/`. The installer does this automatically via
-[`migrate_legacy_root_infra`](../../../scripts/install.sh); the
-agent does not run it from this command. One line of guidance is
-enough:
+If the cleanup removed `.agent-chat-history` or any flavour of
+`.agent-prices.md`, mention that the **file** itself (if still present
+at its old location) may need to move. The installer does this
+automatically via
+[`migrate_legacy_root_infra`](../../../scripts/install.sh) (chat-history,
+root → `agents/`) and
+[`migrate_legacy_prices_file`](../../../scripts/install.sh) (prices,
+root or `agents/` → `agents/runtime/`); the agent does not run them
+from this command. One line of guidance is enough:
 
 ```
-> ℹ️  If `.agent-chat-history` still sits at the project root, re-run the installer (or move it to `agents/.agent-chat-history` by hand) so the runtime can find it again.
+> ℹ️  If `.agent-chat-history` still sits at the project root, or `.agent-prices.md` still sits at the project root or under `agents/`, re-run the installer so the runtime can find them again.
 ```
 
 ## Rules

package/.agent-src/commands/sync-gitignore.md

@@ -7,6 +7,18 @@ disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Settings sync — must be deliberate."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /sync-gitignore
@@ -35,7 +47,7 @@ from anywhere in the consumer's `.gitignore` before re-syncing.
 
 Ensures the consumer project's `.gitignore` contains every entry the
 package expects to be ignored (symlinked `.augment/` subdirectories,
-`/agent-config` CLI wrapper, `.agent-settings*`, `agents/.agent-chat-history*`).
+`/agent-config` CLI wrapper, `.agent-settings*`, `agents/runtime/.agent-chat-history*`).
 Canonical list lives in `config/gitignore-block.txt`; the same file
 drives the installer, so the two cannot drift.
 

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "write tests for these changes, add tests for this branch"
   trigger_context: "code changes on the branch without matching test changes"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /tests create

package/.agent-src/commands/tests/execute.md

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "run the tests, execute the test suite"
   trigger_context: "code changes pending verification"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /tests execute

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "write tests for these changes, run the test suite"
   trigger_context: "user wants to author or run tests for the current branch"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /tests

package/.agent-src/commands/threat-model.md

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "threat model this change, what could go wrong security-wise"
   trigger_context: "changes touching auth, webhooks, uploads, secrets, or public endpoints"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # threat-model

package/.agent-src/commands/update-form-request-messages.md

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "sync the form request messages, update the validation messages"
   trigger_context: "edits to app/Http/Requests/*.php referencing rules without messages"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # update-form-request-messages