formatter hooks: 9 siblings share the out-of-tree noise gap #972 fixed for markdown-format only

[kyle-sexton]

This was generated by AI during triage.

Converted from a #657 sweep line (source: 2026-07-22 work lane, T3, PR #1030 / #972 fix — dispatched-worker self-observation).

Problem

bash-format, biome-format, eol-normalizer, go-format, guardrails, powershell-format, ruff-format, typos-format, actionlint all carry the same hook::read_file_path() gap #972 fixed for markdown-format alone: project-membership scoping is skipped when CLAUDE_PROJECT_DIR is unset, so a PostToolUse hook fires on scratchpad/temp .md-or-equivalent files outside any repo.

Why this isn't status: ready

PR #1030 scoped the #972 fix to markdown-format only after an attempted shared-lib fix (editing lib/hook-utils.sh + syncing all 12 carriers) caused 9 genuine plugins/guardrails/hooks/cli-flag-verify.test.sh regressions and was reverted. Fixing the other 9 as a class needs an opt-in shared scoping mechanism — each formatter hook opts in explicitly; the shared guardrail-adjacent code stays location-agnostic so a future guardrails-side change doesn't cascade into unrelated formatters again. This is a real design call (opt-in mechanism shape), not a mechanical port of #972's fix to 9 more files — hence needs-human rather than status: ready.

Source

PR #1030: #1030
Sweep line: claude-code-plugins#657

[kyle-sexton]

This was generated by AI (triage lane — gate-audit claim). Claiming this item for one gate-audit cycle: an independent panel re-classifies whether the needs-human / status: needs-decision gate is still warranted, or whether the item is C2/C3 and liftable to agent-ready. Outcome comment follows in this cycle.

[kyle-sexton]

This was generated by AI (triage lane — gate audit). Independent panel: two fresh-context agents (one fable, one opus), each given only the issue content and the repo's own plugins/autonomy/reference/guardrails/work-classes.md, plus the triage lane's own read. This lane never executes work items, authors fixes, or merges.

Gate audit: GATE UPHELD — C4, and the mechanical path is empirically disproven

Panel: 2-of-2 STAYS-GATED, both C4. Lane read concurs.

This is not a port of #972's fix. The issue's own body says so — "Fixing the other 9 as a class needs an opt-in shared scoping mechanism" and "This is a real design call (opt-in mechanism shape), not a mechanical port."

And it has already been tried and reverted: PR #1030 attempted the mechanical shared-lib fix, caused 9 genuine plugins/guardrails/hooks/cli-flag-verify.test.sh regressions, and was backed out.

One leg confirmed the blast radius directly: the gap lives in the synced shared source lib/hook-utils.sh (hook::read_file_path skips membership scoping entirely when CLAUDE_PROJECT_DIR is unset), which scripts/sync-hook-utils.sh fans out to roughly 13 plugin copies across 35 carrier files. Any class fix mutates a shared contract that has already cascaded once.

Decision required

What shape should the opt-in scoping mechanism take, so each formatter hook opts in explicitly while guardrails-adjacent shared code stays location-agnostic?

RECOMMENDED — add a distinct opt-in helper alongside hook::read_file_path (a project-scoped variant that callers invoke by name), and migrate the 9 formatter hooks call-site by call-site. Existing callers and guardrails behaviour stay byte-identical, so the exact surface that produced the 9 reverted regressions is never re-touched. Both legs converged on this shape independently.

Alternative — a parameter or env opt-in flag on the existing hook::read_file_path. Keeps one function and avoids a second helper, but it modifies the precise shared surface that already caused a revert — the failure mode is known and repeatable.

Also considered — duplicate #972's fix into each of the 9 hooks (no shared surface, fully mechanical), rejected for 9-way drift risk.

[kyle-sexton]

This was generated by AI (triage lane — claim release). Gate-audit cycle complete for this item; the triage claim posted earlier this cycle is released. No lease is held — another instance or lane may pick this up immediately. The outcome comment above this one carries the classification and either the lift rationale or the decision summary.

[kyle-sexton]

Drain: tracked by open PR #2450 fix(hook-utils): scope read_file_path to git worktrees when project dir unset (no duplicate opened).