@event4u/agent-config 16.2.0 → 16.4.0

package/dist/agent-src/commands/feature/roadmap.md

@@ -252,7 +252,7 @@ Declared by `produces_roadmap: true` in the frontmatter and enforced by
 `lint_roadmap_producers`: a producer that does not end here reds CI.
 
 Read `planning.closure_pass` (missing = `true`). When active, run
-[`/challenge-me closure`](../../../meta/challenge-me/closure/command.md) on the
+`/challenge-me closure` on the
 roadmap this command just produced, before handing back:
 
 ```bash

package/dist/agent-src/commands/fix/ci.md

@@ -96,18 +96,32 @@ branch** — that is what makes the deliverable remote. Then:
 1. Commit the fix (chunked, the agent picks the split per
    [`commit-policy`](../../../rules/commit-policy.md) — never ask how).
 2. Update the branch against its PR base first:
-   `./scripts-run src/scripts/sync_pr_branch`, then regenerate any derived files
-   the merge touched (`task sync && task generate-tools`). A PR left behind its
+   `agent-config git:convention sync --base origin/<base>`, `<base>` being the
+   `baseRefName` of the branch's `OPEN` pull request (`gh pr view --json
+   state,baseRefName`; a closed or merged one does not count) — otherwise, and
+   without `--base`, the target is the default branch, wrong for any other base — then regenerate any derived files
+   the merge touched (`task sync && task generate-tools`). Under
+   `git.update_strategy: rebase` the script refuses a behind branch (exit 3); rebase on the user's request
+   instead ([`branch-update`](../../../../skills/git-workflow/references/branch-update.md)),
+   never merge the base in. An exit 3 whose line reads `TARGET_POLICY_STALE`
+   is not this branch's update: the branch is current with the pull request's
+   non-default target, and that target is itself behind the default branch its
+   convergence policy requires, so a rebase cannot clear it — report it as the target's update and leave the branch. On exit 4 the strategy could not be read — a
+   settings file that does not parse, a value outside the schema, or a value
+   only a user-global file sets; the line names the reason code and the file.
+   Nothing was merged: stop, report that line, and do not push until the file
+   is fixed. A PR left behind its
    base accumulates conflicts for the moment someone wants to merge it, and a
    push against a moved base is rejected — both cost a round trip that this one
    call prevents.
 3. Push. The instruction named it; do not raise a separate ask
-   ([`/create-pr` § 4d item 5](../../../git/pr/create/command.md)).
+   (`/create-pr` § 4d item 5).
 4. Re-verify remotely: `./scripts-run src/scripts/check_pr_ci_current`, then
    settle the check set on the new head. Report the *remote* verdict, never the
    local one.
 
-Bounded by N=3 per failing target ([`autonomous-execution`](../../../rules/autonomous-execution.md)).
+Bounded by the `execution.fix_loop_max` budget (default 10) and its ladder,
+per failing target ([`autonomous-execution`](../../../rules/autonomous-execution.md)).
 
 ### Rules
 

package/dist/agent-src/commands/fix/commit-messages.md

@@ -62,8 +62,15 @@ Stop and report — do not proceed to step 2 — when any holds:
 Run `## Procedure: Establish the house convention` from
 [`conventional-commits-writing`](../../../skills/conventional-commits-writing/SKILL.md)
 verbatim: tier-1 sources first (opened and read, never taken from a grep hit),
-then the capped-weighted consensus pass with bots, merges, reverts and release
-automation excluded.
+then the capped-weighted consensus pass — `agent-config git:convention measure` — with bots, merges, reverts and release
+automation excluded. When that tier-1 search found no configured source, a
+declared `git.commit_format: ticket-conventional` (the skill's tier 1b; `ticket-scope`
+is the template default and declares nothing) is the target: report it as
+`Declared : git.commit_format: …`, skip step 3's style question, and keep the
+other authorisations. A configured source always outranks it — including step
+3's tier-1 veto.
+
+Ticket reading, placement and precedence: [`commit-subject`](../../../../skills/git-workflow/references/commit-subject.md).
 
 Report what it found, in one block, before offering anything:
 
@@ -190,7 +197,7 @@ Then, in one block, state:
   for a branch a teammate already has;
 - whether the range crosses the **default branch** — rewriting merged history
   is a different order of disruption and gets its own sentence;
-- the backup ref you are about to write.
+- the recovery ref you are about to write.
 
 **Ask for the rewrite and, when the range is already pushed, the force-push in
 the same block.** [`git-history-discipline`](../../../rules/git-history-discipline.md)
@@ -207,10 +214,19 @@ Wait. Do not run anything in the turn you ask.
 
 ### 7. Rewrite
 
-**7a. Backup, and capture what the verification will compare against.**
+**7a. Pin the published ref, keep the old head, and capture what the
+verification will compare against.** When the range is already pushed, first
+run the `resolve` block of
+[`branch-update.md` § The rebase sequence](../../../../skills/git-workflow/references/branch-update.md#the-rebase-sequence)
+to set `REMOTE` and `RB` — never `@{u}`, which is the base for a branch pushed
+without `-u`. An unresolved target means no rewrite.
 
 ```bash
-git tag "backup/pre-message-fix-$(date +%Y%m%d-%H%M%S)"
+PUBLISHED=$(git ls-remote "$REMOTE" "refs/heads/$RB") \
+  || { echo "STOP: could not read $REMOTE/$RB — nothing was rewritten" >&2; exit 1; }   # pushed range only
+EXPECTED=$(cut -f1 <<<"$PUBLISHED")
+SAVE="refs/agent-config/rewrites/$(date -u +%Y%m%dT%H%M%SZ)-msgfix/before"
+git update-ref "$SAVE" HEAD
 git rev-list --count HEAD > /tmp/precount.txt
 git log ${BASE:+$BASE..}HEAD --pretty=format:'%aN%x09%aE%x09%ad%x09%s' > /tmp/preplan.txt
 ```
@@ -229,17 +245,21 @@ bracketed form:
 ```bash
 git filter-repo --force --refs "${BASE:+$BASE..}HEAD" \
   --commit-callback '
-    import re
+    import json, re, subprocess
     ME = {b"me@example.com"}                  # the step-5 address set, bare, no <>
-    PAT = re.compile(rb"^\[?([A-Z][A-Z0-9]+-[0-9]+)\]?[: ]\s*(.+)$")
     if len(commit.parents) > 1:
         return
     if commit.author_email not in ME:
         return
     subject, sep, body = commit.message.partition(b"\n")
-    m = PAT.match(subject)
-    if m:
-        commit.message = b"[" + m.group(1) + b"] " + m.group(2) + sep + body
+    out = subprocess.run(["agent-config", "git:convention", "ticket", subject.decode(), "--json"],
+                         capture_output=True, text=True, check=True).stdout
+    ticket = json.loads(out)["ticket"]
+    if ticket is None:
+        return
+    lead = re.compile(rb"^\[?" + re.escape(ticket.encode()) + rb"\]?[: ]\s*")
+    if lead.match(subject):
+        commit.message = b"[" + ticket.encode() + b"] " + lead.sub(b"", subject, count=1) + sep + body
   '
 ```
 
@@ -254,10 +274,12 @@ rewriting nothing:
   cross-wire precisely because they need opposite forms.
 - **Merges are skipped in the callback too**, or the rewrite touches commits the
   step-6 table did not list.
-- **`PAT` and the replacement are the step-3 pattern**, substituted for real.
-  A callback that references a helper nothing defines is not a callback that
-  failed loudly — Python evaluates the name only if control reaches it, so a
-  wrong author filter hides the missing helper completely.
+- **The ticket comes from `agent-config git:convention ticket`**, never a regex
+  literal, so the rewrite reads tickets exactly as `/commit` does — the verb must
+  be on `PATH`, and `check=True` makes a missing one fail loudly. A callback that
+  references a helper nothing defines is not a callback that failed loudly —
+  Python evaluates the name only if control reaches it, so a wrong author filter
+  hides the missing helper completely.
 
 `--refs` implies partial mode, which is what keeps the `origin` remote that
 plain `filter-repo` strips as a safety measure; `--partial` is not needed
@@ -286,7 +308,7 @@ not exit that state.
 
 ```bash
 git rev-list --count HEAD                                  # equals /tmp/precount.txt
-git diff <backup-tag> HEAD --stat                          # MUST be empty
+git diff "$SAVE" HEAD --stat                             # MUST be empty
 git log ${BASE:+$BASE..}HEAD --pretty=format:'%aN%x09%aE%x09%ad%x09%s' > /tmp/postplan.txt
 diff /tmp/preplan.txt /tmp/postplan.txt
 ```
@@ -304,21 +326,24 @@ The authorisation was taken in step 6, together with the rewrite's. Push in this
 turn:
 
 ```bash
-git push --force-with-lease origin <branch>
-git log --oneline -3 origin/<branch>
+git push --force-with-lease="refs/heads/$RB:$EXPECTED" "$REMOTE" "HEAD:refs/heads/$RB"
+[ "$(git ls-remote "$REMOTE" "refs/heads/$RB" | cut -f1)" = "$(git rev-parse HEAD)" ]
 ```
 
-`--force-with-lease`, never bare `--force`. Leave the backup tag in place. Tell
-the user its name, and that recovery is `git reset --hard <backup-tag>` — plus a
-force-push, since the rewrite was already pushed.
+The lease carries the SHA pinned in 7a, never a bare `--force-with-lease`, and
+never `--force`; a rejected lease is a stop — refetch and report. Leave the
+recovery ref in place: it lives outside `refs/tags/`, so `git push --tags`
+cannot publish it. Tell the user its name, that recovery is
+`git reset --keep <ref>` — plus a leased force-push, since the rewrite was
+already pushed — and that `git update-ref -d <ref>` removes it.
 
 ### 9. Report
 
 - Convention chosen, and how it was established (measured / user-supplied / tier-1).
 - Range, author scope, commits rewritten vs unchanged.
 - The `diff /tmp/preplan.txt /tmp/postplan.txt` result and the
-  `git diff <backup-tag> HEAD --stat` result, both quoted.
-- The backup tag and the one-line recovery command.
+  `git diff <recovery-ref> HEAD --stat` result, both quoted.
+- The recovery ref and the one-line recovery command.
 - Whether it was pushed, and to where.
 
 ## Do NOT
@@ -329,7 +354,7 @@ force-push, since the rewrite was already pushed.
   instruction — and never by offering it as a menu option they did not raise.
 - Do NOT compare `commit.author_email` against a bracketed address, or pass a
   bare address to `--author`.
-- Do NOT treat an empty `git diff <backup> HEAD` as proof the rewrite happened.
+- Do NOT treat an empty `git diff <recovery-ref> HEAD` as proof the rewrite happened.
 - Do NOT use `git filter-branch`, bare `git push --force`, or `--no-verify`.
 - Do NOT rewrite into a style the repo's own validator rejects.
 - Do NOT let a chosen style carry an attribution trailer, a subject emoji, or

package/dist/agent-src/commands/fix/pr-comments.md

@@ -183,13 +183,10 @@ already live.
   `"The fallback covers legacy data where getTime() returns a string."`
 - Never start multiple replies with "Fixed". Mix it up: "Done", "Good catch", "Yep", etc.
 
-### Bot icon prefix
+### No bot icon prefix
 
-Read `personal.pr_comment_bot_icon` from `.agent-settings.yml`. If `true` (default),
-prefix every reply with `🤖 ` so reviewers can see at a glance that the reply was
-bot-authored.
-
-Example: `🤖 Good catch, fixed.`
+Never prefix a reply with `🤖 ` — it is on the universal blacklist of
+[`no-decorative-emojis-in-git-surfaces`](../../../rules/no-decorative-emojis-in-git-surfaces.md).
 
 If `false` or `.agent-settings.yml` doesn't exist, do NOT add the prefix.
 

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

@@ -29,8 +29,8 @@ packs:
 Accept one of five input paths:
 
 1. **Explicit key** — `/implement-ticket PROJ-123`
-2. **Branch detection** — no arg → `git branch --show-current` + regex
-   `[A-Z]+-[0-9]+`
+2. **Branch detection** — no arg → `agent-config git:convention ticket` on the
+   current branch ([`commit-subject`](../../../skills/git-workflow/references/commit-subject.md) § Reading the ticket)
 3. **Pasted text** — markdown block under the command
 4. **URL** — `/implement-ticket https://…/browse/PROJ-123`
 5. **Local ticket bundle** — a path to a bundle ticket file,
@@ -131,7 +131,7 @@ On exit `1`, look at the first line after `[halt] outcome=… step=…`:
   options verbatim, wait for the user, write their answer back onto the
   matching state slice, then re-run the engine. Never guess.
 
-A **cross-source discrepancy** discovered while planning or applying — ticket text contradicting an attached mockup, a spec silent on a clearly-needed behavior, or a spec-vs-codebase conflict (per [`cross-source-consistency`](../rules/cross-source-consistency.md), gated by `consistency.cross_source`) — is a blocking user question, not a silent resolution: surface it as the `questions[0]` halt and wait, never expand scope on a plausible inference.
+A **cross-source discrepancy** discovered while planning or applying — ticket text contradicting an attached mockup, a spec silent on a clearly-needed behavior, or a spec-vs-codebase conflict (per [`cross-source-consistency`](../rules/cross-source-consistency.md)) — is a blocking user question, not a silent resolution: surface it as the `questions[0]` halt and wait, never expand scope on a plausible inference.
 
 ### 4. Directive mapping
 
@@ -213,7 +213,7 @@ Declared by `produces_roadmap: true` in the frontmatter and enforced by
 `lint_roadmap_producers`: a producer that does not end here reds CI.
 
 Read `planning.closure_pass` (missing = `true`). When active, run
-[`/challenge-me closure`](../../meta/challenge-me/closure/command.md) on the
+`/challenge-me closure` on the
 roadmap this command just produced, before handing back:
 
 ```bash

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

@@ -95,7 +95,7 @@ Declared by `produces_roadmap: true` in the frontmatter and enforced by
 `lint_roadmap_producers`: a producer that does not end here reds CI.
 
 Read `planning.closure_pass` (missing = `true`). When active, run
-[`/challenge-me closure`](../../meta/challenge-me/closure/command.md) on the
+`/challenge-me closure` on the
 roadmap this command just produced, before handing back:
 
 ```bash

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

@@ -121,22 +121,10 @@ link resolves. Broken link → block and ask the user to fix.
 - Duplicate of an existing entry (step 2) — update instead.
 - Missing `source:` — an entry without evidence cannot be reviewed.
 
-## Output format (verbosity-gated)
-
-Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
-`minimal`).
-
-- `off` → emit nothing on success; surface gate failures only.
-- `minimal` (default) → one line:
-  `✅  Added <type>/<id> (gate: PASS)`.
-- `full` → multi-line block:
-
-  ```
-  ✅  Added <type>/<id> (confidence: <high|medium|low>)
-     Path: agents/memory/<type>.yml (or agents/memory/<type>/<hash>.yml)
-     Gate: scripts/check_memory.ts → PASS
-     Next: commit and link from the relevant skill/command.
-  ```
+## Output format
+
+One line on success: `✅  Added <type>/<id> (gate: PASS)`. Gate failures are
+always surfaced.
 
 ## See also
 

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

@@ -134,15 +134,15 @@ After step 4, count unreviewed intake entries for the same type:
   node -e "const d = []; process.stdin.on('data', c => d.push(c)); process.stdin.on('end', () => console.log(JSON.parse(d.join('')).length))"
 ```
 
-Read `memory.review_threshold` from `.agent-settings.yml` (default 10).
-If the count is **0** or **≤ threshold**, skip this step silently. If
-**> threshold**, surface a numbered preview of the top-3 highest-
+The threshold is a fixed **10** (the `memory.review_threshold` key was retired
+on 2026-10-09 with that default as the behavior). If the count is **≤ 10**,
+skip this step silently. If **> 10**, surface a numbered preview of the top-3 highest-
 confidence intake signals (see
 [`memory-consolidation`](../../skills/memory-consolidation/SKILL.md)
 § Phase 3 for the consolidation contract):
 
 ```
-> ⚠️  {N} unreviewed intake signals for `{type}` (threshold {T}).
+> ⚠️  {N} unreviewed intake signals for `{type}` (threshold 10).
 >     Top 3 by confidence:
 >
 >     1. [conf=high] {sig-id} — {one-line observation}
@@ -156,8 +156,7 @@ confidence intake signals (see
 ```
 
 Default action is **skip** — the load completes regardless. This is a
-nudge, not a gate. If `memory.review_threshold` is `0`, skip this
-step entirely (feature off). Never auto-promote.
+nudge, not a gate. Never auto-promote.
 
 ## When to reject
 

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

@@ -205,23 +205,10 @@ git push -u origin memory/promote-<curated-id>
 # Then route to /create-pr with the memory-promote template hint.
 ```
 
-### 7. Report (verbosity-gated)
+### 7. Report
 
-Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
-`minimal`).
-
-- `off` → emit nothing on success; surface errors only.
-- `minimal` (default) → one line:
-  `→ Promoted <sig-id> → <curated-id> (PR: <url or branch>)`.
-- `full` → multi-line block:
-
-  ```
-  > ✅ Promotion drafted.
-  > - Signal:   <sig-id>
-  > - Curated:  <curated-id> in agents/memory/<type>.yml
-  > - PR:       <url or branch name>
-  > - Next:     review + merge
-  ```
+One line on success: `→ Promoted <sig-id> → <curated-id> (PR: <url or branch>)`.
+Errors are always surfaced.
 
 ## Safety
 

package/dist/agent-src/commands/mission/upgrade.md

@@ -170,8 +170,9 @@ them.
   [`verify-before-complete`](../../rules/verify-before-complete.md).
 - Every catalog `command:` field is restricted to the safe-prefix allowlist.
   Never run arbitrary shell commands from the catalog.
-- The N=3 retry budget from [`autonomous-execution`](../../rules/autonomous-execution.md)
-  applies per breaking-change fix step, not per mission.
+- The `execution.fix_loop_max` retry budget and its ladder from
+  [`autonomous-execution`](../../rules/autonomous-execution.md)
+  apply per breaking-change fix step, not per mission.
 - Never skip the size-tier surface step — the user must see the scope before the
   provisional branch is created.
 

package/dist/agent-src/commands/optimize/agents-dir.md

@@ -97,8 +97,8 @@ surface changes.
    - **Delete** — preview file, confirm, delete, scrub references.
    - **Update** — apply explicit content changes (remove stale refs, refresh sections, add missing info).
    - **Create context** — hand off to `/context create` with area pre-selected.
-4. **Update roadmap progress** — flip `[ ]` → `[x]` after each action; show progress bar. Per `verbosity.routine_confirmations`: `false` → continue silently, user can interrupt; `true` → confirm next.
-5. **Summary** — gated by `verbosity.post_action_reports` (`off` / `minimal` / `full`); minimal = one line counts (moved · merged · deleted · updated · remaining).
+4. **Update roadmap progress** — flip `[ ]` → `[x]` after each action; show progress bar. Continue silently to the next action — the user can interrupt; a routine "next?" confirmation is never asked.
+5. **Summary** — one line of counts (moved · merged · deleted · updated · remaining).
 
 **Rules:** confirm before every destructive action; always update references when moving/renaming; update the roadmap after each completed action; show file content before delete; check `.augment/` references too.
 

package/dist/agent-src/commands/optimize/deep.md

@@ -96,8 +96,10 @@ above that, re-invoke deliberately with fresh context.
   gain is the failure the metric exists to catch.
 - The council splits on the same question twice → STOP, escalate that
   question to the user instead of burning a third loop on it.
-- Any validation target fails 3 consecutive refinement attempts → STOP
-  (N=3 budget, `autonomous-execution`).
+- A validation target failing 3 consecutive refinement attempts triggers
+  the rule's mandatory strategy shift; exhausting the full
+  `execution.fix_loop_max` budget (default 10) on the same target → STOP
+  (`autonomous-execution`).
 
 ### Hard exclusions — never inside this command
 

package/dist/agent-src/commands/optimize/rtk.md

@@ -125,32 +125,10 @@ Run a quick test to confirm rtk picks up the filters:
 rtk config 2>&1 | tail -5
 ```
 
-### 7. Present results (verbosity-gated)
-
-Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
-`minimal`).
-
-- `off` → emit nothing on success; surface errors only.
-- `minimal` (default) → one line: `→ N filters configured in .rtk/rtk.toml`.
-- `full` → multi-line summary table:
-
-  ```
-  | #   | Filter       | Match                                                         | Max  |
-  |-----|--------------|---------------------------------------------------------------|------|
-  | 1   | phpstan      | phpstan\|quality:phpstan\|vendor/bin/phpstan                  | 80   |
-  | 2   | pest         | pest\|phpunit\|artisan test                                   | 60   |
-  | 3   | tsc          | tsc\|tsc --noEmit                                             | 60   |
-  | 4   | eslint       | eslint\|next lint                                             | 50   |
-  | 5   | vitest       | vitest\|jest                                                  | 50   |
-  | 6   | playwright   | playwright\|@playwright/test                                  | 40   |
-  | 7   | ruff         | ruff check\|ruff format                                       | 60   |
-  | 8   | mypy         | mypy\|pyright                                                 | 50   |
-  | 9   | pytest       | pytest\|python -m pytest                                      | 50   |
-  | 10  | golangci     | golangci-lint\|go vet                                         | 50   |
-  | 11  | gotest       | go test                                                       | 40   |
-  | 12  | cargo        | cargo build\|cargo check\|cargo clippy\|cargo test\|cargo fmt | 50   |
-  | ... | ...          | (add per project as the toolchain grows)                      | ...  |
-  ```
+### 7. Present results
+
+One line on success: `→ N filters configured in .rtk/rtk.toml`. Errors are
+always surfaced.
 
 ### Rules
 

package/dist/agent-src/commands/pr/create/description-only.md

@@ -22,11 +22,10 @@ packs:
 
 > **Carve-out:** this command's *purpose* is the copyable preview of
 > the PR description. It therefore **ignores**
-> `verbosity.preview_artifacts` and `commands.create_pr.preview_description`
-> — both flags govern only the bare `/create-pr` flow's preview-and-
-> adjust loop. Removing the preview here would make the command a
-> no-op. Do not "fix" this; the suppression flags only apply when the
-> PR is actually being created.
+> `commands.create_pr.preview_description` — that flag governs only the
+> bare `/create-pr` flow's preview-and-adjust loop. Removing the preview
+> here would make the command a no-op. Do not "fix" this; the suppression
+> flag only applies when the PR is actually being created.
 
 ## Input
 
@@ -87,7 +86,15 @@ That's 6 round-trips for what should be 2.
 
 ### 3. Build the PR title
 
-- Format: `{TICKET-ID}: {summary}` (e.g. `DEV-4673: Fix absence working time calculation`).
+- **Squash merge** — the method `/pr:merge` § 9 reads
+  (`gh repo view --json mergeCommitAllowed,squashMergeAllowed,rebaseMergeAllowed`)
+  is squash: the title becomes the commit subject on the base, so build it as a
+  subject in the convention in force — `DEV-4673 fix(working-time): correct absence calculation`
+  under `ticket-conventional`, `fix(DEV-4673): correct absence calculation` under
+  the default — and pipe it through `agent-config git:convention subject`; act on
+  the exit code as `/commit` step 5 does.
+- **Any other method** — `{TICKET-ID}: {summary}` (e.g. `DEV-4673: Fix absence working time calculation`).
+- The rule: [`commit-subject`](../../../../../skills/git-workflow/references/commit-subject.md) § A title that becomes a commit.
 - Use the Jira ticket summary if available, otherwise derive from commits.
 - If no ticket: use the most descriptive commit message or ask the user.
 
@@ -173,13 +180,12 @@ summary and `## How to test` is omitted):
 
 #### 4.3 API response examples (evidence-grounded)
 
-Read `commands.create_pr.api_examples` (default `true`). When `true` **and**
-the diff touches an API endpoint, add a fenced request/response example under
-the Description.
+When the diff touches an API endpoint, add a fenced request/response example
+under the Description. This is not a setting — it always applies, and the
+grounding rule below is what keeps it honest.
 
 **Detect an API-endpoint change** (fail-open — no false enrichment when
-ambiguous): a changed file matches `commands.create_pr.api_paths` (if set), or
-the light heuristic — a route file (`routes/`, `**/api/**`, `*Controller*`,
+ambiguous) with the light heuristic — a route file (`routes/`, `**/api/**`, `*Controller*`,
 resource/serializer classes) whose diff adds or changes an endpoint or its
 request/response shape. No confident match → skip silently.
 
@@ -212,8 +218,6 @@ Response `201`:
 ```
 ~~~
 
-`api_examples: false` → skip this step entirely.
-
 #### 4.4 Screenshots for frontend changes (capability-gated)
 
 Read `commands.create_pr.screenshots` (default `false`). `false` → skip this
@@ -223,8 +227,7 @@ When `true`, this is a **capability-gated contract, never a runtime
 orchestrator** — the package ships instructions, the host provides the tools:
 
 1. **Frontend-change gate.** Only proceed if the diff touches a frontend
-   surface — a changed file matches `commands.create_pr.ui_paths` (if set), or
-   the light heuristic (`.vue` / `.tsx` / `.jsx` / `.blade.php` / `.svelte`,
+   surface by the light heuristic (`.vue` / `.tsx` / `.jsx` / `.blade.php` / `.svelte`,
    component/view/page/template dirs, CSS/Tailwind). No match → skip silently.
 2. **Capability gate — explicit, never silent.** Screenshots need host
    browser/preview tooling (a Playwright/browser MCP **and** a reachable dev-server