Repository navigation
Description
Plugin: context-budget@melodic-software v0.6.10 · Measured against: Claude Code 2.1.241,
C:\Users\KyleSexton\.local\bin\claude.exe · Mode: sdk (exact), headless · Platform:
Windows 11, cwd $HOME (nonrepo state key) · Agent SDK 0.3.241
Audited after a real end-to-end run: /context-budget:setup check + apply, then
/context-budget:audit --full-sweep (27 tools + additivity), then an applied lever with a
before/after ledger row. Three components in scope: the audit skill, the setup skill, and the
settings-write-ask PreToolUse hook.
Severities are the auditors' own, uncalibrated (no human calibration was applied).
HIGH
H1 — --verify-additivity cannot detect non-additivity on a full sweep
combinedSaved for the observed run was 24,197 — exactly 10854 + 13343, the entire attributed
payload. systemBucketSaving (measure.mjs:610-614) sums both bucket deltas, and a combined deny
drives both to zero, so on any full sweep the check degenerates to sumOfParts === baselineTotal.
It reports additive: false whether or not anything is wrong.
Reproduced: denying only the 11 prefix savers leaves 13 live tools including ToolSearch (worth
+15,824 prefix when denied) and the SDK still omits the bucket, which the engine records as a
measured 0.
Fix: add a saturation guard — additive: null with a reason when either bucket is a synthesized
zero, plus an epsilon. Report additivity per bucket; the data is already on every perTool row.
H2 — SKILL.md's "deltas add" is false as written
SKILL.md:18 claims A/B differencing "is compositional (deltas add), so a basket of trims can be
priced from its members", unconditionally. Non-additivity is real, established from three clean
non-saturated readings: baseline 10,557; denying the 10 prefix savers other than PowerShell →
2,399 (−8,158, shortfall exactly zero); PowerShell solo → −3,355. PowerShell stays live in the
10-deny run, so its marginal contribution is bounded by the 2,399 remaining while its solo value is
3,355 — at least 956 tokens double-counted, with no synthesized zero anywhere in that argument.
Deferred-side additivity, by contrast, is exact: 12 deferred savers summed to 13,343 (the bucket, to
the token), and a 3-tool basket predicted 4,608 and measured 4,608.
The skill-frontmatter-subtraction hypothesis is dead: compareSnapshots requires both sigMatch
and skillTokensMatch (measure.mjs:551-558, 588), so a constant subtraction cancels in a delta;
independently confirmed 1:1 — a 297-token skill moved Skills +297 and System tools −297.
Fix: qualify the claim per bucket in both homes — SKILL.md:18 and
levers.json → deny-bare-tool.categoryBasis (SSOT duplication). Ship with H1 or it is cosmetic.
H3 — measure.mjs:723 discards every deny run's caveats
attribute returns caveats: baseline.caveats, so caveats raised by any deny run — including the
synthesized-zero disclosure promised at engine.md:76-79 — never reach the record. This is what
made H1 shippable: the instrument's own disclosure channel is severed.
Fix: merge deny-run caveats into the attribution record. Smallest diff, highest value in this
report — do this one first regardless of the rest.
H4 — measured counterexample to deny-bare-tool.mechanism (possibly UPSTREAM)
With a bare-name permissions.deny entry for EndConversation in force, the tool remained in
the interactive session's deferred registry, ToolSearch select:EndConversation returned its full
schema, and the call succeeded (the session ended). Verified verbatim against the permissions page
(WebFetch + curl, 498,122 bytes, 2026-08-24): "Bare-name deny rules like Bash remove the tool
from Claude's context before this evaluation begins", and the options table's "The Bash tool
definition is removed from the request. Claude does not see the tool and cannot attempt it." No
carve-out for any tool appears there.
The same mechanism demonstrably works on this machine for other deferred tools: 27 → 24 live,
deferred bucket −4,608, exact. So this is tool-specific, not general breakage.
The row's recheckTrigger is structurally blind to it. It reads "a measured bare-name deny stops
moving the System tools buckets", but EndConversation never enters either bucket headless — the
trigger could never fire for this case. That is a defect in the trigger's design, not a missing row.
⚠️ Likely upstream. The plugin cites the docs accurately; the docs and the binary disagree.
Please do not "fix" a correct citation. Consider escalating to Anthropic.
Fix: add EndConversation to interactive-only-tools.json; record the deny-no-op as a measured
counterexample; widen deny-bare-tool.recheckTrigger to cover tools appearing in neither attributed
bucket.
H5 — apply's scope guidance is refuted on both branches
setup's apply says to "pass the scope claude plugin list reports for this plugin … or the write
lands at a scope that does not load." Both branches fail: project-scope pluginConfigs is ignored
outright per docs, or the write goes to user settings regardless and the -s/cwd ceremony is
inert. It also omits that -s governs enabledPlugins placement, so following it can install the
plugin at a new scope and create a stray <cwd>/.claude/settings.json.
Observed trigger: with cwd == $HOME, claude plugin list reported this plugin twice (user
and project) because project scope resolves to <cwd>/.claude/settings.json — byte-identical to
the user path. One file, two rows. The auditing session initially acted on that and gave the operator
wrong advice.
Fix: replace with doc-grounded facts — default user; -s governs enablement placement;
plugin list can show one file under two labels. Resolve the disjunction before finalizing wording.
H6 — check step 1 cannot detect the failure its own rationale describes
Step 1 argues the hook registers in exec form ("command": "node"), so a bare node must resolve
in the hook's environment, and that an unresolvable node means the checkpoint silently never
fires while the option still reads true. But the prescribed probe is command -v node, which under
fnm returns a per-call ephemeral multishell path (AppData\Local\fnm_multishells\<pid>_<ts>\node
— three probes in one session returned PIDs 64452, 64196, 33540). That is neither the hook's
environment nor the persisted PATH. The check PASSes and stops.
The Windows caveat that would catch this ("confirm the hook's environment resolves the same node")
is filed under the Missing node bullet — reachable only on FAIL. The failure it describes is a
PASS-path failure.
Fix: on Windows, resolve against persisted Machine+User PATH, report in-process resolution
separately, flag PID-bearing shim paths as ephemeral, FAIL when only an ephemeral hit exists.
Ambitious version: a check --deep that fires the PreToolUse path against a throwaway
settings-shaped path and confirms the ask actually arrives.
MEDIUM
M1 — hook matcher cannot see shell writes, but the claim says "any settings-surface write"
Matcher is Write|Edit|MultiEdit|NotebookEdit. A PowerShell Set-Content or a Bash heredoc to
~/.claude/settings.json bypasses the checkpoint entirely, so SKILL.md:224's "any settings-surface
write" and the header's "the ordinary auto-mode path cannot rewrite settings silently" are both
overclaimed. The bypass enumeration names two exotic escapes (PermissionRequest, disableAllHooks)
and omits the reachable one.
Found independently by two auditors, in separate packets. Corroborated in-session: an inline
node -e write to a settings-composing file was stopped by the auto-mode classifier, while the
Edit path — the one the matcher covers — went through.
Fix: extend the matcher to Bash|PowerShell, or keep it and reword the claim. Do not ship
the current claim with the current matcher. (Extending has real false-positive cost; honest scoping
is likely the better fix.)
M2 — the hook does not cover render-into-settings sources (chezmoi class)
The regex (settings-write-ask.mjs:45-46) matches only .claude/settings.json,
.claude/settings.local.json, and managed-settings.json. Four Edit calls landed on
~/.local/share/chezmoi/.chezmoidata/claude.json — which provably composes the deployed
~/.claude/settings.json (chezmoi source-path → dot_claude/modify_settings.json, which consumes
it) — with no ask.
Reranked up on evidence: .claude is a protected directory and .mcp.json/.claude.json are
protected files, so on most paths this hook matches it largely duplicates harness protection. The
in-cwd non-protected file (this class) is the one write path with no harness review at all.
managed-settings.json is on neither protected list and is the hook's only genuinely non-redundant
coverage.
Fix: at minimum document the scope boundary. A general solution is hard (arbitrary templating),
but the class is real and recognizable.
M3 — disable-artifact is offerable but structurally unmeasurable
The row is removes-weight / recommendable-on-fit, yet its own measurement field prescribes
attribute --tools Artifact, and Artifact is in interactive-only-tools.json — never a headless
candidate. Both halves of the route are dead inside the skill's declared scope. Applied live here,
the Skills delta was 0 because the artifact-* skills never enter a headless listing.
knownUncovered protects tools from exactly this misreading; there is no lever-side
equivalent. report.md's "Zeros are findings" then requires publishing the zero — so the contract
actively causes a working lever to be reported as inert.
Fix: add a lever-side unmeasurable-in-this-session-kind marker plus a report.md rule
rendering such levers in their own group rather than as zeros.
M4 — knownUncoveredRecord attributes operator-caused absence to product structure
It computes listing.tools − candidates (measure.mjs:634-641), so AskUserQuestion,
EnterPlanMode, and ExitPlanMode — absent because the operator bare-name-denied them — are
reported under "interactive-only — structurally unreachable."
Fix: subtract known deny entries before attributing absence to interactive-only status.
M5 — works-but-saves-nothing-here asserts a consumer-specific fact statically
skillOverrides / disable-bundled-skills are stored with that category, conditional on cap
saturation. Measured here the cap was slack (13/13 included, 0 collapsed, 2,111 tokens against a
~30,000 budget at skillListingBudgetFraction: 0.03), so the condition resolves the opposite way and
the levers would genuinely remove weight. Separately the saturation signal those rows name is absent
from the record and unit-mismatched (tokens vs characters).
Fix: split into stored mechanism + runtime-resolved saving; note the token-vs-character unit
change wherever the listing budget appears.
M6 — meta.purpose claims completeness that verify-catalogue cannot check
The catalogue claims to hold "every known operator-controllable switch", but verify-catalogue is
one-directional: it confirms stored tokens exist in the binary and cannot see existing-but-unstored
switches. Binary scan of 2.1.241 found CLAUDE_CODE_DISABLE_CRON and CLAUDE_CODE_ENABLE_DESIGN_SYNC
with no rows. (RemoteTrigger / PushNotification genuinely have no native switch — same scan — so
deny is correct for those.)
Fix: add --find-unstored to verify-catalogue; ENV_TOKEN_RE is already the right regex.
M7 — SDK data is fetched and thrown away
The SDK returns per-skill tokens (summing exactly to the Skills bucket) and slashCommands;
measure.mjs:396 discards both. Fix: keep skillFrontmatter[].tokens + pluginName; record
slashCommands in the snapshot.
M8 — a headless artifact is attributed to bypassPermissions
SKILL.md stamps the hook's block behavior as measured at v2.1.232 under bypassPermissions. The
measurement is not wrong; the attribution is imprecise. Re-verified this audit at 2.1.241 across
three headless probes — default, auto, and bypassPermissions — all fired and blocked, no file
created. Fix: re-stamp to 2.1.241 and scope the claim to what was actually exercised.
M9 — custom-output-style detection has no built-in-style branch
Detection reads "keep-coding-instructions in the style's frontmatter", but a built-in style has no
frontmatter file. Confirmed live: outputStyle: "Concise" set, ~/.claude/output-styles/ absent.
M10 — apply prints a write-causing command without the never-run marker
The network-only npm install carries an explicit "operator's to run" marker; the
claude plugin install … --config command — which writes pluginConfigs — does not. An agent
executing apply can therefore cause exactly the write the skill's own contract forbids.
LOW
- L1 —
nonrepocwd additionally drops project settings,.mcp.json, and CLAUDE.md discovery;
nothing states the reported total is a floor. State it inreport.md§1. - L2 —
--full-sweep(argument-hint) vs--tools from-baseline(engine flag); disclosed at
SKILL.md:101, cosmetic. - L3 — the "uninstall drops the entire stored
pluginConfigsentry" claim carries no version
stamp while the--configclaim two sentences earlier does — inconsistent evidence discipline
inside one paragraph. - L4 — step 4's template renders "Report the effective
true": the sentence has no noun.
One-word fix, not a malformed template. - L5 — the printed npm remediation is POSIX shell handed to a Windows operator to run themselves.
- L6 — the skill names an SSOT then restates all three prerequisites inline anyway (drift
surface).
OPEN QUESTION — not a finding, and no remediation depends on it
During this session, four settings-composing Edit calls and one probe write produced no ask,
in an interactive auto-mode session. In fresh headless sessions the hook fires and blocks in all
three permission modes tested. Two hypotheses remain, and nothing runnable from here separates them:
- H-1a — post-
/reload-plugins --forcesession state. That reload reported1 hookreloaded and
1 error during load(unattributed;/pluginis operator-only). Of the two enabled plugins only
context-budgetships a hook, so1 hookcan only be this one. The anomalous counter is
0 skillsagainst 4. - H-1b — an interactive dispatch gap.
hooks.mdL1732 documents that a hook's"ask"forces a
prompt in auto mode, and records a prior bug of this exact shape (pre-2.1.211,Bashonly, not
Write). If this reproduces, it is an upstream Claude Code defect, not a plugin one.
An auto-mode-only gap (H-1c) was tested and disconfirmed: headless auto mode fires normally.
Closing test: a fresh interactive session in auto mode writing to any
managed-settings.json outside .claude/. Manual mode no longer discriminates.
What worked (recorded so it is not regressed)
The engine refused a number for Skill and published the subtraction-artifact reason instead;
preserved CronDelete/CronList zeros rather than dropping them; caveats[] honestly empty;
verify-catalogue returned absent: [] across all 19 rows; the dual-ledger prefixDelta /
deferredDelta split held throughout and is what made the ToolSearch finding legible (deny it and
13,343 tokens migrate into the window, +15,824 prefix). setup apply was genuinely idempotent
and wrote nothing. The disableWorkflows lever was correctly detected as already applied. The ledger
round-trip predicted 4,608 and measured 4,608, exact.
Evidence packets (sealed, with per-file digests) at
~/.claude/plugins/data/plugin-quality-melodic-software/evidence/6cd8f3c9-.../<target>/20260824T203113Z/
— audit-notes.md per target, plus evidence*.md and contract.md.
Activity
claude commentedon Sep 5, 2026
Generated by Claude Code
claude commentedon Sep 5, 2026
This was generated by AI during triage.
Triage: partly aged out → re-verify, then decompose
Lane: autonomous triage, instance
vm-triage-202609050304. Claimed via the tracker seam.Read this before picking up any finding here
The audit was run against
context-budgetv0.6.10. Currentmainships v0.6.22. At least one HIGH finding has been fixed in the interim and at least one is still live. The severity table cannot be trusted as a work list without per-finding re-verification. This triage re-checked the HIGH tier only.HIGH-tier re-verification against current
mainH1 —
--verify-additivitycannot detect non-additivity on a full sweep. FIXED (substantially).The saturation guard H1 asked for now exists.
systemBucketSaving()(measure.mjs:608-612) detects vanished buckets and returnssaved: nullrather than a synthesized zero, with the source comment stating the contract explicitly: "callers publish that as incomparable withvanishednaming the buckets, never coerce it to 0." The--verify-additivityblock (:680-703) consumes it — it computescomparable = cmp.comparability.systemToolsComparable && !vanished.lengthand attachesvanishedReason(vanished)toreasons.Two deltas from what H1 asked for, both minor and both worth a small child rather than reopening the finding:
additiveis still a boolean (comparable && combinedSaved === sumOfParts) rather thannullwhen incomparable. The information is not lost — it rides incomparable: falseplusreasons— but a caller reading onlyadditivestill seesfalsewhere it should see "unmeasured".perToolrow.H2 — SKILL.md's "deltas add" is false as written. STILL LIVE.
plugins/context-budget/skills/audit/SKILL.mdstill reads, unconditionally: "which is compositional (deltas add), so a basket of trims can be priced from its members." No per-bucket qualification was added. The finding's own evidence is strong and does not depend on a synthesized zero — three non-saturated readings put at least 956 tokens of double-counting on the prefix side, while the deferred side was exact to the token (12 savers summing to 13,343; a 3-tool basket predicting and measuring 4,608). H2 also correctly records that the skill-frontmatter-subtraction hypothesis is dead, confirmed 1:1.H3 —
measure.mjs:723discards every deny run's caveats. LIKELY FIXED; line reference has drifted.The cited line is now unrelated code. Caveats are carried through at
measure.mjs:721(caveats: baseline.caveats) and are appended in several places (:388,:505,:866-868). Whether the deny run's own caveats specifically survive was not established here and is the one thing a child must confirm before assuming this is closed.H4, H5, H6 — NOT re-verified by this triage. H4 is flagged in the body as possibly UPSTREAM, which changes its routing entirely.
Why this is not briefed as one item
Six HIGH + ten MEDIUM + a LOW tier + an open question is not one contract. The findings span an engine correctness bug, two SSOT documentation defects, hook-matcher scope, several catalogue-metadata claims, and an upstream-attribution question. Beyond size, the aging problem makes a single brief actively harmful: it would hand a cold agent a work list of which some entries are already done.
Correct next action:
/work-items:decompose, with a mandatory re-verification step per finding.Decomposition plan
Step 0, blocking, for the decompose run. Before creating any child, re-verify each finding against v0.6.22 and drop the ones already fixed. H1 and H3 are the known cases; there may be more in the MEDIUM tier, which this triage did not check. Record each verdict in-thread so the next reader inherits it.
Then create children by cluster, not one per finding — several of these share one contract:
additive-should-be-null nuancework-class: scopedwork-class: scopedwork-class: scoped.claude/rules/hook-budget.mdapply/checkguidance refuted by measurementwork-class: scopedwork-class: read-onlyfirstwork-class: mechanicallikelyCluster 1 is the one to land first. H2 is a false claim in a shipped instruction surface, it is duplicated across two homes (
SKILL.md:18andlevers.json → deny-bare-tool.categoryBasis), and the correct wording is already established by measurement: prefix-side deltas do not add; deferred-side deltas do. Both homes must change together — this repo treats SSOT duplication as a defect in its own right.Do not create a child for the OPEN QUESTION section. The body marks it as not a finding with no remediation depending on it. Leave it in the container.
Classification of this container
priority: mediumapplied. The severities are the auditors' own and explicitly uncalibrated (no human calibration was applied), and the highest-severity finding verified still-live (H2) is a documentation correctness defect rather than a runtime fault. Recorded per convention: reporter tier HIGH, uncalibrated.work-class: read-only— this item is an audit report; its remaining work is re-verification plus decomposition.agent-ready. Handing this to an autonomous lane as filed would produce work on already-fixed findings.Lease released on completion of this triage.
Generated by Claude Code
kyle-sexton commentedon Sep 6, 2026
This was generated by AI during triage.
Decomposition executed, honoring the plan's blocking step 0
The plan posted here on 2026-09-05 was re-verified and executed. Instance
vm-triage-202609050304.Re-verification (2026-09-06) against the current version
The plugin has advanced again since the plan was written. Re-checked directly:
Children created
scopedscopedread-onlyWhy only three, and why one of them is the re-verification itself
The plan opens with a step marked blocking: re-verify every finding against the current version and drop the ones already fixed, before creating any child. That instruction is the most valuable thing in the plan, because this audit has now demonstrably decayed — of the findings checked so far, one is fixed, one is partly fixed, and one is live.
Creating children for the remaining clusters would have violated that step, and would have produced exactly the harm it exists to prevent: work items describing defects that may no longer exist, handed to agents who will find something to change regardless. Re-verifying all sixteen remaining findings properly was more than this pass could do with the care the parent's own evidence deserves.
So the remaining clusters were not sliced. Instead #3865 carries step 0 as a scoped, read-only, delegable work item, with instructions to record a verdict per finding and to verify by behavior rather than by line reference — the audit's line references have already drifted once, and one cited line now points at unrelated code. A second decompose pass on this container turns the survivors into work.
The two clusters that were sliced are the ones this pass re-verified first-hand, so they rest on observation rather than on the audit's word.
Note on #3863
It is the item to land first, as the plan says. Both homes must change in one PR: this repository treats a fact duplicated across two surfaces as a defect in itself, so correcting one and leaving the other is the same defect with a new instance. The corrected wording must state which side composes and which does not, rather than softening into vagueness; "may not always add" would be true and useless.
Not sliced, deliberately
The open-question section, per the plan. It is marked as not a finding, with no remediation depending on it, and stays in the container.
This container stays open and was not modified beyond its labels.
Triage claim released by
vm-triage-202609050304.Generated by Claude Code
fix(context-budget): correct the additivity claim and report the verd…
kyle-sexton commentedon Sep 27, 2026
This was generated by AI during work-loop.
Step 0 re-verification (#3865): verdicts for every finding not already re-checked
Checked against:
context-budget0.6.31 atmaine509cb7b2. Binary scans used Claude Code 2.1.283 (~/.local/share/claude/versions/2.1.283). The pass was read-only and changed no files.Method: each finding was checked against its named behavior or concept in the current source. The audit's line references were not used to locate anything. The line references below are current as of
e509cb7b2.Out of scope, already tracked elsewhere: H1 and H2 (#3863), M1 and M2 (#3864), and the OPEN QUESTION section.
18 findings verified. 15 still reproduce (H4 only on the plugin side), and 3 are fixed.
attributepublishescaveats: baseline.caveats(skills/audit/scripts/measure.mjs:789). The per-tool deny runs (:729-731) and the combined run (:750) never have their.caveatsread. In sdk modesdkSnapshotzero-fills an omitted attributed bucket and pushes a caveat naming the synthesized zero (:385-393). That caveat is therefore the only disclosure: because the bucket is filled with 0, thenull/vanished path insystemBucketSaving(:619-628) never fires in sdk mode. The record breaks the promise inreference/engine.md:94-97that "acaveats[]entry names every synthesized zero".EndConversationis a no-opEndConversationappears nowhere in the plugin (grep), includingreference/interactive-only-tools.json:4-10.deny-bare-tool.recheckTriggeris unchanged (reference/levers.json:48) and can still only fire on movement in the two System tools buckets. Upstream side: the docs still say a bare-name deny rule removes the tool from Claude's context (code.claude.com/docs/en/permissions.mdline 99, fetched this pass), and the 2.1.283 binary still carriesEndConversation. Whether the deny is still a no-op was not tested: it needs a fresh interactive session withpermissions.deny: ["EndConversation"]followed byToolSearch select:EndConversation. Routing: if that reproduces, the docs/binary disagreement goes to an upstream report to Anthropic, not to a change here. The recheck-trigger blind spot and the missing interactive-only listing entry route here regardless of the upstream result.applywas removed in 0.6.16. The same guidance now sits incheck's remediation block: "-sdefaults touser; pass the scopeclaude plugin listreports … or the write lands at a scope that does not load" (skills/setup/SKILL.md:89-92). It still does not say that-sgovernsenabledPluginsplacement, or thatplugin listcan show one file under two labels. The source of truth is shared: the setup text restates caveat 2 ofdocs/conventions/plugin-reconfiguration/README.md:41-43, which every setup skill prints. The fix belongs in the convention, not only in this plugin.checkstep 1 cannot detect its own failurecommand -v node(skills/setup/SKILL.md:33) and still argues the exec-form, hook-environment risk (:37-42). The Windows caveat "confirm the hook's environment resolves the samenode" still appears only under the FAIL-path "Missingnode" bullet (:70-72). Nothing handles persisted PATH or PID-bearing ephemeral shim paths.disable-artifactofferable but unmeasurableremoves-weight/recommendable-on-fit, and itsmeasurementstill prescribesattribute --tools Artifact(reference/levers.json:104).Artifactis still interactive-only (reference/interactive-only-tools.json:5). No lever-side unmeasurable marker exists (grep: no "unmeasurable" in the catalogue orreport.md). "Zeros are findings" is unchanged (reference/report.md:59-60).knownUncoveredRecordreturnslisting.tools − candidateswith the fixed reason "interactive-only — structurally unreachable" (measure.mjs:701-708). The candidates are[...tools, ...baseline.tools](:785-788), and no deny entries are subtracted.AskUserQuestion,EnterPlanModeandExitPlanModeare still on the list (interactive-only-tools.json:6,8,9).works-but-saves-nothing-hereasserted staticallyskill-overridesanddisable-bundled-skillsstill store that category (levers.json:190,:213). The instruction side already routes around it: auditSKILL.md:129-132says "resolve conditions by measurement" andreport.md:42-43requires "the condition's measured resolution". Still missing: the data-model split into a stored mechanism plus a runtime-resolved saving; a collapsed-row count in the snapshot (onlytotalSkills/includedSkills/tokensare recorded,measure.mjs:417-423); and any note on the token-versus-character unit (grep: none).verify-cataloguecannot checkmeta.purposestill reads "every known operator-controllable switch" (levers.json:4).runVerifyCataloguestill iterates only stored rows (measure.mjs:886-955), and there is no--find-unstored. On 2.1.283,CLAUDE_CODE_DISABLE_CRONandCLAUDE_CODE_ENABLE_DESIGN_SYNCboth occur in the binary and neither has a row.skillFrontmatter.map((s) => ({ name: s.name, source: s.source }))still dropstokensandpluginName(measure.mjs:395-396).slashCommandsis never recorded (grep: no occurrence).bypassPermissionsSKILL.md:235-246now scopes the claim to "a headless run that skips permissions". It is re-verified 2026-09-06 against 2.1.263 and three cited pages. Remnant: the hook header comment still carries the old "v2.1.232 … under bypassPermissions" stamp (hooks/settings-write-ask.mjs:8-12). This is a comment, not an instruction surface.custom-output-stylehas no built-in-style branchlevers.json:395) and has no branch for a built-in style that has no file.applywas removed in 0.6.16. Theclaude plugin install … --configline now sits under "Remediation guidance (printed bycheck; the operator applies it)" (skills/setup/SKILL.md:63), and the section states "This skill never writes user settings orpluginConfigs" (:92-93). The skill has no action that executes it.nonrepototal is a floor, and nothing says soreport.md:18-19stamps "the working directory measured from" but has no floor statement.lib/state-key.sh:177still resolves thenonreporung.--full-sweephint versus thefrom-baselineflag[--full-sweep](skills/audit/SKILL.md:3), and the body maps it to--tools from-baseline(:107). The engine has no--full-sweepflag (measure.mjs:154).--configclaimskills/setup/SKILL.md:81-93). That convention's verified-version record stamps only the--configstill-writes claim, at 2.1.240 (docs/conventions/plugin-reconfiguration/README.md:30-36). Its uninstall-drops-pluginConfigscaveat has no stamp (:40-42). The same inconsistency now lives in the shared source of truth.true" has no nounskills/setup/SKILL.md:56still reads "Report the effective${user_config.settings_write_ask_enabled}", which still renders to "Report the effectivetrue".mkdir -p … && npm install --prefix …:skills/setup/SKILL.md:77-78andskills/audit/SKILL.md:64-65.skills/setup/SKILL.md:24-26names the audit's Prerequisites and themeasure.mjsheader as the source of truth, then restatesnode, the CLI and the SDK in:33-55. That is a third copy afterskills/audit/SKILL.md:56-66.Which clusters still have live findings
Cluster numbers follow the 2026-09-05 decomposition plan.
apply/checkguidance): both live. H6 is plugin-local. H5's wording is shared withdocs/conventions/plugin-reconfiguration/README.md, so its slice has to touch the convention, and through it every setup skill, not justcontext-budget.recheckTriggercan be sliced here now. The upstream half stays human-gated and read-only until someone runs the interactive test. If it reproduces, it becomes an upstream report, not a repo change.This container stays open for the second decompose pass. No children were created and nothing was fixed.
3 remaining items
docs(actionlint): align setup --config scope advice with the reconfig…
docs(context-budget): fix spliced knownUncovered sentence, state cli-…
fix(context-budget): release 0.6.45
docs(plugin-reconfiguration): make the scope caveat agree with the me…
docs(actionlint): declare node, restore scope matching, date the hook…
docs(context-budget): name the home-directory scope exception in the …
docs(context-budget): state the ConfigChange claim as the hooks page …
docs(actionlint): align setup --config scope advice with the reconfig…
fix(actionlint): session-only missing-binary notice, /actionlint:chec…
fix(go-format): gate the prerequisite probe on the kill switch; align…
fix(docs-hygiene): close audit findings in audit-derivability, extrac…
fix(context-budget): setup passes the reported scope; audit docs and …
docs(conventions): revert agent rulings on owner-reserved issues and …