R2D2-MERIDIAN/lefthook.yml

# Glob patterns below mirror the `changes` job's dorny/paths-filter groups in
# .github/workflows/ci.yml — keep the two in sync. Deliberate deviations:
# - The `pre-commit` fix commands narrow their globs to the extensions their
#   formatter accepts (`crates/**/*.rs`, not `crates/**`), because they pass the
#   matched paths straight to the formatter. Widening one back to a directory
#   glob hands `rustfmt` a `Cargo.toml`. CI parity lives in the `pre-push`
#   globs, which still mirror the filter groups directly.
# - The `.github/workflows/ci.yml` path CI adds to its `rust`/`mobile` filters
#   is omitted; a CI-workflow-only edit doesn't need a local test run.
# - `desktop-check`/`desktop-test` don't trigger on `rust` changes, though CI's
#   Desktop Core job does. Those commands are pure TS (biome + node:test) with
#   no Rust dependency, so the extra trigger would be spurious locally.
# - Deletion-only surface changes do not trigger local hooks: lefthook 2.1.x
#   drops deleted paths from push-file discovery (`extractFiles` existence
#   check, repository.go). CI's dorny/paths-filter catches deletions.
#   Deliberate — accepted, not worked around.
# - `commit-msg` has no glob: it rewrites the commit message, not files. Note
#   Git only runs it for `git commit` and `git merge` — other flows need their own
#   flag: `git rebase --signoff`, `git cherry-pick -s`.
#
# EVERY fix command below is scoped to `{staged_files}`, and that is load-bearing
# rather than an optimisation. The whole-tree variants (`just fmt`,
# `just desktop-fix`, …) rewrite files the author never staged, and `stage_fixed`
# then adds them to the commit: on 2026-08-07 commit `2c2eb9153` carried seven of
# another agent's in-flight files despite the author staging three paths
# explicitly (bead meridian-jejg, finding F077). This branch is shared by
# construction — the root contract forbids branching so parallel agents
# interleave on `main` — so a formatter with tree-wide reach is a cross-agent
# write, not a tidy-up. Keep the file list in every `run:`; a command that
# formats `.` re-opens the defect.
#
# The whole-tree recipes stay right where they are, for `just fix-all` and CI,
# where formatting the whole tree is the intent.
pre-commit:
  parallel: true
  commands:
    # rustfmt directly rather than `cargo fmt`: `cargo fmt -- <file>` still
    # formats every crate root, so the file list would not scope anything.
    # Edition mirrors `[workspace.package] edition` in Cargo.toml; there is no
    # rustfmt.toml, so the remaining settings are rustfmt's defaults either way.
    rust-fmt:
      glob: ["crates/**/*.rs", "examples/countdown-bot/**/*.rs"]
      run: rustfmt --edition 2021 {staged_files}
      stage_fixed: true
    desktop-tauri-fmt:
      glob: ["REMAPPING/meridian-desktop/src-tauri/**/*.rs"]
      run: rustfmt --edition 2021 {staged_files}
      stage_fixed: true
    # `root:` keeps the working directory at `REMAPPING/meridian-desktop/`, so biome resolves
    # `REMAPPING/meridian-desktop/biome.json` exactly as `just desktop-fix` does. Running biome from
    # the repo root would pick up the root `biome.json` instead and reformat
    # against the wrong ruleset.
    desktop-fix:
      root: "REMAPPING/meridian-desktop/"
      glob: ["*.{ts,tsx,js,jsx,mjs,cjs,json,jsonc,css}"]
      # `*.generated.json` mirrors the `includes` deny-list in `REMAPPING/meridian-desktop/biome.json`.
      # Since the formatters started taking `{staged_files}`, a commit whose only
      # desktop file is a generated artifact handed biome one path that biome's own
      # config ignores; biome then processed zero files and exited 1. That is a
      # normal commit — `just check-mips --write` produces exactly it — so the two
      # ignore lists have to agree or the workflow is unlandable.
      exclude: ["src-tauri/**", "**/*.generated.json"]
      # `check:file-sizes` takes the staged set too. It is a "what am I about
      # to publish" check, and running it over the whole tree in a hook means
      # one agent mid-way through splitting a large module blocks every other
      # agent from committing anything — observed live, two files at once.
      # CI and `just check` still scan the whole project, which is what
      # actually protects `main`.
      run: pnpm exec biome check --write {staged_files} && pnpm check:file-sizes {staged_files}
      stage_fixed: true
    web-fix:
      root: "REMAPPING/meridian-web/"
      glob: ["*.{ts,tsx,js,jsx,mjs,cjs,json,jsonc,css}"]
      # `check:file-sizes` stays whole-project here, unlike desktop above: only
      # the desktop wrapper reads a path list so far, and `REMAPPING/meridian-web/` has not
      # produced a cross-agent block. Unscoped is the safer default — scope it
      # when it actually gets in someone's way, not pre-emptively.
      run: pnpm exec biome check --write {staged_files} && pnpm check:file-sizes
      stage_fixed: true
    # Split from the analyzer: `dart format` takes the staged file list, while
    # `flutter analyze` is whole-project and read-only, so it cannot stage
    # anything and needs no scoping.
    mobile-fmt:
      root: "REMAPPING/meridian-mobile/"
      glob: ["*.dart"]
      run: unset GIT_DIR GIT_WORK_TREE && dart format {staged_files}
      stage_fixed: true
    mobile-analyze:
      root: "REMAPPING/meridian-mobile/"
      glob: ["*"]
      run: unset GIT_DIR GIT_WORK_TREE && flutter analyze

# Appends the DCO Signed-off-by trailer the required "DCO Check" enforces.
# `--if-exists doNothing` makes it idempotent and preserves an existing
# sign-off (including `git commit -s` and a different signer's trailer).
commit-msg:
  commands:
    signoff:
      run: 'git interpret-trailers --if-exists doNothing --trailer "Signed-off-by: $(git var GIT_COMMITTER_IDENT | sed ''s/ [0-9]* [+-][0-9]*$//'')" --in-place {1}'

pre-push:
  parallel: true
  commands:
    branch-skew:
      run: ./scripts/check-branch-skew.sh
    rust-tests:
      glob: ["crates/**", "migrations/**", "schema/**", "Cargo.toml", "Cargo.lock", "rust-toolchain.toml", "deny.toml", "scripts/run-tests.sh", "justfile"]
      run: just test-unit
    desktop-check:
      glob: ["REMAPPING/meridian-desktop/**", "pnpm-lock.yaml"]
      exclude: ["REMAPPING/meridian-desktop/src-tauri/**"]
      # `desktop-check` is biome + guards only; `tsc` is a separate recipe.
      # Without it here a type error survives every local gate and first
      # surfaces in CI's `desktop-build`.
      run: just desktop-check && just desktop-typecheck
    desktop-test:
      glob: ["REMAPPING/meridian-desktop/**", "pnpm-lock.yaml"]
      exclude: ["REMAPPING/meridian-desktop/src-tauri/**"]
      run: just desktop-test
    desktop-tauri-checks:
      # Keep local lint parity with Desktop Core CI for every path that can
      # affect the Tauri crate or its path dependencies. Run clippy and tests
      # serially so parallel pre-push hooks do not contend for Cargo's lock.
      glob: ["REMAPPING/meridian-desktop/src-tauri/**", "crates/**", "migrations/**", "schema/**", "Cargo.toml", "Cargo.lock", "rust-toolchain.toml", "deny.toml", "scripts/run-tests.sh", "justfile"]
      run: just desktop-tauri-clippy && just desktop-tauri-test
    mobile-test:
      glob: ["REMAPPING/meridian-mobile/**"]
      run: just mobile-test
    # A chart-only change matches no other glob above, so before this entry a
    # `deploy/charts/**` push ran ZERO local hooks. That is how b6443a823
    # reached main with an alert group added at Chart.yaml 0.1.13: ArgoCD tracks
    # chart versions, so the cluster kept the previous templates and nothing
    # anywhere said so. Cheap (node, no toolchain) and state-based, so it needs
    # no diff. `scripts/**` is in the glob because the manifest and the guard
    # itself live there.
    chart-version-bump:
      glob: ["deploy/charts/**", "scripts/chart-version-manifest.json", "scripts/check-chart-version-bump*.mjs", "scripts/test-chart-version-bump-guard.sh"]
      run: just check-chart-version-bump