From edcd2085b808030d55a0fb8abce4a7342962654e Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sat, 31 Oct 2026 16:40:42 -0400 Subject: [PATCH 1/2] docs: point wave 4 model and workflow claims at upstream sections Fix the eight wave 4 findings of the repo-mode defaults sweep with pointers, reasons and qualifiers. No step or default changes. - context-guard: the subagent autoCompactWindow row points at its sub-agents section, not the changelog. - bugs: scan gives the opus fallback a reason, notes that a blocked alias can be substituted rather than rejected, and points at the model section. - resolve-config README: states why fable and best resolve to opus and points at the alias list and the subagent-model section. - user-experience: the evaluator's model and effort pins carry reasons and an effort pointer. - guardrails: workflow-resilience-check no longer calls the fan-out un-throttled and points at the runtime's concurrency limit. Refs: #6916 Co-Authored-By: Claude Opus 5.5 --- .../bugs/fix-6916-upstream-pointers-a3b43c16.md | 7 +++++++ .../fix-6916-upstream-pointers-96bf3770.md | 7 +++++++ .../fix-6916-upstream-pointers-c287750c.md | 7 +++++++ .../fix-6916-upstream-pointers-a523cb24.md | 7 +++++++ .github/actions/resolve-config/README.md | 15 ++++++++++++--- plugins/bugs/skills/scan/SKILL.md | 12 +++++++++--- .../context-guard/reference/reader-contract.md | 5 +++-- plugins/guardrails/.claude-plugin/plugin.json | 2 +- plugins/guardrails/README.md | 4 ++-- plugins/user-experience/agents/evaluator.md | 5 +++-- 10 files changed, 58 insertions(+), 13 deletions(-) create mode 100644 .changes/bugs/fix-6916-upstream-pointers-a3b43c16.md create mode 100644 .changes/context-guard/fix-6916-upstream-pointers-96bf3770.md create mode 100644 .changes/guardrails/fix-6916-upstream-pointers-c287750c.md create mode 100644 .changes/user-experience/fix-6916-upstream-pointers-a523cb24.md diff --git a/.changes/bugs/fix-6916-upstream-pointers-a3b43c16.md b/.changes/bugs/fix-6916-upstream-pointers-a3b43c16.md new file mode 100644 index 00000000000..ef6ec35d46d --- /dev/null +++ b/.changes/bugs/fix-6916-upstream-pointers-a3b43c16.md @@ -0,0 +1,7 @@ +--- +bump: patch +--- + +### Fixed + +- `/bugs:scan` gives its `opus` fallback a reason, notes that the harness can run a blocked alias on another model instead of rejecting the dispatch, and points at the sub-agents model section with an as-of date and recheck trigger. diff --git a/.changes/context-guard/fix-6916-upstream-pointers-96bf3770.md b/.changes/context-guard/fix-6916-upstream-pointers-96bf3770.md new file mode 100644 index 00000000000..cbab4f26ff4 --- /dev/null +++ b/.changes/context-guard/fix-6916-upstream-pointers-96bf3770.md @@ -0,0 +1,7 @@ +--- +bump: patch +--- + +### Fixed + +- The reader contract's subagent `autoCompactWindow` row points at the sub-agents docs section that documents the field, in place of the changelog, and no longer says the surface appears only there. diff --git a/.changes/guardrails/fix-6916-upstream-pointers-c287750c.md b/.changes/guardrails/fix-6916-upstream-pointers-c287750c.md new file mode 100644 index 00000000000..5a63b90e5fd --- /dev/null +++ b/.changes/guardrails/fix-6916-upstream-pointers-c287750c.md @@ -0,0 +1,7 @@ +--- +bump: patch +--- + +### Fixed + +- The `workflow-resilience-check` description says the fan-out it flags has no wave cap of its own, in place of calling it un-throttled, and points at the workflow runtime's concurrency limit. diff --git a/.changes/user-experience/fix-6916-upstream-pointers-a523cb24.md b/.changes/user-experience/fix-6916-upstream-pointers-a523cb24.md new file mode 100644 index 00000000000..5aa17f6e2c2 --- /dev/null +++ b/.changes/user-experience/fix-6916-upstream-pointers-a523cb24.md @@ -0,0 +1,7 @@ +--- +bump: patch +--- + +### Fixed + +- The `evaluator` agent's model and effort pins carry their reasons, and the effort pin points at the upstream effort table with an as-of date and recheck trigger. diff --git a/.github/actions/resolve-config/README.md b/.github/actions/resolve-config/README.md index fb609509d7f..6d9a6197d7e 100644 --- a/.github/actions/resolve-config/README.md +++ b/.github/actions/resolve-config/README.md @@ -121,8 +121,13 @@ the `limits` ([README, Limits](../../../docs/conventions/pr-pipeline/README.md#l that profile's `model`, `effort` (null when unset), `subagent-model` (`inherit` when unset) and `max-turns`, from its activity's route, else `models.default-profile`, else, with no `models` block, the built-in `standard` profile (model `opus`, 75 turns); a model outside `haiku`, -`sonnet` and `opus` resolves to `opus`; at input `model-rung` 1 the -profile's `escalate-to` replaces it, one rung at most; a script slot carries `models` +`sonnet` and `opus` resolves to `opus`. That excludes the frontier aliases `fable` and `best` on +purpose: the lanes run no frontier model until the owner sets a Fable allowance for them, and the +schema refuses both on a profile (`pr-pipeline.schema.json`, `model` and `subagent-model`), so +this rule catches a config that reached the resolver unchecked. The upstream alias list is +[model-config, Model aliases](https://code.claude.com/docs/en/model-config#model-aliases), as of +2026-10-31; recheck when an alias is added or retired. At input `model-rung` 1 the +profile's `escalate-to` replaces that profile, one rung at most; a script slot carries `models` null. A skill slot with input `issue`, in a config with `models.issue-dimensions`, also carries `issue-dimensions` and `timeout-minutes`, and its `max-turns` is the dimensions' turn cap; its Complexity's `complexity-profiles` entry, when there is one, replaces the route's profile. The @@ -171,7 +176,11 @@ issue dimensions. `args` is free text and stays in the file. `claude-args` is `--model `, then `--max-turns `, then `--effort ` when the profile sets one; `settings-json` is -`{"env":{"CLAUDE_CODE_SUBAGENT_MODEL":""}}`, or empty for `inherit`. Both are built only +`{"env":{"CLAUDE_CODE_SUBAGENT_MODEL":""}}`, or empty for `inherit`, which upstream treats +the same as unset. The variable is a default a spawn's `model` or an agent's frontmatter outranks: +[sub-agents, Choose a model](https://code.claude.com/docs/en/sub-agents#choose-a-model), as of +2026-10-31; recheck when that section changes the variable's rank or its `inherit` value. +`claude-args` and `settings-json` are built only from schema enums and an integer, and the step fails on any other `claude-args` shape. `model` and `effort` are the same values for a caller on ci-workflows' `run-claude-cli`: `model` is the alias; `effort` is empty when the profile sets none. A script gets all six model outputs empty. diff --git a/plugins/bugs/skills/scan/SKILL.md b/plugins/bugs/skills/scan/SKILL.md index 6f1bdc4cae6..285c83aaf79 100644 --- a/plugins/bugs/skills/scan/SKILL.md +++ b/plugins/bugs/skills/scan/SKILL.md @@ -158,14 +158,20 @@ resolved effort is lower, pass no `effort`. When `/multi-agent:route` does not resolve, omit the model for both stages so they inherit the session's, except when the session model is frontier or unknown, where pass `opus`; say once in the -report that enabling the multi-agent plugin makes this routing configurable. With no role map, gates -pass no `effort` either. Pointer: for the per-spawn +report that enabling the multi-agent plugin makes this routing configurable. The `opus` fallback is +this skill's stand-in for the fan-out guard `/multi-agent:route` applies: it keeps a wide fan-out +off the frontier tier; which model the alias then runs on is the harness's call (model pointer +below). With no role map, gates pass no `effort` either. Pointer: for the per-spawn `effort` and its precedence, see . As of: 2026-10-10. Recheck trigger: that section changes precedence or which spawns honor `effort`. Name the model and effort each stage was dispatched with in the run metadata: the level passed, or `session` when none was. A dispatch the harness rejects means the role map names an alias this -session cannot use: report it rather than substitute one. +session cannot use: report it rather than substitute one. The harness can also run a blocked alias +on another model without rejecting it, so the metadata names the model asked for, not proof of the +model that ran. Pointer: for how a spawn's `model` alias resolves and what happens to a blocked +one, see . As of: 2026-10-31. Recheck +trigger: that section changes how an alias resolves or how a blocked value is handled. **Breadth by scope.** After Step 1 enumerates the files (test suites excluded), classify the scope: diff --git a/plugins/context-guard/reference/reader-contract.md b/plugins/context-guard/reference/reader-contract.md index f3db2b184a0..4fd5a8136f2 100644 --- a/plugins/context-guard/reference/reader-contract.md +++ b/plugins/context-guard/reference/reader-contract.md @@ -466,7 +466,7 @@ precedence. | Surface | Kind | What this plugin relies on | Pointer | |---|---|---|---| | `autoCompactWindow` | settings key (top level or per model) | A token count that moves the trigger for the model it applies to. Unset, the default is the docs' default-thresholds table (pointer above); set where we cannot see it, we assume no number (below). Normalize it into the percentage shape before comparing (below). | [settings-reference: `autoCompactWindow`](https://code.claude.com/docs/en/settings-reference#autocompactwindow); [settings-reference: `modelSettings`](https://code.claude.com/docs/en/settings-reference#modelsettings); [model-config: Set the auto-compact window](https://code.claude.com/docs/en/model-config#set-the-auto-compact-window) | -| `autoCompactWindow` | subagent frontmatter | A subagent can carry its own window (Claude Code 2.1.296). The snapshot cannot see that window, and the surface is in the changelog only and not probed, so we never assume a subagent shares the session's trigger. | [Claude Code changelog](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md) | +| `autoCompactWindow` | subagent frontmatter | A subagent can carry its own window. The snapshot cannot see that window, and the surface is not probed, so we never assume a subagent shares the session's trigger. | [sub-agents: Set the auto-compact window for one subagent](https://code.claude.com/docs/en/sub-agents#set-the-auto-compact-window-for-one-subagent) | | `CLAUDE_CODE_AUTO_COMPACT_WINDOW` | environment variable | Read as the effective window whenever it is set, ahead of the setting, the command, and the flag. | [env-vars: Variables](https://code.claude.com/docs/en/env-vars#variables) | | `CLAUDE_AUTOCOMPACT_PCT_OVERRIDE` | environment variable | Read as able only to move the trigger earlier, never later. | [env-vars: Variables](https://code.claude.com/docs/en/env-vars#variables) | | `autoCompactEnabled` / `DISABLE_AUTO_COMPACT` | `settings.json` key / environment variable | Either one turning auto-compact off leaves the dumb band as the only tripwire. `DISABLE_AUTO_COMPACT` leaves the manual `/compact` command available. | [settings-reference: `autoCompactEnabled`](https://code.claude.com/docs/en/settings-reference#autocompactenabled); [env-vars: Variables](https://code.claude.com/docs/en/env-vars#variables) | @@ -476,7 +476,8 @@ We read a configured window above the model's context window as the model's wind nothing. - **Pointer**: per row above. -- **As of**: 2026-10-10 for the two `autoCompactWindow` rows; 2026-10-15 for the +- **As of**: 2026-10-10 for the settings `autoCompactWindow` row; 2026-10-31 for the subagent + frontmatter `autoCompactWindow` row; 2026-10-15 for the `DISABLE_COMPACT` entry and the `DISABLE_AUTO_COMPACT` manual-`/compact` sentence; 2026-08-19 for the other rows. - **Recheck trigger**: a release note or one of those sections changes a surface's units, range, diff --git a/plugins/guardrails/.claude-plugin/plugin.json b/plugins/guardrails/.claude-plugin/plugin.json index 0adbe541852..180fc5529c2 100644 --- a/plugins/guardrails/.claude-plugin/plugin.json +++ b/plugins/guardrails/.claude-plugin/plugin.json @@ -159,7 +159,7 @@ "workflow_resilience_check_enabled": { "type": "boolean", "title": "Workflow-resilience-check guard", - "description": "Advises on un-throttled Workflow fan-out; never blocks. Off by default since 0.20.0: a behavioral-class prose injector, config-disabled per the instruction-economy evidence gate (#2021). Set true to opt back in.", + "description": "Advises on Workflow fan-out with no wave cap of its own; never blocks. Off by default since 0.20.0: a behavioral-class prose injector, config-disabled per the instruction-economy evidence gate (#2021). Set true to opt back in.", "default": false }, "flag_commit_pr_skill_bypass_enabled": { diff --git a/plugins/guardrails/README.md b/plugins/guardrails/README.md index 168cedd873b..ac3f5fdba5d 100644 --- a/plugins/guardrails/README.md +++ b/plugins/guardrails/README.md @@ -92,7 +92,7 @@ A mod can also approve a call they blocked, because its `tool.check` hook runs a | **block-unresolved-pr-merge** | PreToolUse · Bash \| PowerShell **and** `mcp____merge_pull_request` \| `mcp____enable_pr_auto_merge` | **Blocks** (exit 2) | A pull-request merge while the PR has an unresolved review thread (outdated ones included), a reviewer whose latest decisive review requests changes, or a failed check run or commit status on its head commit (only the newest run of each check by creation order counts, so a run a later run of the same check superseded does not block; a skipped or neutral run never supersedes a completed run with a real conclusion, though it does supersede a pending or cancelled one; a cancelled run is also superseded by a newer successful run of the same app, in another check suite, named ` (...)` (a skipped, neutral or failed leg does not clear it), since a matrix job cancelled before it expanded reports under its bare name, and an unrelated workflow's ` (...)` job in another suite clears it too, which the check-runs payload cannot tell apart; a check listed in `merge_guard_ignored_checks` as `:`, by default `github-actions:merge`, the pr-merge lane's own job, is never judged, and since a check run does not name its workflow, every GitHub Actions job named `merge` is ignored by that default; a failed run whose failure annotation says it was `superseded by full run /actions/runs/ in flight on `, as the contract-only ci-status does, does not count: that full run's run of the same check decides, and the check is pending until it exists); a pending check blocks an immediate merge but not an auto-merge or merge-queue request, which waits for checks by design. Merge paths: `gh pr merge` with any flags (`--admin` and `--auto` included), a `PUT` to `repos/{owner}/{repo}/pulls/{n}/merge` or to the Claude Code cloud route `pulls/{n}/ccr/auto_merge` through `gh api` or `curl`, the `mergePullRequest`, `enablePullRequestAutoMerge` and `enqueuePullRequest` GraphQL mutations through `gh api graphql` or `curl`, and the GitHub MCP server's merge tools under any server prefix. PR state is read over REST; review-thread resolution, which REST does not expose, comes from GraphQL where it is served and from the cloud route `pulls/{n}/ccr/review_threads` where GraphQL is refused (Claude Code on the web). Fails open with a notice to both the user and Claude when `gh` is missing or unauthenticated, a read fails, or its 35 s read budget runs out (kept under the row's 60 s timeout). An unresolvable target fails closed: a `gh pr merge` or REST merge whose repo or PR number comes from a shell variable, `$(...)` or backticks, or a bare `gh pr merge` whose current branch cannot be read or has no open PR, is blocked with the fix of writing `gh pr merge -R owner/repo` literally. So is, on the Bash tool, a command whose text is merge-shaped (`pr merge` after a word that is `gh` or cannot be read, such as `g""h` or `$GH`, a `pulls/.../merge` route, a merge mutation name; prose such as "Gated PR Merge" is not) and holds a backtick anywhere, quoted or not (pass a body that holds one with `--body-file`), a `pr merge` or REST merge route continued with a backslash-newline (write the merge on one line; the command is never rewritten), and a command holding more than one merge (run each merge as its own command). The backtick and backslash-newline tests skip the body of a quoted heredoc (`<<'EOF'`) fed to a program that is not a shell, such as `python3 - <<'EOF'` or `git commit -F - <<'MSG'`; the guard header lists when a body is still read. So is a `gh pr` subcommand or a `-X` method taken from an expansion on a merge route (`gh pr $VERB`, `-X "$M"`), and a `gh pr merge` with no `-R` or URL in a command that also runs `cd`, `pushd` or `popd` or names `GH_REPO`, since it then merges outside the session's repository. A `-R HOST/OWNER/REPO` is read without its host (a host other than github.com goes to `gh api --hostname`), a quote-split `gh pr mer"ge"` is parsed, a branch name is percent-encoded into the lookup, and a 404 on a repo the command wrote is blocked instead of run unchecked. So is a GraphQL merge mutation whose PR cannot be resolved (an id from a variable or `$(...)`, or more than one id bound to `pullRequestId`), with the fix of passing a literal `PR_...` id. Only the id bound to `pullRequestId` is checked, never a `PR_...` in another field. In a Claude Code cloud session GraphQL is refused, so every GraphQL merge mutation is blocked there; use `gh pr merge `. A `curl -T` / `--upload-file` to the merge route counts as a `PUT`. `gh pr merge --help` and `--disable-auto` are not merges. Not covered: a merge from a script (Python, Node) or the web UI; the org ruleset requiring conversation resolution is the server-side backstop. A merge pays five REST calls, plus one per failed check run (three at most) to read its annotations, measured at 3.0 to 3.6 s in a Claude Code cloud session; any other command pays one string test. The guard header in `hooks/block-unresolved-pr-merge.sh` lists the known gaps. Escape: `block_unresolved_pr_merge_enabled` (off switch); `merge_guard_ignored_checks` (comma list of `:` checks never judged; empty judges all). | | **block-fix-request-post** | PreToolUse · Bash \| PowerShell **and** the GitHub MCP comment, review, issue and pull-request write tools (`mcp__github__add_issue_comment`, `pull_request_review_write`, and the rest named in `hooks/hooks.json`) | **Blocks** (exit 2) | An agent posting the PR-fix lane fix request: a line starting `PR-fix lane: please fix this finding`, any case, which the address-feedback lane (`FIX_REQUEST` in `.github/scripts/pr-unblock/address-feedback.mjs`) acts on with push credentials when someone with write access posts it. A local session posts with the owner's token, so only the owner posts it, typed in the GitHub UI ([#8438](https://github.com/melodic-software/claude-code-plugins/issues/8438)). Covers `gh pr\|issue comment\|review\|create\|edit`, a writing `gh api` (GraphQL only for a mutation), and `curl` with a body to a GitHub API route; the body is read inline, from heredocs, and from every `--body-file`, `-F k=@file`, `--input`, `-d @file`, `cat` or `<` file. A line after `>`, inside a fence, or a mention later in a line passes, as does a command that only reads or greps the phrase. The guard header lists the known gaps. Escape: `block_fix_request_post_enabled`. | | **cli-flag-verify** | git pre-push, `reference-verify` entry, on `.md`, `.sh`, `.bash`, `.ps1`, `.psm1` | **Fails the push** (exit 1) | Hallucinated CLI flags: a `--flag` written as a command, on a line the pushed commits add, that does not exist in the binary's actual `--help` output. | -| **workflow-resilience-check** | PreToolUse · Workflow | **Advisory** (exit 0) | Un-throttled Workflow fan-out: a script calling `parallel()` / `pipeline()` with no wave-cap throttle (`inWaves` / `inWavesPipeline`) and no retry wrapper (`agentRetry`), which risks a burst 529 under wide Opus fan-out. Surfaces a one-line advisory via `additionalContext` that points at the workflow-authoring skill and names the overloaded-retry backoff ceiling variable with a link to its docs section, never blocks. **Opt-in. Default off since 0.20.0** (behavioral-class injector config-disabled per #2021; set `workflow_resilience_check_enabled=true` to enable). | +| **workflow-resilience-check** | PreToolUse · Workflow | **Advisory** (exit 0) | Workflow fan-out with no wave cap of its own: a script calling `parallel()` / `pipeline()` with no wave-cap throttle (`inWaves` / `inWavesPipeline`) and no retry wrapper (`agentRetry`), which risks a burst 529 under wide Opus fan-out. The runtime's own concurrency limit still applies ([workflows: Behavior and limits](https://code.claude.com/docs/en/workflows#behavior-and-limits), as of 2026-10-31; recheck when that limit or its default changes). Surfaces a one-line advisory via `additionalContext` that points at the workflow-authoring skill and names the overloaded-retry backoff ceiling variable with a link to its docs section, never blocks. **Opt-in. Default off since 0.20.0** (behavioral-class injector config-disabled per #2021; set `workflow_resilience_check_enabled=true` to enable). | | **block-noncanonical-commit** | PreToolUse · Bash \| PowerShell | **Blocks** (exit 2) | `git commit -m` whose message holds a `$` or a backtick the shell expands before git sees it: double-quoted or unquoted in Bash (`$x`, `$(...)`, backticks), double-quoted in PowerShell (`$x`, and a backtick escape such as `` `f ``), and a PowerShell `@"` here-string. A newline alone is no hazard, so a plain message passes, multi-line included, and so do single quotes, fully escaped double quotes, Bash `"$(cat <<'EOF' ... EOF)"` and a PowerShell `@'` here-string; `-F -` / `--file -` is always safe. Exempt: `--amend`, `-C`/`-c`/`--reuse-message`/`--reedit-message`, `--fixup`/`--squash`, `-F `, and any commit taken while a merge/rebase/cherry-pick/revert is in progress. Resolves `bash -lc` wrappers and git aliases (inline `-c` and persisted config alike). | | **block-convention-violation** | PreToolUse · Bash \| PowerShell | **Blocks** (exit 2) | A commit subject or `gh pr create --title` that violates the team-tracked convention pattern declared in `docs/conventions/source-control.yaml` (for one release, else `.claude/source-control.md`). No tracked pattern means no enforcement. Same exemptions as `block-noncanonical-commit`. | | **flag-commit-pr-skill-bypass** | PreToolUse · Bash \| PowerShell | **Advisory** (exit 0) | Any `gh pr create`, bypassing this marketplace's own `/source-control:pull-request` skill. Only fires when the consuming project's own `.claude/settings.json` enables the `source-control` plugin, and is silent otherwise. Surfaces via `additionalContext` once per session and agent, never blocks. **Opt-in. Default off since 0.20.0** (behavioral-class injector config-disabled per #2021; set `flag_commit_pr_skill_bypass_enabled=true` to enable). | @@ -1647,7 +1647,7 @@ reads it from. | `block_noncanonical_commit_allow` | string | *(none)* | `CLAUDE_PLUGIN_OPTION_BLOCK_NONCANONICAL_COMMIT_ALLOW` | Comma-separated form tokens block-noncanonical-commit permits. The only token today is message-flag, which permits a -m message the shell would expand. Empty, the default, permits none. | | `block_convention_gate_enabled` | boolean | `true` | `CLAUDE_PLUGIN_OPTION_BLOCK_CONVENTION_GATE_ENABLED` | Blocks a commit subject or gh pr create --title that violates the team-tracked convention pattern in docs/conventions/source-control.yaml, or for one release in .claude/source-control.md. On by default; with no tracked pattern nothing is enforced. Same exemptions as block-noncanonical-commit. | | `git_hooks_notice_enabled` | boolean | `true` | `CLAUDE_PLUGIN_OPTION_GIT_HOOKS_NOTICE_ENABLED` | At session start, names /guardrails:setup apply install-git-hooks once when this clone lacks a guardrails git-hook entry or holds a drifted one; a declined entry stays quiet. Turning it off also silences the session-start notice that jq is missing. On by default. | -| `workflow_resilience_check_enabled` | boolean | `false` | `CLAUDE_PLUGIN_OPTION_WORKFLOW_RESILIENCE_CHECK_ENABLED` | Advises on un-throttled Workflow fan-out; never blocks. Off by default since 0.20.0: a behavioral-class prose injector, config-disabled per the instruction-economy evidence gate (#2021). Set true to opt back in. | +| `workflow_resilience_check_enabled` | boolean | `false` | `CLAUDE_PLUGIN_OPTION_WORKFLOW_RESILIENCE_CHECK_ENABLED` | Advises on Workflow fan-out with no wave cap of its own; never blocks. Off by default since 0.20.0: a behavioral-class prose injector, config-disabled per the instruction-economy evidence gate (#2021). Set true to opt back in. | | `flag_commit_pr_skill_bypass_enabled` | boolean | `false` | `CLAUDE_PLUGIN_OPTION_FLAG_COMMIT_PR_SKILL_BYPASS_ENABLED` | Advises when a direct gh pr create bypasses the source-control pull-request skill; never blocks. Off by default since 0.20.0: a behavioral-class prose injector, config-disabled per the instruction-economy evidence gate (#2021). Set true to opt back in. | | `stdin_read_timeout` | number
*min 1* | `2` | `CLAUDE_PLUGIN_OPTION_STDIN_READ_TIMEOUT` | Idle bound on reading the hook payload from stdin: how long a silent pipe is tolerated before a blocking guard fails closed. Default 2. Only a JSON payload the pipe closed on mid-document is allowed with a notice; a stalled pipe stays a block. | diff --git a/plugins/user-experience/agents/evaluator.md b/plugins/user-experience/agents/evaluator.md index 1633342912a..d67caead2bd 100644 --- a/plugins/user-experience/agents/evaluator.md +++ b/plugins/user-experience/agents/evaluator.md @@ -2,8 +2,9 @@ name: evaluator description: "Fresh-context UX evaluator: judges a flow, journey or synthesis produced earlier in the same session against the method its brief names, and returns findings only. Dispatched by /user-experience:evaluate with the artifact's path and the method; not intended for direct ad-hoc use." tools: Read, Grep, Glob -model: opus -effort: high +model: opus # reason: this repository's choice; a fresh-context judge of another agent's artifact gets a strong model, and no upstream page sets one +# effort: https://code.claude.com/docs/en/model-config#choose-an-effort-level, as of 2026-10-31; recheck when that table's levels or rows change +effort: high # reason: an evaluation is verification work, which the linked table maps to this level maxTurns: 30 --- From b9651fd1165232b3545f1fa68c35a9bb6e377902 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Sat, 31 Oct 2026 17:56:37 -0400 Subject: [PATCH 2/2] docs(bugs): keep blocked-alias behavior behind the scan pointer The scan body described what the harness does with a blocked alias, which restates upstream behavior the pointer already covers. Keep the local statement that the metadata names the requested model, and the dated sub-agents pointer. Refs: #6916 Co-Authored-By: Claude Opus 5.5 --- .changes/bugs/fix-6916-upstream-pointers-a3b43c16.md | 2 +- plugins/bugs/skills/scan/SKILL.md | 5 ++--- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/.changes/bugs/fix-6916-upstream-pointers-a3b43c16.md b/.changes/bugs/fix-6916-upstream-pointers-a3b43c16.md index ef6ec35d46d..ee71eea82f7 100644 --- a/.changes/bugs/fix-6916-upstream-pointers-a3b43c16.md +++ b/.changes/bugs/fix-6916-upstream-pointers-a3b43c16.md @@ -4,4 +4,4 @@ bump: patch ### Fixed -- `/bugs:scan` gives its `opus` fallback a reason, notes that the harness can run a blocked alias on another model instead of rejecting the dispatch, and points at the sub-agents model section with an as-of date and recheck trigger. +- `/bugs:scan` gives its `opus` fallback a reason, says its run metadata names the model asked for rather than proving the model that ran, and points at the sub-agents model section with an as-of date and recheck trigger. diff --git a/plugins/bugs/skills/scan/SKILL.md b/plugins/bugs/skills/scan/SKILL.md index 285c83aaf79..1cadbb1e5fc 100644 --- a/plugins/bugs/skills/scan/SKILL.md +++ b/plugins/bugs/skills/scan/SKILL.md @@ -167,9 +167,8 @@ As of: 2026-10-10. Recheck trigger: that section changes precedence or which spa Name the model and effort each stage was dispatched with in the run metadata: the level passed, or `session` when none was. A dispatch the harness rejects means the role map names an alias this -session cannot use: report it rather than substitute one. The harness can also run a blocked alias -on another model without rejecting it, so the metadata names the model asked for, not proof of the -model that ran. Pointer: for how a spawn's `model` alias resolves and what happens to a blocked +session cannot use: report it rather than substitute one. The metadata names the model asked for, +not proof of the model that ran. Pointer: for how a spawn's `model` alias resolves and what happens to a blocked one, see . As of: 2026-10-31. Recheck trigger: that section changes how an alias resolves or how a blocked value is handled.