@event4u/agent-config 1.14.0 → 1.16.0

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

@@ -8,7 +8,9 @@ source: package
 
 ## Positioning — reference, not executor
 
-`fe-design` is a **universal reference skill**, not an executor. Stack-agnostic heuristics that the UI directive set cites; does **not** own the flow.
+`fe-design` is a **universal reference skill**, not an executor. It carries
+stack-agnostic heuristics that the UI directive set cites; it does **not**
+own the flow.
 
 | Concern | Owner |
 |---|---|
@@ -35,7 +37,10 @@ Do NOT use this skill to:
 
 ## How the directive set cites this skill
 
-`directives/ui/design.py` produces the design brief (layout, components, states, microcopy, a11y). Brief picks heuristics from this reference when audit doesn't already pin a project pattern. Stack-specific choices come from the dispatched implementation skill.
+`directives/ui/design.py` produces the design brief (layout, components,
+states, microcopy, a11y). The brief picks heuristics from this reference
+when the audit doesn't already pin a project pattern. Stack-specific
+choices come from the dispatched implementation skill, not from here.
 
 ## Component Architecture
 
@@ -53,7 +58,8 @@ Page layout
 └── Footer (static)
 ```
 
-Stack-specific mapping (Blade partial vs. Livewire component vs. React island vs. Vue SFC) is the apply-step's concern.
+The stack-specific mapping (Blade partial vs. Livewire component vs.
+React island vs. Vue SFC) is the apply-step's concern, not this skill's.
 
 ### When to use what (kind, not framework)
 
@@ -69,7 +75,7 @@ Stack-specific mapping (Blade partial vs. Livewire component vs. React island vs
 
 - **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 provides (audit findings tell you which).
+- **Use the project's library primitives first** — never rebuild what the design system already provides (audit findings tell you which).
 - **Extract when used 3+ times** — DRY applies to UI too.
 
 ## Form Design
@@ -194,20 +200,20 @@ Step indicator (1 — 2 — 3)
 
 When `directives/ui/design.py` (or any caller) cites this skill:
 
-1. **Confirm audit ran first** — `state.ui_audit` from [`existing-ui-audit`](../existing-ui-audit/SKILL.md) is mandatory. Stop and request audit if missing.
-2. **Pick smallest matching section** — Component Architecture, Form Design, Table Design, Responsive Strategy, Accessibility, or UX Principles. Cite by H2/H3 heading, never paste whole skill.
-3. **Defer to audit findings** — when audit pins a project pattern (token, primitive, layout convention), use it. Heuristics here are fallbacks for gaps, not overrides.
-4. **Defer to stack apply skill** — Blade vs. Livewire vs. Flux vs. React-shadcn choices come from dispatched implementation skill, never from this reference.
-5. **Surface conflicts** — if heuristic here contradicts an audit finding or stack convention, name both and let caller decide; do not silently pick.
+1. **Confirm the audit ran first** — `state.ui_audit` from [`existing-ui-audit`](../existing-ui-audit/SKILL.md) is mandatory. Stop and request the audit if missing.
+2. **Pick the smallest matching section** — Component Architecture, Form Design, Table Design, Responsive Strategy, Accessibility, or UX Principles. Cite by H2/H3 heading, never paste the whole skill.
+3. **Defer to audit findings** — when the audit pins a project pattern (token, primitive, layout convention), use it. The heuristics here are fallbacks for gaps, not overrides.
+4. **Defer to the stack apply skill** — Blade vs. Livewire vs. Flux vs. React-shadcn choices come from the dispatched implementation skill, never from this reference.
+5. **Surface conflicts** — if a heuristic here contradicts an audit finding or stack convention, name both and let the caller decide; do not silently pick.
 
 ## Output format
 
 When this skill's content is folded into a design brief or review:
 
-1. Quote cited heuristic verbatim, with H2/H3 heading and one-line "why this applies" tie-back to request.
-2. Map each heuristic to a concrete artifact in brief (component, form section, table column, breakpoint rule, a11y check, UX state).
-3. Keep stack-agnostic — never name Blade/Livewire/Flux/React primitives in cited prose; apply step adds those.
-4. Mark anything overridden by audit findings as `[audit override]` and link to audit entry.
+1. Quote the cited heuristic verbatim, with the H2/H3 heading and a one-line "why this applies" tie-back to the request.
+2. Map each heuristic to a concrete artifact in the brief (component, form section, table column, breakpoint rule, a11y check, UX state).
+3. Keep stack-agnostic — never name Blade/Livewire/Flux/React primitives in the cited prose; the apply step adds those.
+4. Mark anything overridden by audit findings as `[audit override]` and link to the audit entry.
 
 ## Related
 
@@ -222,7 +228,7 @@ When this skill's content is folded into a design brief or review:
 
 ## Gotcha
 
-- Don't design components without running `existing-ui-audit` first — audit's component/token inventory is canonical for "what already exists in this project". Reinventing is the #1 failure mode.
+- Don't design components without running `existing-ui-audit` first — the audit's component/token inventory is the canonical source for "what already exists in this project". Reinventing is the #1 failure mode.
 - Heuristics in this reference apply across stacks; do not promote them to project rules without checking the audit.
 - Mobile-first is not optional — every layout must work on 320px width.
 
@@ -232,4 +238,3 @@ When this skill's content is folded into a design brief or review:
 - Do NOT use fixed pixel widths for responsive layouts.
 - Do NOT ignore accessibility requirements.
 - Do NOT use this skill as an executor — it is a reference cited by `directives/ui/design.py`.
-

package/.agent-src/skills/file-editor/SKILL.md

@@ -8,6 +8,8 @@ execution:
   allowed_tools: []
 ---
 
+<!-- cloud_safe: noop -->
+
 # file-editor
 
 ## When to use
@@ -127,3 +129,10 @@ code app/Models/User.php
 - Do NOT prompt the user about IDE settings during normal work — suggest `/onboard` (for first-run) or editing `.agent-settings.yml` directly.
 - Do NOT open files that were only read, not edited.
 - Do NOT open more than 10 files at once — summarize instead.
+
+## Cloud Behavior
+
+On cloud surfaces (Claude.ai Web, Skills API) this skill is **fully inert** —
+there is no local IDE to open files in, no `.agent-settings.yml` to read, and
+no shell handler available. The cloud agent simply finishes its edits and
+reports back; file-opening is a local-agent concern.

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

@@ -1,6 +1,6 @@
 ---
 name: flux
-description: "Stack-implementation skill for Laravel Flux — dispatched by `directives/ui/apply.py` (and `review.py` / `polish.py`) when the project uses `livewire/flux`. Covers Flux components, slots, variants, and form primitives."
+description: "Use when the project uses `livewire/flux` — dispatched by `directives/ui/{apply,review,polish}.py`. Covers Flux components, slots, variants, and form primitives."
 source: package
 ---
 

package/.agent-src/skills/git-workflow/SKILL.md

@@ -20,7 +20,7 @@ Do NOT use when:
 
 ## Conventions
 
-→ See guideline `guidelines/php/git.md` for branch naming, commit messages, PR conventions.
+→ See guideline `docs/guidelines/php/git.md` for branch naming, commit messages, PR conventions.
 → See `commit-conventions` rule for commit format, types, and scope rules.
 → Use `conventional-commits-writing` skill for generating/reviewing commit messages.
 

package/.agent-src/skills/guideline-writing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: guideline-writing
-description: "Use when creating or editing a guideline in .agent-src.uncompressed/guidelines/ — reference material cited by skills, no auto-triggers — even when the user just says 'write up our naming conventions'."
+description: "Use when creating or editing a guideline in docs/guidelines/ — reference material cited by skills, no auto-triggers — even when the user just says 'write up our naming conventions'."
 source: package
 ---
 
@@ -10,7 +10,7 @@ source: package
 
 ## When to use
 
-* Creating a new guideline in `.agent-src.uncompressed/guidelines/{topic}/{name}.md`
+* Creating a new guideline in `docs/guidelines/{topic}/{name}.md`
 * Rewriting an existing guideline (not a typo fix)
 * Extracting reference material out of a bloated skill or rule
 * Consolidating repeated explanations from multiple skills
@@ -42,7 +42,7 @@ Creating or materially rewriting a guideline **must** go through Understand
 
 * **Understand** — which skills or rules will cite this guideline? If the
   answer is "none", the guideline has no home — stop.
-* **Research** — **inspect** `guidelines/` for overlap and grep
+* **Research** — **inspect** `docs/guidelines/` for overlap and grep
   `.agent-src.uncompressed/` for pages that already cover the topic.
   **Analyze** 1–2 peer guidelines in the same topic folder for tone.
 * **Draft** — propose location (topic folder + filename) and outline. Only
@@ -50,7 +50,7 @@ Creating or materially rewriting a guideline **must** go through Understand
 
 ### 1. Pick the right topic folder
 
-Folders under `.agent-src.uncompressed/guidelines/`:
+Folders under `docs/guidelines/`:
 
 | Folder | Contents |
 |---|---|
@@ -89,7 +89,7 @@ approval-gated flow as for skills and rules.
 A guideline is useless if nothing cites it. Before closing the task:
 
 * Add a link from at least one skill or rule using the pattern
-  `→ See 'guidelines/{topic}/{name}.md' for full X`.
+  `→ See 'docs/guidelines/{topic}/{name}.md' for full X`.
 * Keep the citing skill/rule **executable** — do not hollow it out into a
   pointer. (Normative source: [`preservation-guard`](../../rules/preservation-guard.md).)
 
@@ -107,16 +107,16 @@ Above the split signal, break by sub-topic into sibling files in the same folder
 
 ### 6. Validate
 
-* Run `python3 scripts/skill_linter.py .agent-src.uncompressed/guidelines/{topic}/{name}.md`
+* Run `python3 scripts/skill_linter.py docs/guidelines/{topic}/{name}.md`
   → 0 FAIL (guidelines have relaxed linting but must still parse).
-* Run `bash scripts/compress.sh --sync` → regenerates `.agent-src/guidelines/`.
+* Run `bash scripts/compress.sh --sync` → projects updates.
 * Run `python3 scripts/check_references.py` → no broken links.
 * Run the full CI pipeline locally (see `Taskfile.yml` in this repo for
   the script list) — must exit 0 except for tolerated warnings.
 
 ## Output format
 
-1. Complete guideline at `.agent-src.uncompressed/guidelines/{topic}/{name}.md`
+1. Complete guideline at `docs/guidelines/{topic}/{name}.md`
 2. At least one skill or rule linking to it
 3. Linter + `check_references.py` clean
 4. `bash scripts/compress.sh --sync` confirmation
@@ -135,7 +135,7 @@ Above the split signal, break by sub-topic into sibling files in the same folder
 * Do NOT add `type:` or `alwaysApply:` to the frontmatter
 * Do NOT embed numbered procedures — those belong in skills
 * Do NOT create an orphan guideline with no inbound links
-* Do NOT edit `.agent-src/guidelines/` or `.augment/guidelines/` — generated
+* Do NOT reintroduce `.agent-src.uncompressed/guidelines/` — relocated to `docs/guidelines/`
 
 ## Cloud Behavior
 
@@ -151,7 +151,7 @@ validation:
 * Self-check the body: reference material, no numbered procedures,
   named in a topic folder.
 * Tell the user to save under
-  `.agent-src.uncompressed/guidelines/{topic}/{name}.md` and run
+  `docs/guidelines/{topic}/{name}.md` and run
   `task sync && task lint-skills && task check-refs` locally before
   committing.
 * Do not call the linter, ref-checker, or compressor — they only
@@ -161,7 +161,7 @@ validation:
 
 Good guideline name + description:
 
-> Path: `guidelines/agent-infra/size-and-scope.md`
+> Path: `docs/guidelines/agent-infra/size-and-scope.md`
 > Description: "Golden size rules for rules, skills, commands, and guidelines"
 
 Bad:

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

@@ -119,7 +119,7 @@ Choose one:
 
 A grep that returns zero hits is **not** proof of no overlap. Knowledge in
 this package is distributed across **four surfaces** — `skills/`, `rules/`,
-`guidelines/`, `commands/`. Skip any of them and recall drops to ~25 %.
+`docs/guidelines/`, `commands/`. Skip any of them and recall drops to ~25 %.
 Run all four steps before declaring "no overlap":
 
 **Step 1 — list all four surfaces.** Directory taxonomy is free evidence:
@@ -127,11 +127,11 @@ Run all four steps before declaring "no overlap":
 ```bash
 ls .agent-src.uncompressed/skills/ \
    .agent-src.uncompressed/rules/ \
-   .agent-src.uncompressed/guidelines/ \
+   docs/guidelines/ \
    .agent-src.uncompressed/commands/
 ```
 
-Sub-directories matter — `guidelines/php/patterns/`, `guidelines/agent-infra/`,
+Sub-directories matter — `docs/guidelines/php/patterns/`, `docs/guidelines/agent-infra/`,
 etc. carry topic taxonomies a flat file scan misses. Always descend one level.
 
 **Step 2 — grep with both vocabularies.** Search for **solution-words** *and*
@@ -194,7 +194,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`](../../guidelines/agent-infra/self-improvement-pipeline.md).
+[`self-improvement-pipeline`](../../../docs/guidelines/agent-infra/self-improvement-pipeline.md).
 
 Mandatory fields the draft MUST fill:
 

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

@@ -1,6 +1,6 @@
 ---
 name: livewire
-description: "Stack-implementation skill for Livewire — dispatched by `directives/ui/apply.py` (and `review.py` / `polish.py`) when the project's frontend stack is Livewire. Covers reactive state, events, lifecycle hooks, and component/view separation."
+description: "Use when the project's frontend stack is Livewire — dispatched by `directives/ui/{apply,review,polish}.py`. Covers reactive state, events, lifecycle hooks, and component/view separation."
 source: package
 ---
 
@@ -8,7 +8,11 @@ source: package
 
 ## Positioning — dispatched, not standalone
 
-`livewire` is the **apply-step executor** for the Livewire stack. Invoked by [`directives/ui/apply.py`](../../templates/scripts/work_engine/directives/ui/apply.py) once the design brief is locked, and revisited by `review.py` / `polish.py` during the design-review loop. Does **not** own the flow, drive the audit, or lock the design.
+`livewire` is the **apply-step executor** for the Livewire stack. It is
+invoked by [`directives/ui/apply.py`](../../templates/scripts/work_engine/directives/ui/apply.py)
+once the design brief is locked, and revisited by `review.py` /
+`polish.py` during the design-review loop. It does **not** own the
+flow, does **not** drive the audit, and does **not** lock the design.
 
 | Concern | Owner |
 |---|---|
@@ -77,12 +81,27 @@ Do NOT use when:
 
 ### Review pass — a11y findings + preview envelope
 
-When dispatched by `directives/ui/review.py` (test slot) or `directives/ui/polish.py` (verify slot) — review/polish run, not initial apply — also emits:
-
-- `state.ui_review.a11y` — `{violations: [{rule, selector, severity}, ...], severity_floor?, accepted_violations?}`. Use same `(rule, selector)` shape as `state.ui_audit.a11y_baseline` so engine's de-dup matches pre-existing entries on replay. Omit envelope on apply passes; engine's `_apply_a11y_gate` only fires when baseline present.
-- `state.ui_review.preview` — `{render_ok: bool, screenshot_path?, dom_dump_path?, error?, skipped?}`. `render_ok: false` with `error` populated triggers `preview_render_failed` halt; `render_ok: true` with `screenshot_path` threads screenshot into delivery report's `artifacts` list. Browser tooling (Playwright/Cypress/…) is consumer-project dependency — package does not ship one.
-
-Polish dispatch: when dispatcher skips `review` because previous review pass returned `SUCCESS`, this skill MUST itself synthesise updated `state.ui_review.findings` (including remaining `a11y_violation` entries) so engine's gate sees current state on next polish round.
+When this skill is dispatched by `directives/ui/review.py` (test slot)
+or `directives/ui/polish.py` (verify slot) — i.e. a review/polish run,
+not the initial apply — it also emits:
+
+- `state.ui_review.a11y` — `{violations: [{rule, selector, severity}, ...],
+  severity_floor?, accepted_violations?}`. Use the same `(rule, selector)`
+  shape as `state.ui_audit.a11y_baseline` so the engine's de-dup matches
+  pre-existing entries on replay. Omit the envelope on apply passes; the
+  engine's `_apply_a11y_gate` only fires when a baseline is present.
+- `state.ui_review.preview` — `{render_ok: bool, screenshot_path?,
+  dom_dump_path?, error?, skipped?}`. `render_ok: false` with `error`
+  populated triggers the `preview_render_failed` halt; `render_ok: true`
+  with `screenshot_path` threads the screenshot into the delivery
+  report's `artifacts` list. Browser tooling (Playwright/Cypress/…) is
+  a consumer-project dependency — this package does not ship one.
+
+Polish dispatch: when the dispatcher skips `review` because a previous
+review pass already returned `SUCCESS`, this skill MUST itself
+synthesise the updated `state.ui_review.findings` (including any
+remaining `a11y_violation` entries) so the engine's gate sees the
+current state on the next polish round.
 
 ## Gotcha
 

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

@@ -70,13 +70,13 @@ 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` |
-| `.augment/guidelines/php/controllers.md` | `agents/overrides/guidelines/php-controllers.md` |
+| `../../../docs/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`),
 but the override is a single file (`skills/{name}.md`).
 
-**Guidelines** are flattened with a prefix: `guidelines/php/controllers.md` → `guidelines/php-controllers.md`.
+**Guidelines** are flattened with a prefix: `docs/guidelines/php/controllers.md` → `guidelines/php-controllers.md`.
 
 **Templates** keep their original filename: `templates/roadmaps.md` → `templates/roadmaps.md`.
 

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

@@ -54,7 +54,7 @@ Trigger keywords in the task or surrounding code:
 - allowlist constants: `private const SUPPORTED_FOO = [Type::A, Type::B]`
 
 → Run the sniff test in
-[`guidelines/php/patterns/strategy.md`](../../guidelines/php/patterns/strategy.md#sniff-test--when-an-enumstring-discriminator-wants-to-become-a-strategy).
+[`docs/guidelines/php/patterns/strategy.md`](../../../docs/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/.agent-src/skills/playwright-testing/SKILL.md

@@ -16,12 +16,12 @@ Use this skill when:
 - Debugging flaky E2E tests
 - Configuring Playwright for CI/CD
 
-**Guideline:** `.augment/guidelines/e2e/playwright.md` — full conventions, config templates, CI setup.
+**Guideline:** `../../../docs/guidelines/e2e/playwright.md` — full conventions, config templates, CI setup.
 **Rule:** `.augment/rules/e2e-testing.md` — constraints enforced during E2E test work.
 
 ## Procedure: Write Playwright tests
 
-1. **Read the guideline** — `.augment/guidelines/e2e/playwright.md` for detailed conventions.
+1. **Read the guideline** — `../../../docs/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/.agent-src/skills/readme-reviewer/SKILL.md

@@ -136,7 +136,7 @@ Structure checks:
 - No duplication between README and `/docs/` (drifts over time)
 - Each `/docs/` file linked from README is self-contained (not just a fragment)
 
-→ See `guidelines/docs/readme-size-and-splitting.md` for full thresholds,
+→ See `docs/guidelines/docs/readme-size-and-splitting.md` for full thresholds,
 splitting strategies, anti-patterns.
 
 ## Output format

package/.agent-src/skills/readme-writing/SKILL.md

@@ -100,7 +100,7 @@ lines: split deep content to `/docs/` or `references/`. Use `<details>`
 only for secondary, bulky content — never for install, first example, or
 requirements.
 
-→ See `guidelines/docs/readme-size-and-splitting.md` for thresholds,
+→ See `docs/guidelines/docs/readme-size-and-splitting.md` for thresholds,
 splitting strategies (reference-split, deep-link tables, collapsibles),
 multi-audience handling, anti-patterns.
 

package/.agent-src/skills/readme-writing-package/SKILL.md

@@ -138,7 +138,7 @@ links over stacked inline blocks. Occasionally-needed detail (long
 platform quirks, troubleshooting): use `<details>` — never for install,
 first example, or requirements.
 
-→ See `guidelines/docs/readme-size-and-splitting.md` for thresholds,
+→ See `docs/guidelines/docs/readme-size-and-splitting.md` for thresholds,
 deep-link-table pattern, collapsibles, anti-patterns (premature
 splitting, duplication between README and `/docs/`).
 

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

@@ -75,7 +75,7 @@ For each blocking/important comment:
 * Check whether the suggested fix would break another test or caller
 * Check `git blame` / history — current code may be that way for a reason
 * **Consult memory for prior context.** Via
-  [`memory-access`](../../guidelines/agent-infra/memory-access.md),
+  [`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md),
   call `retrieve(types=["historical-patterns", "architecture-decisions"],
   keys=<files in the review>, limit=3)`. A registered historical pattern
   may confirm the reviewer's concern (accept) or an architecture

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

@@ -47,19 +47,24 @@ execution:
 
 ## Language strategy
 
-Pick output prose language once, up front; apply to every section.
-First hit wins:
+The refined output's prose language is picked once, up front, and
+applied to every section (refined description, risks, persona voices,
+orchestration notes, close-prompt). Fallback order — first hit wins:
 
-1. **User-message language.** Latest user message decides. Honours the
-   global `language-and-tone` iron law.
+1. **User-message language.** If the latest user message is in
+   German, the entire output is German; if English, English; etc.
+   This honours the global `language-and-tone` iron law.
 2. **Ticket body language.** When the user's message is ambiguous
-   (one-word `/refine-ticket PROJ-123`), mirror the language the ticket
-   is written in (summary + description).
-3. **`.agent-settings.yml` default** (`personal.language` or equivalent).
-   If missing, default to English.
+   (one-word `/refine-ticket PROJ-123`), mirror the language the
+   ticket is written in — detected from the summary + description.
+3. **`.agent-settings.yml` default.** If both are silent or unclear,
+   fall back to the project default in `.agent-settings.yml`
+   (`personal.language` or equivalent). If that is also missing,
+   default to English.
 
-Quoted identifiers (keys, paths, commands, code) stay native. Only
-prose mirrors the picked language.
+Quoted identifiers (ticket keys, file paths, command names, code
+snippets) stay in their native form. Only the prose mirrors the
+selected language.
 
 ## Inputs (four equivalent paths)
 
@@ -88,8 +93,8 @@ Delegate to `jira-ticket` §1-3:
 If pasted text: skip API, parse markdown, extract title + AC
 bullets + body.
 
-**Auto-fetch parent (Phase F4).** Before detection, check the issue
-type and fold parent context in:
+**Auto-fetch parent (Phase F4).** Before detection, check the
+issue type and fold parent context in:
 
 ```python
 from scripts.refine_ticket_detect import (
@@ -105,18 +110,19 @@ if issuetype_needs_parent(ticket["issuetype"]):
 ```
 
 Rules:
-- Applies to `Story` and `Sub-task` (and Linear / Shortcut equivalents).
-  `Task` / `Bug` / `Epic` skip the auto-fetch unless a `parent` link is
-  populated — then the agent folds explicitly without the issuetype guard.
+- Applies to `Story` and `Sub-task` (and their Linear / Shortcut
+  equivalents). `Task` / `Bug` / `Epic` skip the auto-fetch unless a
+  `parent` link field is already populated — in that case the agent
+  folds explicitly without the issuetype guard.
 - `fold_parent_context()` is idempotent; folding twice with the same
   parent does not duplicate the block.
-- Parent fetch fails (404, permission, network) → skip the fold, append
-  to orchestration notes:
+- When the parent fetch fails (404, permission, network), skip the
+  fold and append a line to orchestration notes:
   *"Parent `<key>` not reachable — AC may lack upstream context."*
 
-Parent AC lines surfaced this way must be cited verbatim in the refined
-output's *Open questions* section so the user sees which constraints
-come from the parent.
+Parent AC lines surfaced this way must be cited verbatim in the
+refined output's *Open questions* section so the user sees which
+constraints come from the parent.
 
 ### 2. Inspect ticket + detect orchestration triggers
 
@@ -246,8 +252,8 @@ so the user can grab it verbatim.
 
 ## Close-prompt (mandatory final step)
 
-**Probe write access first (Phase F6).** Cheap upfront check before
-rendering:
+**Probe write access first (Phase F6).** Before rendering, do a
+cheap upfront check:
 
 ```python
 from scripts.refine_ticket_detect import render_close_prompt
@@ -271,8 +277,8 @@ Behaviour:
 | Probe failed (`None`) | Full three-option prompt; skill degrades to copy-paste on selection (v1 fallback) |
 
 Per user interaction rules, accept number or free text. `editmeta`
-is cheap and cacheable; cache per Jira project key for the session,
-re-probe on project change.
+is cheap and cacheable; cache the result per Jira project key for
+the session, re-probe on project change.
 
 ## Output format
 

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

@@ -53,7 +53,7 @@ back. If neither file exists, emit the generic role-based fallback
 using [`reviewer-awareness`](../../rules/reviewer-awareness.md).
 
 **Also** pull agent-written signals via the shared abstraction (see
-[`memory-access`](../../guidelines/agent-infra/memory-access.md)):
+[`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md)):
 
 ```python
 from scripts.memory_lookup import retrieve
@@ -189,7 +189,7 @@ Data source: <"ownership-map.yml + historical-bug-patterns.yml"
 
 - [`reviewer-awareness`](../../rules/reviewer-awareness.md)
 - [`review-routing-awareness`](../../rules/review-routing-awareness.md)
-- [`review-routing-data-format`](../../guidelines/agent-infra/review-routing-data-format.md)
+- [`review-routing-data-format`](../../../docs/guidelines/agent-infra/review-routing-data-format.md)
 - [`create-pr-description`](../create-pr-description/SKILL.md)
 - [`judge-test-coverage`](../judge-test-coverage/SKILL.md) — consumes
   the `required_test` entries from matched patterns.

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

@@ -30,12 +30,13 @@ the dashboard **in the same response**.
 `count_open == 0` (pure `[x]`, or `[x]` + `[~]`/`[-]`), `git mv`
 it into `agents/roadmaps/archive/` **before** regenerating — see
 the auto-archive decision table under "Check completion status"
-below. A 100%-complete roadmap left in `agents/roadmaps/` makes
-the next reader think work is still open.
+below. A 100%-complete roadmap left in `agents/roadmaps/` makes the
+next reader think work is still open.
 
-Enforced by [`roadmap-progress-sync`](../../rules/roadmap-progress-sync.md).
-Batching edits in one response is fine — one final regeneration before
-replying is enough. But the response must not end without it.
+This is enforced by the [`roadmap-progress-sync`](../../rules/roadmap-progress-sync.md)
+rule. Batching multiple edits in one response is fine — one final
+regeneration before replying is enough. But the response must not end
+without it.
 
 ## Procedure: Manage a roadmap
 
@@ -100,11 +101,13 @@ Every roadmap follows this structure:
 
 ## Key rules for roadmaps
 
-### Checkboxes
+### Checkboxes — mandatory, not decorative
 
+- **Every active roadmap MUST contain at least one `- [ ]` per non-intro phase.** Decision tables, ICE matrices, and block-sequencing tables are valid rationale, but they do not satisfy this rule on their own — pair them with a `## Phase N` or `## Implementation Checklist` section whose checkboxes execute the decision. A roadmap without checkboxes is invisible to `agents/roadmaps-progress.md` and violates [`roadmap-progress-sync`](../../rules/roadmap-progress-sync.md) Iron Law #2.
 - Every actionable step uses `- [ ]` (unchecked) or `- [x]` (completed).
 - Mark steps as `[x]` immediately after completing them.
 - Never remove completed steps — they serve as history.
+- **Status is binary: `ready` (default, implicit) or `draft`.** New roadmaps are created **ready** unless the user explicitly says otherwise — `ready` is implicit and need not be written. A roadmap that is still being authored, awaiting upstream decisions, or capturing options without a worked plan declares `status: draft` in YAML frontmatter at the top of the file. Drafts are hidden from `agents/roadmaps-progress.md` until the flag is removed or flipped to `ready`. There are no other status values; legacy banners (`**Status: directional**`, `Status: capture-only`, `mode: feedback`) are removed.
 
 ### Phases
 
@@ -138,12 +141,13 @@ Every roadmap implicitly includes these gates (run after each step that changes
 1. Ask the user for goal, context-create, and phases.
 2. Use the template structure from `.augment/templates/roadmaps.md`.
 3. Review with the user iteratively until approved.
-4. **Branch & release questions — ask at most once, only if genuinely useful.**
-   Default: stay on current branch, no version numbers in roadmap.
-   Only propose a separate branch with concrete evidence (e.g. risky
-   migration → spike branch). Never include releases, deprecation dates,
-   or git tags in roadmap text. If user declines, do **not** re-propose
-   during `roadmap-execute`. Decline = silence. See [`scope-control`](../../rules/scope-control.md#decline--silence--no-re-asking-on-the-same-task).
+4. **Branch & release questions — at most once, only if genuinely useful.**
+   Default: stay on the current branch, no version numbers in the
+   roadmap. Only propose a separate branch when there is concrete,
+   evidence-based reason (e.g. risky migration benefits from a spike).
+   Never include release versions, deprecation dates, or git tags in
+   the roadmap text. If the user declines, do **not** re-propose during
+   `roadmap-execute`. Decline = silence. See [`scope-control`](../../rules/scope-control.md#decline--silence--no-re-asking-on-the-same-task).
 5. Save with a kebab-case filename (e.g. `optimize-webhook-jobs.md`).
 6. Regenerate the dashboard so the new roadmap is included.
 
@@ -272,8 +276,10 @@ Command:
 ./agent-config roadmap:progress-check     # CI: fail if stale
 ```
 
-The `./agent-config` wrapper is written into the project root by the
-installer and always works — no global tooling or task runner required.
+The `./agent-config` wrapper lives in the project root (written by the
+package installer, gitignored) and delegates to the master CLI inside
+`node_modules/@event4u/agent-config/` or `vendor/event4u/agent-config/`.
+No global tooling required.
 
 The dashboard is a **read-only snapshot**. Do not edit it by hand — regenerate it.
 
@@ -309,5 +315,5 @@ The dashboard is a **read-only snapshot**. Do not edit it by hand — regenerate
 - Do NOT archive roadmaps with open `[ ]` items without asking the user.
 - Do NOT delete roadmaps — always move to `archive/` or `skipped/`.
 - Do NOT use `skipped/` as a dumping ground for partially-finished work — that is what `archive/` with deferred items is for.
-- Do NOT assign version numbers, git tags, deprecation dates, or release identifiers to phases. Hard rule — see [`scope-control`](../../rules/scope-control.md#git-operations--permission-gated).
-- Do NOT propose a branch switch while executing a roadmap. Branch question is settled at creation; declined or never-asked = silent. See [`scope-control`](../../rules/scope-control.md#decline--silence--no-re-asking-on-the-same-task).
+- Do NOT assign version numbers, git tags, deprecation dates, or release identifiers to phases. Roadmaps plan work; releases and tags are decided by the user separately. Hard rule — see [`scope-control`](../../rules/scope-control.md#git-operations--permission-gated).
+- Do NOT propose a branch switch while executing a roadmap. The branch question is settled at creation time; if the user already declined (or you never asked because it wasn't sensible), stay silent. See [`scope-control`](../../rules/scope-control.md#decline--silence--no-re-asking-on-the-same-task).

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

@@ -85,7 +85,7 @@ no silent edits, max two rounds.
 ### 4. Enforce the size budget
 
 Normative source: [`size-enforcement`](../../rules/size-enforcement.md) +
-`guidelines/agent-infra/size-and-scope.md`.
+`docs/guidelines/agent-infra/size-and-scope.md`.
 
 | Category | Target |
 |---|---|

package/.agent-src/skills/skill-reviewer/SKILL.md

@@ -83,7 +83,7 @@ The highest-signal content in a skill. Documents failure patterns.
 
 ### Killer 5: Monolithic Blob
 
-Skill exceeds size limits (see `guidelines/agent-infra/size-and-scope.md`).
+Skill exceeds size limits (see `docs/guidelines/agent-infra/size-and-scope.md`).
 
 **Check:** Review at >300 lines. Strongly consider split at >1200 words / >1500 words.
 **Fix:** Extract reference tables, templates, and examples into separate files