@event4u/agent-config 14.23.0 → 16.0.0

package/dist/agent-src/skills/reasoning-orchestrator/SKILL.md

@@ -73,7 +73,7 @@ Each link **delegates** to the artifact that owns it (no duplication):
 1. **ground** — close constraints/tools/info-gaps before designing
    ([`think-before-action` § Environment grounding](../../rules/think-before-action.md));
    seed the read from the **repo** slot of the
-   [context-spine](../../../docs/contracts/context-spine.md) when present.
+   [context-spine](../../docs/contracts/context-spine.md) when present.
 2. **intent** — state the inferred goal + one recommendation, standard host only
    ([`improve-before-implement` § Intent inference](../../rules/improve-before-implement.md)).
 3. **notes** — hypotheses/predictions/decisions/uncertainty to the notes file, not
@@ -146,4 +146,4 @@ action — grounding and the load-bearing-unknown resolution precede any edit):
   [`verify-before-complete`](../../rules/verify-before-complete.md)) instead of the
   whole chain.
 - Needing the rationale behind the protocol — read
-  [`frontier-reasoning-operating-profile`](../../../../docs/guidelines/agent-infra/frontier-reasoning-operating-profile.md).
+  [`frontier-reasoning-operating-profile`](../../guidelines/agent-infra/frontier-reasoning-operating-profile.md).

package/dist/agent-src/skills/receiving-code-review/SKILL.md

@@ -83,7 +83,7 @@ For each comment classified as blocking/important:
 * Check `git blame` / history — the current code may be the way it is
   for a reason
 * **Consult memory for prior context.** Via
-  [`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md),
+  [`memory-access`](../../guidelines/agent-infra/memory-access.md),
   call `retrieve(types=["historical-patterns"],
   keys=<files in the review>, limit=3)`. A registered historical pattern
   may confirm the reviewer's concern (accept). For architectural rationale

package/dist/agent-src/skills/refine-ticket/SKILL.md

@@ -149,7 +149,7 @@ Check the loaded ticket for clarity signals before orchestrating:
 - **silent-but-needed** — is the spec silent on a clearly-needed behavior (weekend/holiday shift, empty state, error path, timezone, permissions)? Surface it and ask before it becomes an implementation assumption — an inferred behavior is a scope expansion, not a given.
 - **intra-ticket** — do the AC, description, and comments contradict each other?
 
-Fold every discrepancy into the refined output's *Open questions* section (one batched list), never a second prompt. Full taxonomy + scan procedure: [`cross-source-consistency-mechanics`](../../../docs/guidelines/agent-infra/cross-source-consistency-mechanics.md).
+Fold every discrepancy into the refined output's *Open questions* section (one batched list), never a second prompt. Full taxonomy + scan procedure: [`cross-source-consistency-mechanics`](../../guidelines/agent-infra/cross-source-consistency-mechanics.md).
 
 Then run the deterministic detection helper — do **not** re-derive trigger
 logic in prose:
@@ -231,7 +231,7 @@ lens. v1 is CLI-only (no skill-level default; no frontmatter list). The
 user-type voice renders as one paragraph in *Persona voices* labelled
 `**User: <label>**`, citing Daily Workflow, Vocabulary, Operational
 Constraints, and Ticket Red Flags from the loaded user-type. Contract:
-[`docs/contracts/user-type-schema.md`](../../../docs/contracts/user-type-schema.md).
+[`docs/contracts/user-type-schema.md`](../../docs/contracts/user-type-schema.md).
 
 ### 5. Synthesize + close-prompt
 

package/dist/agent-src/skills/release-comms/SKILL.md

@@ -34,7 +34,7 @@ discovery — this skill assumes the change is **shipped**.
 - **Mental model 16 — Leading vs. lagging indicators.** A release
   note is the lagging artifact; the leading version is the in-app
   prompt that fired before the user found the change-log. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 16.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 16.
 - **Value-not-feature heuristic.** Every paragraph passes the *"so
   the user can ___"* completion. Failing rows go back for re-write.
 
@@ -43,7 +43,7 @@ discovery — this skill assumes the change is **shipped**.
 ### Step 0: Ground the release
 
 1. Read the merged PR list / changelog block / release branch diff. The release is the **what**; comms is the **so what**. Conflate the two and you ship marketing.
-2. Read the **product** and **team** slots of the [context-spine](../../../docs/contracts/context-spine.md) (if the consumer project has filled them) for bounded scope and release cadence — surface choice depends on cadence (weekly: in-app + log; quarterly: email + post; major: all four).
+2. Read the **product** and **team** slots of the [context-spine](../../docs/contracts/context-spine.md) (if the consumer project has filled them) for bounded scope and release cadence — surface choice depends on cadence (weekly: in-app + log; quarterly: email + post; major: all four).
 3. Identify the **single dominant change** the release ships. A release with three "headliners" reads as three half-announcements.
 
 ### Step 1: Audience-segment

package/dist/agent-src/skills/retention-loops/SKILL.md

@@ -36,7 +36,7 @@ Do NOT use to fix days 0–30 onboarding friction (route to
   *gain* (how strong the reward is) and *delay* (how long until
   the reward lands), not in the surface UI. Pick the leverage
   point — gain or delay — over surface polish. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 14.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 14.
 - **Mental model 8 — Compounding.** A loop with even small gain
   per cycle compounds across cohorts; a one-time activation
   bump does not. Verify which loops compound before investing
@@ -51,7 +51,7 @@ Do NOT use to fix days 0–30 onboarding friction (route to
   **customer-segment** slot for which segments have the latent
   need the loop addresses, and the **funnel-stage** slot for where
   the loop sits relative to activation and paid. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/review-routing/SKILL.md

@@ -58,7 +58,7 @@ back. If neither file exists, emit the generic role-based fallback
 using the common role vocabulary below.
 
 **Also** pull agent-written signals via the shared abstraction (see
-[`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md)):
+[`memory-access`](../../guidelines/agent-infra/memory-access.md)):
 
 ```bash
 agent-config memory:lookup \
@@ -209,7 +209,7 @@ Data source: <"ownership-map.yml + historical-bug-patterns.yml"
 ## See also
 
 - [`reviewer-awareness`](../../rules/reviewer-awareness.md) — the rule that routes here: anchor reviewer choice in paths and risk, never seniority
-- [`review-routing-data-format`](../../../docs/guidelines/agent-infra/review-routing-data-format.md)
+- [`review-routing-data-format`](../../guidelines/agent-infra/review-routing-data-format.md)
 - [`/pr:create:description-only`](../../domains/git/pr/create/description-only/command.md)
 - [`judge-test-coverage`](../judge-test-coverage/SKILL.md) — consumes
   the `required_test` entries from matched patterns.

package/dist/agent-src/skills/roadmap-management/SKILL.md

@@ -85,7 +85,7 @@ different agents.
 
 **Module path resolution.** `{module_root}` and `{agent_folder}` come from
 `modules.root_paths` and `modules.agent_folder` in
-`.agent-project-settings.yml` — see [`layered-settings`](../../../../../docs/guidelines/agent-infra/layered-settings.md).
+`.agent-project-settings.yml` — see [`layered-settings`](../../guidelines/agent-infra/layered-settings.md).
 Common shapes:
 
 - Laravel — `app/Modules/{Module}/agents/roadmaps/`

package/dist/agent-src/skills/roadmap-management/references/archival.md

@@ -27,7 +27,7 @@ After the last step of a roadmap is done, check completion status:
    - Work findings in priority order — each ends `fixed` / `accepted-risk` /
      `deferred`. No code surface → explicit skip, never silent.
    - Grammar, scope-hash binding, escape hatch:
-     [`plan-review-gates § 2`](../../../../docs/contracts/plan-review-gates.md).
+     [`plan-review-gates § 2`](../../../docs/contracts/plan-review-gates.md).
 
 1. **Scan the file** for all checkbox markers: `- [x]`, `- [ ]`, `- [~]`, `- [-]`.
 2. **Classify:**

package/dist/agent-src/skills/roadmap-writing/SKILL.md

@@ -22,7 +22,7 @@ packs:
 * Rewriting an existing roadmap (phase restructure, goal pivot,
   council-pass integration — not a checkbox flip)
 * Drafting a phase block, exit criteria, or rollback section that
-  will land inside an existing roadmap — an operator **symptom** as the input has its own entry procedure: [`symptom-driven harvest`](../../../docs/guidelines/agent-infra/symptom-driven-harvest-loop.md)
+  will land inside an existing roadmap — an operator **symptom** as the input has its own entry procedure: [`symptom-driven harvest`](../../guidelines/agent-infra/symptom-driven-harvest-loop.md)
 
 Do NOT use this skill when:
 
@@ -86,7 +86,7 @@ carry `parent_roadmap:` (rule 17).
 Default `lightweight` (≤ 6 phases, ≤ 600 lines). Only use
 `structural` when the change touches a contract, kernel rule, or
 budget invariant — the complexity linter enforces it. Standard:
-[`roadmap-complexity-standard`](../../../docs/contracts/roadmap-complexity-standard.md).
+[`roadmap-complexity-standard`](../../docs/contracts/roadmap-complexity-standard.md).
 
 ### 3. Write the goal first
 
@@ -107,7 +107,7 @@ built over a text↔image contradiction or a silent-but-needed behavior
 every downstream step. Surface each discrepancy as one batched open
 question first; an inferred behavior is a scope expansion to confirm, not
 to plan silently. Taxonomy + procedure:
-[`cross-source-consistency-mechanics`](../../../docs/guidelines/agent-infra/cross-source-consistency-mechanics.md).
+[`cross-source-consistency-mechanics`](../../guidelines/agent-infra/cross-source-consistency-mechanics.md).
 
 ### 4. Phase blocks carry checkboxes
 
@@ -199,7 +199,7 @@ Omit it entirely when there is no such gate; run the § 4c gate-test first.
   from a fresh C→R1 handoff state (never re-ask a resolved branch).
 - Product AND implementation risks ranked descending, one mitigation per row,
   each anchored to a phase/step here; none → exact honest-null grammar.
-- Schema, staleness, grandfather, drafts-exempt: [`plan-review-gates § 1`](../../../docs/contracts/plan-review-gates.md).
+- Schema, staleness, grandfather, drafts-exempt: [`plan-review-gates § 1`](../../docs/contracts/plan-review-gates.md).
 
 ### 6. Step-marker semantics — pick `[~]` (defer) vs `[-]` (cancel) honestly
 
@@ -352,7 +352,7 @@ to every roadmap you author.
   `<!-- carve-out: new-gate-verification -->` when it verifies a NEW
   gate this roadmap introduces.
 * Use ALL-CAPS Iron-Law fenced blocks — those belong in
-  [`kernel-membership`](../../../docs/contracts/kernel-membership.md)-listed rules.
+  [`kernel-membership`](../../docs/contracts/kernel-membership.md)-listed rules.
 * Adopt items from an external source / harvest **without a
   `KEEP`/`FOLD`/`CUT` gap-table** against the existing surface (§ 8) —
   that is a skill dump, not integration.

package/dist/agent-src/skills/rule-writing/SKILL.md

@@ -95,13 +95,13 @@ Three different surfaces, three different rules. Mixing them up will
 either fail the schema (`./scripts-run src/scripts/validate_frontmatter`) or
 fail `./scripts-run src/scripts/lint_load_context`. Canonical reference:
 [`templates/rule.md`](../../templates/rule.md) § Path conventions and
-[`docs/contracts/load-context-schema.md`](../../../docs/contracts/load-context-schema.md).
+[`docs/contracts/load-context-schema.md`](../../docs/contracts/load-context-schema.md).
 
 | Field | Form | Example |
 |---|---|---|
 | `load_context:` / `load_context_eager:` | **Logical name** rooted at the source — never `src/` | `contexts/execution/verification-mechanics.md` |
 | `triggers[].path_prefix:` | **Literal match pattern** the host evaluates against the file the agent is editing — not rewritten | `src/skills/` (source-of-truth rules) or `agents/`, `app/`, `.augment/` |
-| Body links to guidelines / contracts | **Verbatim relative form** — `../../docs/...` works in any markdown viewer; rewriter handles depth | `[guideline](../../docs/guidelines/<group>/<name>.md)` |
+| Body links to guidelines / contracts | **Verbatim relative form** — `../../docs/...` works in any markdown viewer; rewriter handles depth | `[guideline](../../guidelines/<group>/<name>.md)` |
 
 The condense-time rewriter (`scripts/condense.ts::_rewrite_paths`) is
 idempotent and depth-aware — it resolves logical names and body links
@@ -307,7 +307,7 @@ to every rule you author.
   body — start with the obligation, not a setup paragraph.
 - Per the Iron-Law literal predicate, ALL-CAPS fenced obligations
   belong only when the rule sits on the
-  [`kernel-membership`](../../../docs/contracts/kernel-membership.md)
+  [`kernel-membership`](../../docs/contracts/kernel-membership.md)
   list.
 - Per the cheap-question check, the rule's "When to ask" guidance
   must list decidable triggers, not vibe-based judgment.
@@ -364,9 +364,9 @@ an interrupt, which reply mirrors the user's language — needs the same treatme
 for the **behaviour**, not just the frontmatter.
 
 Six live corpora already carry those pairs:
-[`direct-answers-demos`](../../../docs/guidelines/agent-infra/direct-answers-demos.md),
-[`asking-and-brevity-examples`](../../../docs/guidelines/agent-infra/asking-and-brevity-examples.md),
-[`language-and-tone-examples`](../../../docs/guidelines/agent-infra/language-and-tone-examples.md),
+[`direct-answers-demos`](../../guidelines/agent-infra/direct-answers-demos.md),
+[`asking-and-brevity-examples`](../../guidelines/agent-infra/asking-and-brevity-examples.md),
+[`language-and-tone-examples`](../../guidelines/agent-infra/language-and-tone-examples.md),
 and `autonomy-examples` / `interrupt-examples` / `cheap-question-mechanics` under
 `src/agent-src/contexts/execution/`. Follow one; do not invent a format.
 

package/dist/agent-src/skills/runway-cognition/SKILL.md

@@ -33,10 +33,10 @@ Do NOT use for per-customer economics (route to `unit-economics-modeling` (O1)),
 
 ## Cognition cluster
 
-- **Mental model 21 — Second-order thinking.** *"If we cut here, then ___, and then ___."* Runway decisions are second-order by construction: the first-order effect (extended runway) is trivial; the second-order effect (slower growth → next-round terms → dilution) is the real decision. See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 21.
+- **Mental model 21 — Second-order thinking.** *"If we cut here, then ___, and then ___."* Runway decisions are second-order by construction: the first-order effect (extended runway) is trivial; the second-order effect (slower growth → next-round terms → dilution) is the real decision. See [`mental-models.md`](../../docs/contracts/mental-models.md) § 21.
 - **Mental model 28 — Inversion.** *"What would force a down-round?"* Invert the fundraise question: instead of *"can we raise?"* ask *"what evidence would the market need to fund us at this valuation?"* and work backwards. See `mental-models.md` § 28.
 - **Mental model 16 — Leading vs lagging indicators.** Cash balance is lagging; **net burn trend over the last 3 fiscal-periods** + **pipeline coverage of next-window revenue** are leading. A runway model that reads only cash balance is reading yesterday's weather. See `mental-models.md` § 16.
-- **Context-spine — org-stage + fiscal-period + product.** Read the **org-stage** slot for what bands apply (pre-seed / seed / Series A / Series B+ / growth / public — each has a different "healthy runway" band; do not hardcode 18 months). Read **fiscal-period** for the cadence the runway model rolls forward against. Read **product** for what's GA-shippable in the window — pre-revenue product changes the cognition shape (extend until traction) vs post-revenue (extend until next milestone). See [`context-spine`](../../../docs/contracts/context-spine.md).
+- **Context-spine — org-stage + fiscal-period + product.** Read the **org-stage** slot for what bands apply (pre-seed / seed / Series A / Series B+ / growth / public — each has a different "healthy runway" band; do not hardcode 18 months). Read **fiscal-period** for the cadence the runway model rolls forward against. Read **product** for what's GA-shippable in the window — pre-revenue product changes the cognition shape (extend until traction) vs post-revenue (extend until next milestone). See [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/scenario-modeling/SKILL.md

@@ -28,10 +28,10 @@ Do NOT use for per-customer economics (route to `unit-economics-modeling` (O1)),
 
 ## Cognition cluster
 
-- **Mental model 21 — Second-order thinking.** Each scenario is a chain: revenue → margin → burn → runway → fundraise → dilution. Single-statement scenarios (just revenue) skip the chain and read like wishlists. See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 21.
+- **Mental model 21 — Second-order thinking.** Each scenario is a chain: revenue → margin → burn → runway → fundraise → dilution. Single-statement scenarios (just revenue) skip the chain and read like wishlists. See [`mental-models.md`](../../docs/contracts/mental-models.md) § 21.
 - **Mental model 29 — Premortem.** *"It's two windows from now and the downside scenario happened. Walk back."* The premortem forces concrete failure paths into the model; without it the downside is just a 20 % discount on base. See `mental-models.md` § 29.
 - **Mental model 26 — Optionality.** Optionality = preserved future choices. Read each scenario by what choices it preserves vs forecloses. Bounded downside + preserved optionality > unbounded upside with foreclosed optionality. See `mental-models.md` § 26.
-- **Context-spine — org-stage + fiscal-period + product.** Read **org-stage** for which scenarios matter (pre-revenue → upside is traction speed; growth → downside is competitive pressure). Read **fiscal-period** for the modeling horizon. Read **product** for which revenue lines are real vs roadmap. See [`context-spine`](../../../docs/contracts/context-spine.md).
+- **Context-spine — org-stage + fiscal-period + product.** Read **org-stage** for which scenarios matter (pre-revenue → upside is traction speed; growth → downside is competitive pressure). Read **fiscal-period** for the modeling horizon. Read **product** for which revenue lines are real vs roadmap. See [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/skill-writing/SKILL.md

@@ -181,7 +181,7 @@ the one the task calls for.
 ### Cross-references and paths
 
 * Body links to guidelines / contracts use the verbatim relative form
-  (`../../docs/guidelines/<group>/<name>.md`,
+  (`../../guidelines/<group>/<name>.md`,
   `../../docs/contracts/<name>.md`). The condense-time rewriter
   resolves them to depth-aware single-up form — do not pre-rewrite in
   source.
@@ -269,4 +269,4 @@ Workflow sequencing, preconditions, ID/output provenance ("copy ids verbatim,
 never from memory"), a mandatory "why" intent field, and turn-end contracts
 belong INSIDE this artifact's description/frontmatter — where they fire at the
 decision point — not in always-on prose. See
-[`tool-description-as-policy`](../../../docs/guidelines/agent-infra/tool-description-as-policy.md).
+[`tool-description-as-policy`](../../guidelines/agent-infra/tool-description-as-policy.md).

package/dist/agent-src/skills/skill-writing/references/procedure.md

@@ -56,7 +56,7 @@ ships is worse than no record.
 **Surface overlap before deciding** — run `./scripts-run src/scripts/skill_overlap`
 (or `audit_skill_overlap`) and read the nearest matches; a high-overlap hit is a
 merge signal, not a green light. This gate is the authoring-time companion to the
-[capability-boundary matrix](../../../../../docs/contracts/capability-boundary.md): the
+[capability-boundary matrix](../../../docs/contracts/capability-boundary.md): the
 matrix governs packs, this governs the skills inside them.
 
 ### 1. Define the trigger

package/dist/agent-src/skills/skill-writing/references/section-patterns.md

@@ -282,9 +282,9 @@ edge is.
 Where a skill's guidance is easy to agree with and hard to apply — tone, phrasing,
 question shape, what counts as evidence — a wrong/right pair does what prose
 cannot: it shows the near-miss. Six live corpora already carry them:
-[`direct-answers-demos`](../../../../../docs/guidelines/agent-infra/direct-answers-demos.md),
-[`asking-and-brevity-examples`](../../../../../docs/guidelines/agent-infra/asking-and-brevity-examples.md),
-[`language-and-tone-examples`](../../../../../docs/guidelines/agent-infra/language-and-tone-examples.md),
+[`direct-answers-demos`](../../../guidelines/agent-infra/direct-answers-demos.md),
+[`asking-and-brevity-examples`](../../../guidelines/agent-infra/asking-and-brevity-examples.md),
+[`language-and-tone-examples`](../../../guidelines/agent-infra/language-and-tone-examples.md),
 and `autonomy-examples` / `interrupt-examples` / `cheap-question-mechanics` under
 `src/agent-src/contexts/execution/`.
 

package/dist/agent-src/skills/spreadsheet-authoring/SKILL.md

@@ -21,7 +21,7 @@ execution:
 # spreadsheet-authoring
 
 > The spreadsheet surface's correctness floor (per
-> [`surface-agent-contracts`](../../../docs/contracts/surface-agent-contracts.md)):
+> [`surface-agent-contracts`](../../docs/contracts/surface-agent-contracts.md)):
 > a spreadsheet's **truth source is the formula read-back**, not a plausible
 > table of numbers. A cell that holds a hardcoded computed value is a latent
 > lie — it silently goes stale the moment an input changes.

package/dist/agent-src/skills/stakeholder-tradeoff/SKILL.md

@@ -55,7 +55,7 @@ Do NOT use when:
   also an opportunity cost on the stakeholders not getting that
   benefit; the matrix only earns its keep when it surfaces who pays
   for the chosen `+`. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 5.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 5.
 - **Mental model 27 — Outcome over output.** Picking the option with
   the most checkmarks is output theatre; pick the option whose `–`
   cells land on stakeholders who can execute mitigations. See
@@ -67,7 +67,7 @@ Do NOT use when:
 - **Team + product context-spine slots.** Read **team** for the
   silent-stakeholders inventory (on-call, support, finance) and
   **product** for end-user / segment lenses (free vs paid, region,
-  cohort). See [`context-spine`](../../../docs/contracts/context-spine.md).
+  cohort). See [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 
@@ -145,7 +145,7 @@ column is missing.
   but PO wants to ship) — start with `code-review-multi-lens`
   (sibling C8); a C8 verdict that surfaces stakeholder conflict
   becomes input to this skill for escalation. Boundary prose lives
-  in [`docs/guidelines/cross-role-handoff.md`](../../../docs/guidelines/cross-role-handoff.md).
+  in [`docs/guidelines/cross-role-handoff.md`](../../guidelines/cross-role-handoff.md).
 - The trade-off is purely technical (perf vs storage, sync vs async)
   — route to [`decision-record`](../decision-record/SKILL.md); if it is
   one costly choice on ≥ 3 options with user-weighted criteria, its

package/dist/agent-src/skills/subagent-orchestration/SKILL.md

@@ -386,4 +386,4 @@ Skip emit when `emergency.orchestration_halt` is set or `spawn_count == 0`
 | External / networked second opinion  | [`ai-council`](../ai-council/SKILL.md) |
 | Cross-model review WITH repo access   | [`/team`](../../domains/meta/team/command.md) (collaborative; subagents are in-session same-weights) |
 | Verifying completeness               | [`verify-completion-evidence`](../verify-completion-evidence/SKILL.md) |
-| What a subagent owns vs never owns   | [`subagent-boundary`](../../../docs/contracts/subagent-boundary.md) |
+| What a subagent owns vs never owns   | [`subagent-boundary`](../../docs/contracts/subagent-boundary.md) |

package/dist/agent-src/skills/supply-chain-intake/SKILL.md

@@ -39,7 +39,7 @@ PIN IT, LOCK IT, CVE-SCAN IT. NEVER PIPE A REMOTE SCRIPT STRAIGHT TO A SHELL.
    (`crypto.randomUUID` before a uuid package, `Intl` before a formatting
    library, `AbortSignal.timeout` before a timeout helper, the database's own
    full-text / JSON support before an application-side index)? Full ordering:
-   [`agent-interaction-and-decision-quality` § 8b-ladder](../../../docs/guidelines/agent-infra/agent-interaction-and-decision-quality.md).
+   [`agent-interaction-and-decision-quality` § 8b-ladder](../../guidelines/agent-infra/agent-interaction-and-decision-quality.md).
    A dependency added for something already present is permanent cost — install
    surface, CVE surface, upgrade surface — bought against a capability you had.
 1. **Existence** — confirm the exact string resolves on the real registry, published before your session and with real usage:

package/dist/agent-src/skills/systematic-debugging/SKILL.md

@@ -107,7 +107,7 @@ Goal: locate the failure in a single component, layer, or call site.
 3. Check recent changes: `git log`, `git blame` on the failing line,
    recent dependency updates, config edits, infra changes.
 4. **Consult memory for prior matches.** Via
-   [`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md):
+   [`memory-access`](../../guidelines/agent-infra/memory-access.md):
    ```bash
    agent-config memory:lookup \
      --types incident-learnings,historical-patterns \
@@ -228,7 +228,7 @@ right line beats five minutes of IDE breakpoints.
 tool/agent loop, HTTP 429, `ECONNREFUSED`, `ENOENT`, timeout/hang, OOM, flaky
 test, works-locally-fails-in-CI, or repeated attempts at a tool that is not
 available — consult the symptom → cause → first-check
-lookup in [`failure-signatures`](../../../docs/guidelines/agent-infra/failure-signatures.md)
+lookup in [`failure-signatures`](../../guidelines/agent-infra/failure-signatures.md)
 to shortcut Phase 2 (Isolate) with the highest-probability first check. Each row
 carries a stable id you can cite, and a discrimination drill that produces its
 documented symptom. It supplements the loop; it does not replace it.

package/dist/agent-src/skills/tailwind-engineer/SKILL.md

@@ -83,9 +83,15 @@ as `blocker: approximation-tolerance` and `blocker: fidelity-default-flip` on
 `road-to-design-intent-conformance`. Until they land, a skill granting that
 autonomy would be re-writing the rule from underneath it.
 
-Structure, controls, icons, grid and breakpoints are never this skill's to
-adjust; those stay 1:1 with the artifact and belong to the rule, not to a
-utility-class decision.
+Structure, controls, grid and breakpoints are never this skill's to adjust;
+those stay 1:1 with the artifact and belong to the rule, not to a
+utility-class decision. **Icons are out of scope here as well, and this skill
+asserts no obligation about them** — the icon system belongs to
+[`icon-consistency`](../../rules/icon-consistency.md). An earlier revision of
+this paragraph claimed icons "stay 1:1 with the artifact" with no citation of
+any kind, while putting them outside its own scope in the same sentence; the
+claim is withdrawn rather than defended, because a clause that reached the tree
+first does not thereby earn an evidentiary bar for its own reversal.
 
 Token authoring (DTCG 3-layer model, CSS-var/Tailwind generation) lives
 in [`design-tokens`](../design-tokens/SKILL.md); its
@@ -113,7 +119,7 @@ manually. Reviewer should read intent in one pass.
 
 The first two repetitions of a **utility-class string** are noise; the third
 is a pattern (the utility-class row of the per-class canon,
-[`abstraction-thresholds`](../../../docs/guidelines/abstraction-thresholds.md)).
+[`abstraction-thresholds`](../../guidelines/abstraction-thresholds.md)).
 Extract via:
 
 | Mechanism | When |
@@ -183,7 +189,7 @@ Risks:          <arbitrary values, !important, dark-mode gaps>
   in files Tailwind scans, not in vendor CSS.
 - **Anti-AI-slop catalog.** The bullets below are the Tailwind-specific
   manifestations of the stack-agnostic patterns in
-  [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)
+  [`docs/guidelines/design-antipatterns.md`](../../guidelines/design-antipatterns.md)
   (C1 gradients, T7 fonts, L1/L2 layout, V1 side-stripe). Pull the catalog
   for the full list; the objective subset (contrast, font-size floor,
   reduced-motion) is validated via `accessibility-auditor`'s checklist —

package/dist/agent-src/skills/throughput-vs-morale-tradeoff/SKILL.md

@@ -28,7 +28,7 @@ Do NOT use this for individual performance issues (route to Q4 `perf-feedback-cr
 
 ## Cognition cluster
 
-- **Mental model — Theory of constraints.** Team throughput has one binding constraint at a time — usually code review queue, single-threaded role, on-call load, or focus-fragmentation. Identifying the constraint with file:line precision is the most leveraged hour an EM spends in a quarter; lifting non-constraint loads produces zero throughput gain. See [`mental-models.md`](../../../docs/contracts/mental-models.md).
+- **Mental model — Theory of constraints.** Team throughput has one binding constraint at a time — usually code review queue, single-threaded role, on-call load, or focus-fragmentation. Identifying the constraint with file:line precision is the most leveraged hour an EM spends in a quarter; lifting non-constraint loads produces zero throughput gain. See [`mental-models.md`](../../docs/contracts/mental-models.md).
 - **Mental model 21 — Second-order thinking.** Throughput borrowed from morale always compounds back. A two-quarter sprint to a deadline costs three-to-four quarters of slower hiring (reputation), slower velocity (post-burnout shape), and senior-IC attrition. Compute the round-trip, not just the deadline.
 - **Mental model 28 — Inversion.** *"What would make this team silently disengage by quarter-end?"* — usually: chronic on-call without recovery, focus-fragmentation > 4 context-switches / day, reorg-shock without re-shape time, leadership-promised-relief that doesn't arrive. Inversion surfaces the 4 canonical morale-collapse causes.
 - **Mental model — Base rates.** A team running at 80% utilization has zero slack for incidents; this is the base rate, not a worst case. A team running at 90% utilization for two quarters has 50%+ attrition base rate. Most EMs over-estimate sustainable utilization by 20 percentage points.

package/dist/agent-src/skills/token-optimizer/SKILL.md

@@ -78,7 +78,7 @@ INTENT
 │
 └── API-bill lever (stable prefix reused across calls · non-interactive
     bulk cohort · model/effort pick against the paid Anthropic bill)
-      → cite [api-cost-levers](../../../docs/guidelines/agent-infra/api-cost-levers.md)
+      → cite [api-cost-levers](../../guidelines/agent-infra/api-cost-levers.md)
         (prompt caching ~0.1x reads · Batch -50% · model tiering · effort)
 ```
 

package/dist/agent-src/skills/typography-system/SKILL.md

@@ -101,7 +101,7 @@ brand already registers fonts, use them and skip the filter.
 ## Delivery — hosting mode (self-hosted by default)
 
 The delivery policy is **owned** by
-[`design-fidelity-mechanics`](../../../docs/guidelines/design-fidelity-mechanics.md)
+[`design-fidelity-mechanics`](../../guidelines/design-fidelity-mechanics.md)
 § Asset & imagery discipline ([`ADR-205`](../../../docs/decisions/ADR-205-webfont-delivery-ownership.md));
 this skill is a consumer and emits the route, never a competing policy. A font
 CDN link transmits the **visitor's IP** to that third party on every page view —
@@ -174,7 +174,7 @@ the shorter line.
 
 ## See also
 
-- [`design-canon.md`](../../../docs/guidelines/design-canon.md) — named-systems + typography-craft (foundry/theory) grounding index; pull to escape the AI-default fonts.
+- [`design-canon.md`](../../guidelines/design-canon.md) — named-systems + typography-craft (foundry/theory) grounding index; pull to escape the AI-default fonts.
 - [`design-tokens`](../design-tokens/SKILL.md) — toolchain that generates CSS
   vars and the Tailwind snippet from `tokens.json`.
 - [`design-intelligence`](../design-intelligence/SKILL.md) — idiom corpus that

package/dist/agent-src/skills/ui-component-architect/SKILL.md

@@ -46,7 +46,7 @@ Do NOT use when:
 
 Extract a **stateful component** only when an element **repeats ~4× or more AND
 carries real props/state** (the stateful-component bar of the per-class canon,
-[`abstraction-thresholds`](../../../docs/guidelines/abstraction-thresholds.md) —
+[`abstraction-thresholds`](../../guidelines/abstraction-thresholds.md) —
 it does not lower the code-level two-repetition bar). One or two repeats, or a
 repeat with no varying props, is not a component — inline it (a props-only
 shell earns extraction at 3+ uses). A long single-file body is **normal**, not a smell;
@@ -69,13 +69,33 @@ still exists in the tree. Absent or empty → fall through to
 Then review existing components in the codebase for the same
 responsibility — extend rather than rebuild when a match is found.
 
-**A new component's workshop is part of its design, on every React lane and not
-only `react-shadcn`.** When the extraction is agreed, the story set comes from
-[`storybook-workshop`](../storybook-workshop/SKILL.md) — one story per concept
-off the state-coverage matrix below, which is what makes the component
-agent-readable and its contrast floor checkable before it reaches a page. That
-skill is stack-agnostic and ships in `engineering-base`, so a plain-`react`
-project receives it exactly as a `react-shadcn` one does.
+**A new component's workshop is part of its design where the project has one —
+size-conditional, never a generic mandate.** The boundary is
+[`component-oriented-and-oop-development`](../../guidelines/component-oriented-and-oop-development.md)
+§ Component workshop: a workshop pays for itself on a real, growing shared
+component library and is not worth the setup for a handful of one-off
+components. Where it applies, the story set comes from
+[`storybook-workshop`](../storybook-workshop/SKILL.md) — one story per concept,
+which is what makes the component agent-readable and its contrast floor
+checkable before it reaches a page. That skill is stack-agnostic and ships in
+`engineering-base`, so a plain-`react` project receives it exactly as a
+`react-shadcn` one does. The state-coverage matrix the story set is derived
+from is React-specific and lives in
+[`react-shadcn-ui`](../react-shadcn-ui/SKILL.md) § Step 3, deliberately not
+duplicated here; a Blade, Vue or Livewire lane derives its story set from that
+lane's own state list instead.
+
+**No order is prescribed among stories, component and page — and that is a
+positive statement, not an omission.** The observed pattern, described rather
+than required: when porting existing UI the first move is inventory, not
+construction (this lifecycle excludes Plan by definition), and stories are
+written concurrent with the component rather than as a phase gate before or
+after it. No primary source states a required order, Storybook's own tutorial
+writes the component before the story, Atomic Design's author calls it "not a
+linear process", and measured evidence comparing build orders is **absent**,
+not merely weak. A claimed order is therefore a preference someone holds, never
+this skill's instruction.
+
 If none exists, write the new component's purpose: *"Renders a
 labelled input with inline error and hint."* If the sentence has an
 "and" joining two unrelated jobs, the component is two components.

package/dist/agent-src/skills/unit-economics-modeling/SKILL.md

@@ -34,7 +34,7 @@ Do NOT use for full-business intrinsic-value modeling, OKR setting, funnel-stage
   customer and one fully-loaded acquisition dollar. Aggregate ratios
   ride on per-unit truth; if the unit is mis-defined (trial vs paid,
   household vs seat), every ratio downstream is decoration. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 1.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 1.
 - **Mental model 8 — Second-order thinking.** A CAC drop driven by
   discounting lifts LTV/CAC on paper while shortening cohort
   retention — the second-order effect lands two quarters later in
@@ -46,7 +46,7 @@ Do NOT use for full-business intrinsic-value modeling, OKR setting, funnel-stage
   **fiscal-period** slot for the close-window the ratios must
   reconcile against (monthly close vs quarterly board pack vs
   annual plan). See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/upstream-contribute/SKILL.md

@@ -222,7 +222,7 @@ If not in the package repo, note that these checks will run in CI after the PR i
 
 If the contribution originates from a proposal under `agents/proposals/`
 (produced by `learning-to-rule-or-skill` via the pipeline in
-[`self-improvement-pipeline`](../../../docs/guidelines/agent-infra/self-improvement-pipeline.md)),
+[`self-improvement-pipeline`](../../guidelines/agent-infra/self-improvement-pipeline.md)),
 run the Stage-4 gate before opening the PR:
 
 ```bash

package/dist/agent-src/skills/validate-feature-fit/SKILL.md

@@ -53,7 +53,7 @@ Verify the request doesn't conflict with:
 - Data flow (does it bypass existing services or repositories?)
 - **Product rules and domain invariants** — pull active rules via the
   shared abstraction (see
-  [`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md)):
+  [`memory-access`](../../guidelines/agent-infra/memory-access.md)):
 
   ```bash
   agent-config memory:lookup \
@@ -66,7 +66,7 @@ Verify the request doesn't conflict with:
   (e.g., "free plan caps at 3 users"); the feature must either respect
   it or explicitly propose to retire it. Cite the matching `id:` in
   the findings. Schema:
-  [`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).
 
 **If contradiction found** → show the existing pattern, explain why it matters.
 

package/dist/agent-src/skills/verify-repair-loop/SKILL.md

@@ -156,7 +156,7 @@ iterating against a stale contract.
 
 State lives in the conversation, optionally mirrored to a re-read working file —
 **never** a daemon or persistent cross-session store (honors
-[`resident-process-governance`](../../../docs/contracts/resident-process-governance.md)).
+[`resident-process-governance`](../../docs/contracts/resident-process-governance.md)).
 
 ## Validation
 
@@ -261,7 +261,7 @@ iter2 fixes A, breaks B, 92% → "PASS"      ✗ regression ignored
   `tests/fixtures/tamper-corpus/` and its polarity proven both ways by
   `--self-test`.
 * [`autonomous-execution`](../../rules/autonomous-execution.md) — the N=3 cap.
-* [`resident-process-governance`](../../../docs/contracts/resident-process-governance.md) — the
+* [`resident-process-governance`](../../docs/contracts/resident-process-governance.md) — the
   runtime-free constraint this loop honors.
 * Optional impact pre-step (when a code-graph is present, ADR-124): run
   `agent-config code-graph affected --since <ref>` to scope which symbols a

package/dist/agent-src/skills/vision-articulation/SKILL.md

@@ -26,7 +26,7 @@ Do NOT use for outward-facing fundraise pitch (route to Wing-3 `fundraising-narr
 
 ## Cognition cluster
 
-- **Mental model 27 — Why now.** Vision without a *why now* is a wishlist. The market shift, technology wave, regulatory change, or demographic inflection that makes the vision *achievable in this window* is the load-bearing claim. See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 27.
+- **Mental model 27 — Why now.** Vision without a *why now* is a wishlist. The market shift, technology wave, regulatory change, or demographic inflection that makes the vision *achievable in this window* is the load-bearing claim. See [`mental-models.md`](../../docs/contracts/mental-models.md) § 27.
 - **Mental model 1 — First principles.** Strip the vision to outcomes for a named cohort, not feature lists or company milestones. *"Be the X for Y"* is shape; *"customer C does outcome O 10× faster"* is substance. See `mental-models.md` § 1.
 - **Mental model 21 — Second-order thinking.** *"If this vision is realised, what does the world look like in 5 years?"* If the answer is just *"we got bigger"*, the vision isn't load-bearing; if the answer is structural change (workflow shift, market re-shape), it is. See `mental-models.md` § 21.
 - **Context-spine — org-stage + product + customer-segment.** Read **org-stage** for vision-horizon (pre-seed = 3-year survival vision; growth = 5–7-year market-shape vision; mature = 10-year). Read **product** for the realistic shipping shape. Read **customer-segment** for the cohort whose outcome anchors the vision.

package/dist/agent-src/skills/voc-extract/SKILL.md

@@ -47,7 +47,7 @@ quantitative funnel diagnosis ([`funnel-analysis`](../funnel-analysis/SKILL.md))
 - **Mental model 15 — Signal vs noise.** A loud single reporter
   swamps quiet recurring patterns; rank by **distinct authors**, not
   comment count. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 15.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 15.
 - **Mental model 14 — Pareto.** Roughly 20% of themes carry 80% of
   the contact volume; cut the long tail explicitly so the team acts
   on the head. See `mental-models.md` § 14.
@@ -57,7 +57,7 @@ quantitative funnel diagnosis ([`funnel-analysis`](../funnel-analysis/SKILL.md))
 - **Product context-spine slot.** Read **product** for segments,
   non-goals, and focal jobs; do not surface themes that fall outside
   the declared scope without a scope-violation flag. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/voice-and-tone-design/SKILL.md

@@ -36,7 +36,7 @@ subject lines or ad creative formats (channel-agnostic skill).
   segment can recognise across surfaces is the voice that survives
   contact with three writers under deadline. A five-attribute voice
   that no one remembers is brand-theatre. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 13.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 13.
 - **Mental model 15 — Signal vs. noise.** Voice is the
   identification signal embedded in copy — without distinctiveness
   it is noise that competes with every peer's noise. Cut to the
@@ -46,7 +46,7 @@ subject lines or ad creative formats (channel-agnostic skill).
   for the proofs the voice must carry (a voice that promises what
   the product cannot back is fiction); read **customer-segment**
   for the listening-register the audience already lives in. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure