@event4u/agent-config 14.22.0 → 15.0.0

package/dist/agent-src/skills/php-coder/SKILL.md

@@ -64,7 +64,7 @@ Trigger keywords in the task or surrounding code:
 - allowlist constants: `private const SUPPORTED_FOO = [Type::A, Type::B]`
 
 → Run the sniff test in
-[`docs/guidelines/php/patterns/strategy.md`](../../../docs/guidelines/php/patterns/strategy.md#sniff-test--when-an-enumstring-discriminator-wants-to-become-a-strategy).
+[`docs/guidelines/php/patterns/strategy.md`](../../guidelines/php/patterns/strategy.md#sniff-test--when-an-enumstring-discriminator-wants-to-become-a-strategy).
 Two "yes" answers → propose Strategy + Registry **before** adding the new
 branch. Three "yes" → it is already overdue and the refactor is the change.
 

package/dist/agent-src/skills/pipeline-strategy/SKILL.md

@@ -37,7 +37,7 @@ skill is strategy, not tooling).
   binding stage at any time; rates upstream of the constraint are
   inventory that never ships, rates downstream cannot exceed the
   constraint. Find the constraint before changing anything else. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 6.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 6.
 - **Mental model 16 — Leading vs. lagging indicators.** Stage-to-stage
   conversion is leading; closed-won is lagging. A coverage call built
   on lagging signals can only confirm the miss after it lands. See
@@ -51,7 +51,7 @@ skill is strategy, not tooling).
   quarter, the **customer-segment** slot for which segments belong in
   pipeline (and which are pre-pipeline education), and the
   **channel-stage** slot for where each segment enters. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/playwright-testing/SKILL.md

@@ -17,7 +17,7 @@ triggers:
 ## When to use
 
 > **Design verification.** When exercising a UI artifact, run the
-> [design-artifact verification checklist](../../../docs/contracts/design-artifact-verification.md#verification-checklist)
+> [design-artifact verification checklist](../../docs/contracts/design-artifact-verification.md#verification-checklist)
 > (open → console/load → viewport → text-fit → assets → interaction) and capture
 > evidence; a design task with browser capability present is not "done" without it.
 
@@ -29,12 +29,12 @@ Use this skill when:
 - Debugging flaky E2E tests
 - Configuring Playwright for CI/CD
 
-**Guideline:** `../../../docs/guidelines/e2e/playwright.md` — full conventions, config templates, CI setup.
+**Guideline:** `../../guidelines/e2e/playwright.md` — full conventions, config templates, CI setup.
 **Mobile:** for native iOS/Android or React Native E2E, do NOT reuse Playwright — see the `mobile-e2e-strategy` skill for framework selection.
 
 ## Procedure: Write Playwright tests
 
-1. **Read the guideline** — `../../../docs/guidelines/e2e/playwright.md` for detailed conventions.
+1. **Read the guideline** — `../../guidelines/e2e/playwright.md` for detailed conventions.
 2. **Check Playwright config** — `playwright.config.ts` for browsers, base URL, timeouts.
 3. **Check existing tests** — match patterns in `tests/e2e/` or `e2e/`.
 4. **Check test utilities** — look for page objects, fixtures, helpers.

package/dist/agent-src/skills/po-discovery/SKILL.md

@@ -81,7 +81,7 @@ not name an implementation**. Use Given / When / Then or a numbered
 list. Reject ACs that hide assumptions ("works correctly", "is fast
 enough") — replace with measurable thresholds or strike them.
 
-**Cross-source discrepancy scan** (per [`cross-source-consistency`](../../rules/cross-source-consistency.md), gated by `consistency.cross_source`): when the raw input includes a screenshot / mockup alongside the story text, check the sources against each other and surface any conflict as a `gap` / open question — never resolve it silently. Watch for: story text contradicting an attached screenshot; the AC contradicting the description; a clearly-needed behavior the input never states (weekend/holiday shift, empty/error state). Batch them into one clarifying question. Taxonomy: [`cross-source-consistency-mechanics`](../../../docs/guidelines/agent-infra/cross-source-consistency-mechanics.md).
+**Cross-source discrepancy scan** (per [`cross-source-consistency`](../../rules/cross-source-consistency.md), gated by `consistency.cross_source`): when the raw input includes a screenshot / mockup alongside the story text, check the sources against each other and surface any conflict as a `gap` / open question — never resolve it silently. Watch for: story text contradicting an attached screenshot; the AC contradicting the description; a clearly-needed behavior the input never states (weekend/holiday shift, empty/error state). Batch them into one clarifying question. Taxonomy: [`cross-source-consistency-mechanics`](../../guidelines/agent-infra/cross-source-consistency-mechanics.md).
 
 ### 5. Surface non-functional gaps
 

package/dist/agent-src/skills/positioning-strategy/SKILL.md

@@ -34,7 +34,7 @@ Do NOT use for peer-versus-peer feature comparison (route to
   the underlying job: who fires what, to make what progress, under
   what pressure. Inherited category labels are the trap; the unit of
   positioning is the job, not the label. 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 30 — Inversion.** For every positioning claim, ask
   *"what would a competitor with a credible alternative argue against
   this?"* A claim that has no opposable counter is either trivially
@@ -43,7 +43,7 @@ Do NOT use for peer-versus-peer feature comparison (route to
   slot for non-goals and the **customer-segment** slot for the ICP
   shape before locking the frame. Positioning that contradicts either
   slot fails its own audit. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

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

@@ -28,7 +28,7 @@ Do NOT use as a substitute for qualified privacy counsel (this skill produces th
 
 ## Cognition cluster
 
-- **Mental model 28 — Inversion.** *"What's the worst-case if this data flow leaks, is subpoenaed, or is mis-consented?"* Inversion sizes the regulatory tail before consent / DPA shape is debated. See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 28.
+- **Mental model 28 — Inversion.** *"What's the worst-case if this data flow leaks, is subpoenaed, or is mis-consented?"* Inversion sizes the regulatory tail before consent / DPA shape is debated. See [`mental-models.md`](../../docs/contracts/mental-models.md) § 28.
 - **Mental model 1 — First principles.** Strip the data flow to: *who* (data subject), *what* (data category), *why* (lawful basis / purpose), *where* (residency / transfer), *how long* (retention), *who else* (sub-processors). Six primitives anchor every regime delta. See `mental-models.md` § 1.
 - **Mental model 21 — Second-order thinking.** Consent design at signup interacts with marketing automation; retention defaults interact with data-subject-rights workflow; sub-processor chains interact with breach-notification timelines. Each privacy choice has downstream regime obligations. See `mental-models.md` § 21.
 - **Context-spine — regulatory-regime + customer-segment + product.** Read **regulatory-regime** (J1) for the applicable floor (GDPR, CCPA/CPRA, HIPAA, PIPEDA, LGPD, sector-specific). Read **customer-segment** for who the data subjects are (B2C-EU = GDPR primary; US-healthcare = HIPAA primary; B2B-EU-of-US-customers = mixed). Read **product** for which features touch sensitive categories.

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

@@ -40,7 +40,7 @@ packs:
    - *Complex / multi-step* → chain-of-thought + systematic framing (template: **CoT** or **ReAct**)
    - *Image AI (Midjourney / SD / DALL·E)* → **Visual Descriptor** or **Reference-Image-Edit**
    - Assign an AI role/expertise; layer context; add logical structure.
-   - Full template catalogue + when-to-pick rubric: [`docs/guidelines/prompt-templates.md`](../../../docs/guidelines/prompt-templates.md).
+   - Full template catalogue + when-to-pick rubric: [`docs/guidelines/prompt-templates.md`](../../guidelines/prompt-templates.md).
 4. **Deliver** — output the optimized prompt + a short "what changed" + (DETAIL only) techniques applied + one pro-tip.
 
 ## Setting awareness
@@ -136,7 +136,7 @@ Format per § Output format. Do **not** execute the optimized prompt yourself un
 - The model tends to **preserve a presupposed canon while sharpening around it** — asked to improve "apply the 7 laws of X", it produces a cleaner prompt that still presupposes seven laws, and the target model then invents them. Turn the presupposition into a DETAIL question or a stated BASIC assumption; never carry it through polished.
 - The model tends to **keep every demand in a scope-stuffed prompt** because each one came from the author — four deliverables in one prompt produce four shallow answers. Name the primary deliverable, and surface the rest as a numbered option rather than silently answering all of them.
 - The model tends to **over-apply de-inflation once it has the concept** — stripping a constraint the author meant, because it read as verbose. Exactly three patterns are strippable (§ 3b); everything else the author wrote is a requirement. Removing a requirement is the worse failure of the two, and it is silent.
-- The model tends to inherit upstream dogma that "only 5 techniques are safe" (few-shot, role, structured-output, constraint-based, chain-of-thought). That claim travels with an external prompt-collection and is **rejected here** — CO-STAR, RISEN, CRISPE, ReAct, and the image-AI templates land in [`docs/guidelines/prompt-templates.md`](../../../docs/guidelines/prompt-templates.md) and are first-class. Pick by request type, not by upstream whitelist.
+- The model tends to inherit upstream dogma that "only 5 techniques are safe" (few-shot, role, structured-output, constraint-based, chain-of-thought). That claim travels with an external prompt-collection and is **rejected here** — CO-STAR, RISEN, CRISPE, ReAct, and the image-AI templates land in [`docs/guidelines/prompt-templates.md`](../../guidelines/prompt-templates.md) and are first-class. Pick by request type, not by upstream whitelist.
 
 ## Do NOT
 
@@ -149,5 +149,5 @@ Format per § Output format. Do **not** execute the optimized prompt yourself un
 ## See also
 
 - [`refine-prompt`](../refine-prompt/SKILL.md) — engine-inbound sibling; same `prompt_optimization` setting controls its mode
-- [`docs/guidelines/prompt-templates.md`](../../../docs/guidelines/prompt-templates.md) — 12-template catalogue cited from Develop step
+- [`docs/guidelines/prompt-templates.md`](../../guidelines/prompt-templates.md) — 12-template catalogue cited from Develop step
 - AI Council session: `agents/runtime/council/responses/prompt-master-mini.json` (2026-05-17) — analysis behind template adoption and the 5-safe-dogma rejection <!-- council-ref-allowed: ADR decision trace -->

package/dist/agent-src/skills/react-shadcn-ui/SKILL.md

@@ -121,7 +121,7 @@ Do NOT use when:
   breaks consistency — variation lives between projects, not between
   components in the same surface.
 - **Anti-AI-slop catalog + linter.** Pull
-  [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)
+  [`docs/guidelines/design-antipatterns.md`](../../guidelines/design-antipatterns.md)
   before the polish step (Visual V1–V8, Layout L1–L10 are the React-component
   slop tells); the objective quality floors (WCAG contrast, focus-visible,
   reduced-motion) are validated via `accessibility-auditor`'s checklist —

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

@@ -51,6 +51,48 @@ radius, spacing, shadow, font-size to a configured token. If the design hands yo
 (`bg-[#3B82F6]`, `mt-[17px]`) are a smell — accept only with a
 one-line comment naming the design source.
 
+**That paragraph is written for greenfield, and artifact-bound work inverts
+it.** When a provided finished design is the spec
+([`design-fidelity`](../../rules/design-fidelity.md)), `#3B82F6` is a decision
+somebody already made and `bg-blue-500` is a guess about it. Three obligations
+follow, and the third is the one this skill used to get wrong:
+
+1. **Do not snap.** Replacing the artifact's value with the nearest configured
+   token is the deviation the rule's Iron Law forbids — *"NEVER SWAP … SPACING,
+   OR COLOUR"* without explicit confirmation. An artifact-derived exact value is
+   not a smell here: it *is* the spec, and the source-naming comment the
+   paragraph above asks for is what records it.
+2. **Translate once, not per call site.** Where the artifact's literal genuinely
+   needs to live in the project's system, add **one** named project token
+   carrying that exact value and use it everywhere — one token the project owns
+   beats N approximations of the same colour. That is a token duty, not a
+   deviation: the value does not change.
+3. **Reconcile as a proposal, never autonomously.** Report each value's
+   distance to the nearest project token on the `Reconciled:` line below, and
+   let the human decide. Writing a *different* project value because the
+   difference looks small is exactly the unconfirmed swap (1) rules out — the
+   mode table at `design-fidelity.md:117-121` grants no visibility exemption,
+   and `structural` grants only the filling of a spec that is genuinely
+   **silent**, which an artifact stating `#3B82F6` is not.
+
+**Why not "just approximate within tolerance", which is the eventual intent:**
+that needs a tolerance to exist. There is none — no `reconcile`, `tolerance`,
+`approximat` or `nearest` in the rule or its guideline — and both the threshold
+and whether approximation is autonomous by default are owner decisions, tracked
+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, 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
 `tokens.ts validate --dir <path>` is the **single token-discipline
@@ -77,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 |
@@ -103,7 +145,11 @@ When reviewing or proposing styles, return:
 
 1. Token map — every colour, spacing, radius, shadow, font-size mapped
    to its configured token; arbitrary values flagged with the design
-   source they cite.
+   source they cite. Artifact-bound work adds a **Reconciled** block here:
+   one line per value, as `<artifact value> → <kept, or the token that
+   carries it exactly> (<distance to the nearest project token>)`. This is
+   the destination "report the distance" means; without it the obligation
+   has nowhere to land and is unobservable in the deliverable.
 2. Class list — ordered (layout → box-model → typography → colour →
    state → responsive); inline-style use justified per element.
 3. Extraction + risk call-out — component / constant / `@apply` / none
@@ -115,6 +161,7 @@ Concrete shape:
 ```
 Element:        <selector or component name>
 Token map:      <colour/spacing/etc → config token>
+Reconciled:     <artifact value → kept or exact-carrying token, + distance>
 Class list:     <ordered classes>
 Inline style:   <only if runtime-computed; else "none">
 Extraction:     <component | constant | @apply | none — reason>
@@ -128,12 +175,21 @@ Risks:          <arbitrary values, !important, dark-mode gaps>
 - `dark:` variants need a token map in both modes; one-sided dark
   styling is half a feature.
 - Arbitrary values (`mt-[17px]`) survive Tailwind upgrades but
-  break the design system; they accumulate silently.
+  break the design system; they accumulate silently. **Artifact-bound is the
+  exception, not a loophole:** a value the provided design specifies is not
+  accumulation, and step 1's three obligations decide it. An arbitrary value
+  nobody can trace to a source is still the smell this bullet is about.
+- **The carrier is CSS or a utility class; the value is the design's.** Static
+  presentation belongs in CSS / tokens / classes — `style=` is for what only
+  the runtime knows (a computed width, a live transform, a measured offset).
+  Porting an artifact's inline `style=` into classes is therefore expected and
+  is not a deviation, **as long as the resolved value comes out identical**.
+  Changing the carrier is free; changing the number is not.
 - `@apply` inside component CSS interacts with PurgeCSS — keep it
   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.