@event4u/agent-config 7.5.0 → 8.0.0

package/docs/comparison.yaml

@@ -0,0 +1,35 @@
+# B7 — comparison-honesty rows for the proof page.
+#
+# The point is the `checkable` column, not a takedown. For each dimension we
+# cite OUR evidence as a resolvable pointer (file / file#substring / ledger id),
+# and state what is PUBLICLY OBSERVABLE about the wider category — never a named
+# competitor (source-confidentiality), never a counter-claim to their headline
+# number. A category headline figure (e.g. an "84.8%" score) is cited ONLY as
+# uncheckable: no reproducible methodology is published, so it cannot be verified
+# either way — that is the whole point.
+#
+# check_comparison.ts enforces: every `our_evidence` resolves (reuses the
+# check_claims pointer resolver); every `checkable: true` row's `our_evidence`
+# resolves. build_proof renders these rows. check_no_external_sources guarantees
+# no named source leaks in.
+
+rows:
+  - claim: "No runtime — no background daemon, no state database, no auto-write memory."
+    our_evidence: "docs/contracts/no-runtime-boundary.md#file-first"
+    their_evidence: "Swarm-runtime tools in this category ship a background process and/or a state store by design; that is an architectural fact of the runtime approach, not a defect."
+    checkable: true
+
+  - claim: "Capability/benchmark results are published — including the runs where the package changed nothing."
+    our_evidence: "docs/benchmark.md"
+    their_evidence: "A category headline figure (e.g. an '84.8%' score) appears across marketing surfaces with no reproducible methodology published — so it cannot be verified either way."
+    checkable: true
+
+  - claim: "Every public claim binds to machine-checked evidence."
+    our_evidence: "docs/CLAIMS.md"
+    their_evidence: "Marketing claims in this category are not bound to a machine-checked ledger a reader can reproduce."
+    checkable: true
+
+  - claim: "Skills publish their own known limits, each with a witness test."
+    our_evidence: "tests/scripts/witness/check_refs_relative_gap.test.ts"
+    their_evidence: "Published known-limitation surfaces backed by reproducing tests are not a standard artifact in this category."
+    checkable: true

package/docs/contracts/agents-layout.md

@@ -0,0 +1,148 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
+# `agents/` Directory Layout Contract
+
+> **Do not bypass this contract.** Every entry at the `agents/` root — file or
+> directory — must appear in this table. Unknown entries are CI violations
+> (`lint_agents_layout.ts` enforces this in source-repo mode, warns in consumer
+> mode). Adding a new top-level entry requires a PR that also updates this table
+> and the classification manifest (`src/config/agents-paths.yml`).
+
+## Design invariants
+
+1. **The `agents/` root stays flat-minimal.** Content lives in typed
+   subdirectories. New flat files require a contract edit and explicit rationale
+   (six whitelisted flat files exist; no new ones without a deliberate decision).
+2. **`agents/tmp/` is the user's inbox; `agents/tmp.old/` is the processed
+   archive.** The agent reads inbox files and moves them to `tmp.old/` after
+   consumption. The agent's own scratch goes to `agents/runtime/tmp/` or the
+   session scratchpad. See § User Inbox Workflow below.
+3. **Both `tmp/` and `tmp.old/` are gitignored in every scope.** Consumer
+   projects would commit their inbox without the managed block entry.
+
+---
+
+## Whitelisted flat files
+
+| File | Git policy | Owner | Rationale |
+|---|---|---|---|
+| `index.md` | tracked-durable | agents (auto-regenerated) | Human-readable full index; regenerated by `./agent-config roadmap:progress` |
+| `roadmaps-progress.md` | tracked-durable | agents (auto-regenerated) | Roadmap dashboard; regenerated by `./agent-config roadmap:progress` |
+| `.agent-tools.yml` | tracked-durable | maintainer | Declares which tool projections `task generate-tools` builds |
+| `.maintainer-workspace.md` | tracked-durable | maintainer | Maintainer-facing workspace notes; source-repo only |
+| `.gitkeep` | tracked-durable | — | Keeps `agents/` in the tree even when all other files are ignored |
+| `installed-tools.lock` | **local-only** (gitignored) | installer (`scripts/install.py`) | Per-user install inventory; leaks `$HOME`; consumer-only artefact, must never be committed in the source repo |
+
+---
+
+## Directory table
+
+Scope column: `pkg` = source repo only · `consumer` = consumer projects only · `both` = all.
+
+| Directory | Scope | Git policy | Retention | Owner | Purpose |
+|---|---|---|---|---|---|
+| `decisions/` | pkg | tracked-durable | permanent | council + humans | Low-impact council corpus, open questions, per-decision ADRs |
+| `evidence/` | pkg | tracked-durable (see notes) | permanent | tooling + humans | Research, analysis, audits, eval findings, metrics — everything evidential. Sub-dirs: `analysis/`, `audits/`, `architectural-drift/`, `archived-skills/`, `council/`, `eval-findings/`, `eval-corpora/`, `investigations/`, `mcp-sessions/`, `metrics/`, `notes/`, `reports/` |
+| `features/` | pkg | tracked-durable | permanent | maintainer | Feature-flag status docs (long-form complement to `.agent-tools.yml`) |
+| `knowledge/` | both | tracked-durable | permanent | human-gated (`/team-knowledge` skills) | Curated committed knowledge pages (sessions/, concepts/, procedures/, decisions/). Committed only after human review; never auto-written |
+| `memory/` | both | mixed (see notes) | permanent (durable) / TTL (intake) | `/memory:*` skills | Layer 1 memory pipeline: `intake/` (gitignored JSONL), `knowledge/` subdir (mirrors top-level knowledge/). Intake is local-only; curated YAML in subdirs is committed |
+| `notes/` | pkg | tracked-durable | permanent | maintainer | Ad-hoc analyst notes that are not evidence/reports (e.g. `visibility-sync-audit.md`). **Merge candidate** — new notes land in `evidence/notes/` going forward; existing file stays for now |
+| `overrides/` | both | tracked-durable | permanent | humans (`/override:*`) | Per-project skill/rule/command/guideline overrides; the only consumer-committed customisation layer |
+| `recruit-sessions/` | pkg | tracked-durable | permanent | maintainer | User-recruit study session data and runbooks |
+| `reference/` | pkg | tracked-durable | permanent | maintainer | External reference material: `ai-video/`, `docs/`, `ghostwriter/` |
+| `roadmap-assets/` | pkg | tracked-durable | permanent | maintainer | Supplemental assets for specific roadmaps (e.g. design-asset `.assets.md` files). **Merge candidate** — new assets can land in `evidence/` or alongside the roadmap file |
+| `roadmaps/` | pkg | tracked-durable | permanent | agents + maintainer | Active roadmaps; sub-dirs: `archive/`, `later/`, `skipped/`, `stubs/` |
+| `roles/` | pkg | tracked-durable | permanent | maintainer | Role-definition docs for consumer user-types (consultant, galabau, support, …) |
+| `runtime/` | both | **local-only** (gitignored, entire tree) | session / TTL | multiple scripts | Volatile runtime artefacts: council sessions/responses, price cache, chat-history, budget history, hook state, logs, mcp-telemetry, dispatcher lock, tmp scratch. Nothing inside is ever committed |
+| `settings/` | pkg | tracked-durable | permanent | maintainer | Long-lived package-level configuration and context documents: `contexts/`, `policies/` |
+| `state/` | both | **local-only** (gitignored) | session / TTL | hooks | Tier-1 hook runtime state (context-hygiene, verify-before-complete, etc.), the hot-context working-memory cache (`hot-context.md` — bounded 400 words, fixed sections `Last Updated / Branch / Key Facts / Active Threads / Open Verifications / Recent Changes`, overwritten on every `stop`, restored on `session_start`), and GUI wizard resume snapshot. Never committed |
+| `templates/` | pkg | tracked-durable | permanent | maintainer | Reusable template files for agents (currently empty; reserved for future use) |
+| `tickets/` | pkg | tracked-durable | permanent | maintainer + `emit-tickets` | Ticket bundles (`_registry.yml`, per-bundle dirs); governed by `road-to-ticket-bundles.md` |
+| `tmp/` | both | **local-only** (gitignored, BOTH scopes) | user-owned | **user only** | User inbox: free-form notes/todos for the agent to consume. Never auto-swept. See § User Inbox Workflow |
+| `tmp.old/` | both | **local-only** (gitignored, BOTH scopes) | TTL (30 days) | agent (moves only) | Processed inbox archive: the agent moves consumed `tmp/` files here after processing. Auto-swept by janitor at 30-day TTL; user can also delete manually |
+| `.harvest-local/` | pkg | **local-only** (gitignored) | retained evidence | maintainer | Source-confidentiality: named external-reference harvest evidence. 74 MB; never committed (see `source-confidentiality` rule) |
+
+---
+
+## User Inbox Workflow
+
+```
+agents/tmp/        ← USER drops notes, todos, draft ideas here
+     ↓ agent reads + processes (roadmap create, memory promote, etc.)
+agents/tmp.old/    ← AGENT moves the consumed file here, same reply
+     ↓ janitor sweeps after 30 days
+     (deleted)
+```
+
+**Rules:**
+
+- `agents/tmp/` is the **user's space** — the agent only reads and moves from
+  it; the agent never writes files into it.
+- After consuming a file from `agents/tmp/` (as a command input), the agent
+  moves it to `agents/tmp.old/<original-name>` in the **same reply** as the
+  processing. No confirmation needed (gitignored, reversible, local-only).
+- The agent's own scratch (intermediate calculations, session notes) goes to
+  the **session scratchpad** or `agents/runtime/tmp/` — never into `agents/tmp/`.
+- `agents/tmp/` is **never** auto-swept by the janitor — it belongs to the user.
+  The janitor only touches `agents/tmp.old/` (TTL = 30 days).
+- Both directories are gitignored in **package and consumer scope** (entry in
+  `src/config/agents-paths.yml` with `scope: both`).
+
+---
+
+## Consumer-only scope (slim profile)
+
+After `agent-config migrate`, a consumer project's `agents/` contains only:
+
+| Entry | Rationale |
+|---|---|
+| `overrides/` | Per-project skill/rule customisation |
+| `.event4u-bridge.yml` | ADR-020 bridge marker (global-only install) |
+| `.gitkeep` | Keeps `agents/` in the tree |
+| `knowledge/` | Optional: curated project-specific knowledge pages |
+| `memory/` | Optional: promotion pipeline (intake gitignored, curated YAML committed) |
+| `roadmaps/` | Optional: project-local roadmaps |
+| `tmp/` | Optional: user inbox (gitignored) |
+| `tmp.old/` | Optional: processed inbox archive (gitignored) |
+
+Entries that are **not** expected in consumers (and that `agent-config doctor`
+will warn about): `evidence/`, `decisions/`, `features/`, `reports/`,
+`recruit-sessions/`, `settings/`, `roles/`, `reference/`, `roadmap-assets/`,
+`notes/`, `tickets/`, `templates/`, `runtime/`, `state/`.
+
+---
+
+## Overlap decisions (2026-07-06)
+
+| Pair | Decision |
+|---|---|
+| `evidence/` vs `reports/` vs `notes/` | **Keep `evidence/` as the umbrella.** `evidence/reports/` and `evidence/notes/` already exist as subdirs. New reports/notes land there. The top-level `reports/` and `notes/` are **legacy** — no new files; existing files can be migrated per future clean-up PR (non-blocking). |
+| `memory/` vs `knowledge/` | **Keep both** with a crisp boundary: `knowledge/` = committed curated pages (human-reviewed); `memory/` = promotion pipeline (intake is gitignored JSONL; only curated YAML subsets get committed). |
+| `templates/` vs `roadmap-assets/` | **Both empty/minimal — keep as reserved.** `templates/` = reusable agent-facing templates; `roadmap-assets/` = supplemental for specific roadmaps. New assets prefer `evidence/` sub-dirs unless they are true roadmap supplements. No migration needed today. |
+| `recruit-sessions/`, `features/`, `tickets/` | **Keep all three** — distinct purposes, each has an active owner and lifecycle (recruit-sessions = user research; features = flag docs; tickets = bundle system). |
+
+---
+
+## What needs a contract edit
+
+Any PR that:
+- Adds a new top-level directory to `agents/`
+- Adds a new whitelisted flat file to `agents/`
+- Changes the git policy of an existing entry
+- Changes the consumer-scope subset
+
+...must update this table in the same commit, update `src/config/agents-paths.yml`,
+and add the new entry to `ALLOWED_SOURCE_DIRS` (or `ALLOWED_FLAT_FILES`) in
+`src/scripts/lint_agents_layout.ts`.
+
+## See also
+
+- `src/config/agents-paths.yml` — machine-readable classification manifest (Phase 3)
+- `src/scripts/lint_agents_layout.ts` — CI enforcement
+- `docs/contracts/migrate-command.md` — consumer migration flow
+- ADR-020 — global-only install; bridge marker
+- ADR-050 — workspace vs package root boundary
+- `source-confidentiality` rule — `.harvest-local/` rationale

package/docs/contracts/brand-token-consumption.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # Brand-Token Consumption Contract (greenfield interface stub)
 
 > **Status:** interface stub. This contract is the **only** greenfield surface

package/docs/contracts/capability-boundary.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # Capability Boundary Matrix
 
 The per-pack safety posture at a glance: is a pack on by default, does it need

package/docs/contracts/command-category-governance.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # Command-category governance
 
 > **Status (2026-06-09):** Phase-2b resolved as **Option 1 (light)** — an

package/docs/contracts/command-clusters.md

@@ -56,6 +56,7 @@ column 1 of this table.
 | `image` | — | `analyse` · `create` · `verify` | new cluster 2026-05-31 (`road-to-character-image-fidelity` Phase 4) — character-image fidelity surface mirroring `/video:*`. `:analyse` extracts a per-feature spec from an image and diffs it against a Canon Spec down to the smallest mole (OCR for lettered tattoos, per-section severity scores, canon-breaking hard gate); `:create` assembles a max-fidelity anchors-first generation prompt from the Canon Spec, governance- + provider-gated, `AIV_DRYRUN=true` default; `:verify` runs the analyser in loop mode against a candidate and reports the gate verdict + remaining diff with plateau/oscillation/budget stop conditions. Skills: [`image-analyser`](../../skills/image-analyser/SKILL.md) + [`image-creator`](../../skills/image-creator/SKILL.md); schema/rubric/loop in [`canon-spec.md`](../../skills/image-analyser/canon-spec.md). |
 | `brand` | — | `strategy` · `identity` · `tokens` · `review` · `voice` | new cluster 2026-06-17 (`road-to-image-brand-followups` Phase 3) — brand-as-first-class-UX surface for `pack-brand`, consulted before `design-intelligence` so brand bounds style. `:strategy` (positioning/archetype/voice/messaging over the brand corpus), `:identity` (logo/colour/type/imagery direction — defines the tokens downstream generation consumes), `:tokens` (derive a DTCG `.tokens.json` source of truth → CSS/Tailwind, no Node), `:review` (audit emitted UI/copy/assets against active brand tokens + voice per the `brand-consistency` gate), `:voice` (voice-and-tone profile). Skills: [`brand-strategy`](../../skills/brand-strategy/SKILL.md) · [`brand-identity`](../../skills/brand-identity/SKILL.md) · [`brand-to-tokens`](../../skills/brand-to-tokens/SKILL.md) · [`brand-audit`](../../skills/brand-audit/SKILL.md) · [`voice-and-tone-design`](../../skills/voice-and-tone-design/SKILL.md). The companion `/imagegen:*` generation cluster (pack-ai-image) is deferred until its adapters' live submit/poll/fetch is wired. |
 
+| `team-knowledge` | — | `consolidate` · `bootstrap` | new cluster 2026-07-05 (`road-to-knowledge-system` Phases 5-6) — the repo-tracked team-knowledge layer under `agents/knowledge/{sessions,concepts,procedures,decisions}/`. Distinct from the pre-existing [`knowledge`](#locked-clusters) cluster (arbitrary local-file ingestion into `agents/memory/knowledge/`) — different namespace, different concern. `:consolidate` reads pending typed-observation events (`consolidate_knowledge_events.ts`), finds the nearest existing page per topic (mechanical similarity), and presents a NEW/EXTEND/CONFIRM/CONFLICT batch for human approval — never writes a page automatically. `:bootstrap` (`bootstrap_knowledge.ts`) stages a one-shot deterministic seed (detected package manifest, top-level directories, known config filenames — never file content, never an LLM-invented claim) to a gitignored staging dir for review-then-commit. |
 | `profile` | — | `activate` · `deactivate` · `show` | new cluster 2026-06-02 (`road-to-session-profile-activation`) — session-profile activation: an ephemeral `runtime.active_packs` overlay that biases the surfaced command/skill set to the active pack closure, with no persistence and no execution-gating (recommendation-bias MVP). `:activate <name…>` resolves an alias (`src/config/discovery/session-profiles.yml`) or a raw pack id, fails fast on a not-installed pack, expands the `requires_hint` closure, and writes the overlay atomically to `agents/settings/.agent-settings.local.yml`; `:deactivate [name…]` clears it (or drops named packs, keeping deps a still-active pack needs); `:show` is the observability surface (active packs + surfaced/hidden counts). Overlay = runtime modulation of the existing `pack` axis, not a fifth axis (ADR-010 addendum). Library: `scripts/config/session_profiles.py`; schema in [`session-profile-overlay`](session-profile-overlay.md). |
 
 **Net change:** Phase 1 collapsed 15 atomics → 3 clusters; Phase 2

package/docs/contracts/command-surface-tiers.md

@@ -41,7 +41,7 @@ The path a new contributor walks on day one. Visible in
 2. **Stable surface.** The command name + flag set has not changed
    in the last two minor releases (or is brand-new with a
    commitment to two-release stability).
-3. **No prerequisite tooling beyond `bash` + `python3`.** Docker,
+3. **No prerequisite tooling beyond `bash` + `node`.** Docker,
    GPG, jq, gh CLI, npm globals are all Tier-1+ territory.
 4. **Cited in the `init → sync → validate → work` outcome path.**
    Setup helpers (`first-run`, `keys:install-*`) and AI-Council entry

package/docs/contracts/conformance.md

@@ -0,0 +1,84 @@
+---
+stability: beta
+keep-beta-until: 2026-10-01
+---
+
+# Conformance contract — green means installed AND firing
+
+> **Status:** active · **Owner:** maintainer · **Siblings:**
+> [`install-layout.md`](install-layout.md) · [`smoke-contracts.md`](smoke-contracts.md)
+
+`task conformance` (equivalently `agent-config conformance`) is the
+consumer-runnable, CI-shaped answer to one question:
+
+> **Is agent-config installed *and firing* in this repo?**
+
+It is deterministic — no LLM, no network — and safe to wire into a
+consumer repo's CI. A green run is the "conformance badge" a repo earns;
+a red run names the exact broken surface and its remedy.
+
+## § 1 — What runs
+
+Two legs, one exit code:
+
+1. **Doctor under the `--ci` contract.** `agent-config doctor --ci` runs
+   the full drift scan plus every registered health check, emits a JSON
+   payload, and — unlike the default doctor run, which keys its exit off
+   drift only — folds **any check failure** into the exit code.
+2. **Five conformance checks** (registered in
+   `src/scripts/_cli/cmd_conformance.ts`):
+
+| id | proves | red when |
+|---|---|---|
+| `txlog-clean` | the last install completed | the install-log tail is an abandoned `abort` |
+| `router-pointers` | the installed rule index is intact | any rule id or `routes_to` target does not resolve on disk |
+| `hook-dispatcher` | hooks actually fire on this host | the dispatcher errors on a synthetic `session_start` / `stop` envelope |
+| `lean-projection` | `lean_projection.mode` matches reality | projected non-kernel rules contradict the configured mode |
+| `host-manifest` | `subagents.host_capabilities` is well-formed | unknown keys / non-boolean values (typo guard) |
+
+Every check returns `ok` / `warn` / `fail` / `skipped` with a one-line
+remedy. `skipped` means "not applicable here", never "silently passed".
+
+## § 2 — Exit-code contract
+
+| Exit | Meaning |
+|---|---|
+| `0` | Green — no check failed, no drift. Warnings allowed. |
+| `1` | Red — at least one check failed, or manifest drift present. |
+| `2` | Environment unresolvable (no project root, corrupt setup). |
+
+The same contract applies to `agent-config doctor --ci` standalone.
+
+## § 3 — Report line (fleet aggregation)
+
+Every run appends exactly one JSONL line — mirroring the install-txlog
+entry shape — to `~/.event4u/agent-config/conformance-log.jsonl`
+(override: `AGENT_CONFIG_CONFORMANCE_LOG`):
+
+```json
+{"ts":"2026-07-07T10:00:00.000Z","kind":"conformance","path":"/repo","sha256":null,"note":"5/5 ok; fails: none"}
+```
+
+Fleet installs (`--fleet`) aggregate these lines into their per-repo
+summary; the line is append-only and never breaks the exit contract.
+
+## § 4 — Pre-install twin: `init --validate-only`
+
+`agent-config init --validate-only` is the **pre-install** gate — the
+typed pre-flight suite (`src/install/preflight.ts`): target-root
+permissions, free-disk floor, conflict detection, host-detection
+sanity. Nothing is written. Exit `0` = clear, `1` = blocking finding,
+`2` = no runner. `--dry-run` (full plan print) and `--minimal`
+(settings-only bootstrap) are the existing siblings; `--validate-only`
+completes the trio.
+
+## § 5 — CI wiring (consumer)
+
+```yaml
+- name: agent-config conformance
+  run: npx @event4u/agent-config conformance
+```
+
+Green conformance in a consumer pipeline is the supported way to assert
+"the OS is installed and firing here" — instead of hand-rolled greps
+over projected files.

package/docs/contracts/creative-pack-boundary.md

@@ -1,3 +1,8 @@
+---
+stability: beta
+keep-beta-until: 2026-08-17
+---
+
 # Creative Pack boundary — video is an optional pack, not core identity
 
 The `ai-video` (Creative) pack is a **bounded, optional** capability: a first-class

package/docs/contracts/discovery-manifest.schema.json

@@ -151,7 +151,7 @@
       "additionalProperties": false,
       "properties": {
         "path": { "type": "string", "minLength": 1, "description": "POSIX path relative to repo root." },
-        "category": { "type": "string", "enum": ["skill", "rule", "command", "template"] },
+        "category": { "type": "string", "enum": ["skill", "rule", "command", "template", "subagent"] },
         "name": { "type": "string" },
         "pack": { "$ref": "#/$defs/pack_id", "description": "capability-packs.md — canonical OWNER pack (ownership/budget unit). Orthogonal to `packs` (discovery tags); the owner need not appear in `packs`." },
         "tier": { "type": "integer", "enum": [0, 1, 2], "description": "6.0.0-C — command-surface tier surfaced on `category: command` artefacts so the CLI discovery surface reads the manifest, not a parallel catalog. DEPRECATED back-compat alias of `visibility` since ADR-090; still dual-emitted (non-breaking) but announced for removal in the top-level `deprecations` block (road-to-tier-removal Phase 1 / ADR-092). Read `visibility`." },
@@ -160,8 +160,8 @@
         "routes_to": { "type": "array", "items": { "type": "string" }, "description": "6.0.0-C — command routing metadata (skill/cluster-sub/command slugs the intent routes to)." },
         "replaces": { "type": "array", "items": { "type": "string" }, "description": "6.0.0-C — command routing metadata (prior names/aliases this command absorbs; may be empty)." },
         "slug": { "type": "string", "description": "6.0.0-D — canonical path-derived invocation slug (ADR-044; pack-stripped subpath + opt-in slug_prefix). Distinct from `name` (display, may still be colon for renames deferred to 6.1). The identity `commands ls --profile` matches on." },
-        "workspaces": { "type": "array", "items": { "$ref": "#/$defs/workspace_id" }, "minItems": 1 },
-        "packs": { "type": "array", "items": { "$ref": "#/$defs/pack_id" }, "minItems": 1 },
+        "workspaces": { "type": "array", "items": { "$ref": "#/$defs/workspace_id" }, "description": "Non-empty for skill/rule/command/template (enforced by build_discovery_manifest._classify). ADR-109 subagents legitimately carry [] — default-off, opt-in-by-name, never pack/workspace-scoped." },
+        "packs": { "type": "array", "items": { "$ref": "#/$defs/pack_id" }, "description": "Non-empty for skill/rule/command/template (enforced by build_discovery_manifest._classify). ADR-109 subagents legitimately carry [] — recommended for no pack; included only via include: [\"subagent:<name>\"]." },
         "requires": {
           "type": "array",
           "items": { "$ref": "#/$defs/pack_id" },
@@ -218,7 +218,8 @@
             "skill":    { "type": "integer", "minimum": 0 },
             "rule":     { "type": "integer", "minimum": 0 },
             "command":  { "type": "integer", "minimum": 0 },
-            "template": { "type": "integer", "minimum": 0 }
+            "template": { "type": "integer", "minimum": 0 },
+            "subagent": { "type": "integer", "minimum": 0 }
           },
           "required": ["skill", "rule", "command", "template"]
         },