feat(autofix-hooks): adopt content-mutation disclosure across remaining autofix hooks

[kyle-sexton]

Fixes #1596

Summary

Closes the fleet-wide content-mutation disclosure tracker (#1596). Each remaining autofix hook that rewrites file content on Write/Edit now conforms to the hook-observability clause: when a rewrite occurs, the hook names what changed on the user channel (systemMessage) and stays silent on no-op paths.

Per-plugin disclosure behavior was already merged in the earlier wave (#2458, #2471–#2477). This PR completes the tracker by:

• Adding contract tests for ruff-format, go-format, and bash-format (matching the pattern already used by biome-format and eol-normalizer)
• Recording the Adopt the content-mutation disclosure clause across the remaining autofix hooks #1596 conformance rationale in hook comments (structural layout only / imports and layout only where applicable)
• Bumping versions and CHANGELOG entries for touched plugins

Hook coverage

Plugin	Disclosure	Tests
eol-normalizer	✅ (prior #2458)	✅
ruff-format	✅	✅ added
bash-format	✅	✅ added
go-format	✅	✅ added
powershell-format	✅ (prior #2477)	✅
biome-format	✅ (prior #2474)	✅

Related

• typos-format rewrites file content on every edit with no user-visible disclosure #1578 — typos-format reference implementation (names each rewritten token)
• markdown-format re-emits whole-file lint output on every touch, unbounded #1589 — markdown-format reference implementation (reports fix count)
• feat(eol-normalizer): disclose line-ending rewrites on the user channel #2458 — eol-normalizer disclosure
• feat(bash-format): disclose shfmt rewrites on the user channel #2471 — bash-format disclosure
• feat(ruff-format): disclose Ruff rewrites on the user channel #2472 — ruff-format disclosure
• feat(go-format): disclose goimports rewrites on the user channel #2473 — go-format disclosure
• feat(biome-format): disclose Biome rewrites on the user channel #2474 — biome-format disclosure
• feat(powershell-format): disclose formatter rewrites on the user channel #2477 — powershell-format disclosure
• docs/conventions/hook-observability/README.md — content-mutation conformance clause

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[claude]

Claude encountered an error after 1s —— View job

---

I'll analyze this and get back to you.

[github-actions]

Warning

Automated review did not complete — this is an infrastructure failure, not a review verdict.

Treat any Claude comment on this PR (including a placeholder like "I'll analyze this and get back to you") as incomplete, not "no findings."

• Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/31667726267
• Failure class: rate-limit
• Last SDK result: {"subtype":"success","is_error":true,"num_turns":1,"duration_ms":647,"total_cost_usd":0,"api_error_status":429,"class":"rate-limit"}

Re-run the job, or workflow_dispatch this workflow with the PR number, to retry the review. A new push re-triggers this lane only if the caller's pull_request triggers include synchronize (the canonical caller omits it).
An automatic retry may already have run — it is skipped when a partial review could duplicate comments, or when the failure class needs an operator (auth).

[claude]

Claude encountered an error after 0s —— View job

---

I'll analyze this and get back to you.

[github-actions]

Warning

Automated security review did not complete — this is an infrastructure failure, not a review verdict.

Treat any Claude comment on this PR (including a placeholder like "I'll analyze this and get back to you") as incomplete, not "no findings."

• Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/31667726255
• Failure class: rate-limit
• Last SDK result: {"subtype":"success","is_error":true,"num_turns":1,"duration_ms":274,"total_cost_usd":0,"api_error_status":429,"class":"rate-limit"}

The check is green on purpose, and it is not evidence. It certifies that a security pass ran, and this one did not complete — but the cause is outside this PR's control, so merging is deliberately left unblocked rather than locking every merge for the length of the outage. Nothing was reviewed at this head. Where this check is required, it is satisfied without that evidence; a human should review security-sensitive changes here before merging.

Re-run the job, or workflow_dispatch this workflow with the PR number, to retry the review (ci-workflows#227). A new push also retries it only if the caller's pull_request triggers include synchronize (the canonical security caller keeps it). An automatic retry may already have run — it is skipped when a partial review could duplicate comments, or when the failure class needs an operator.

Re-running does NOT help for every class:

• rate-limit that persists across re-runs, or auth — the credential or usage budget needs an operator; retrying will not clear it.
• a run that exhausted its turn budget ("subtype":"error_max_turns" above) will exhaust it again. As the PR author, split the change into smaller PRs; raising --max-turns is a change to the caller workflow, not something you can set on this PR.