Make Local Pre-Commit Hooks Strongly Suggested Fleet-Wide

.agents/skills/dotnet-codestyle/SKILL.md

@@ -49,8 +49,9 @@ All builds must complete without warnings, enforced three ways:
   surfaced as a warning fails the build and must be fixed or deliberately suppressed at the
   narrowest scope that fits (see Analyzer suppressions below), never left to accumulate.
 - **CI lint backstop.** CI runs the clean-compile checks on every PR as the authoritative gate.
-  Git hooks are optional, and a repo may wire a local runner (Husky.Net, with `dotnet husky run`
-  as a style step) for pre-commit enforcement, but CI is the gate that matters.
+  A working local hook is strongly suggested, not optional: wire Husky.Net from the canonical
+  `catalog/snippets/husky/` config. See GOVERNANCE.md "Running the Linters Locally" for what the
+  hook must cover and what its absence means.
 
 **A new port is not a license to silence diagnostics.** Brownfield or just-ported status never
 justifies relaxing analyzer severities or muting newly surfaced warnings. Fix them. (The only
@@ -94,8 +95,8 @@ updates, dependency upgrades, benchmarks) on top:
   `dotnet format style --verify-no-changes --severity=info --verbosity=detailed`.
 - **`dotnet-outdated-tool`** checks for dependency updates, and Nerdbank.GitVersioning owns
   version management.
-- CI is the authoritative lint backstop. Local pre-commit hooks are optional, wire Husky.Net (or
-  another runner) if you want local enforcement.
+- CI is the authoritative lint backstop. A local pre-commit hook is strongly suggested: wire
+  Husky.Net from `catalog/snippets/husky/` for local enforcement, including the shared doc gates.
 - **Required VS Code extensions**: CSharpier, markdownlint, CSpell. Use the workspace settings
   without overrides.
 

.agents/skills/python-codestyle/SKILL.md

@@ -90,8 +90,10 @@ The Python clean-compile is `uv run ruff format` + `uv run ruff check` + the rep
 both (see Type checking above). Run it, plus `uv run pytest`, before committing. These are
 documented commands, and an optional VS Code tasks mirror (all `type: process`, no `&&` shell
 chaining, so it runs the same on any task shell) is in the hub `vscode-tasks-python.json` snippet.
-CI runs the same clean-compile commands as the authoritative backstop. Git hooks are opt-in, so
-wire `pre-commit` for `ruff` and the type checker yourself if you want local enforcement.
+CI runs the same clean-compile commands as the authoritative backstop. A working local hook is
+strongly suggested, not opt-in: wire the Python `pre-commit` framework from the canonical
+`catalog/snippets/pre-commit/.pre-commit-config.yaml`. See GOVERNANCE.md "Running the Linters
+Locally" for what the hook must cover and what its absence means.
 
 A restricted executor gives each task a cache directory under a writable temporary root. Point
 `UV_CACHE_DIR`, `RUFF_CACHE_DIR`, `MYPY_CACHE_DIR`, and `COVERAGE_FILE` into that directory before

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-85b7db1858ecd00a
+309580363f245493

.claude-plugin/fleet-skills/skills/dotnet-codestyle/SKILL.md

@@ -49,8 +49,9 @@ All builds must complete without warnings, enforced three ways:
   surfaced as a warning fails the build and must be fixed or deliberately suppressed at the
   narrowest scope that fits (see Analyzer suppressions below), never left to accumulate.
 - **CI lint backstop.** CI runs the clean-compile checks on every PR as the authoritative gate.
-  Git hooks are optional, and a repo may wire a local runner (Husky.Net, with `dotnet husky run`
-  as a style step) for pre-commit enforcement, but CI is the gate that matters.
+  A working local hook is strongly suggested, not optional: wire Husky.Net from the canonical
+  `catalog/snippets/husky/` config. See GOVERNANCE.md "Running the Linters Locally" for what the
+  hook must cover and what its absence means.
 
 **A new port is not a license to silence diagnostics.** Brownfield or just-ported status never
 justifies relaxing analyzer severities or muting newly surfaced warnings. Fix them. (The only
@@ -94,8 +95,8 @@ updates, dependency upgrades, benchmarks) on top:
   `dotnet format style --verify-no-changes --severity=info --verbosity=detailed`.
 - **`dotnet-outdated-tool`** checks for dependency updates, and Nerdbank.GitVersioning owns
   version management.
-- CI is the authoritative lint backstop. Local pre-commit hooks are optional, wire Husky.Net (or
-  another runner) if you want local enforcement.
+- CI is the authoritative lint backstop. A local pre-commit hook is strongly suggested: wire
+  Husky.Net from `catalog/snippets/husky/` for local enforcement, including the shared doc gates.
 - **Required VS Code extensions**: CSharpier, markdownlint, CSpell. Use the workspace settings
   without overrides.
 

.claude-plugin/fleet-skills/skills/python-codestyle/SKILL.md

@@ -90,8 +90,10 @@ The Python clean-compile is `uv run ruff format` + `uv run ruff check` + the rep
 both (see Type checking above). Run it, plus `uv run pytest`, before committing. These are
 documented commands, and an optional VS Code tasks mirror (all `type: process`, no `&&` shell
 chaining, so it runs the same on any task shell) is in the hub `vscode-tasks-python.json` snippet.
-CI runs the same clean-compile commands as the authoritative backstop. Git hooks are opt-in, so
-wire `pre-commit` for `ruff` and the type checker yourself if you want local enforcement.
+CI runs the same clean-compile commands as the authoritative backstop. A working local hook is
+strongly suggested, not opt-in: wire the Python `pre-commit` framework from the canonical
+`catalog/snippets/pre-commit/.pre-commit-config.yaml`. See GOVERNANCE.md "Running the Linters
+Locally" for what the hook must cover and what its absence means.
 
 A restricted executor gives each task a cache directory under a writable temporary root. Point
 `UV_CACHE_DIR`, `RUFF_CACHE_DIR`, `MYPY_CACHE_DIR`, and `COVERAGE_FILE` into that directory before

.github/skills/dotnet-codestyle/SKILL.md

@@ -49,8 +49,9 @@ All builds must complete without warnings, enforced three ways:
   surfaced as a warning fails the build and must be fixed or deliberately suppressed at the
   narrowest scope that fits (see Analyzer suppressions below), never left to accumulate.
 - **CI lint backstop.** CI runs the clean-compile checks on every PR as the authoritative gate.
-  Git hooks are optional, and a repo may wire a local runner (Husky.Net, with `dotnet husky run`
-  as a style step) for pre-commit enforcement, but CI is the gate that matters.
+  A working local hook is strongly suggested, not optional: wire Husky.Net from the canonical
+  `catalog/snippets/husky/` config. See GOVERNANCE.md "Running the Linters Locally" for what the
+  hook must cover and what its absence means.
 
 **A new port is not a license to silence diagnostics.** Brownfield or just-ported status never
 justifies relaxing analyzer severities or muting newly surfaced warnings. Fix them. (The only
@@ -94,8 +95,8 @@ updates, dependency upgrades, benchmarks) on top:
   `dotnet format style --verify-no-changes --severity=info --verbosity=detailed`.
 - **`dotnet-outdated-tool`** checks for dependency updates, and Nerdbank.GitVersioning owns
   version management.
-- CI is the authoritative lint backstop. Local pre-commit hooks are optional, wire Husky.Net (or
-  another runner) if you want local enforcement.
+- CI is the authoritative lint backstop. A local pre-commit hook is strongly suggested: wire
+  Husky.Net from `catalog/snippets/husky/` for local enforcement, including the shared doc gates.
 - **Required VS Code extensions**: CSharpier, markdownlint, CSpell. Use the workspace settings
   without overrides.
 

.github/skills/python-codestyle/SKILL.md

@@ -90,8 +90,10 @@ The Python clean-compile is `uv run ruff format` + `uv run ruff check` + the rep
 both (see Type checking above). Run it, plus `uv run pytest`, before committing. These are
 documented commands, and an optional VS Code tasks mirror (all `type: process`, no `&&` shell
 chaining, so it runs the same on any task shell) is in the hub `vscode-tasks-python.json` snippet.
-CI runs the same clean-compile commands as the authoritative backstop. Git hooks are opt-in, so
-wire `pre-commit` for `ruff` and the type checker yourself if you want local enforcement.
+CI runs the same clean-compile commands as the authoritative backstop. A working local hook is
+strongly suggested, not opt-in: wire the Python `pre-commit` framework from the canonical
+`catalog/snippets/pre-commit/.pre-commit-config.yaml`. See GOVERNANCE.md "Running the Linters
+Locally" for what the hook must cover and what its absence means.
 
 A restricted executor gives each task a cache directory under a writable temporary root. Point
 `UV_CACHE_DIR`, `RUFF_CACHE_DIR`, `MYPY_CACHE_DIR`, and `COVERAGE_FILE` into that directory before

AUDIT.md

@@ -87,7 +87,7 @@ A check with `intentRef`/`workflowRef` points at the prose section that owns the
 - **carried-scope** - the repo carries no file the hub hosts rather than carries. The set is derived, not listed: the hub's git-tracked paths minus the [`spec/files.json`][files] baseline, so a file dropped from the manifest starts being reported on the next run with no retirement list to remember to edit. The remedy is the opposite of every other file finding, a **deletion**, since the repo reaches the hub's copy per [GOVERNANCE.md "Hub-Hosted Tooling"][governance-hub-hosted-tooling]. The match is on path alone, so a hit is a candidate and not a verdict: a repo's own content at a path the hub also uses matches while carrying nothing of the hub's, which the first fleet run showed twice, a KiCad tooling doc at `scripts/README.md` and per-repo formatting hooks at `.husky/pre-commit`. A [`spec/divergences.json`][divergences] `gaps` disposition decides which case a hit is, so only `retire` asserts a deletion, `accepted` closes a collision or a repo-owned file, and an untriaged hit is read before it is acted on.
 - **verbatim-tree** - every applicable `trees[]` declaration in [`spec/files.json`][files] owns its target tree. The audit reports missing files as letter findings, stale or modified bytes as drift, and extra files under a pruned target as drift. An unreadable or truncated repository tree is undecided and produces drift rather than a clean result.
 - **repo-setup** - every required secret for the repo's publish mechanisms is configured, and no forbidden secret is present (per [`spec/secrets.json`][secrets]).
-- **linter-parity** - one config per linter (`.markdownlint-cli2.jsonc`, `cspell.json`, ruff/pyright, editorconfig/csharpier, actionlint) drives the editor extension, the CLI, and CI, and CI runs each.
+- **linter-parity** - one config per linter (`.markdownlint-cli2.jsonc`, `cspell.json`, ruff/pyright, editorconfig/csharpier, actionlint) drives the editor extension, the CLI, and CI, and CI runs each. A local hook exists and runs at minimum the diff-scoped prose gate and the eol check (`parity.hooks`, intent). A repo with none wired is a defect, and one mid-convergence on the language-formatting half stays operational.
 - **recurring-violations** - comments concise and non-narrative, ASCII only (no em-dash, no smart quotes), US spelling, line endings per `.editorconfig`. These are frequent regressions, so this dimension is high priority and always runs, and each check is grep-able (see below).
 - **readme-structure** - the README follows [`spec/readme-structure.md`][readme-structure] (applicable sections, in order). Mechanically checked against the declared model in [`spec/readme-sections.json`][readme-sections]: required sections present, declared sections in their relative order, `License` last, the shields each deliverable implies, the license shield in the closing License section, and the tagline and its mirrors. A heading the model does not name is dropped before the order comparison, so a repo-specific section is never a finding.
 

CODESTYLE.md

@@ -18,7 +18,7 @@ Each language defines a **clean-compile** verification: the combination of build
 
 - **Run it after every code change, and it is not the whole gate.** The relevant language's clean-compile must pass before you commit. CI runs those same language checks as a backstop **plus everything else its validation workflow runs**, and all of it reports into the one required status, so a green clean-compile does not predict a green CI. That remainder is at least the doc-lint set (markdownlint, cspell, actionlint, `editorconfig-checker`) and whatever spec, config, and script gates the repo carries, so read the workflow for the full list rather than assuming this sentence enumerates it. What has to pass before a push is the repo's **whole** lint gate, per [GOVERNANCE.md "Verification Discipline"][governance-verification-discipline]. Each linter's known-working invocation is in [GOVERNANCE.md "Running the Linters Locally"][governance-running-the-linters-locally].
 - **The named task definition is the canonical spec** - its exact command sequence, arguments, and strictness. You may run it through the VS Code task **or** by invoking the equivalent native commands directly, and either is fine **only if the sequence, arguments, and strictness match exactly**. No shortcuts and no more-lenient options (for example, never drop `--verify-no-changes` or loosen a `--severity`).
-- **A local commit/pre-commit gate is the repo's choice.** No single hook runner fits every language (a `dotnet`-tool runner like Husky.Net suits .NET but not Python), so none is mandated, but that is **not** a recommendation against commit gates. CI is the authoritative backstop regardless, and a local gate is an additive convenience a repo may wire and keep: Husky.Net (and `dotnet husky run` as a style step) for .NET, `pre-commit` for Python. Keeping a working gate is not drift.
+- **A working local commit/pre-commit gate is strongly suggested, not the repo's free choice to skip.** No single hook runner fits every language (a `dotnet`-tool runner like Husky.Net suits .NET but not Python), so the *mechanism* stays the repo's choice: Husky.Net for .NET, `pre-commit` for Python, canonical configs for both in `catalog/snippets/`. What that gate must cover, and what its absence means for the audit, is [GOVERNANCE.md "Running the Linters Locally"][governance-running-the-linters-locally], not restated here. Keeping a working gate is not drift.
 
 ### Analyzer Diagnostics and Suppressions