@event4u/agent-config 14.22.0 → 15.0.0

package/README.md

@@ -4,7 +4,7 @@
 
 [![Smoke](https://github.com/event4u-app/agent-config/actions/workflows/smoke.yml/badge.svg)](https://github.com/event4u-app/agent-config/actions/workflows/smoke.yml) [![Public install smoke (3 OS × 2 Node)](https://github.com/event4u-app/agent-config/actions/workflows/smoke-public-install.yml/badge.svg)](https://github.com/event4u-app/agent-config/actions/workflows/smoke-public-install.yml) [![npm](https://img.shields.io/npm/v/@event4u/agent-config?style=flat-square&label=npm&color=orange)](https://www.npmjs.com/package/@event4u/agent-config) [![agent-config MCP server](https://glama.ai/mcp/servers/event4u-app/agent-config/badges/score.svg)](https://glama.ai/mcp/servers/event4u-app/agent-config) [![MCP Toplist](https://mcptoplist.com/badge/glama%2Fevent4u-app%2Fagent-config.svg)](https://mcptoplist.com/server/glama%2Fevent4u-app%2Fagent-config)
 
-[![Skills](https://img.shields.io/badge/Skills-299-orange?style=flat-square)](dist/agent-src/skills/) [![Rules](https://img.shields.io/badge/Rules-120-orange?style=flat-square)](dist/agent-src/rules/) [![Commands](https://img.shields.io/badge/Commands-204-orange?style=flat-square)](dist/agent-src/commands/) [![Guidelines](https://img.shields.io/badge/Guidelines-118-orange?style=flat-square)](docs/guidelines/) [![Personas](https://img.shields.io/badge/Personas-29-orange?style=flat-square)](dist/agent-src/personas/) [![Advisors](https://img.shields.io/badge/Advisors-5-orange?style=flat-square)](dist/agent-src/personas/advisors/) <!-- claim:published-artifact-counts -->
+[![Skills](https://img.shields.io/badge/Skills-299-orange?style=flat-square)](dist/agent-src/skills/) [![Rules](https://img.shields.io/badge/Rules-120-orange?style=flat-square)](dist/agent-src/rules/) [![Commands](https://img.shields.io/badge/Commands-202-orange?style=flat-square)](dist/agent-src/commands/) [![Guidelines](https://img.shields.io/badge/Guidelines-121-orange?style=flat-square)](docs/guidelines/) [![Personas](https://img.shields.io/badge/Personas-29-orange?style=flat-square)](dist/agent-src/personas/) [![Advisors](https://img.shields.io/badge/Advisors-5-orange?style=flat-square)](dist/agent-src/personas/advisors/) <!-- claim:published-artifact-counts -->
 
 <sub>**How these are counted** — one canonical counter, `agent-config` → `update_counts --check`, re-derives all six from the tree and fails CI on a drift of one. Two bases are not what the linked directory shows, so they are stated here rather than left to be inferred: **Commands 202** counts every command file **recursively** (the linked directory holds 61 at its top level), and **Rules 120** counts the **source** rules while the linked projection holds 119 — one rule is dormant and is not projected. **Personas 29** excludes the directory README. Counts are of files and directories: none of them measures quality, activation, or adoption. <!-- claim:published-artifact-counts --></sub>
 

package/dist/agent-src/commands/agent-handoff.md

@@ -250,19 +250,20 @@ do not auto-execute.
   fingerprint derived from the platform `session_id` (schema v4, see
   [`chat-history-platform-hooks`](../../agents/settings/contexts/chat-history-platform-hooks.md)).
   Works only on the same machine and same repo, but captures every
-  phase / decision any session logged. Pull prior-session context into
-  the current chat verbatim with `/chat-history import`; mine a prior
-  session for project-improving learnings with
+  phase / decision any session logged. Automatic continuity recording
+  preserves a continuity record when the supported recording path
+  completes; mine a prior session for project-improving learnings with
   `/memory mine-session --mode=proposals`.
 
-Prefer `/agent-handoff` for planned context switches and session resumes;
-use `/chat-history import` after a crash or fresh-chat reopen on the same
-workspace to surface prior-session context verbatim.
+Prefer `/agent-handoff` for planned context switches and session resumes.
+After a restart, inspect the most recent continuity record and manually
+reconstruct the context needed to continue.
 
 Three distinct mechanisms — do not conflate them:
 
 - **handoff** (this command) — a one-shot seed for the *next* chat;
   generated from a picked session (or pushed from the live one), ephemeral,
   verbatim on the user's instructions.
-- **[`chat-history import`](../chat-history/import/command.md)** — pull a prior *session's* logged context into the current chat.
+- **transcript import** — no longer available. Legacy transcripts without a
+  usable continuity record require manual reconstruction.
 - **durable memory** ([`memory-consolidation`](../../../skills/memory-consolidation/SKILL.md)) — cross-*run* curated facts; a handoff is not memory, and memory is not a transcript.

package/dist/agent-src/commands/agents/init.md

@@ -171,7 +171,7 @@ If the JSON `candidates` array is non-empty, render the proposed
 
 On accept, append the `modules:` block to the team file
 `.agent-project-settings.yml` (preserve comments + ordering per the
-[`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md)
+[`layered-settings`](../../guidelines/agent-infra/layered-settings.md)
 contract). On skip, do nothing — the block stays opt-in.
 
 ### 8. Follow-ups

package/dist/agent-src/commands/agents/user/accept.md

@@ -20,7 +20,7 @@ packs:
 # /agents user accept
 
 Apply a buffered observation from either
-[the project-local or the global observation buffer](../../../../../docs/contracts/agent-user-schema.md#observation-buffer)
+[the project-local or the global observation buffer](../../../docs/contracts/agent-user-schema.md#observation-buffer)
 to the matching profile file — `.agent-user.md` for a project-local
 observation, the global `~/.event4u/agent-config/user/profile.md` for a
 global one (ADR-138, road-to-global-user-memory Phase 2) — after
@@ -159,7 +159,7 @@ On `1. Apply`:
   never appears in `profile.md`, alongside `context`/`seen_in`, which are
   likewise never written. This is the only generalisation path, and it
   leaves the durable profile with zero project references (see
-  [`agent-user-schema.md § Project attribution`](../../../../../docs/contracts/agent-user-schema.md#project-attribution-road-to-global-user-memory-phase-3)).
+  [`agent-user-schema.md § Project attribution`](../../../docs/contracts/agent-user-schema.md#project-attribution-road-to-global-user-memory-phase-3)).
 
 Either layer: drop **all** applied observations for that field from
 **that layer's own buffer only** (rewrite the JSONL minus matching
@@ -201,8 +201,8 @@ Do NOT commit. Do NOT auto-chain to a second field.
 
 ## See also
 
-- Schema + buffer contract: [`agent-user-schema § Observation buffer`](../../../../../docs/contracts/agent-user-schema.md#observation-buffer).
-- Project attribution + promotion: [`agent-user-schema § Project attribution`](../../../../../docs/contracts/agent-user-schema.md#project-attribution-road-to-global-user-memory-phase-3).
+- Schema + buffer contract: [`agent-user-schema § Observation buffer`](../../../docs/contracts/agent-user-schema.md#observation-buffer).
+- Project attribution + promotion: [`agent-user-schema § Project attribution`](../../../docs/contracts/agent-user-schema.md#project-attribution-road-to-global-user-memory-phase-3).
 - Global write primitive: [`agent_user_profile.applyObservationToGlobalProfile`](../../../../src/scripts/_lib/agent_user_profile.ts).
 - Promotion primitives: [`findPromotionCandidates`, `promotionValueFor`](../../../../../src/scripts/_lib/user_global_observations.ts).
 - Parent: [`/agents user`](../user.md).

package/dist/agent-src/commands/agents/user/delete.md

@@ -24,7 +24,7 @@ road-to-global-user-memory Phase 4, the delete counterpart of
 [`/agents user accept`](accept.md). Every deletion writes an
 append-only tombstone to the revocation ledger BEFORE the underlying
 file is rewritten without it — see
-[`agent-user-schema § Delete, revoke, and audit`](../../../../../docs/contracts/agent-user-schema.md#delete-revoke-and-audit-road-to-global-user-memory-phase-4).
+[`agent-user-schema § Delete, revoke, and audit`](../../../docs/contracts/agent-user-schema.md#delete-revoke-and-audit-road-to-global-user-memory-phase-4).
 
 Three targets, one per invocation:
 
@@ -140,7 +140,7 @@ Do NOT commit. Do NOT auto-chain to a second deletion.
 
 ## See also
 
-- Schema: [`agent-user-schema § Delete, revoke, and audit`](../../../../../docs/contracts/agent-user-schema.md#delete-revoke-and-audit-road-to-global-user-memory-phase-4) — the write→delete mapping and the ADR-121 reuse this command exposes.
+- Schema: [`agent-user-schema § Delete, revoke, and audit`](../../../docs/contracts/agent-user-schema.md#delete-revoke-and-audit-road-to-global-user-memory-phase-4) — the write→delete mapping and the ADR-121 reuse this command exposes.
 - Audit source: [`/agents user show --audit`](show.md) — the read surface that surfaces what there is to delete.
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user review`](review.md), [`/agents user accept`](accept.md) — the write side this command undoes.

package/dist/agent-src/commands/agents/user/init.md

@@ -21,7 +21,7 @@ packs:
 
 Short interactive interview that creates **`.agent-user.md`** at the
 project root from the locked v1 schema in
-[`docs/contracts/agent-user-schema.md`](../../../../../docs/contracts/agent-user-schema.md).
+[`docs/contracts/agent-user-schema.md`](../../../docs/contracts/agent-user-schema.md).
 
 Use when:
 
@@ -98,7 +98,7 @@ Before writing, scan the collected `voice_sample` and `role` for:
 - Health/legal status keywords.
 
 Hit → surface the line and ask the user to redact before proceeding.
-Per [`agent-user-schema § Explicit exclusions`](../../../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
+Per [`agent-user-schema § Explicit exclusions`](../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
 
 ### 5. Render and write
 
@@ -160,5 +160,5 @@ Do NOT commit. Do NOT run any other `/agents user` sub-sub-command.
 
 ## See also
 
-- Schema: [`agent-user-schema`](../../../../../docs/contracts/agent-user-schema.md).
+- Schema: [`agent-user-schema`](../../../docs/contracts/agent-user-schema.md).
 - Parent: [`/agents user`](../user.md).

package/dist/agent-src/commands/agents/user/review.md

@@ -95,7 +95,7 @@ Promotion candidates — seen in 3+ projects:
 
 This is candidacy only, never a promotion — crossing the threshold makes
 `/agents user accept` able to offer promoting it, nothing more (see
-[`agent-user-schema.md § Project attribution`](../../../../../docs/contracts/agent-user-schema.md#project-attribution-road-to-global-user-memory-phase-3)).
+[`agent-user-schema.md § Project attribution`](../../../docs/contracts/agent-user-schema.md#project-attribution-road-to-global-user-memory-phase-3)).
 
 ### 3. Ask
 
@@ -120,7 +120,7 @@ One question per turn. Wait for the user's number.
 ### 4. Privacy-floor verify
 
 Before printing any observation's `evidence` text, scan it for the
-[exclusions list](../../../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
+[exclusions list](../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
 Match → replace the offending substring with `[redacted]` in the
 rendered output.
 
@@ -143,7 +143,7 @@ turn.
 
 ## See also
 
-- Schema + buffer contract: [`agent-user-schema § Observation buffer`](../../../../../docs/contracts/agent-user-schema.md#observation-buffer).
+- Schema + buffer contract: [`agent-user-schema § Observation buffer`](../../../docs/contracts/agent-user-schema.md#observation-buffer).
 - Global buffer implementation: [`user_global_observations.ts`](../../../../src/scripts/_lib/user_global_observations.ts).
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user accept`](accept.md), [`/agents user update`](update.md).

package/dist/agent-src/commands/agents/user/show.md

@@ -22,7 +22,7 @@ packs:
 Read-only render of the **effective, merged** user profile — the
 global `~/.event4u/agent-config/user/profile.md` layer plus the
 project-root `.agent-user.md` layer — per
-[`docs/contracts/agent-user-schema.md`](../../../../../docs/contracts/agent-user-schema.md)
+[`docs/contracts/agent-user-schema.md`](../../../docs/contracts/agent-user-schema.md)
 and its Loader contract / merge rule (ADR-138).
 
 Use when:
@@ -70,7 +70,7 @@ fix it via `/agents user update`).
 ### 3. Merge
 
 Apply the deepest-wins merge rule per
-[`agent-user-schema.md § Global profile layer`](../../../../../docs/contracts/agent-user-schema.md#global-profile-layer-adr-138):
+[`agent-user-schema.md § Global profile layer`](../../../docs/contracts/agent-user-schema.md#global-profile-layer-adr-138):
 for each field (`identity.name`, `language`, `role`, `style.pace`,
 `voice_sample`, `last_updated`), the project layer's value wins when
 present, otherwise the global layer's value is used. `# Notes`
@@ -162,6 +162,6 @@ the project it lives in, so there is nothing to audit for it here.
 
 ## See also
 
-- Schema: [`agent-user-schema`](../../../../../docs/contracts/agent-user-schema.md) — see § Global profile layer for the merge rule this command renders, and § Delete, revoke, and audit for `--audit`'s contract.
+- Schema: [`agent-user-schema`](../../../docs/contracts/agent-user-schema.md) — see § Global profile layer for the merge rule this command renders, and § Delete, revoke, and audit for `--audit`'s contract.
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user init`](init.md), [`/agents user update`](update.md), [`/agents user delete`](delete.md) — the delete/revoke counterpart `--audit` informs.

package/dist/agent-src/commands/agents/user/update.md

@@ -60,7 +60,7 @@ When called with `--validate` (or after the user confirms "done"):
 
 1. Read `.agent-user.md`.
 2. Parse frontmatter; check every required field per
-   [`agent-user-schema § Field reference`](../../../../../docs/contracts/agent-user-schema.md#field-reference).
+   [`agent-user-schema § Field reference`](../../../docs/contracts/agent-user-schema.md#field-reference).
 3. Check file size ≤100 lines.
 4. Run the privacy-floor scan (same as `init` step 4): credentials,
    third-party PII, financial figures, health/legal status.
@@ -98,6 +98,6 @@ Do NOT commit. Do NOT chain to another `/agents user *` command.
 
 ## See also
 
-- Schema: [`agent-user-schema`](../../../../../docs/contracts/agent-user-schema.md).
+- Schema: [`agent-user-schema`](../../../docs/contracts/agent-user-schema.md).
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user init`](init.md), [`/agents user show`](show.md), [`/agents user review`](review.md).

package/dist/agent-src/commands/agents/user.md

@@ -20,14 +20,14 @@ packs:
 # /agents user
 
 Sub-dispatcher for the user-persona file
-[`/.agent-user.md`](../../../docs/contracts/agent-user-schema.md) — a
+[`/.agent-user.md`](../../docs/contracts/agent-user-schema.md) — a
 single, project-root, gitignored Markdown file that captures who the
 user is and how they want the agent to address them.
 
 Since ADR-138, a weaker global layer
 (`~/.event4u/agent-config/user/profile.md`) sits beneath the
 project-local file — see
-[`agent-user-schema.md § Global profile layer`](../../../docs/contracts/agent-user-schema.md#global-profile-layer-adr-138)
+[`agent-user-schema.md § Global profile layer`](../../docs/contracts/agent-user-schema.md#global-profile-layer-adr-138)
 for the merge rule. `init` and `update` operate on the **project-local**
 file only; `review` and `accept` cover BOTH layers' observation buffers
 (road-to-global-user-memory Phase 2/3); `show` renders the merged,
@@ -53,7 +53,7 @@ separate sub-commands for separation of concerns.
 | `/agents user delete` | `commands/agents/user/delete.md` | Delete an observation, purge a project's observations, or revoke a profile field — with a tombstone |
 
 Schema contract:
-[`docs/contracts/agent-user-schema.md`](../../../docs/contracts/agent-user-schema.md).
+[`docs/contracts/agent-user-schema.md`](../../docs/contracts/agent-user-schema.md).
 
 ## Dispatch
 
@@ -70,15 +70,15 @@ Schema contract:
   explicitly authorizes it.
 - **Do NOT write third-party PII** — names, dates, financial figures,
   health/legal status. See the
-  [exclusions list](../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
+  [exclusions list](../../docs/contracts/agent-user-schema.md#explicit-exclusions).
 - **Do NOT introduce network code** in this package. External
   enrichment is rejected for v1 — see the
-  [determinism floor](../../../docs/contracts/agent-user-schema.md#determinism-floor).
+  [determinism floor](../../docs/contracts/agent-user-schema.md#determinism-floor).
 - **Edit `src/` only.** `dist/agent-src/` and
   `.augment/` regenerate from source.
 
 ## See also
 
-- [`agent-user-schema`](../../../docs/contracts/agent-user-schema.md) — locked v1 frontmatter and field reference.
+- [`agent-user-schema`](../../docs/contracts/agent-user-schema.md) — locked v1 frontmatter and field reference.
 - [`/agents`](../AGENTS.md) — parent cluster.
 - [`/agents init`](init.md) — project-side bootstrap (separate primitive).

package/dist/agent-src/commands/analytics/prune.md

@@ -66,5 +66,5 @@ other pass finishes.
 ## See also
 
 - [`/analytics show`](show.md) — render the (post-prune) report.
-- [`local-analytics`](../../../docs/contracts/local-analytics.md)
+- [`local-analytics`](../../docs/contracts/local-analytics.md)
   § Storage — atomicity guarantees and lock semantics.

package/dist/agent-src/commands/analytics/show.md

@@ -88,13 +88,13 @@ and offer the next step:
 
 - Read-only. Never writes to the JSONL, never opens the network.
 - The opt-out check (env + settings) short-circuits before the file is
-  opened — see [`local-analytics`](../../../docs/contracts/local-analytics.md)
+  opened — see [`local-analytics`](../../docs/contracts/local-analytics.md)
   § Opt-out.
 
 ## See also
 
 - [`/analytics prune`](prune.md) — drop events older than 90 days.
-- [`local-analytics`](../../../docs/contracts/local-analytics.md) — full
+- [`local-analytics`](../../docs/contracts/local-analytics.md) — full
   schema and retention contract.
 - [`local-analytics walkthrough`](../../../docs/guides/local-analytics.md)
   — the 3-minute read for end-users.

package/dist/agent-src/commands/analyze/decision.md

@@ -61,7 +61,7 @@ available at the time it was made, not against the outcome alone.
 
 Before drafting a new candidate, call `retrieve()` over the same
 key-space (decision area, affected paths) per
-[`analysis-memory-loop.md § 2`](../../../../docs/contracts/analysis-memory-loop.md):
+[`analysis-memory-loop.md § 2`](../../docs/contracts/analysis-memory-loop.md):
 
 - **Match found** → propose a `frequency` / `supersedes` update.
 - **No match** → draft a new `historical-patterns` candidate:
@@ -110,5 +110,5 @@ suggest deferring or strengthening evidence before proposing.
 ## See also
 
 - [`decision-review`](../../../../skills/decision-review/SKILL.md)
-- [`analysis-memory-loop.md`](../../../../docs/contracts/analysis-memory-loop.md)
+- [`analysis-memory-loop.md`](../../docs/contracts/analysis-memory-loop.md)
 - [`/analyze`](../command.md) — cluster orchestrator

package/dist/agent-src/commands/analyze/inbox.md

@@ -271,7 +271,7 @@ file's mtime against the tree's movement since.
 **Read the provenance line first — it is the cheapest column in the table.** An
 artifact may open with `drafted-against: <short-SHA>` or
 `drafted-at: <YYYY-MM-DD>` (optional by design — see
-[`agents-layout`](../../../../../docs/contracts/agents-layout.md) § Snapshot
+[`agents-layout`](../../docs/contracts/agents-layout.md) § Snapshot
 provenance). When a SHA is present, run `git log --oneline <SHA>..HEAD` **before**
 any deep read: what merged in that window is the set of claims that may be
 *stale rather than wrong*, and that is one command instead of a verification
@@ -619,7 +619,7 @@ coverage.
 **The bound — our tree, read-only, offline, no secrets.** Reproduction runs *our*
 commands against *our* tree: reads, greps, a `--dry-run`, a targeted test filter.
 Writes go only to `agents/runtime/tmp/`
-([`agents-layout`](../../../../../docs/contracts/agents-layout.md)), which is
+([`agents-layout`](../../docs/contracts/agents-layout.md)), which is
 gitignored — never the tracked tree.
 
 The bound is the **five stop-classes this file already declared** in the
@@ -711,7 +711,7 @@ remedy [`systematic-debugging`](../../../../skills/systematic-debugging/SKILL.md
 
 **A `reproduced` that came easily is the verdict to distrust.** A verification
 far easier than expected is a signal to check the path, not a signal of success
-([`false-green`](../../../../../docs/guidelines/agent-infra/false-green.md)
+([`false-green`](../../guidelines/agent-infra/false-green.md)
 § The ease tripwire); the specific failure here is a probe that never actually
 exercised the step. So run the step against the case the file says it handles —
 not only against a case where nothing could have gone wrong. An instrument that
@@ -723,7 +723,7 @@ detectors.
 names, straight from its own wording. That read is free and it is what sorts a
 step into `out-of-bound` before anything is spent finding out. The repo already
 draws this static/dynamic line for installed skills
-([`skill-dry-run`](../../../../../docs/contracts/skill-dry-run.md) § Explicit
+([`skill-dry-run`](../../docs/contracts/skill-dry-run.md) § Explicit
 non-goals: declared intent is rendered, never executed) — cited as the precedent
 for the distinction, **not** as a tool to invoke here: that surface takes an
 installed skill name resolving under `dist/agent-src/skills/`, and an inbox
@@ -1018,7 +1018,7 @@ the class ("an external acceptance-pipeline reference") and put the identity in
 the encrypted intake note.
 
 Then the inbox contract from
-[`agents-layout`](../../../../docs/contracts/agents-layout.md), in the **same
+[`agents-layout`](../../docs/contracts/agents-layout.md), in the **same
 reply**: `mv` the consumed file to `agents/tmp.old/`, point the roadmap's
 `Source:` line at its new path — still the codename — and regenerate the
 dashboard. A consumed file

package/dist/agent-src/commands/analyze/incident.md

@@ -42,7 +42,7 @@ and follow its procedure verbatim:
 
 **Handoff trigger:** mitigation confirmed → proceed to Phase 2.
 Per
-[`analysis-memory-loop.md § 5`](../../../../docs/contracts/analysis-memory-loop.md),
+[`analysis-memory-loop.md § 5`](../../docs/contracts/analysis-memory-loop.md),
 the skeleton is acceptable input with open root-cause items.
 
 ### Phase 2 — Root-cause analysis
@@ -74,7 +74,7 @@ and produce the full write-up:
 
 Dedup pre-check: call `retrieve()` over the same key-space (incident
 type, affected paths) per
-[`analysis-memory-loop.md § 2`](../../../../docs/contracts/analysis-memory-loop.md):
+[`analysis-memory-loop.md § 2`](../../docs/contracts/analysis-memory-loop.md):
 
 - **Match found** → propose a `frequency` / `supersedes` update.
 - **No match** → draft a new `incident-learnings` candidate:
@@ -114,6 +114,6 @@ Surface the draft and ask:
 - [`incident-commander`](../../../../skills/incident-commander/SKILL.md)
 - [`root-cause-frameworks`](../../../../skills/root-cause-frameworks/SKILL.md)
 - [`blameless-post-mortem`](../../../../skills/blameless-post-mortem/SKILL.md)
-- [`analysis-memory-loop.md`](../../../../docs/contracts/analysis-memory-loop.md)
+- [`analysis-memory-loop.md`](../../docs/contracts/analysis-memory-loop.md)
 - [`/analyze:postmortem`](../postmortem/command.md) — post-incident write-up only (no live coordination)
 - [`/analyze`](../command.md) — cluster orchestrator

package/dist/agent-src/commands/analyze/near-miss.md

@@ -45,7 +45,7 @@ with `status: draft`.
 
 Before drafting, call `retrieve()` over the same key-space (affected
 system, incident type, decision area) per
-[`analysis-memory-loop.md § 2`](../../../../docs/contracts/analysis-memory-loop.md):
+[`analysis-memory-loop.md § 2`](../../docs/contracts/analysis-memory-loop.md):
 
 - **Stale entries** (age > `review_after_days`) are in `skipped` —
   surface them; do not silently use them.
@@ -72,7 +72,7 @@ call.
 ### 4. Draft the memory candidate
 
 Per
-[`analysis-memory-loop.md § 1`](../../../../docs/contracts/analysis-memory-loop.md),
+[`analysis-memory-loop.md § 1`](../../docs/contracts/analysis-memory-loop.md),
 draft an `incident-learnings` candidate via `/memory propose`:
 
 ```jsonc
@@ -107,6 +107,6 @@ draft an `incident-learnings` candidate via `/memory propose`:
 ## See also
 
 - [`blameless-post-mortem`](../../../../skills/blameless-post-mortem/SKILL.md)
-- [`analysis-memory-loop.md`](../../../../docs/contracts/analysis-memory-loop.md)
+- [`analysis-memory-loop.md`](../../docs/contracts/analysis-memory-loop.md)
 - [`/analyze:postmortem`](../postmortem/command.md) — same flow, full incident
 - [`/analyze`](../command.md) — cluster orchestrator

package/dist/agent-src/commands/analyze/postmortem.md

@@ -38,14 +38,14 @@ Ask the user (in their language) for what is known:
 - Any existing `incident-commander` skeleton to consume.
 
 Accept an incomplete skeleton per
-[`analysis-memory-loop.md § 5`](../../../../docs/contracts/analysis-memory-loop.md):
+[`analysis-memory-loop.md § 5`](../../docs/contracts/analysis-memory-loop.md):
 a missing root cause is normal, not a blocker.
 
 ### 2. Retrieve prior incident-learnings
 
 Before drafting, call `retrieve()` over the same key-space (incident
 type, affected paths, decision areas) per
-[`analysis-memory-loop.md § 2`](../../../../docs/contracts/analysis-memory-loop.md).
+[`analysis-memory-loop.md § 2`](../../docs/contracts/analysis-memory-loop.md).
 
 - **Stale entries** (age > `review_after_days`) appear in `skipped`
   — surface them to the user, do not silently use them.
@@ -82,7 +82,7 @@ Systems and processes are examined — never individuals.
 ### 5. Draft the memory candidate
 
 Per
-[`analysis-memory-loop.md § 1`](../../../../docs/contracts/analysis-memory-loop.md),
+[`analysis-memory-loop.md § 1`](../../docs/contracts/analysis-memory-loop.md),
 draft an `incident-learnings` candidate using `/memory propose`:
 
 ```jsonc
@@ -125,5 +125,5 @@ Present the draft candidate and ask:
 
 - [`blameless-post-mortem`](../../../../skills/blameless-post-mortem/SKILL.md)
 - [`root-cause-frameworks`](../../../../skills/root-cause-frameworks/SKILL.md)
-- [`analysis-memory-loop.md`](../../../../docs/contracts/analysis-memory-loop.md)
+- [`analysis-memory-loop.md`](../../docs/contracts/analysis-memory-loop.md)
 - [`/analyze`](../command.md) — cluster orchestrator

package/dist/agent-src/commands/analyze/premortem.md

@@ -61,7 +61,7 @@ If the analysis surfaces a pattern worth preserving for future plans:
 
 1. Dedup pre-check: call `retrieve()` over the same key-space (plan
    type, affected paths, decision area) per
-   [`analysis-memory-loop.md § 2`](../../../../docs/contracts/analysis-memory-loop.md).
+   [`analysis-memory-loop.md § 2`](../../docs/contracts/analysis-memory-loop.md).
    - **Match found** → propose a `frequency` / `supersedes` update.
    - **No match** → draft a new `historical-patterns` candidate.
 
@@ -99,5 +99,5 @@ If the analysis surfaces a pattern worth preserving for future plans:
 ## See also
 
 - [`premortem`](../../../../skills/premortem/SKILL.md)
-- [`analysis-memory-loop.md`](../../../../docs/contracts/analysis-memory-loop.md)
+- [`analysis-memory-loop.md`](../../docs/contracts/analysis-memory-loop.md)
 - [`/analyze`](../command.md) — cluster orchestrator

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

@@ -122,11 +122,11 @@ and ask which one was intended. One question, no guessing.
 - **Memory loop applies** — every sub-command that produces an
   analysis output MUST draft a memory candidate via
   `/memory propose` per
-  [`docs/contracts/analysis-memory-loop.md`](../../docs/contracts/analysis-memory-loop.md).
+  [`docs/contracts/analysis-memory-loop.md`](../docs/contracts/analysis-memory-loop.md).
 
 ## See also
 
-- [`docs/contracts/analysis-memory-loop.md`](../../docs/contracts/analysis-memory-loop.md) — produce → propose → promote → retrieve contract
+- [`docs/contracts/analysis-memory-loop.md`](../docs/contracts/analysis-memory-loop.md) — produce → propose → promote → retrieve contract
 - [`blameless-post-mortem`](../../../skills/blameless-post-mortem/SKILL.md) — post-mortem + near-miss skill
 - [`root-cause-frameworks`](../../../skills/root-cause-frameworks/SKILL.md) — RCA engine
 - [`premortem`](../../../skills/premortem/SKILL.md) — forward-looking imagined-failure skill

package/dist/agent-src/commands/bug/fix.md

@@ -192,4 +192,4 @@ What next?
 
 ## See also
 
-- [`role-contracts`](../../../docs/guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract (Goal / Plan / Changes / Tests / Open questions)
+- [`role-contracts`](../../guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract (Goal / Plan / Changes / Tests / Open questions)

package/dist/agent-src/commands/bug/investigate.md

@@ -184,5 +184,5 @@ What's next?
 
 ## See also
 
-- [`role-contracts`](../../../docs/guidelines/agent-infra/role-contracts.md#incident) — Incident mode output contract (Symptom / Reproduction / Minimal reversible change / Deferred verification / Follow-up commitment) — use when the bug is a live production issue with `break-glass: true`
-- [`role-contracts`](../../../docs/guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract for non-incident bugs
+- [`role-contracts`](../../guidelines/agent-infra/role-contracts.md#incident) — Incident mode output contract (Symptom / Reproduction / Minimal reversible change / Deferred verification / Follow-up commitment) — use when the bug is a live production issue with `break-glass: true`
+- [`role-contracts`](../../guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract for non-incident bugs

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

@@ -35,7 +35,7 @@ the [`agent-settings` template](../../templates/agent-settings.md#cost-profiles)
 - For first-run setup use [`/onboard`](onboard.md).
 - For any other single-value change, edit `.agent-settings.yml`
   directly or ask the agent — the merge rules live in
-  [`layered-settings`](../../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
+  [`layered-settings`](../../guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
 - For role modes use [`/mode`](mode.md) — different concept (sets
   `roles.active_role`, not `rule_loading_tier`).
 
@@ -83,7 +83,7 @@ value directly — still echo the old → new line in step 6.
 ### 5. Write the value
 
 Update `rule_loading_tier` in `.agent-settings.yml` using the
-[section-aware merge rules](../../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
+[section-aware merge rules](../../guidelines/agent-infra/layered-settings.md#section-aware-merge-rules)
 (preserve comments, preserve key order, touch only the changed field).
 
 If the user picked "Keep current", do nothing and stop.
@@ -117,6 +117,6 @@ flip. Cost behaviour on those surfaces is governed by the platform itself.
 ## See also
 
 - [`agent-settings`](../../templates/agent-settings.md) — profile matrix and settings reference
-- [`layered-settings`](../../../docs/guidelines/agent-infra/layered-settings.md) — merge rules for settings edits
+- [`layered-settings`](../../guidelines/agent-infra/layered-settings.md) — merge rules for settings edits
 - [`onboard`](onboard.md) — first-run setup (includes profile confirmation)
 - [`mode`](mode.md) — role-mode setter (different concept)

package/dist/agent-src/commands/design.md

@@ -44,7 +44,7 @@ adds a router rather than a 295th entry to it.
 ## The six verbs are one field, not six commands
 
 Each verb declares the `ui_authority` dimensions it may touch
-([contract](../../../docs/contracts/ui-authority.md) § The six operations).
+([contract](../docs/contracts/ui-authority.md) § The six operations).
 That makes a collision **decidable** rather than a judgement call:
 
 ```

package/dist/agent-src/commands/feature/explore.md

@@ -188,4 +188,4 @@ What's next?
 
 ## See also
 
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#po) — PO mode output contract (Goal / Assumptions / Acceptance criteria / Impacted modules / Risks / Open questions for stakeholder)
+- [`role-contracts`](../../guidelines/agent-infra/role-contracts.md#po) — PO mode output contract (Goal / Assumptions / Acceptance criteria / Impacted modules / Risks / Open questions for stakeholder)

package/dist/agent-src/commands/feature/plan.md

@@ -303,7 +303,7 @@ If picked **2** → continue.
 - Set status to `📋 Planned`.
 - If Jira tickets were provided, add them to the `Jira` field and reference them in the feature doc.
 - **Risk review (Gate R1)** — before saving, add a `## Risk Register`
-  section per [`plan-review-gates § 1`](../../../docs/contracts/plan-review-gates.md):
+  section per [`plan-review-gates § 1`](../../docs/contracts/plan-review-gates.md):
   read the C→R1 handoff state from step 0 if present (resolved branches
   seed the risks — never re-ask them), rank the highest product and
   implementation risks descending, one mitigation per row, each row
@@ -386,6 +386,6 @@ What's next?
 
 ## See also
 
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#po) — PO mode output contract (Goal / Assumptions / Acceptance criteria / Impacted modules / Risks / Open questions for stakeholder)
+- [`role-contracts`](../../guidelines/agent-infra/role-contracts.md#po) — PO mode output contract (Goal / Assumptions / Acceptance criteria / Impacted modules / Risks / Open questions for stakeholder)
 - [`refine-ticket`](refine-ticket.md) — optional upstream step: run first when the input is a Jira/Linear ticket rather than a fresh idea
 - [`estimate-ticket`](estimate-ticket.md) — sibling of `refine-ticket`; size + risk + split recommendation for an already-refined ticket

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

@@ -153,7 +153,7 @@ auto-suffix without the user's pick.
 
 **Risk review (Gate R1)** — every generated roadmap that is saved ready
 (non-draft) carries a `## Risk Register` per
-[`plan-review-gates § 1`](../../../docs/contracts/plan-review-gates.md):
+[`plan-review-gates § 1`](../../docs/contracts/plan-review-gates.md):
 read the C→R1 handoff state from step 2 if present (resolved branches
 seed the risks — never re-ask them), rank the highest product and
 implementation risks descending, one mitigation per row, each row
@@ -238,4 +238,4 @@ What's next?
 
 ## See also
 
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#planner) — Planner mode output contract (Goal / Constraints / Option set / Recommendation / Dependencies / Rollback)
+- [`role-contracts`](../../guidelines/agent-infra/role-contracts.md#planner) — Planner mode output contract (Goal / Constraints / Option set / Recommendation / Dependencies / Rollback)

package/dist/agent-src/commands/ghostwriter/fetch.md

@@ -28,7 +28,7 @@ Build (or refresh) a ghostwriter profile at
 
 Zero network code in the package — the host agent performs the fetch /
 search; this command is procedural only. Schema:
-[`ghostwriter-schema`](../../../docs/contracts/ghostwriter-schema.md).
+[`ghostwriter-schema`](../../docs/contracts/ghostwriter-schema.md).
 
 ## Steps
 
@@ -54,7 +54,7 @@ Existing `agents/reference/ghostwriter/<slug>.md`?
 
 Print verbatim, one question per turn, **all four** required before any
 write. Mirrors the deterministic gate in
-[`ghostwriter-schema § public-figure gate`](../../../docs/contracts/ghostwriter-schema.md).
+[`ghostwriter-schema § public-figure gate`](../../docs/contracts/ghostwriter-schema.md).
 
 1. *"Is the target a documented public figure with a public-facing role
    (author / executive / academic / politician / journalist /
@@ -109,7 +109,7 @@ profile.
 ### 4. Derive frontmatter
 
 From the gathered material, populate the locked frontmatter per
-[`ghostwriter-schema § locked frontmatter (v1)`](../../../docs/contracts/ghostwriter-schema.md):
+[`ghostwriter-schema § locked frontmatter (v1)`](../../docs/contracts/ghostwriter-schema.md):
 
 - `identity.*` — name, role, category (from Step 2), source URLs,
   `fetched_at` (today, ISO date), `attestation_recorded_at` (Step 2).
@@ -184,7 +184,7 @@ Non-blocking.
 
 ## See also
 
-- [`ghostwriter-schema`](../../../docs/contracts/ghostwriter-schema.md) — locked v1 frontmatter, verification levels, confidence derivation.
+- [`ghostwriter-schema`](../../docs/contracts/ghostwriter-schema.md) — locked v1 frontmatter, verification levels, confidence derivation.
 - [`/ghostwriter`](../ghostwriter.md) — parent cluster.
 - [`/ghostwriter:write`](write.md) — consume side; appends the mandatory disclosure footer.
 - [`/agents:user:accept`](../agents/user/accept.md) — the diff-and-accept flow this command mirrors on re-fetch.

package/dist/agent-src/commands/ghostwriter/list.md

@@ -104,4 +104,4 @@ guards the package side (run via the package's CI), and consumer-side
 - [`/ghostwriter:show`](show.md) — render a single profile in full.
 - [`/ghostwriter:fetch`](fetch.md) — refresh stale profiles with `--force-refresh`.
 - [`/ghostwriter:write`](write.md) — consume side; reuses the slugs listed here via `--as=<slug>`.
-- [`ghostwriter-schema`](../../../docs/contracts/ghostwriter-schema.md) — field definitions used in the table.
+- [`ghostwriter-schema`](../../docs/contracts/ghostwriter-schema.md) — field definitions used in the table.

package/dist/agent-src/commands/ghostwriter/show.md

@@ -116,4 +116,4 @@ Non-blocking.
 - [`/ghostwriter:fetch`](fetch.md) — refresh path; `--force-refresh` rebuilds from scratch.
 - [`/ghostwriter:delete`](delete.md) — hard-delete the profile.
 - [`/ghostwriter:write`](write.md) — consume the rendered voice.
-- [`ghostwriter-schema`](../../../docs/contracts/ghostwriter-schema.md) — field definitions used here.
+- [`ghostwriter-schema`](../../docs/contracts/ghostwriter-schema.md) — field definitions used here.