@event4u/agent-config 2.26.0 → 3.0.0

package/docs/distribution/mcp-submission-checklist.md

@@ -0,0 +1,95 @@
+# MCP registry submission checklist
+
+> One-shot procedure for opening a submission PR to an external MCP
+> registry. The manifest under `dist/mcp/` is the source of truth;
+> this file is what the maintainer runs through at submission time.
+
+## Before submitting
+
+1. Confirm the npm package is published with **2FA-required** for new
+   releases. A downstream user clicking the registry link must not
+   land on a hijacked release.
+2. Re-run the builder so payloads reflect the current package:
+   ```bash
+   python3 scripts/build_discovery_manifest.py --write --strict
+   python3 scripts/build_mcp_registry_manifest.py --write --strict
+   python3 scripts/lint_mcp_registry_manifest.py
+   ```
+3. Confirm `dist/mcp/registry-manifest.json` `package.version`
+   matches the latest published npm version (or the version about to
+   be released in the same change set).
+
+## Per-registry steps
+
+### `awesome-mcp-servers`
+
+- Upstream: <https://github.com/punkpeye/awesome-mcp-servers>
+- Target file: `README.md`, section **"Server Frameworks / Agents"**.
+  *Verify the section heading before each submission — upstream
+  reorganises occasionally.*
+- Payload to paste: the row in `dist/mcp/awesome-mcp-servers.row.md`.
+  ```bash
+  cat dist/mcp/awesome-mcp-servers.row.md
+  ```
+- Open the upstream PR. Title: `Add @event4u/agent-config`.
+- After opening, update `dist/mcp/registry-manifest.json`:
+  ```jsonc
+  {
+    "id": "awesome-mcp-servers",
+    "status": "pending",     // → "listed" once merged, "rejected" if closed
+    "submitted_at": "YYYY-MM-DD",
+    "pr_url": "https://github.com/punkpeye/awesome-mcp-servers/pull/NNN",
+    "last_verified": null
+  }
+  ```
+  Then commit the manifest change as a follow-up.
+
+### `mcp-cloudflare-catalogue`
+
+- Upstream: <https://github.com/cloudflare/mcp-server-cloudflare>
+- Target file: the catalogue JSON file the repository documents
+  (verify path against the upstream README before each submission).
+- Payload to paste: the JSON object in
+  `dist/mcp/mcp-cloudflare-catalogue.json`.
+  ```bash
+  cat dist/mcp/mcp-cloudflare-catalogue.json
+  ```
+- Same lifecycle update as above once the PR is open.
+
+## After the upstream PR closes
+
+The submission PR can end in three states. Each maps to a `status`
+value in the manifest. Do **not** silently drop entries.
+
+- **merged** → `status: "listed"`, set `last_verified` to today, open
+  the live listing once and confirm the link still resolves to this
+  package. Refresh `last_verified` every release.
+- **closed without merge** → `status: "rejected"`. Leave
+  `submitted_at` and `pr_url` populated so the rejection is
+  auditable. Do **not** auto-resubmit; the next attempt is a
+  judgment call by the maintainer.
+- **listing removed later** → `status: "unlisted"`. Refresh
+  `last_verified` to the date of removal so the audit trail is
+  intact.
+
+`scripts/lint_mcp_registry_manifest.py` exits non-zero if any
+registry entry uses a value outside the four-state enum.
+
+## Submitting to a new registry
+
+The schema's `id` vocabulary is closed (`awesome-mcp-servers`,
+`mcp-cloudflare-catalogue`). Adding a third registry is a
+**schema-version bump**:
+
+1. Update `docs/contracts/mcp-registry-manifest.schema.json`:
+   add the new `id` value, bump the top-level `version` const if
+   the field shape changes.
+2. Update `scripts/build_mcp_registry_manifest.py`'s
+   `REGISTRIES_SEED` with the new entry (id, label,
+   listing_format, submission_url, rendered_payload).
+3. Add a new renderer for the rendered payload (Markdown row,
+   JSON entry, or whatever the new registry expects).
+4. Add a new payload-shape check to
+   `scripts/lint_mcp_registry_manifest.py`.
+5. Land it as its own PR so the schema change is reviewed
+   independently of the submission itself.

package/docs/distribution/topics-equivalents-decay-policy.md

@@ -0,0 +1,51 @@
+# Topics-equivalents decay policy
+
+The `equivalents:` map in [`.github/topics.yml`](../../.github/topics.yml)
+is a manually-curated paraphrase dictionary. Without a review cadence
+it rots: the README's prose evolves, the equivalents stay frozen, the
+positioning lint quietly accepts dead phrases, and a topic that *used*
+to be discoverable in the README becomes a ghost mapping.
+
+This policy locks down the review cadence so the map stays load-bearing.
+
+## Review cadence
+
+- **Every release cycle that touches the README tagline, H1, or any
+  section heading enumerated in `.github/topics.yml`** — the PR
+  author must re-run `task lint-positioning` *after* the README edit
+  and visually re-confirm that every entry under `equivalents:` still
+  matches a phrase in the current README. The lint only checks that
+  *at least one* needle hits — it cannot detect a stale entry.
+- **Six-monthly** — a dedicated `chore(visibility): refresh topics
+  equivalents` PR walks every key in `equivalents:` and either:
+  removes it (the equivalent now appears literally in the README),
+  rewrites it (the README phrase changed), or removes the parent
+  topic (no longer positioned).
+
+## Removal heuristics
+
+Drop an `equivalents:` entry when **any** of these holds:
+
+- The topic key appears verbatim (case-insensitive) in the current
+  README — the equivalents row is redundant.
+- The README phrase the equivalent was mapped to no longer exists —
+  the row is a stale alias and the lint is silently passing on a
+  ghost.
+- The topic itself is no longer in `topics:` — orphan entry.
+
+## Why not a runtime lint?
+
+The original AI-Council suggestion was to "replace the map with a
+runtime lint that warns when a tagline word appears in a topic
+equivalent but the parent README phrase has changed." That requires
+storing a hash of the matched README phrase per equivalent and
+re-validating on every lint run — extra moving parts for a low-yield
+gate. The cheaper contract is the six-monthly human review documented
+above. If the map grows past ~15 keys or rots faster than two release
+cycles, revisit and promote to a runtime check.
+
+## Tracking
+
+Maintainers log each refresh in
+[`agents/evidence/notes/visibility-sync-audit.md`](../../agents/evidence/notes/visibility-sync-audit.md)
+with a one-line entry: date, PR, keys touched.

package/docs/examples/agent-user.example.md

@@ -4,7 +4,9 @@ identity:
   name: "Mathias"
   nickname: "Matze"
 language: "de"
-role: "founder/engineer"
+role:
+  - founder
+  - engineer
 style:
   formality: "informal"
   pace: "pragmatic"

package/docs/getting-started.md

@@ -146,15 +146,16 @@ Your agent now understands slash commands:
 | `/quality-fix` | Run and fix all quality checks |
 | `/chat-history` | Inspect the persistent chat-history log (read-only `show`) |
 
-→ [Browse all 129 active commands](../.agent-src/commands/)
+→ [Browse all 128 active commands](../.agent-src/commands/)
 
 ---
 
-## Crash recovery — `agents/.agent-chat-history`
+## Crash recovery — `agents/runtime/.agent-chat-history`
 
 When `chat_history.enabled: true` in `.agent-settings.yml` (on by default
 for every profile), the agent keeps a JSONL log of your conversation in
-`agents/.agent-chat-history`. The file is git-ignored and rotates at the
+`agents/runtime/.agent-chat-history`. The file is git-ignored (covered
+by the `/agents/runtime/` catch-all) and rotates at the
 size configured in the profile (`128 KB` on `minimal`, `256 KB` on
 `balanced`, `512 KB` on `full`).
 
@@ -169,7 +170,7 @@ the log size, last entries, and current fingerprint. For the rare case
 where auto-adopt misfires (corrupted file, hook misconfiguration), run
 `./agent-config chat-history:adopt` as the manual recovery lever.
 
-See [`agents/contexts/chat-history-platform-hooks.md`](../agents/contexts/chat-history-platform-hooks.md)
+See [`agents/settings/contexts/chat-history-platform-hooks.md`](../agents/settings/contexts/chat-history-platform-hooks.md)
 and [`scripts/chat_history.py`](../scripts/chat_history.py) for the mechanics.
 
 ---

package/docs/guidelines/agent-infra/ask-when-uncertain-demos.md

@@ -106,7 +106,7 @@ Agent: Bevor ich die Roadmap übergebe:
 - Welcher Branch?
 - Soll ich PRs erwähnen?
 - Welches Modell für die Fortsetzung?
-- Soll ich agents/.agent-chat-history zitieren?
+- Soll ich agents/runtime/.agent-chat-history zitieren?
 
 Antworte als 1, 2, 3, 4.
 ```

package/docs/guidelines/agent-infra/roadmap-progress-mechanics.md

@@ -112,7 +112,7 @@ When the agent autonomously creates a roadmap, it owns the placement
 in the **same response**:
 
 - **Phase plan** (checkboxes, multi-turn execution) → `agents/roadmaps/<name>.md`, `status: ready` (default), regen dashboard.
-- **Decision matrix / ADR / pattern / lookup** (no `Phase N`, durable rationale) → `agents/contexts/<name>.md`.
+- **Decision matrix / ADR / pattern / lookup** (no `Phase N`, durable rationale) → `agents/settings/contexts/<name>.md`.
 - **Completed work snapshot** → `agents/roadmaps/archive/<name>.md`.
 
 A non-trackable file in `agents/roadmaps/` is a rule violation — the
@@ -146,6 +146,15 @@ dashboard, commit if commit policy allows.
 **Required:** each turn — implement step, flip `[x]`, regen, commit (if policy allows).
 A reply that lands a verified step without flipping its checkbox is a rule violation.
 
+**Deterministic flip-guard.** The autonomous loop carries a per-step
+guard at [`roadmap-process-loop § 5b`](../../.agent-src.uncompressed/contexts/execution/roadmap-process-loop.md#5b-flip-guard--deterministic):
+after the atomic flip, the loop runs
+`git diff --name-only -- agents/roadmaps/<file>.md` and halts loudly
+when the diff is empty. The `command:` triggers on
+`roadmap-progress-sync` keep the rule loaded for the entire
+`/roadmap:process-*` run; the guard is the deterministic backstop
+that catches a forgotten flip per step rather than at run end.
+
 **In-progress marker:** when a step takes more than one reply,
 mark it `[~]` the moment work starts on it and regenerate. The
 user sees one row move from `[ ]` to `[~]` to `[x]` instead of

package/docs/guidelines/agent-infra/rule-type-governance.md

@@ -48,7 +48,7 @@ The `description` field IS the trigger. It must describe **when** the rule appli
 
 Every new rule, and every edited rule whose body changes the trigger
 or the obligation, MUST classify itself against the hardening tiers
-documented in [`rule-trigger-matrix.md`](../../agents/contexts/rule-trigger-matrix.md):
+documented in [`rule-trigger-matrix.md`](../../agents/settings/contexts/rule-trigger-matrix.md):
 
 | Tier | Meaning |
 |---|---|
@@ -64,7 +64,7 @@ Classification surface: the optional `tier:` frontmatter field
 rules; bulk-retrofit of existing rules is tracked separately.
 
 Tier 3 dispositions are recorded centrally in
-[`agents/contexts/tier-3-dispositions.md`](../../agents/contexts/tier-3-dispositions.md)
+[`agents/settings/contexts/tier-3-dispositions.md`](../../agents/settings/contexts/tier-3-dispositions.md)
 with a 6-month re-audit clock. New Tier 3 rules append to that list
 on landing.
 

package/docs/guidelines/agent-infra/tool-integration.md

@@ -54,7 +54,7 @@ tool_permissions:
 New tools require:
 1. An adapter implementation in `scripts/tools/`
 2. Registration in the tool registry
-3. Documentation in `agents/docs/tools/`
+3. Documentation in `agents/reference/docs/tools/`
 
 ## Validation rules (linter)
 

package/docs/guidelines/php/api-design.md

@@ -43,7 +43,7 @@ $projects = Project::query()
 
 ## Filtering and Sorting
 
-- Use the project's **filter pipeline** pattern (see `agents/docs/query-filter.md`).
+- Use the project's **filter pipeline** pattern (see `agents/reference/docs/query-filter.md`).
 - Filter classes are dedicated, testable units — not inline query logic.
 - Sorting via `sort` query parameter.
 

package/docs/guidelines/prompt-templates.md

@@ -153,7 +153,7 @@ This package **rejects** that whitelist. CO-STAR, RISEN, CRISPE,
 ReAct, and the image-AI templates above are first-class. The
 "5 safe" framing came from a single benchmark on a single LLM
 generation — it does not generalise. See AI Council session
-`agents/council-responses/prompt-master-mini.json` (2026-05-17) for the analysis behind this rejection. <!-- council-ref-allowed: ADR decision trace -->
+`agents/runtime/council/responses/prompt-master-mini.json` (2026-05-17) for the analysis behind this rejection. <!-- council-ref-allowed: ADR decision trace -->
 
 The right gate is request-type fit, not technique-whitelist
 membership.
@@ -163,4 +163,4 @@ membership.
 - [`prompt-optimizer`](../../.agent-src.uncompressed/skills/prompt-optimizer/SKILL.md) — engine-outbound; cites this catalogue in its Develop step
 - [`refine-prompt`](../../.agent-src.uncompressed/skills/refine-prompt/SKILL.md) — engine-inbound; uses templates in `mini` mode for stack-aware shaping
 - [`prompt-engineering-patterns`](../../.agent-src.uncompressed/skills/prompt-engineering-patterns/SKILL.md) — production-LLM prompt patterns (sibling skill, not a catalogue)
-- AI Council session: `agents/council-responses/prompt-master-mini.json` (2026-05-17) <!-- council-ref-allowed: ADR decision trace -->
+- AI Council session: `agents/runtime/council/responses/prompt-master-mini.json` (2026-05-17) <!-- council-ref-allowed: ADR decision trace -->

package/docs/hook-payload-capture.md

@@ -2,7 +2,7 @@
 
 **Purpose:** walk through the live-session payload capture for one platform
 in roughly 5 minutes, so the corresponding entry in
-[`agents/contexts/chat-history-platform-hooks.md`](../agents/contexts/chat-history-platform-hooks.md)
+[`agents/settings/contexts/chat-history-platform-hooks.md`](../agents/settings/contexts/chat-history-platform-hooks.md)
 can move from `docs-verified` to `payload-verified`.
 
 **Scope:** Cursor · Cline · Windsurf · Gemini CLI. Augment Code and Claude
@@ -158,7 +158,7 @@ then flip the `[ ] Optional upgrade — payload-verified` checkbox to
 `[x]`.
 
 Then update the matching row in
-[`agents/contexts/chat-history-platform-hooks.md`](../agents/contexts/chat-history-platform-hooks.md):
+[`agents/settings/contexts/chat-history-platform-hooks.md`](../agents/settings/contexts/chat-history-platform-hooks.md):
 the `Verification` column moves from `docs-verified` to
 `payload-verified`.
 
@@ -216,6 +216,6 @@ before paste because the redacted output goes into a tracked file
 - Capture engine: [`scripts/hooks/dispatch_hook.py`](../scripts/hooks/dispatch_hook.py) — `_maybe_capture_payload`
 - Redactor: [`scripts/redact_hook_capture.py`](../scripts/redact_hook_capture.py)
 - Per-platform install logic: [`scripts/install.py`](../scripts/install.py) — search `ensure_<platform>_bridge` / `ensure_<platform>_user_hooks`
-- Platform matrix + payload schemas: [`agents/contexts/chat-history-platform-hooks.md`](../agents/contexts/chat-history-platform-hooks.md)
+- Platform matrix + payload schemas: [`agents/settings/contexts/chat-history-platform-hooks.md`](../agents/settings/contexts/chat-history-platform-hooks.md)
 - Hook architecture: [`docs/contracts/hook-architecture-v1.md`](contracts/hook-architecture-v1.md)
 - Archived roadmap with per-phase paste sections: [`agents/roadmaps/archive/road-to-verified-chat-history-platforms.md`](../agents/roadmaps/archive/road-to-verified-chat-history-platforms.md)

package/docs/installation.md

@@ -127,6 +127,14 @@ the per-IDE index above.
 >
 > Python 3.10+ is required for bridges. If it is missing, the orchestrator
 > prints a warning and continues with the payload sync only.
+>
+> **Node.js 20.11+** is required for the `agent-config` binary itself.
+> Starting with the TypeScript CLI shell (ADR-012, road
+> `typescript-cli-and-local-gui-foundation`), the published `bin/`
+> entry is the compiled `dist/cli/agent-config.js`; `npx` resolves it
+> through the registry, so consumers do not need to install Node
+> dependencies into their own project. The package's `engines.node`
+> pin is the source of truth.
 
 | Mode | Best for | Scope |
 |---|---|---|
@@ -706,7 +714,7 @@ writes two local-only files outside the repo contract:
   `mode: cli` members. Daily UTC reset. Inspect with
   `agent-config council quota`; clear today's counter for one provider
   with `agent-config council quota --reset <provider> --confirm`.
-- `agents/council-events.log` — JSONL audit trail. One line per
+- `agents/runtime/council/events.log` — JSONL audit trail. One line per
   necessity-gate decision and per quota block. Gitignored by the
   installer (managed `.gitignore` block); never committed.
   `original_ask` is hashed `sha256[:12]` before write — the raw prompt
@@ -722,7 +730,7 @@ Per-feature environment overrides for ephemeral worktrees, CI runners,
 or sandbox testing:
 
 - `AGENT_CONFIG_NO_EVENTS_LOG=1` — disables every write to
-  `agents/council-events.log` in-process. Quota counter and council
+  `agents/runtime/council/events.log` in-process. Quota counter and council
   output stay untouched.
 - `AGENT_CONFIG_LEGACY_ANCHOR=1` — reverts project-root discovery to
   the pre-step-7 `.git`-only walk. See [Migration — Step 7 anchor
@@ -750,13 +758,13 @@ anchor** wins:
 
 1. `.git` (file or directory).
 2. `agents/` directory containing **any** of `roadmaps/`,
-   `.ai-council.yml`, or `roadmaps-progress.md` — bare `agents/`
+   `settings/.ai-council.yml`, or `roadmaps-progress.md` — bare `agents/`
    does **not** anchor (D1).
 
 If no boundary anchor exists in any ancestor, the **outermost**
 (closest-to-fs-root) `.agent-settings.yml` becomes the root. This
 preserves the layered-settings cascade — see
-[`agents/council-sessions/step-7-d3-cascade-conflict-decision.md`](../agents/council-sessions/step-7-d3-cascade-conflict-decision.md)
+[`agents/runtime/council/sessions/step-7-d3-cascade-conflict-decision.md`](../agents/runtime/council/sessions/step-7-d3-cascade-conflict-decision.md)
 for the rationale.
 
 When a single ancestor carries multiple anchors, the **diagnostic

package/docs/migrations/commands-1.15.0.md

@@ -58,7 +58,7 @@ rg -n '/(fix|optimize|feature)-[a-z-]+' \
 Common spots:
 
 - `agents/roadmaps/*.md` — roadmap steps that name commands
-- `agents/contexts/*.md` — context docs cross-linking commands
+- `agents/settings/contexts/*.md` — context docs cross-linking commands
 - Custom skills/rules under `.augment/` overrides
 - Internal team docs / runbooks / onboarding pages
 
@@ -88,12 +88,12 @@ the deprecation cycle for Phase 1 closes. Tracked in
 ## Related rule split — `chat-history` (post-1.15.0, superseded)
 
 > **Superseded · 2026-05-04** by
-> [`agents/contexts/chat-history-platform-hooks.md`](../../agents/contexts/chat-history-platform-hooks.md).
+> [`agents/settings/contexts/chat-history-platform-hooks.md`](../../agents/settings/contexts/chat-history-platform-hooks.md).
 > The three sibling rules (`chat-history-ownership`,
 > `chat-history-cadence`, `chat-history-visibility`) and the heartbeat
 > marker no longer exist. Persistence is now a pure platform-hook
 > contract — `session_start` auto-adopts foreign sessions silently;
-> the agent never reads or writes `agents/.agent-chat-history` cooperatively.
+> the agent never reads or writes `agents/runtime/.agent-chat-history` cooperatively.
 > Manual recovery lever: `./agent-config chat-history:adopt`.
 
 For historical context: the monolithic `rules/chat-history.md` was

package/docs/parity/bench-ruflo.json

@@ -5,7 +5,7 @@
   "parity_doc": "docs/parity/ruflo.md",
   "parent_bench": "docs/parity/bench.json",
   "claim_under_test": {
-    "source": "agents/audit-2026-05-14-north-star/external-findings.md § 2",
+    "source": "agents/evidence/audits/2026-05-14-north-star/external-findings.md § 2",
     "headline": "Average dollar cost per 25-prompt corpus run, separated by model tier (Haiku / Sonnet / Opus) and by token class (input / output / cache-read / cache-write).",
     "comparison_target": "ruflo cost-tracker README (claimed upstream, not yet pulled into this repo)",
     "type": "claimed_upstream_not_verified_in_repo"

package/docs/parity/ruflo.md

@@ -2,7 +2,7 @@
 
 > Per-row verdict against the eight Ruflo measurement-governance patterns
 > catalogued in
-> [`external-findings.md § 2`](../../agents/council-sessions/audit-2026-05-14-north-star/external-findings.md).
+> [`external-findings.md § 2`](../../agents/evidence/audits/2026-05-14-north-star/external-findings.md).
 > Owner roadmap: [`step-11-ruflo-parity.md`](../../agents/roadmaps/step-11-ruflo-parity.md)
 > (Phase 6 Step 1). Cross-index lives at
 > [`step-99-north-star-restructure.md`](../../agents/roadmaps/step-99-north-star-restructure.md)
@@ -10,7 +10,7 @@
 >
 > **Verdict legend:** `[x] covered by <file:line>` · `[~] superseded by <approach>` · `[!] gap`.
 > **Acceptance:** zero `[!]` rows. Closure flips the corresponding cell in the
-> [composite scorecard](../../agents/council-sessions/audit-2026-05-14-north-star/external-findings.md#5-composite-scorecard--agent-config-vs-the-field)
+> [composite scorecard](../../agents/evidence/audits/2026-05-14-north-star/external-findings.md#5-composite-scorecard--agent-config-vs-the-field)
 > `vs Ruflo` column from `–` to `=` or `+`.
 
 **Measured-vs-claimed disclaimer:** Each row cites the **mechanism** that
@@ -41,6 +41,6 @@ mechanisms remain claimed until [`bench.json`](bench.json) soak completes
 
 ## Cross-references
 
-- Composite scorecard refresh: owned by [`step-99-north-star-restructure.md`](../../agents/roadmaps/step-99-north-star-restructure.md) Phase 5 Step 4 (replaces [`external-findings.md § 5`](../../agents/council-sessions/audit-2026-05-14-north-star/external-findings.md)).
+- Composite scorecard refresh: owned by [`step-99-north-star-restructure.md`](../../agents/roadmaps/step-99-north-star-restructure.md) Phase 5 Step 4 (replaces [`external-findings.md § 5`](../../agents/evidence/audits/2026-05-14-north-star/external-findings.md)).
 - Bench-ruflo redundancy verdict: [`bench-ruflo.json`](bench-ruflo.json) (step-11 Phase 6 Step 2).
 - G5 redundancy gate cite: step-99 Acceptance Criteria row "G5 — external redundancy (Domination Mandate)".

package/docs/profiles.md

@@ -1,7 +1,7 @@
 # Six entry paths — by `profile.id`
 
 Each block below is the first-screen for one shipped profile. The
-`profile.id` written by `/onboard` selects the anchor; the block names
+`profile.id` written by `agent-config setup` selects the anchor; the block names
 the audience, the first three things the agent does for that role,
 and the exact commands and skills wired into the profile YAML at
 [`.agent-src.uncompressed/profiles/<id>.yml`](../.agent-src.uncompressed/profiles/).

package/docs/quality.md

@@ -27,7 +27,7 @@ This runs, in order:
 The linter (`scripts/skill_linter.py`) validates:
 
 - **Required structure** — YAML frontmatter, description, triggers
-- **Frontmatter schema** — Each artefact type has a JSON-Schema in `scripts/schemas/`; violations surface as `schema_<rule>` errors (see [frontmatter contract](../agents/docs/frontmatter-contract.md))
+- **Frontmatter schema** — Each artefact type has a JSON-Schema in `scripts/schemas/`; violations surface as `schema_<rule>` errors (see [frontmatter contract](../agents/reference/docs/frontmatter-contract.md))
 - **Anti-patterns** — Procedural rules in behavior rules, overlong skills, scope creep
 - **Compression quality** — Key sections preserved after compression
 
@@ -86,7 +86,7 @@ task consistency-fix     # Regenerate ALL derived outputs
 Skills dispatched via `scripts/runtime_dispatcher.py run --skill NAME --output FILE`
 write a typed `ExecutionResult` JSON (exit code, stdout, stderr, duration,
 artifacts) to the given path. In CI, the two pilot skills `lint-skills`
-and `check-refs` write to `agents/reports/runs/` and
+and `check-refs` write to `agents/runtime/reports/runs/` and
 `scripts/ci_summary.py` renders them into the GitHub Step Summary so
 failures are visible on the PR page.
 

package/docs/recruits/_template.md

@@ -23,7 +23,7 @@
 - **Consent record:** `<link-to-dm-or-email-thread-or-signed-form>`
 
 > Consent gate per step-13 Phase 1 row 3 — a recruit without an explicit
-> consent record cannot anchor `agents/eval-findings/`. Anonymised
+> consent record cannot anchor `agents/evidence/eval-findings/`. Anonymised
 > finding is acceptable; missing consent record is not.
 
 ## Pre-session readiness
@@ -61,11 +61,11 @@ Empty list = the session wasn't real.
 - **MCP setup time:** `__ minutes __ seconds` (gate: `< 10 min`)
 - **First useful invocation reached without terminal?:** (yes | no | partial)
 - **Recruit would recommend to a peer?:** (yes | maybe | no | declined-to-answer)
-- **Eligible to anchor `agents/eval-findings/`?:** (yes | no — reason)
+- **Eligible to anchor `agents/evidence/eval-findings/`?:** (yes | no — reason)
 
 ## Cross-links
 
-- **Eval-finding file (if logged):** `agents/eval-findings/YYYY-MM-DD-<slug>.md`
+- **Eval-finding file (if logged):** `agents/evidence/eval-findings/YYYY-MM-DD-<slug>.md`
 - **Case-study file (if subject opted in):** `docs/case-studies/YYYY-MM-DD-<type>-<slug>.md`
 - **Roadmap rows closed by this session:**
   - step-13 P1 row 1 (recruit) — yes / no

package/docs/setup/enterprise-and-offline.md

@@ -10,7 +10,7 @@
 
 Re-introducing a Composer-published distribution was evaluated in the
 Phase 0 council session
-(`agents/council-questions/composer-fallback-feasibility.md`) and
+(`agents/runtime/council/questions/composer-fallback-feasibility.md`) and
 **rejected** on three grounds:
 
 1. **Lock-shape mismatch.** `installed.lock` is npm-shaped (flat dep
@@ -193,9 +193,9 @@ A developer arrives on Monday with no network and finds a broken
 
 - `agents/roadmaps/road-to-distribution-maturity.md` § Phase 2 — the
   roadmap entry that produced this document.
-- `agents/council-questions/composer-fallback-feasibility.md` — the
+- `agents/runtime/council/questions/composer-fallback-feasibility.md` — the
   question that rejected the Composer path.
-- `agents/council-questions/hermetic-install-scaffolding.md` — the
+- `agents/runtime/council/questions/hermetic-install-scaffolding.md` — the
   question that shaped Path D.
 - `docs/decisions/ADR-007-agent-discovery-scopes.md` — the lock
   manifest contract that Phase 2 extends additively.

package/docs/setup/mcp-server-docker.md

@@ -61,12 +61,14 @@ for semantics.
 ## Volume mounts (`chat_history_append`)
 
 The `chat_history_append` tool writes to
-`agents/.agent-chat-history` **inside the container**. For writes to
-survive container lifecycle, mount the host directory:
+`agents/runtime/.agent-chat-history` **inside the container**
+(`agents/.agent-chat-history` and `.agent-chat-history` are accepted
+for back-compat). For writes to survive container lifecycle, mount
+the host directory:
 
 ```bash
 docker run --rm -i \
-  -v "$(pwd)/agents/.agent-chat-history:/app/agents/.agent-chat-history" \
+  -v "$(pwd)/agents/runtime/.agent-chat-history:/app/agents/runtime/.agent-chat-history" \
   agent-config-mcp:local
 ```