@event4u/agent-config 2.25.0 → 3.0.0

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

@@ -1,13 +1,26 @@
 ---
 name: update-form-request-messages
 tier: 2
+framework: laravel
 skills: [laravel-validation]
-description: Sync the messages() method of a FormRequest class — add missing entries, link them to language keys, and clean up stale ones
+description: "Sync the messages() method of a FormRequest class — add missing entries, link them to language keys, and clean up stale ones."
 disable-model-invocation: true
 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

package/.agent-src/commands/upstream-contribute.md

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "contribute this back to agent-config, upstream this learning"
   trigger_context: "project-local skill/rule that fits the shared package"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /upstream-contribute

package/.agent-src/commands/video/from-script.md

@@ -11,6 +11,18 @@ suggestion:
   eligible: true
   trigger_description: "render a video from a script, full AI video pipeline, multi-scene generation"
   trigger_context: "user supplies a Markdown script with `## Scene N` headings and wants a final MP4"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /video:from-script

package/.agent-src/commands/video/scene.md

@@ -11,6 +11,18 @@ suggestion:
   eligible: true
   trigger_description: "render a single video scene, iterate on one shot, test a prompt without a full script"
   trigger_context: "user supplies a one-line scene idea and wants a single clip, no multi-scene stitching"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /video:scene

package/.agent-src/commands/video/stitch.md

@@ -11,6 +11,18 @@ suggestion:
   eligible: true
   trigger_description: "re-stitch existing video clips, rebuild final MP4 after edits, ffmpeg concat existing scenes"
   trigger_context: "user has edited clips in `<project>/scenes/*/` and wants the final.mp4 rebuilt without paying for re-renders"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /video:stitch
@@ -40,7 +52,7 @@ declared; no skill stack to resolve.)
 ### 2. Locate the project
 
 Resolve `<project-slug>` against the working directory. If neither
-`<slug>/manifest.json` nor `agents/ai-video/projects/<slug>/manifest.json`
+`<slug>/manifest.json` nor `agents/reference/ai-video/projects/<slug>/manifest.json`
 exists, fail with the searched paths.
 
 ### 3. Honor operator overrides

package/.agent-src/commands/video/storyboard.md

@@ -11,6 +11,18 @@ suggestion:
   eligible: true
   trigger_description: "build a storyboard, contact sheet of scenes, image-only preview, validate a script visually before video render"
   trigger_context: "user wants to see all scenes as stills before committing to motion calls"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /video:storyboard

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "create a video from a script, render a single scene, build a storyboard, re-stitch existing clips, AI video pipeline"
   trigger_context: "user mentions video generation, scene rendering, storyboard, ffmpeg stitch, or a `.ai-video.xml` config"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /video

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

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "build this, implement this, drive this end-to-end"
   trigger_context: "free-form prompt without a ticket key"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # work

package/.agent-src/contexts/augment-infrastructure.md

@@ -57,17 +57,14 @@ Define hard constraints: coding standards, Docker usage, language preferences, s
 |---|---|
 | `quality-workflow.md` | PHP (PHPStan → Rector → PHPStan) and JS/TS pipelines |
 | `downstream-changes.md` | After every edit, find and update ALL callers, tests, imports |
-| `docs-sync.md` | Keep docs in sync when skills/rules change |
+| `augment-edit-discipline.md` | Edits inside `.augment/` / `.agent-src.uncompressed/` stay project-agnostic AND sync counts + cross-references in the same edit |
 | `context-hygiene.md` | 3-failure rule, state dumps |
 | `architecture.md` | Architecture principles, file placement |
 | `docker-commands.md` | All PHP commands run inside Docker containers |
 | `commit-conventions.md` | Conventional Commits format |
 | `dev-efficiency.md` | Running CLI commands with verbose output — git, tests, linters, docker, build tools |
-| `e2e-testing.md` | Playwright E2E tests — locators, assertions, Page Objects, CI |
 | `lang-files.md` | Laravel lang files, both de/ and en/ always in sync |
 | `rtk.md` | Using rtk for token-efficient CLI output filtering |
-| `agent-docs.md` | When to read/create/update documentation |
-| `augment-portability.md` | Everything in `.augment/` must be project-agnostic |
 | `roadmap-progress-sync.md` | Checkbox edits in `agents/roadmaps/*.md` must regenerate `agents/roadmaps-progress.md` in the same response |
 
 ### Skills (`.augment/skills/`)
@@ -79,14 +76,14 @@ Skills organized by domain:
 
 | Category | Skills |
 |---|---|
-| **PHP/Laravel** | `php`, `php-coder`, `laravel`, `eloquent`, `laravel-validation`, `php-service`, `dto-creator`, `artisan-commands`, `laravel-horizon`, `laravel-mail`, `laravel-middleware`, `laravel-notifications`, `laravel-pennant`, `laravel-pulse`, `laravel-reverb`, `laravel-scheduling` |
+| **PHP/Laravel** | `php`, `php-coder`, `laravel`, `eloquent`, `laravel-validation`, `php-service`, `laravel-dto`, `artisan-commands`, `laravel-horizon`, `laravel-mail`, `laravel-middleware`, `laravel-notifications`, `laravel-pennant`, `laravel-pulse`, `laravel-reverb`, `laravel-scheduling` |
 | **API** | `api-endpoint`, `api-design`, `api-versioning`, `api-testing`, `openapi` |
 | **Analysis** | `analysis-autonomous-mode`, `universal-project-analysis`, `project-analysis-laravel`, `bug-analyzer`, `security-audit`, `performance-analysis` |
 | **Testing** | `pest-testing`, `test-generator`, `test-performance`, `php-debugging`, `playwright-testing` |
 | **Frontend** | `javascript`, `typescript`, `vue`, `react`, `nextjs`, `nuxt`, `tailwind`, `livewire`, `flux`, `blade-ui`, `fe-design` |
 | **Infrastructure** | `docker`, `aws-infrastructure`, `terraform`, `terragrunt`, `devcontainer`, `github-ci`, `cloudflare-workers`, `traefik` |
-| **Data** | `database`, `migration-creator`, `multi-tenancy`, `performance`, `sql-writing` |
-| **Jobs/Events** | `jobs-events`, `logging-monitoring`, `grafana`, `websocket` |
+| **Data** | `database`, `laravel-migration`, `multi-tenancy`, `performance`, `sql-writing` |
+| **Jobs/Events** | `jobs-events`, `logging-monitoring`, `grafana`, `laravel-websocket` |
 | **Packages** | `composer`, `composer-packages`, `npm`, `npm-packages` |
 | **Design** | `dashboard-design`, `design-review`, `fe-design` |
 | **Agent System** | `agent-docs-writing`, `agents-audit`, `context-create`, `commands`, `copilot-config`, `copilot-agents-optimization`, `feature-planning`, `file-editor`, `guidelines`, `mcp`, `override-management`, `project-docs`, `roadmap-management`, `module-management`, `naming`, `project-analyzer`, `sequential-thinking`, `skill-reviewer` |
@@ -155,7 +152,7 @@ Each guideline has a consistent header with **Related Skills**, **Related Rules*
 |---|---|
 | `features.md` | `agents/features/` or module `agents/features/` |
 | `roadmaps.md` | `agents/roadmaps/` or module `agents/roadmaps/` |
-| `contexts.md` | `agents/contexts/` or module `agents/contexts/` |
+| `contexts.md` | `agents/settings/contexts/` or module `agents/settings/contexts/` |
 | `overrides/rule.md` | `agents/overrides/rules/` |
 | `overrides/skill.md` | `agents/overrides/skills/` |
 | `overrides/command.md` | `agents/overrides/commands/` |
@@ -167,7 +164,7 @@ Each guideline has a consistent header with **Related Skills**, **Related Rules*
 **Shared context documents** about the `.augment/` system itself.
 These help agents understand the infrastructure they operate in.
 
-Unlike project contexts (`agents/contexts/`), these are part of the shared package
+Unlike project contexts (`agents/settings/contexts/`), these are part of the shared package
 and describe the agent system, not the project's business domain.
 
 ## Key Principles