@event4u/agent-config 2.25.0 → 3.0.0

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "run a saved orchestration / pipeline / chain"
   trigger_context: "user names a pipeline file or asks to replay a chain"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # orchestrate
@@ -107,7 +119,7 @@ When the pipeline reaches the end of `steps[]`:
 
 Per [`audit-log-v1`](../docs/contracts/audit-log-v1.md), append
 one JSONL entry per step boundary to the current month's audit file
-under `agents/state/audit/`. Counts + ids only — never the step's
+under `agents/runtime/state/audit/`. Counts + ids only — never the step's
 output body.
 
 ### 9. What this command does NOT do

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

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "override this skill for the project, customize this rule locally"
   trigger_context: "prompt names a shared skill/rule needing project-specific behavior"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /override create

package/.agent-src/commands/override/manage.md

@@ -10,6 +10,18 @@ suggestion:
   eligible: true
   trigger_description: "review my overrides, update the project overrides"
   trigger_context: "existing entries under agents/overrides/"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /override manage

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

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "create an override, manage existing overrides, refactor an override"
   trigger_context: "user wants to add or curate project-level overrides under agents/overrides/"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /override

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

@@ -7,6 +7,18 @@ disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Package-internal destructive reset."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # package-reset

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

@@ -1,12 +1,24 @@
 ---
 name: package-test
 tier: 2
-skills: [composer, npm]
+skills: [composer, npm, python-packages, go-modules, cargo-packages]
 description: /package-test
 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
 ---
 
 # package-test
@@ -17,15 +29,28 @@ Test a local package in the current project by linking it via Composer or npm.
 
 ### 1. Detect or ask for package manager
 
-Check the project root for `composer.json` and `package.json`.
+Check the project root for a package manifest. Supported (try in this order, take the first match — the project can have several):
 
-- **Both exist** → ask:
+| Manifest                                                          | Ecosystem        | Link mechanism                                           |
+|-------------------------------------------------------------------|------------------|----------------------------------------------------------|
+| `composer.json`                                                   | PHP / Composer   | `repositories[].type: path` + `composer require @dev`    |
+| `package.json`                                                    | JS / TS / Node   | `npm link` / `pnpm link` / `yarn link` / `file:../path`  |
+| `pyproject.toml`, `setup.py`, or `setup.cfg`                      | Python           | `pip install -e <path>` / `uv pip install -e <path>` / `poetry add --editable <path>` |
+| `go.mod`                                                          | Go               | `go mod edit -replace example.com/pkg=<path>`            |
+| `Cargo.toml`                                                      | Rust             | `cargo add --path <path>` or `[patch.crates-io]` block   |
+| `Gemfile`                                                         | Ruby             | `bundle config local.<gem> <path>`                       |
+
+- **Multiple manifests exist** → ask:
 
 ```
 Which package manager?
 
 1. Composer (PHP)
-2. npm (JavaScript/TypeScript)
+2. npm / pnpm / yarn (JavaScript / TypeScript)
+3. Python (pip / poetry / uv)
+4. Go modules
+5. Cargo (Rust)
+6. Bundler (Ruby)
 ```
 
 - **Only one exists** → use that one automatically, confirm:
@@ -37,7 +62,7 @@ Detected: {manager}. Proceeding.
 - **Neither exists** → abort:
 
 ```
-❌  No composer.json or package.json found in project root. Cannot link a local package.
+❌  No supported package manifest (composer.json / package.json / pyproject.toml / setup.py / go.mod / Cargo.toml / Gemfile) found in project root. Cannot link a local package.
 ```
 
 ### 2. Ask for the local package path
@@ -51,15 +76,19 @@ Example: ../my-package or /Users/me/projects/my-package
 
 Validate:
 - Path exists and is a directory
-- For Composer: directory contains `composer.json`
-- For npm: directory contains `package.json`
+- The directory contains a manifest matching the ecosystem chosen in the detection step (`composer.json`, `package.json`, `pyproject.toml` / `setup.py`, `go.mod`, `Cargo.toml`, or `Gemfile`)
+- If the directory has multiple manifests, ask the user which one to link (rare but possible — e.g. a Composer package that also ships a JS bundle)
 
 If invalid, show error and ask again.
 
 ### 3. Read the package name
 
-- **Composer:** Read `name` from the package's `composer.json`
-- **npm:** Read `name` from the package's `package.json`
+- **Composer:** Read `name` from the package's `composer.json` (e.g. `vendor/package`)
+- **npm / pnpm / yarn:** Read `name` from the package's `package.json` (e.g. `@scope/package`)
+- **Python:** Read `[project].name` from `pyproject.toml`, or `setup(name=...)` from `setup.py`
+- **Go:** Read `module` from `go.mod` (e.g. `example.com/vendor/package`)
+- **Rust:** Read `[package].name` from `Cargo.toml`
+- **Ruby:** Read the gem name from the `*.gemspec` file in the package directory
 
 Confirm:
 
@@ -118,10 +147,69 @@ Or for workspaces, add to `package.json`:
 
 Then: `npm install`
 
+#### Python
+
+Editable install (preferred):
+
+```bash
+pip install -e {package-path}
+# or, if the project uses uv:
+uv pip install -e {package-path}
+# or, if the project uses poetry:
+cd {project-root} && poetry add --editable {package-path}
+```
+
+Re-sync after upstream changes:
+
+```bash
+pip install -e {package-path} --force-reinstall --no-deps
+```
+
+#### Go
+
+Edit `go.mod` in the **project** root to add a `replace` directive:
+
+```
+replace example.com/vendor/package => ../my-package
+```
+
+Then run `go mod tidy` so the lockfile picks up the local path. Remove the `replace` line before publishing.
+
+#### Rust / Cargo
+
+Add as a path dependency in the **project's** `Cargo.toml`:
+
+```toml
+[dependencies]
+vendor_package = { path = "../my-package" }
+```
+
+Or, to override a published crate without rewriting the dependency line, use `[patch.crates-io]`:
+
+```toml
+[patch.crates-io]
+vendor_package = { path = "../my-package" }
+```
+
+Run `cargo build` to re-resolve.
+
+#### Ruby / Bundler
+
+```bash
+bundle config local.{gem-name} {package-path}
+bundle install
+```
+
+Remove with `bundle config --delete local.{gem-name}`.
+
 ### 5. Verify
 
 - **Composer:** Check that `vendor/{package-name}` is a symlink → the local path
-- **npm:** Check that `node_modules/{package-name}` is a symlink → the local path
+- **npm / pnpm / yarn:** Check that `node_modules/{package-name}` is a symlink → the local path
+- **Python:** `pip show {package-name}` → `Location` should point inside `{package-path}` (editable installs show the source dir, not site-packages)
+- **Go:** `go list -m {module-path}` → resolved path should match the `replace` target
+- **Rust:** `cargo metadata --format-version 1 | jq '.packages[] | select(.name=="{package-name}") | .manifest_path'` → should point inside `{package-path}`
+- **Ruby:** `bundle config get local.{gem-name}` → should return the linked path
 
 Report result:
 

package/.agent-src/commands/post-as/ghostwriter.md

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "post as ghostwriter, draft as a public figure, write in style of X, post-as alias for ghostwriter:write"
   trigger_context: "user invokes /post-as:ghostwriter as a discoverable alias for /ghostwriter:write — same flags, same output, same mandatory disclosure footer"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /post-as:ghostwriter

package/.agent-src/commands/post-as/me.md

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "write as me, draft in my own voice, post as myself, draft from .agent-user.md"
   trigger_context: "user wants a copyable draft in their own captured voice from .agent-user.md; no third-party voice, no disclosure footer"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /post-as:me
@@ -103,7 +115,7 @@ commit, no save. The user copies the output manually.
 - **Do NOT commit, push, or open a PR.** The user owns the git surface.
 - **Do NOT append a disclosure footer.** This command is the self-author
   path; appending the ghostwriter footer here is wrong by design.
-- **Do NOT consume `personas/*.md` or `agents/ghostwriter/*.md`** —
+- **Do NOT consume `personas/*.md` or `agents/reference/ghostwriter/*.md`** —
   those are separate primitives.
 - **Do NOT write the draft to disk.** This command prints only.
 - **Do NOT proceed when `.agent-user.md` is missing or

package/.agent-src/commands/post-as.md

@@ -9,6 +9,18 @@ suggestion:
   eligible: true
   trigger_description: "write as me, post as me, draft in my voice, draft as ghostwriter, post-as alias"
   trigger_context: "user wants a copyable draft in their own voice (.agent-user.md) or in a captured public-figure voice (/ghostwriter:write alias)"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # /post-as

package/.agent-src/commands/prepare-for-review.md

@@ -8,6 +8,18 @@ suggestion:
   eligible: true
   trigger_description: "get this branch ready for review, rebase and prep for PR"
   trigger_context: "branch behind base or part of a PR chain"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # prepare-for-review

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

@@ -6,8 +6,20 @@ description: Run quality pipeline (PHP and/or JS/TS) and fix all errors — auto
 disable-model-invocation: true
 suggestion:
   eligible: true
-  trigger_description: "fix the quality errors, run PHPStan and fix issues, fix code style"
-  trigger_context: "PHPStan/Rector/ECS output in recent tool results"
+  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
@@ -33,34 +45,56 @@ git diff --name-only origin/{default}..HEAD
 ### Prerequisites
 
 - All commands run **inside the PHP container** (e.g. `docker compose exec -T <service> ...`).
-- Detect the project type:
-  - Project ships a `quality:*` wrapper (Artisan or Composer script) → prefer `php artisan quality:phpstan` / `php artisan quality:rector --fix`
-  - `phpstan/phpstan` installed → `vendor/bin/phpstan analyse`
-  - `rector/rector` installed → `vendor/bin/rector process`
-  - `symplify/easy-coding-standard` installed → `vendor/bin/ecs check --fix`
-
-### Step 1: PHPStan — fix all errors
-
-1. Run PHPStan and capture the full output.
+- Detect the project's quality toolchain **before** doing anything else. Pick the first match:
+  1. Project ships a wrapper script — prefer the wrapper over invoking tools directly:
+     - PHP: `php artisan quality:*` (Laravel), `composer run quality`, `composer run lint`
+     - JS / TS: `npm run lint`, `npm run typecheck`, `pnpm lint`, `pnpm typecheck`, `yarn lint`, `yarn typecheck`
+     - Python: `make lint`, `nox -s lint`, `tox -e lint`
+     - Polyglot: `Taskfile.yml`, `Makefile`, or `justfile` with a `quality` / `lint` / `check` target
+  2. No wrapper — invoke tools directly based on which are installed:
+     - PHP: `vendor/bin/phpstan analyse`, `vendor/bin/rector process`, `vendor/bin/ecs check --fix`
+     - JS / TS: `npx tsc --noEmit`, `npx eslint . --fix`, `npx prettier . --write`, `npx biome check --apply`
+     - Python: `ruff check . --fix`, `ruff format .`, `mypy .`, `pyright`
+     - Go: `golangci-lint run --fix`, `go vet ./...`, `gofmt -w .`
+     - Rust: `cargo clippy --fix --allow-dirty`, `cargo fmt`
+  3. Nothing detected → ask the user which command runs the project's quality pipeline. Do not invent one.
+
+### Step 1: Type-checker — fix all errors
+
+Run the project's type-checker (chosen in the detection step):
+- PHP → PHPStan
+- JS / TS → `tsc --noEmit`
+- Python → mypy / pyright
+- Go → `go vet` + `go build`
+- Rust → `cargo check`
+
+1. Run the type-checker and capture the full output.
 2. For each error, **fix it in code**. Resolve the root cause.
-3. **Do NOT add errors to the baseline or phpstan.neon ignore lists.**
-4. If truly impossible (confirmed false positive), use inline ignore with reason.
-5. After fixing, run PHPStan again.
+3. **Do NOT add errors to the baseline or ignore list** (`phpstan-baseline.neon`, `tsconfig.json` `exclude`, `# type: ignore`, `// @ts-ignore`, `#[allow(...)]`, `//nolint`).
+4. If truly impossible (confirmed false positive), use the language-native inline ignore with a one-line reason: `@phpstan-ignore`, `// @ts-expect-error: <reason>`, `# type: ignore[<code>]  # <reason>`, `//nolint:<linter> // <reason>`, `#[allow(<lint>)] // <reason>`.
+5. After fixing, re-run the type-checker.
 6. Repeat until **0 errors**.
 
-### Step 2: Rector — apply automated refactoring
+### Step 2: Auto-fixer / refactoring tool — apply transforms
+
+Run the project's auto-fixer / refactoring tool (skip the step entirely if the project does not ship one):
+- PHP → `vendor/bin/rector process`
+- JS / TS → `npx eslint . --fix` (rule auto-fixes), `npx biome check --apply-unsafe` (safe transforms only)
+- Python → `ruff check . --fix` (lint auto-fixes), `ruff check . --fix --unsafe-fixes` (broader)
+- Go → `golangci-lint run --fix`, `gofmt -w .`, `goimports -w .`
+- Rust → `cargo clippy --fix --allow-dirty --allow-staged`, `cargo fmt`
 
-1. Run Rector with the fix flag.
-2. Review what Rector changed — it may introduce new PHPStan errors.
-3. Run Rector again to verify no further changes are applied.
-4. Repeat until Rector produces no more changes.
+1. Run the auto-fixer with the apply / fix flag.
+2. Review the diff — auto-fixes may introduce new type-checker errors or change semantics on edge cases.
+3. Re-run the auto-fixer to verify it produces no further changes.
+4. Repeat until the auto-fixer is idempotent.
 
-### Step 3: Final PHPStan verification
+### Step 3: Final type-checker verification
 
-1. Run PHPStan one more time.
-2. If new errors appeared (e.g. from Rector changes), fix them as in Step 1.
+1. Run the type-checker (from Step 1) one more time.
+2. If new errors appeared (e.g. from auto-fixer changes), fix them as in Step 1.
 3. If fixes were needed, go back to Step 2.
-4. Done when PHPStan reports **0 errors** and Rector has **no changes**.
+4. Done when the type-checker reports **0 errors** **and** the auto-fixer is idempotent. Also run the formatter once at the very end (`vendor/bin/ecs check --fix` / `prettier --write` / `ruff format` / `cargo fmt`) to normalise whitespace.
 
 ---
 
@@ -105,7 +139,7 @@ git diff --name-only origin/{default}..HEAD
 ## Rules
 
 - **Do NOT commit or push.** Only apply local changes.
-- **Do NOT modify baseline files** (`phpstan-baseline.neon`) or config files (`biome.json`, `tsconfig.json`).
-- **Do NOT add entries to `ignoreErrors`** in `phpstan.neon`.
-- Inline ignores (`@phpstan-ignore`, `@ts-expect-error`, `biome-ignore`) are a last resort.
-- Run `php -l` on modified PHP files if you made significant structural changes.
+- **Do NOT modify baseline files** (`phpstan-baseline.neon`, `tsconfig.json` `exclude`, `.mypy.ini` ignore list, `.eslintrc` `ignorePatterns`, `clippy.toml` `allow` list).
+- **Do NOT widen ignore lists** in the config (`ignoreErrors`, `exclude`, `# type: ignore` blanket, `eslint-disable` file-wide).
+- Inline ignores (`@phpstan-ignore`, `@ts-expect-error`, `# type: ignore[code]`, `biome-ignore`, `eslint-disable-next-line`, `//nolint:`, `#[allow(...)]`) are a last resort and must carry a one-line reason.
+- After significant structural changes, run a language-level syntax check (`php -l <file>`, `node --check <file>`, `python -m py_compile <file>`, `go build ./...`, `cargo check`) before claiming the file is fixed.

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