@event4u/agent-config 14.22.0 → 15.0.0

package/dist/agent-src/skills/fe-design/SKILL.md

@@ -246,13 +246,13 @@ When this skill's content is folded into a design brief or review:
 ## Read the authority object — never re-infer it
 
 Read the resolved `ui_authority`
-([contract](../../../docs/contracts/ui-authority.md)) before the loop:
+([contract](../../docs/contracts/ui-authority.md)) before the loop:
 `surface_mode`, `register`, `change_intent`, `reference_maturity`,
 `constraints`. This skill is a **declared consumer** — a second decision table
 beside the object is a drift surface, so do not re-derive any field.
 
 `surface_mode` sets density, hierarchy and expressiveness only, per
-[`design-modes`](../../../docs/guidelines/design-modes.md) § The second axis.
+[`design-modes`](../../guidelines/design-modes.md) § The second axis.
 
 ```
 QUALITY FLOORS DO NOT VARY BY SURFACE MODE.
@@ -274,7 +274,7 @@ provenance belongs to `road-to-frontend-fidelity-calibration` Phases 0 and 2.
 ## Anti-slop discipline
 
 Before proposing a direction, scan the Visual (V1–V8) and Layout (L1–L10)
-sections of [`design-antipatterns`](../../../docs/guidelines/design-antipatterns.md),
+sections of [`design-antipatterns`](../../guidelines/design-antipatterns.md),
 plus Motion (M1–M8) for the interaction layer.
 On a match, choose differently or invoke the entry's own override condition in
 the brief — every entry has one. Two of them, T7 and T8, are additionally

package/dist/agent-src/skills/fe-design/references/design-patterns.md

@@ -38,7 +38,7 @@ React island vs. Vue SFC) is the apply-step's concern, not this skill's.
 - **One stateful component per concern** — don't build mega-components.
 - **Compose with reusable UI components** for shared shells, headers, fields.
 - **Use the project's library primitives first** — never rebuild what the design system already provides (audit findings tell you which).
-- **Extract a props-only UI shell when used 3+ times** — DRY applies to UI too; stateful components carry a higher bar (~4 + real state) — per-class canon: [`abstraction-thresholds`](../../../../docs/guidelines/abstraction-thresholds.md).
+- **Extract a props-only UI shell when used 3+ times** — DRY applies to UI too; stateful components carry a higher bar (~4 + real state) — per-class canon: [`abstraction-thresholds`](../../../guidelines/abstraction-thresholds.md).
 - **Component workshop when the project is large enough** — for a real, growing shared-component library, isolate and document each reusable component in a component workshop so it stays discoverable and reused, not re-invented; skip it for a small surface of one-offs. Tool-specific setup is a carve-out (Storybook et al.) — see the implementation skill (e.g. [`react-shadcn-ui`](../react-shadcn-ui/SKILL.md) § Component workshop), never a generic mandate.
 
 ## Form Design

package/dist/agent-src/skills/fe-design/references/design-read-and-memory.md

@@ -22,7 +22,7 @@ suggest adding to PRODUCT.md: [pattern description]."*
 ## Register — brand vs product
 
 Before applying heuristics, determine the register (see
-[`docs/guidelines/design-modes.md`](../../../../docs/guidelines/design-modes.md)):
+[`docs/guidelines/design-modes.md`](../../../guidelines/design-modes.md)):
 brand mode (impression-first) vs product mode (task-first). Form-heavy, table-heavy,
 and dashboard surfaces are almost always product mode — favour the standard
 patterns in this skill (Form Design, Table Design) over expressive variance.
@@ -42,7 +42,7 @@ Reading this as: <page-kind> for <audience>, <vibe> language, leaning <design-sy
 
 **Anti-Default Discipline:** Before committing to any layout or component
 pattern, cross-check your first impulse against
-[`design-antipatterns.md`](../../../../docs/guidelines/design-antipatterns.md) —
+[`design-antipatterns.md`](../../../guidelines/design-antipatterns.md) —
 the L1/L2 "AI landing page" layout (centered hero + 3-column grid + CTA), the
 V1 side-stripe card, the T7 default-font pick, and V2 decorative glassmorphism.
 If a tell was the first impulse, choose a different approach or explicitly
@@ -56,7 +56,7 @@ burden does not apply to them: build them as given. The carve-out is scoped to
 decisions the artifact actually covers — anything it leaves open (a state it
 never shows, a surface it never had) is your first impulse again and gets the
 full scan. See
-[`design-fidelity-mechanics`](../../../../docs/guidelines/design-fidelity-mechanics.md)
+[`design-fidelity-mechanics`](../../../guidelines/design-fidelity-mechanics.md)
 § Provided-artifact precedence.
 
 ## Aesthetic direction

package/dist/agent-src/skills/fe-design/references/source-led-port.md

@@ -1,7 +1,7 @@
 # Source-led port — adopt the mechanics, do not re-derive them
 
 Pulled when `ui_authority.reference_maturity` is `runnable-artifact`. Contract:
-[`ui-authority`](../../../../../docs/contracts/ui-authority.md).
+[`ui-authority`](../../../docs/contracts/ui-authority.md).
 
 When `reference_maturity` is `runnable-artifact`, the artifact's own markup, CSS
 and JS is the data basis and adapting it is the DEFAULT. A from-scratch

package/dist/agent-src/skills/feature-planning/SKILL.md

@@ -28,7 +28,7 @@ Do NOT use when:
 
 ## Procedure: Plan a feature
 
-1. **Gather requirements** — What problem does this solve? Who benefits? What's the expected outcome? Run a **cross-source discrepancy scan** (per [`cross-source-consistency`](../../rules/cross-source-consistency.md), gated by `consistency.cross_source`): where the source ticket carries text + an attachment/mockup, or leaves a clearly-needed behavior unstated (weekend/holiday shift, empty/error state, timezone), surface the conflict/gap as an *Open question* before drafting phases — an inferred behavior is a scope expansion to confirm, not to bake in. See [`cross-source-consistency-mechanics`](../../../docs/guidelines/agent-infra/cross-source-consistency-mechanics.md).
+1. **Gather requirements** — What problem does this solve? Who benefits? What's the expected outcome? Run a **cross-source discrepancy scan** (per [`cross-source-consistency`](../../rules/cross-source-consistency.md), gated by `consistency.cross_source`): where the source ticket carries text + an attachment/mockup, or leaves a clearly-needed behavior unstated (weekend/holiday shift, empty/error state, timezone), surface the conflict/gap as an *Open question* before drafting phases — an inferred behavior is a scope expansion to confirm, not to bake in. See [`cross-source-consistency-mechanics`](../../guidelines/agent-infra/cross-source-consistency-mechanics.md).
 2. **Analyze scope** — Which modules, routes, models, services are affected?
 3. **Write the plan** — Create a feature plan document (see template below).
 4. **Verify** — Confirm all affected areas are identified, no missing dependencies.

package/dist/agent-src/skills/flux/SKILL.md

@@ -126,7 +126,7 @@ When `DESIGN.md` declares `## Taste Dials`, honour them: Variance → layout-fam
 ## Anti-slop
 
 Flux primitives carry sane defaults, but composition still drifts into slop —
-pull [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)
+pull [`docs/guidelines/design-antipatterns.md`](../../guidelines/design-antipatterns.md)
 and check Layout (L1/L2 hero-metric + identical-card grids) and Color
 (C1 gradient defaults) before shipping. Tailwind-level bans:
 [`tailwind-engineer`](../tailwind-engineer/SKILL.md).

package/dist/agent-src/skills/forecast-accuracy/SKILL.md

@@ -38,7 +38,7 @@ via the `forecast-construction-shape` interface).
   is lagging; per-stage conversion and MEDDIC-slot completeness
   are leading. A forecast built on lagging signals can only confirm
   the result after it lands. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 16.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 16.
 - **Mental model 29 — Premortem.** Before locking the call, write
   the post-quarter retro as if commit missed by 20 %. The premortem
   surfaces which categorisations are riding on weak evidence; demote
@@ -54,7 +54,7 @@ via the `forecast-construction-shape` interface).
   **customer-segment** slot for segment-historical close rates —
   pricing-power and cycle-length differ by segment and the forecast
   must too. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/forecasting/SKILL.md

@@ -32,7 +32,7 @@ Do NOT use to qualify a single deal (route to `deal-qualification-meddic`), cons
 - **Mental model 9 — Hypothesis-driven thinking.** Each forecast is
   a falsifiable claim about a window. If the call cannot be falsified
   inside the window, the call is a narrative, not a forecast. See
-  [`mental-models.md`](../../../docs/contracts/mental-models.md) § 9.
+  [`mental-models.md`](../../docs/contracts/mental-models.md) § 9.
 - **Mental model 29 — Premortem.** Before locking the call, write the
   post-window retro as if commit missed by 20 %. The premortem
   surfaces which construction inputs were riding on weak evidence;
@@ -47,7 +47,7 @@ Do NOT use to qualify a single deal (route to `deal-qualification-meddic`), cons
   reconcile against (monthly close vs quarterly board pack vs annual
   plan vs multi-year plan); the **customer-segment** slot for
   segment-historical close rates. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/fundraising-narrative/SKILL.md

@@ -35,7 +35,7 @@ are siblings, not the same artefact).
   the load-bearing claim and the one most often borrowed. Build
   it from the segment-shift up — what changed in the world, the
   customer, the technology — not from a deck template. 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 9 — Hypothesis-driven development.** A pitch is
   a falsifiable hypothesis: *if X is true, our round closes.*
   Name the X. Investors who disagree with the hypothesis are not
@@ -55,7 +55,7 @@ are siblings, not the same artefact).
   for the proofs the traction story can actually back; read
   **customer-segment** for the TAM/SAM argument that survives a
   bottom-up scrutiny. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/funnel-analysis/SKILL.md

@@ -32,7 +32,7 @@ Do NOT use for ranking features, valuation, or OKR decomposition (see Related Sk
   lagging; activation is leading; signup is upstream of both. A
   funnel decision built on the lagging stage can only confirm the
   miss; the leading stage names the binding fix. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 16.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 16.
 - **Mental model 13 — Occam's razor.** When a stage drops, the
   simpler explanation usually wins: *"acquisition mix shifted"*
   beats *"users no longer understand the product."* Pick the simpler
@@ -47,7 +47,7 @@ Do NOT use for ranking features, valuation, or OKR decomposition (see Related Sk
   **customer-segment** slot for which segments' switch-events the
   funnel is built for, and the **funnel-stage** slot for the
   position of each stage relative to the buying journey. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/git-workflow/references/push-closes-its-loop.md

@@ -68,6 +68,15 @@ returned 0, the turn closed, and the red arrived where the user found it.
   ending the turn silently on one is what the reminder exists to stop. Whether
   the reminder changes behavior is unmeasured — it ships as a carrier, not as a
   claim.
+- **`ci_settle` will not answer for a head that stopped mattering.** Since
+  2026-09-08 it reads the PR's `state` and compares its recorded head against
+  `git ls-remote` — before the wait and again at verdict time — and exits 2 with
+  a reason when the PR is merged, closed, or record-behind-branch. A green names
+  the head it is about. The measured reason: a merged PR's rollup kept answering
+  with its merge-time checks, so the tool reported `SETTLED GREEN — 40 check(s)`
+  for a commit that had zero check runs. The check does not apply to a fork PR
+  whose ref is not under this `origin`, and the line says so instead of claiming
+  it passed.
 - **Neither reaches a host without the slot.** `agent-config hooks:status`
   answers which slots are bound where you actually are; `post_tool_use` is
   unbound on windsurf and copilot, and there the settle obligation is

package/dist/agent-src/skills/gtm-launch/SKILL.md

@@ -36,7 +36,7 @@ post-launch retention loops (route to `retention-loops`).
   expectations after public launch costs more than re-shipping the
   product. Alpha and beta are reversible; treat them as the
   decision-quality buffer. See
-  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 10.
+  [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 10.
 - **Mental model 29 — Premortem.** Before the wave plan locks, write
   the post-mortem of the launch as if it failed. The premortem
   surfaces the gates that need to hold; the wave plan is the inverse
@@ -50,7 +50,7 @@ post-launch retention loops (route to `retention-loops`).
   **customer-segment** slot for who hears the launch on which wave,
   and the **channel-stage** slot for where each wave's audience lives
   in the awareness → decision arc. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/hiring-loop-design/SKILL.md

@@ -28,7 +28,7 @@ Do NOT use this for non-engineering hiring as the primary surface (sales / GTM h
 
 ## Cognition cluster
 
-- **Mental model 1 — First principles.** Strip hiring to: *what signal does each stage produce that no other stage can produce?* Stages that duplicate signal waste candidate-time and interviewer-time. The strongest loops have one stage per signal, not five stages probing the same thing. See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 1.
+- **Mental model 1 — First principles.** Strip hiring to: *what signal does each stage produce that no other stage can produce?* Stages that duplicate signal waste candidate-time and interviewer-time. The strongest loops have one stage per signal, not five stages probing the same thing. See [`mental-models.md`](../../docs/contracts/mental-models.md) § 1.
 - **Mental model 28 — Inversion.** *"What would make a great hire withdraw from this loop?"* — usually: 7+ stages, take-home > 6 hours, no role-context conversation, long calendar gaps, no senior-IC time, no offer-narrative. Inversion surfaces the canonical withdrawal causes; great candidates have options and use them.
 - **Mental model 21 — Second-order thinking.** A loose bar at L4 produces a chain: weaker L4 → harder L5 calibration → erodes ladder credibility → ICs leave. A single accept-the-no-vote ripples for 2+ years. The cost of a wrong hire dwarfs the cost of a missed hire; bar discipline is a multi-year compounding decision.
 - **Mental model — Base rates.** Most signals in interviews are noise; the most-confident signal-claim is usually the most-overfit to one observation. Calibrate against the base rate: *"out of 10 candidates who passed this stage with this signal, how many succeeded at 12 months?"* If unknown, the stage is unfalsifiable.

package/dist/agent-src/skills/html-deck/SKILL.md

@@ -29,7 +29,7 @@ letterbox to any viewport. A deck is fixed-canvas media (default 1920×1080,
 
 > **Cross-surface handoff.** A deck often consumes upstream analysis
 > (spreadsheet → deck, research → deck). Read the handoff envelope from
-> [`surface-agent-contracts`](../../../docs/contracts/surface-agent-contracts.md#cross-surface-handoff-envelope):
+> [`surface-agent-contracts`](../../docs/contracts/surface-agent-contracts.md#cross-surface-handoff-envelope):
 > trust `verification_already_done` (don't recompute the source's numbers),
 > carry the asset list, and keep source restrictions intact.
 
@@ -44,7 +44,7 @@ options of one screen → [`design-variations`](../design-variations/SKILL.md).
 ## Deck fidelity floor
 
 The deck surface's floor (per
-[`surface-agent-contracts`](../../../docs/contracts/surface-agent-contracts.md)):
+[`surface-agent-contracts`](../../docs/contracts/surface-agent-contracts.md)):
 
 - **Outline before slides.** Draft the slide outline (title + one-line intent
   per slide) before building any slide; when audience or tone is ambiguous, ask
@@ -58,7 +58,7 @@ The deck surface's floor (per
   brand evidence ([`design-fidelity`](../../rules/design-fidelity.md) § Asset &
   imagery discipline).
 - **Export verification.** Verify the deck exports/renders
-  ([`design-artifact-verification`](../../../docs/contracts/design-artifact-verification.md));
+  ([`design-artifact-verification`](../../docs/contracts/design-artifact-verification.md));
   on a host without export capability, say what could not be verified rather
   than claiming a clean export.
 
@@ -98,7 +98,7 @@ The deck surface's floor (per
    per-slide `<aside hidden>`, never printed.
 6. **Quality gate.** Run `lint_design_slop` over the file; honor the
    outward-artifact hygiene floor (Q13 in
-   [`design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md))
+   [`design-antipatterns.md`](../../guidelines/design-antipatterns.md))
    — no workspace paths, skill/tool names, or generator traces in markup or
    comments; final pass → [`design-review`](../design-review/SKILL.md).
    Verify scaling + navigation + persistence once in a browser before
@@ -150,4 +150,4 @@ The deck surface's floor (per
 - [`design-intelligence`](../design-intelligence/SKILL.md) — direction/palette/type grounding.
 - [`design-tokens`](../design-tokens/SKILL.md) / [`brand-to-tokens`](../brand-to-tokens/SKILL.md) — token precedence and emission.
 - [`design-review`](../design-review/SKILL.md) — final review gate.
-- [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md) — catalog, CP5, Q13.
+- [`docs/guidelines/design-antipatterns.md`](../../guidelines/design-antipatterns.md) — catalog, CP5, Q13.

package/dist/agent-src/skills/humanizer/SKILL.md

@@ -26,7 +26,7 @@ install:
 - A drafted deliverable (post, article, README section on request, release
   note) reads AI-generated and should read human-written.
 - The write engine reaches step 4b (humanize audit) —
-  [`write-engine § 4b`](../../../docs/contracts/write-engine.md).
+  [`write-engine § 4b`](../../docs/contracts/write-engine.md).
 - The user pastes text and asks to remove AI-isms, de-slop, or "make it
   sound less like ChatGPT".
 

package/dist/agent-src/skills/humanizer/data/patterns.md

@@ -161,7 +161,7 @@ Not reliable indicators on their own — leave these alone:
 - **Mixed registers.** Often a person, not a bot.
 - **Unsourced claims.** Most human web writing is unsourced.
 - **Quoted text, titles, proper names, and discussed-not-used phrases.**
-  Never rewrite secondhand text ([`content-quoting-floor`](../../../src/rules/content-quoting-floor.md)).
+  Never rewrite secondhand text ([`content-quoting-floor`](../../../rules/content-quoting-floor.md)).
 
 Decide on **clusters**: two or more distinct pattern groups co-occurring.
 Below that, say "no reliable tells found" and stop.

package/dist/agent-src/skills/iconography/SKILL.md

@@ -89,7 +89,7 @@ rung 3 and is exactly the scaffold inheritance
 
 Before resolving any new icon, honour the project's existing icon system — the
 Inspect stage of the
-[design-artifact lifecycle](../../../docs/contracts/design-artifact-lifecycle.md).
+[design-artifact lifecycle](../../docs/contracts/design-artifact-lifecycle.md).
 
 - **Inspect first.** Detect the icon set already in use (imports, existing
   `set:name` usages, brand assets) before picking one. A new icon matches the
@@ -140,9 +140,9 @@ Inspect stage of the
 
 ## See also
 
-- [`design-canon.md`](../../../docs/guidelines/design-canon.md) § Icon systems — prefer a named system's icon set (Material Symbols / SF Symbols / Fluent / Carbon) when that system is in play.
+- [`design-canon.md`](../../guidelines/design-canon.md) § Icon systems — prefer a named system's icon set (Material Symbols / SF Symbols / Fluent / Carbon) when that system is in play.
 - [`design-tokens`](../design-tokens/SKILL.md) — token system the icon color/size variables should reference.
 - [`typography-system`](../typography-system/SKILL.md) — sibling visual-consistency skill.
 - [`fe-design`](../fe-design/SKILL.md) — broader frontend design discipline.
 - [`icon-consistency`](../../rules/icon-consistency.md) — enforced rule for set discipline across the project.
-- [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md) — icon-relevant slop tells: V5 (hand-drawn SVG mixed with crisp icon-system icons) and T3 (small rounded-square icon tile above every feature heading — the universal AI feature-card template).
+- [`docs/guidelines/design-antipatterns.md`](../../guidelines/design-antipatterns.md) — icon-relevant slop tells: V5 (hand-drawn SVG mixed with crisp icon-system icons) and T3 (small rounded-square icon tile above every feature heading — the universal AI feature-card template).

package/dist/agent-src/skills/judge-synthesis/SKILL.md

@@ -75,7 +75,7 @@ reproduces the pre-filter defect one layer up — the finding was found, the
 reviewer reported it, and the aggregator withheld it. Filtering is the
 consumer's pass, after the ledger is whole. Output shape, the separate
 `Confidence` field, and the preserve-an-unverified-S0 rule are specified once in
-[`adversarial-review-protocol`](../../../docs/contracts/adversarial-review-protocol.md)
+[`adversarial-review-protocol`](../../docs/contracts/adversarial-review-protocol.md)
 § 3.
 
 ### 2. Find consensus (highest confidence)

package/dist/agent-src/skills/laravel-api-endpoint/SKILL.md

@@ -39,8 +39,8 @@ Do NOT use when:
 
 ## What to generate
 
-1. **Controller** — Single Action (invokable). Read `agents/reference/docs/controller.md` and `../../../docs/guidelines/php/controllers.md`.
-2. **FormRequest** — Validation rules, `authorize()` via policies. Read `../../../docs/guidelines/php/validations.md`.
+1. **Controller** — Single Action (invokable). Read `agents/reference/docs/controller.md` and `../../guidelines/php/controllers.md`.
+2. **FormRequest** — Validation rules, `authorize()` via policies. Read `../../guidelines/php/validations.md`.
 3. **Resource** — JSON response transformation. Read `agents/reference/docs/api-resources.md`.
 4. **Route** — Add to the correct versioned route file.
 5. **Policy** — If authorization is needed.

package/dist/agent-src/skills/launch-readiness/SKILL.md

@@ -33,7 +33,7 @@ This skill produces the **decision** to ship and the rollback contract.
 - **Mental model 10 — Reversible vs irreversible.** Map every step
   of the rollout to a reversibility class; the rollback criteria
   must name the irreversible steps and the abort threshold for each.
-  See [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 10.
+  See [`docs/contracts/mental-models.md`](../../docs/contracts/mental-models.md) § 10.
 - **Mental model 29 — Pre-mortems.** Imagine the rollout failed in
   six hours; what failed first? The pre-mortem becomes the rollback
   criteria, not a separate document. See `mental-models.md` § 29.
@@ -43,7 +43,7 @@ This skill produces the **decision** to ship and the rollback contract.
 - **Team + product context-spine slots.** Read **team** for the
   on-call rotation and ops handoff path; read **product** for the
   segment / cohort exposure of the rollout. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 
@@ -71,7 +71,7 @@ hand-wave.
 ### 2b. Epistemics block — the diagnostic report (contract-backed)
 
 For a consumer-facing diagnostic (not just the merge decision), emit a
-report per [`docs/contracts/prelaunch-diagnostics.md`](../../../docs/contracts/prelaunch-diagnostics.md)
+report per [`docs/contracts/prelaunch-diagnostics.md`](../../docs/contracts/prelaunch-diagnostics.md)
 (schema: `prelaunch-report.schema.json`). Rules:
 
 - **Coverage backbone** — diagnose exactly the fixed area vocabulary

package/dist/agent-src/skills/learning-to-rule-or-skill/SKILL.md

@@ -30,7 +30,7 @@ Use this skill when:
 * Deciding whether a learning belongs in a rule or a skill
 * After completing a task — reflecting on what worked or caused friction
 * Mining the audit log (`agents/runtime/state/audit/<YYYY-MM>.jsonl`,
-  [`audit-log-v1`](../../../docs/contracts/audit-log-v1.md)) surfaced
+  [`audit-log-v1`](../../docs/contracts/audit-log-v1.md)) surfaced
   a repeated phase pattern via
   [`extract_audit_patterns.ts`](../../../scripts/extract_audit_patterns.ts)
   — the pattern's `count` ≥ 2 already satisfies the repetition gate
@@ -223,7 +223,7 @@ The output of this skill is a **curated proposal** under
 `.augment/templates/agents/proposal.example.md` (shipped by the
 package). This is the input to the five-stage pipeline
 (capture → classify → propose → gate → upstream); see
-[`self-improvement-pipeline`](../../../docs/guidelines/agent-infra/self-improvement-pipeline.md).
+[`self-improvement-pipeline`](../../guidelines/agent-infra/self-improvement-pipeline.md).
 
 Mandatory fields the draft MUST fill:
 
@@ -235,7 +235,7 @@ Mandatory fields the draft MUST fill:
   file this proposal was captured from
 * `evidence` — **at least two independent** references (PR, issue,
   incident, review-comment, test-failure, **or audit-log line ids**
-  per [`audit-log-v1`](../../../docs/contracts/audit-log-v1.md));
+  per [`audit-log-v1`](../../docs/contracts/audit-log-v1.md));
   entries that all resolve to the same PR or the same audit-log
   `run_id` are rejected by the gate (independence floor)
 * `Proposed artefact` (§4) — the full draft body, no `TODO` / `TBD`
@@ -350,7 +350,7 @@ the gap is documented in its skill body.
 When the input is a pattern surfaced by
 [`extract_audit_patterns.ts`](../../../scripts/extract_audit_patterns.ts)
 mining `agents/runtime/state/audit/<YYYY-MM>.jsonl`
-([`audit-log-v1`](../../../docs/contracts/audit-log-v1.md)):
+([`audit-log-v1`](../../docs/contracts/audit-log-v1.md)):
 
 1. Treat the script's pattern record as the **State the learning**
    step input (§1) — `pattern.summary` is the one-sentence
@@ -381,8 +381,8 @@ step):
 2. **Ground the draft in the original session logs, never the
    consolidated summary alone.** The candidate entry's `Sessions:`
    list names the chat-history session ids the topic recurred in —
-   pull those via [`/chat-history import`](../../../commands/chat-history/import.md)
-   (select by id) or the host's native transcript view before
+   read those from the host's native transcript view, or reconstruct
+   them manually from the retained continuity records, before
    drafting. A skill written purely from the recurrence-counter
    summary tends to be plausible but wrong; the original transcripts
    carry the detail the summary dropped.

package/dist/agent-src/skills/livewire/SKILL.md

@@ -134,7 +134,7 @@ current state on the next polish round.
 ## Anti-slop
 
 When a Livewire component renders UI, pull
-[`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)
+[`docs/guidelines/design-antipatterns.md`](../../guidelines/design-antipatterns.md)
 for the Visual / Layout / Motion checks (loading states that animate layout
 properties — M2 — are a common Livewire `wire:loading` pitfall). Stack styling
 bans: [`tailwind-engineer`](../tailwind-engineer/SKILL.md).

package/dist/agent-src/skills/market-entry-analysis/SKILL.md

@@ -26,7 +26,7 @@ Do NOT use for build-vs-buy decisions on capability gaps (route to `build-buy-pa
 
 ## Cognition cluster
 
-- **Mental model 23 — Beachhead.** Pick a single segment / geo / vertical where the constraints favour winning, then expand from a position of strength. Trying to enter "the whole market" with no beachhead is the canonical failure pattern. See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 23.
+- **Mental model 23 — Beachhead.** Pick a single segment / geo / vertical where the constraints favour winning, then expand from a position of strength. Trying to enter "the whole market" with no beachhead is the canonical failure pattern. See [`mental-models.md`](../../docs/contracts/mental-models.md) § 23.
 - **Mental model 21 — Second-order thinking.** Entry costs (sales motion, regulatory compliance, segment-specific support) compound across markets. Reading entry as *"just open the door"* misses the second-order shape of multi-market operations. See `mental-models.md` § 21.
 - **Mental model 16 — Leading vs lagging.** Revenue from new market is lagging; **segment-specific pipeline coverage** + **win rates against incumbents in target segment** are leading. Reading only lagging signals = entering markets that already won't work. See `mental-models.md` § 16.
 - **Context-spine — customer-segment + regulatory-regime + product.** Read **customer-segment** for which buyer cohort the entry targets; **regulatory-regime** for the compliance delta (often the load-bearing cost in geo expansion); **product** for what's GA-shippable in the target market without re-platforming.

package/dist/agent-src/skills/mcp-builder/SKILL.md

@@ -118,4 +118,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/memory-consolidation/SKILL.md

@@ -32,7 +32,7 @@ user-scoped channel (§ Global user-scoped channel, below) — never into
 - **Mental model 5 — Signal vs. noise.** A consolidation pass that
   promotes 30 entries from a 50-message session is noise; the Pareto
   cut is roughly 3–5 promote-worthy signals per cycle. 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 12 — Defense in depth.** Date-discipline, tag
   intersection, and per-invocation transcript-access confirmation are
   three independent guards; any one alone fails open. See § 12.
@@ -55,7 +55,7 @@ not advance until the gate is green.
    once here — CONSOLIDATE step 2 needs the answer to know whether
    project-scoped facts land in `agents/memory/intake/` or route through
    the global buffer instead (§ Project attribution channel, below).
-3. Review the **repo** slot of the [context-spine](../../../docs/contracts/context-spine.md)
+3. Review the **repo** slot of the [context-spine](../../docs/contracts/context-spine.md)
    for project boundaries (modules, owners, sensitive paths). If empty,
    note the gap in the consolidation report; do not invent.
 4. Resolve the `TranscriptAdapter` for the current host (see Adapter
@@ -119,7 +119,7 @@ Read it before touching either path — the guards are restated there, not linke
 
    A fact may carry **two** tags; the promoter resolves via tag
    intersection, not by file extension. See
-   [`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md)
+   [`memory-access`](../../guidelines/agent-infra/memory-access.md)
    for the file-backed retrieval contract over the curated YAML.
 
 2. **Managed project only** (§ Project attribution channel, above, for the

package/dist/agent-src/skills/messaging-architecture/SKILL.md

@@ -36,7 +36,7 @@ launch sequencing (route to `gtm-launch`).
   segment's noise floor, not just be true. Estimate the noise before
   drafting; without it, every line looks distinctive in the doc and
   forgettable in market. 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 30 — Inversion.** Ask *"what is the strongest
   message a credible alternative would land against us?"* The answer
   exposes the proofs the message stack must carry, not the words.
@@ -45,7 +45,7 @@ launch sequencing (route to `gtm-launch`).
   slot for the proofs the team can actually back; read the
   **customer-segment** slot for the buyer's listening posture.
   Architecture that exceeds the proofs available is fiction. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/monorepo-workspace/SKILL.md

@@ -172,4 +172,4 @@ When the runner was absent, the last line reads
 - [`standards-from-config`](../standards-from-config/SKILL.md) — the Class-A pointer+digest shape this follows.
 - [`workspace-link`](../workspace-link/SKILL.md) — when a cross-workspace import will not resolve.
 - [`blast-radius-analyzer`](../blast-radius-analyzer/SKILL.md) — § Monorepo consumes this graph.
-- [`monorepo-antipatterns`](../../../docs/guidelines/monorepo-antipatterns.md) — diff-detectable task-graph mistakes.
+- [`monorepo-antipatterns`](../../guidelines/monorepo-antipatterns.md) — diff-detectable task-graph mistakes.

package/dist/agent-src/skills/onboarding-design/SKILL.md

@@ -37,7 +37,7 @@ to `funnel-analysis`).
   reshapes retention more than a change in the welcome email. Pick
   the leverage point — milestone definition 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 16 — Leading vs. lagging indicators.**
   Time-to-first-value and milestone-completion are leading; D30
   retention is lagging. Onboarding decisions built on lagging
@@ -54,7 +54,7 @@ to `funnel-analysis`).
   configure unattended, the **customer-segment** slot for the
   segment's job and switch-event, and the **funnel-stage** slot for
   where activation sits relative to signup and paid. See
-  [`context-spine`](../../../docs/contracts/context-spine.md).
+  [`context-spine`](../../docs/contracts/context-spine.md).
 
 ## Procedure
 

package/dist/agent-src/skills/onboarding-program/SKILL.md

@@ -28,7 +28,7 @@ Do NOT use as a customer-onboarding surface (route to Wing-3 [`onboarding-design
 
 ## Cognition cluster
 
-- **Mental model 1 — First principles.** Strip onboarding to: *what does this person need to know, do, and decide alone before being net-positive?* Most onboarding programs over-index on what's easy to teach (history, slides) and under-index on what's hard (decision rights, who-knows-what, codebase / domain context). See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 1.
+- **Mental model 1 — First principles.** Strip onboarding to: *what does this person need to know, do, and decide alone before being net-positive?* Most onboarding programs over-index on what's easy to teach (history, slides) and under-index on what's hard (decision rights, who-knows-what, codebase / domain context). See [`mental-models.md`](../../docs/contracts/mental-models.md) § 1.
 - **Mental model 21 — Second-order thinking.** Onboarding is paid for in mentor time. A 4-hour-per-week mentor commitment from a senior person costs more than people realise; mentor capacity is the binding constraint on hiring velocity. Read mentor cost as part of the program, not a free input.
 - **Mental model 28 — Inversion.** *"What would make this hire fail in their first 90 days?"* Inversion surfaces the load-bearing risks (unclear scope, no early win, missing tools, no peer relationship). Most onboarding failures trace to one of these four, not to skill gaps.
 - **Mental model 26 — Optionality.** A heavy template onboarding preserves *consistency* optionality but forecloses *role-specific* optionality. A pure free-form onboarding preserves customization but forecloses scalability. Pick the trade explicitly per role family.

package/dist/agent-src/skills/one-on-one-cadence/SKILL.md

@@ -28,7 +28,7 @@ Do NOT use this for non-engineering teams as the primary lens (Q4 `perf-feedback
 
 ## Cognition cluster
 
-- **Mental model 1 — First principles.** Strip the 1:1 to: *what conversation can only happen between this manager and this report, that wouldn't happen anywhere else?* If the answer is "status that fits in standup", the 1:1 is mis-shaped. See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 1.
+- **Mental model 1 — First principles.** Strip the 1:1 to: *what conversation can only happen between this manager and this report, that wouldn't happen anywhere else?* If the answer is "status that fits in standup", the 1:1 is mis-shaped. See [`mental-models.md`](../../docs/contracts/mental-models.md) § 1.
 - **Mental model 21 — Second-order thinking.** A cancelled 1:1 signals more than a missed conversation. Two consecutive cancellations from the manager side recalibrate the report's read of priority for months. Cancellation has compounding cost; protect the slot.
 - **Mental model 28 — Inversion.** *"What 1:1 shape would make this report stop bringing up real problems?"* — usually: pure status-update format, manager-talks-most, no growth dimension, recurring cancellation, public location. Inversion surfaces the 5 canonical failure modes.
 - **Mental model — Theory of constraints.** In a manager's week, 1:1 time is the binding constraint on people-leverage. Reducing per-1:1 time below 30 minutes for direct reports usually starves the channel; protecting 30–45 minutes weekly is the canonical default.

package/dist/agent-src/skills/org-design/SKILL.md

@@ -28,7 +28,7 @@ Do NOT use as a hiring-plan substitute (route to forthcoming hiring-loop / comp
 
 ## Cognition cluster
 
-- **Mental model — Theory of constraints.** Org bottlenecks live in one or two places at a time; reorging everywhere else is theatre. Find the constraint (decision queue, dependency hub, single-threaded role), reshape around it, leave the rest. See [`mental-models.md`](../../../docs/contracts/mental-models.md).
+- **Mental model — Theory of constraints.** Org bottlenecks live in one or two places at a time; reorging everywhere else is theatre. Find the constraint (decision queue, dependency hub, single-threaded role), reshape around it, leave the rest. See [`mental-models.md`](../../docs/contracts/mental-models.md).
 - **Mental model — Conway's law.** Systems mirror the communication structure that shipped them. If two services must integrate cleanly, the two teams must communicate cleanly. Org boundary = future architecture boundary. Use the inverse: pick the architecture you want, then draw the org to match.
 - **Mental model 28 — Inversion.** *"What problem does the proposed structure prevent us from solving?"* Every structure trades one class of problem for another. The honest question is which trade is acceptable, not which structure is best.
 - **Mental model 26 — Optionality.** Reorgs cost 3–6 months of throughput; the reorg is worth it only if the new shape preserves more optionality than the old shape forecloses. Reorging for short-term symptoms usually destroys optionality.

package/dist/agent-src/skills/overbuild-review-lens/SKILL.md

@@ -23,7 +23,7 @@ packs:
 - A diff adds a helper, a wrapper, a config layer, an abstraction, or a
   dependency.
 - A rewrite, v2, or large refactor landed — the peak over-build context
-  (see [`minimal-safe-diff-mechanics`](../../../docs/guidelines/agent-infra/minimal-safe-diff-mechanics.md)
+  (see [`minimal-safe-diff-mechanics`](../../guidelines/agent-infra/minimal-safe-diff-mechanics.md)
   § The sanctioned-rewrite trap).
 - A reviewer asks "is all of this needed?", "could the platform do
   this?", or "why is this so clever?".
@@ -70,7 +70,7 @@ demands is not, however large.
 
 For every new unit (function, class, module, config key, dependency),
 find the highest rung that would have carried it — see
-[`agent-interaction-and-decision-quality`](../../../docs/guidelines/agent-infra/agent-interaction-and-decision-quality.md)
+[`agent-interaction-and-decision-quality`](../../guidelines/agent-infra/agent-interaction-and-decision-quality.md)
 § 8b-ladder:
 
 | Tag | Meaning | The evidence that makes it a finding |
@@ -94,7 +94,7 @@ Chesterton's Fence, operationalised. Agents are documented as
 especially fence-blind: complex code reads as an invitation to simplify
 when the complexity may exist for a reason the reader has no context
 for. This does not restate
-[`minimal-safe-diff`](../../../src/rules/minimal-safe-diff.md)'s "never
+[`minimal-safe-diff`](../../rules/minimal-safe-diff.md)'s "never
 delete code that *looks* dead without proof" — it is the output contract
 that makes the proof visible.
 

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

@@ -78,7 +78,7 @@ Override files **must match the original filename** exactly:
 | `.augment/rules/php-coding.md` | `agents/overrides/rules/php-coding.md` |
 | `.augment/skills/eloquent/SKILL.md` | `agents/overrides/skills/eloquent.md` |
 | `.augment/commands/feature/plan.md` | `agents/overrides/commands/feature/plan.md` |
-| `../../../docs/guidelines/php/controllers.md` | `agents/overrides/guidelines/php-controllers.md` |
+| `../../guidelines/php/controllers.md` | `agents/overrides/guidelines/php-controllers.md` |
 | `.augment/templates/roadmaps.md` | `agents/overrides/templates/roadmaps.md` |
 
 **Skills** are flattened: the original lives in a directory (`skills/{name}/SKILL.md`),

package/dist/agent-src/skills/perf-feedback-craft/SKILL.md

@@ -28,7 +28,7 @@ Do NOT use as a comp-decision surface (route to Q2 `comp-banding`; feedback info
 
 ## Cognition cluster
 
-- **Mental model 1 — First principles.** Strip feedback to: *what observation, about what behavior, with what impact, requesting what change?* Most feedback fails because it skips the observation (jumps to interpretation) or skips the impact (assumes it's obvious). See [`mental-models.md`](../../../docs/contracts/mental-models.md) § 1.
+- **Mental model 1 — First principles.** Strip feedback to: *what observation, about what behavior, with what impact, requesting what change?* Most feedback fails because it skips the observation (jumps to interpretation) or skips the impact (assumes it's obvious). See [`mental-models.md`](../../docs/contracts/mental-models.md) § 1.
 - **Mental model — Ladder of inference.** Behavior observed → data selected → meaning inferred → assumptions made → conclusions drawn → beliefs adopted → action taken. Most feedback exchanges fail because giver and receiver are on different rungs. Naming the rung you're on (and inviting the other party to do the same) is the single highest-leverage feedback skill.
 - **Mental model 28 — Inversion.** *"What would make this feedback land as an attack instead of a gift?"* — usually: public delivery, surprise (no prior signal), interpretation-as-fact, no specific request, no listening turn. Inversion surfaces the four canonical mis-deliveries.
 - **Mental model 21 — Second-order thinking.** Feedback ripples. Praise in public, correction in private — the inverse damages both giver and receiver. A single mishandled feedback exchange damages trust for 6+ months; a single well-handled one banks trust that compounds.

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

@@ -146,7 +146,7 @@ to every persona you author.
 * Author a persona that nobody cites.
 * Restate Iron-Law text from rules inside `## Output expectations`.
 * Use ALL-CAPS Iron-Law fenced blocks — those belong in rules on the
-  [`kernel-membership`](../../../docs/contracts/kernel-membership.md)
+  [`kernel-membership`](../../docs/contracts/kernel-membership.md)
   list.
 * Ship a persona that overlaps an existing one's focus by more than
   50 % — merge instead.