@event4u/agent-config 14.23.0 → 15.0.0

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.

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

@@ -20,7 +20,7 @@ packs:
 
 Generate a copyable markdown draft in the voice of a captured
 ghostwriter profile under `agents/reference/ghostwriter/<slug>.md`. Implements
-the [`write-engine`](../../../docs/contracts/write-engine.md) contract
+the [`write-engine`](../../docs/contracts/write-engine.md) contract
 with **mandatory disclosure footer** appended by this command's output
 template (not by the model, no opt-out).
 
@@ -40,7 +40,7 @@ Argument shapes:
 `<value>` resolves against **slugs** and (when
 `ghostwriter.aliases: true` in `.agent-project-settings.yml` — default
 on) the `aliases:` list of every consumer profile. See
-[`ghostwriter-schema § Aliases`](../../../docs/contracts/ghostwriter-schema.md#aliases).
+[`ghostwriter-schema § Aliases`](../../docs/contracts/ghostwriter-schema.md#aliases).
 
 Scan `agents/reference/ghostwriter/*.md`, excluding `README.md` and any file
 with `fictional: true` (fixtures are not consumable from this
@@ -68,7 +68,7 @@ User picks by number or value. No default — explicit choice required.
 ### 2. Load the style source
 
 Read the selected file's frontmatter. Required keys (per
-[`ghostwriter-schema`](../../../docs/contracts/ghostwriter-schema.md)):
+[`ghostwriter-schema`](../../docs/contracts/ghostwriter-schema.md)):
 `identity.name`, `style.fingerprint.*`, `style.free_form_notes`,
 `voice_samples`, `taboos`, `source_provenance.verification`.
 
@@ -78,7 +78,7 @@ Style fidelity may be lower."* Non-blocking.
 
 ### 3. Collect topic + modifiers
 
-Per [`write-engine § 2`](../../../docs/contracts/write-engine.md).
+Per [`write-engine § 2`](../../docs/contracts/write-engine.md).
 Flag form: `--tone=<formal|casual|neutral>`,
 `--length=<words>`, `--channel=<linkedin-post|tweet|blog|freeform>`,
 `--audience=<text>`. The channel values and their length defaults are
@@ -93,13 +93,13 @@ and the vocab-register → tone mapping in the engine contract.
 ### 4. Negative-constraint pass
 
 Apply the loaded `taboos` list as exclusions before drafting (per
-[`write-engine § 3`](../../../docs/contracts/write-engine.md)). Print
+[`write-engine § 3`](../../docs/contracts/write-engine.md)). Print
 a one-line acknowledgement: *"Excluding N taboos from this profile."*
 
 ### 5. Draft
 
 Generate the body as a single fenced markdown block per
-[`write-engine § 4`](../../../docs/contracts/write-engine.md). Honour
+[`write-engine § 4`](../../docs/contracts/write-engine.md). Honour
 fingerprint constraints: sentence-length ±25 %, opener / closer
 patterns, hashtag / emoji rules, ±15 % length tolerance.
 
@@ -116,7 +116,7 @@ This footer is appended **by this command's output template** as a
 fixed string. It is not produced by the model. No `--no-disclosure`
 flag, no `--internal` flag, no opt-out. The absence of any such flag
 is the acceptance criterion (locked in
-[`ghostwriter-schema`](../../../docs/contracts/ghostwriter-schema.md)
+[`ghostwriter-schema`](../../docs/contracts/ghostwriter-schema.md)
 § Mandatory disclosure footer).
 
 **The footer always uses `identity.name`, never the alias that
@@ -161,8 +161,8 @@ Non-blocking.
 
 ## See also
 
-- [`write-engine`](../../../docs/contracts/write-engine.md) — shared procedural contract.
-- [`ghostwriter-schema`](../../../docs/contracts/ghostwriter-schema.md) — locked v1 frontmatter.
+- [`write-engine`](../../docs/contracts/write-engine.md) — shared procedural contract.
+- [`ghostwriter-schema`](../../docs/contracts/ghostwriter-schema.md) — locked v1 frontmatter.
 - [`/ghostwriter`](../ghostwriter.md) — parent cluster.
 - [`/ghostwriter:fetch`](fetch.md) — the producer side.
 - [`/post-as:ghostwriter`](../post-as/ghostwriter.md) — thin alias for this command.

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

@@ -19,7 +19,7 @@ packs:
 
 # /humanize
 
-Run the [`humanizer`](../../../src/skills/humanizer/SKILL.md) skill's
+Run the [`humanizer`](../skills/humanizer/SKILL.md) skill's
 full draft→audit→final loop on a piece of deliverable prose. On-demand
 counterpart to the write-engine's built-in step 4b audit.
 
@@ -34,7 +34,7 @@ counterpart to the write-engine's built-in step 4b audit.
 - `/humanize <path>` — read the file at `<path>` (read-only).
 - `/humanize --voice=<ghostwriter-slug|me>` — optionally resolve a voice
   via the write-engine's style-source resolution (§ 1 of the
-  [`write-engine`](../../docs/contracts/write-engine.md) contract):
+  [`write-engine`](../docs/contracts/write-engine.md) contract):
   a ghostwriter slug loads `agents/reference/ghostwriter/<slug>.md`, `me`
   loads `.agent-user.md`. The resolved fingerprint takes precedence over
   humanizer defaults (a voice that legitimately uses em dashes wins). No
@@ -88,7 +88,7 @@ because it produces no text at all.
 
 ### 2. Run the humanizer loop
 
-Follow [`humanizer § Procedure`](../../../src/skills/humanizer/SKILL.md):
+Follow [`humanizer § Procedure`](../skills/humanizer/SKILL.md):
 load `data/patterns.md`, draft the rewrite (full coverage, voice
 precedence: fingerprint > brand voice > defaults), audit ("what still
 reads AI-generated?"), final rewrite.
@@ -137,9 +137,9 @@ Default form:
 
 ## See also
 
-- [`humanizer`](../../../src/skills/humanizer/SKILL.md) — the skill this
+- [`humanizer`](../skills/humanizer/SKILL.md) — the skill this
   command wraps.
-- [`write-engine § 4b`](../../docs/contracts/write-engine.md) — the
+- [`write-engine § 4b`](../docs/contracts/write-engine.md) — the
   built-in audit for ghostwriter/post-as drafts.
-- [`content-quoting-floor`](../../../src/rules/content-quoting-floor.md)
+- [`content-quoting-floor`](../rules/content-quoting-floor.md)
   — quoted text is never rewritten.

package/dist/agent-src/commands/jira-ticket.md

@@ -81,4 +81,4 @@ packs:
 
 ## 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/judge/solo.md

@@ -94,4 +94,4 @@ Next step: <what the user should do based on the verdict>
 - [`subagent-orchestration`](../skills/subagent-orchestration/SKILL.md)
 - [`/judge on-diff`](do-and-judge.md) — if a revision loop is wanted
 - [`/review-changes`](review-changes.md) — human-oriented self-review
-- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#reviewer) — Reviewer mode output contract (Summary / Risks / Findings / Required actions / Verdict)
+- [`role-contracts`](../../guidelines/agent-infra/role-contracts.md#reviewer) — Reviewer mode output contract (Summary / Risks / Findings / Required actions / Verdict)

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

@@ -84,4 +84,4 @@ the implementer loop, so it never fires on a bare safe-default fallback.
 
 - [`subagent-orchestration`](../skills/subagent-orchestration/SKILL.md)
 - [`/review`](review-changes.md) — human-oriented self-review (Reviewer-mode contract)
-- [`role-contracts`](../docs/guidelines/agent-infra/role-contracts.md#reviewer)
+- [`role-contracts`](../guidelines/agent-infra/role-contracts.md#reviewer)

package/dist/agent-src/commands/knowledge/cross-repo.md

@@ -23,7 +23,7 @@ Targeted, **read-only** retrieval across the IDE-attached sibling repos the user
 has opted into (`linked_projects[].include: true`). Returns a bounded set of
 matches — a shared type, an API contract the frontend consumes, a config the
 sibling owns — **without bulk-including** any sibling file. Implements
-[`cross-repo-retrieval`](../../../docs/contracts/cross-repo-retrieval.md) and
+[`cross-repo-retrieval`](../../docs/contracts/cross-repo-retrieval.md) and
 stays inside [ADR-032](../../../docs/decisions/ADR-032-linked-projects-scope.md)
 Option A.
 

package/dist/agent-src/commands/knowledge/forget.md

@@ -93,5 +93,5 @@ If the prefix matched multiple ingests:
 
 - [`/knowledge ingest`](ingest.md) — add a new ingest.
 - [`/knowledge list`](list.md) — find an id prefix.
-- [`local-knowledge-ingestion`](../../../docs/contracts/local-knowledge-ingestion.md)
+- [`local-knowledge-ingestion`](../../docs/contracts/local-knowledge-ingestion.md)
   § Storage — directory layout.

package/dist/agent-src/commands/knowledge/ingest.md

@@ -21,7 +21,7 @@ packs:
 
 Indexes a local path into the agent's memory namespace. Local-only,
 single-user, bounded. Implements the
-[`local-knowledge-ingestion`](../../../docs/contracts/local-knowledge-ingestion.md)
+[`local-knowledge-ingestion`](../../docs/contracts/local-knowledge-ingestion.md)
 contract.
 
 ## Prerequisites
@@ -107,7 +107,7 @@ Show the user how to retrieve:
 
 ## See also
 
-- [`local-knowledge-ingestion`](../../../docs/contracts/local-knowledge-ingestion.md)
+- [`local-knowledge-ingestion`](../../docs/contracts/local-knowledge-ingestion.md)
   — contract (input shapes, bounds, storage, redaction).
 - [`/knowledge list`](list.md) — what's been ingested, pinning.
 - [`/knowledge forget`](forget.md) — drop an ingest atomically.

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

@@ -100,5 +100,5 @@ user has already provided. See also
 
 - [`/knowledge ingest`](ingest.md) — add a new ingest.
 - [`/knowledge forget`](forget.md) — drop an ingest atomically.
-- [`local-knowledge-ingestion`](../../../docs/contracts/local-knowledge-ingestion.md)
+- [`local-knowledge-ingestion`](../../docs/contracts/local-knowledge-ingestion.md)
   § Bounds — when LRU fires.

package/dist/agent-src/commands/memory/add.md

@@ -20,7 +20,7 @@ packs:
 Creates or updates a single entry in one of the four engineering-memory
 YAML files under `agents/memory/` in the consumer project. The entry
 is validated against the schema in
-[`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md)
+[`engineering-memory-data-format`](../../guidelines/agent-infra/engineering-memory-data-format.md)
 before the file is written.
 
 Absence of these files is legal — this command is the entry point for
@@ -65,7 +65,7 @@ sharded layout: `agents/memory/<type>/*.yml`). For each existing
 ### 3. Collect the required fields
 
 All four types share the frontmatter in
-[`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md#shared-frontmatter-fields).
+[`engineering-memory-data-format`](../../guidelines/agent-infra/engineering-memory-data-format.md#shared-frontmatter-fields).
 Collect in this order, one numbered question at a time:
 
 1. `id` — kebab-case slug, unique within the type.
@@ -140,7 +140,7 @@ Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
 
 ## See also
 
-- [`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md)
+- [`engineering-memory-data-format`](../../guidelines/agent-infra/engineering-memory-data-format.md)
   — full schema
 - [`skill:learning-to-rule-or-skill`](../skills/learning-to-rule-or-skill/SKILL.md) —
   when a learning is better captured as an `incident-learnings` entry vs

package/dist/agent-src/commands/memory/load.md

@@ -122,7 +122,7 @@ opts in.
 
 The agent should now treat every loaded entry as an authority signal
 with its declared `confidence` — see
-[`memory-access`](../../docs/guidelines/agent-infra/memory-access.md) for
+[`memory-access`](../../guidelines/agent-infra/memory-access.md) for
 how entries modulate edits.
 
 ### 5. Inline-review hook (intake backlog)
@@ -184,8 +184,8 @@ When resolving a knowledge/memory read — including cross-project access — cl
 the ladder and stop at the first rung that answers; do not jump straight to a
 full scan:
 
-1. **Hot cache** — the already-loaded session slice (`hot-context.md` / the
-   Tier-0 slice above); zero new reads.
+1. **Already loaded** — the session slice already in context (the Tier-0 slice
+   above, plus the `session_start` memory index when armed); zero new reads.
 2. **Index** — the lexical index / `memory_lookup retrieve_v1` over the keys.
 3. **Type index** — narrow to the relevant type directory, then its entries.
 4. **Entry** — read the specific entry only once the first three located it.
@@ -198,5 +198,5 @@ nothing on this" — never invent an entry to fill the gap.
 - [`memory-add`](memory-add.md) — add a single entry
 - [`memory-promote`](memory-promote.md) — promote an intake signal to
   a curated entry
-- [`memory-access`](../../docs/guidelines/agent-infra/memory-access.md) —
+- [`memory-access`](../../guidelines/agent-infra/memory-access.md) —
   how entries flow into agent decisions

package/dist/agent-src/commands/memory/mine-session.md

@@ -180,5 +180,5 @@ Confirm:
   `TranscriptAdapter` matches the current host.
 - [`memory:promote`](promote.md) — lifts validated intake lines into
   curated YAML.
-- [`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md) —
+- [`memory-access`](../../guidelines/agent-infra/memory-access.md) —
   file-backed retrieval contract for curated + intake entries.

package/dist/agent-src/commands/memory/promote.md

@@ -69,7 +69,7 @@ gate script to lower the bar.
 ### 3. Draft the curated entry
 
 Using the schema in
-[`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md),
+[`engineering-memory-data-format`](../../guidelines/agent-infra/engineering-memory-data-format.md),
 hydrate the full frontmatter:
 
 - `id` — kebab-case slug (not the `sig-*` id — that is an intake marker).
@@ -83,7 +83,7 @@ hydrate the full frontmatter:
   on every `/memory:load` regardless of query — e.g. a tenant-isolation
   invariant or a payment-flow rule. The validator warns when a type
   accumulates more than 10 active critical entries; raise the bar
-  deliberately. See [`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md)
+  deliberately. See [`engineering-memory-data-format`](../../guidelines/agent-infra/engineering-memory-data-format.md)
   § Priority semantics for the full contract.
 - `ts_week:` — optional ISO-week stamp `YYYY-Www` (e.g. `2026-W17`).
   **Convention, not enforced.** Stamp the curated entry with the week
@@ -94,7 +94,7 @@ hydrate the full frontmatter:
   ```bash
   date -u +'%G-W%V'   # POSIX ISO week-numbering year + ISO week
   ```
-  See [`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md)
+  See [`engineering-memory-data-format`](../../guidelines/agent-infra/engineering-memory-data-format.md)
   § Temporal jitter for rationale.
 - Type-specific fields (`rule`, `symptom`, `path`, …).
 
@@ -236,4 +236,4 @@ Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
 
 - [`/propose-memory`](propose-memory.md) — write-side entry point.
 - [`/memory-add`](memory-add.md) — direct curated write (skips intake).
-- [`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md)
+- [`engineering-memory-data-format`](../../guidelines/agent-infra/engineering-memory-data-format.md)

package/dist/agent-src/commands/memory/propose.md

@@ -131,6 +131,6 @@ is intended (rarely).
 ## See also
 
 - [`/memory-add`](memory-add.md) — curated (reviewer-validated) entries.
-- [`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md)
-- [`memory-access`](../../docs/guidelines/agent-infra/memory-access.md) — the
+- [`engineering-memory-data-format`](../../guidelines/agent-infra/engineering-memory-data-format.md)
+- [`memory-access`](../../guidelines/agent-infra/memory-access.md) — the
   read-side contract that consumes what this command writes.