fix(hooks): ask the NOW range at push, with the gate's own reader

[gHashTag]

Refs #3303 — closes two of its six.

Reproduced before acting. A commit whose diff is CHANGELOG.md and nothing else passes the whole local barrier at exit 0, with NOW gate PASSED naming a neighbour's entry from the day before:

$ git diff --cached --diff-filter=A --name-only | grep -c '^docs/now/'
0
$ tri hooks pre-commit ; echo $?
NOW gate PASSED: 2026-09-04-the-notice-fires-on-my-own-publish.md (2026-09-04)
tri hooks pre-commit: PASSED
0

now_gate reads the docs/now directory listing. The commit is not one of its inputs, and 165 in-window entries sit on master, so the directory is fresh whatever the change does. The required check-now-freshness context then refuses the range — a full CI round spent on a question that could have been asked locally.

The correct reader already existed and was reachable from nothing. scripts/ci/now-sync-gate-diff.sh is what tri gates preview shells out to; grep -rn 'gates preview' .githooks/ scripts/ .github/workflows/ returns 0. This calls that script rather than re-implementing the question — a sixth vocabulary is how the previous five drifted.

Push and not commit, deliberately. The gate asks about a RANGE, and a branch may legitimately add its entry in a later commit than the code (tri now add is naturally run after the work). Refusing at commit time would block that; at push the range is the same object CI reads.

A base that will not resolve is could-not-run, never a pass. This worktree has been seen carrying remote.origin.fetch narrowed to master alone, under which every other origin/<branch> answers bad revision whatever the truth is.

The pointer was wrong too. tri now check told the reader that tri hooks now-gate asks whether an entry is REQUIRED. It does not, and cannot. Fixed to name the command that does.

Controls, both sides, plus live. A range with no entry exits 1 naming the reason; the same range with one added exits 0. And this PR's own push went through the new hook, which passed naming this PR's entry.

[github-actions]

PR Dashboard

Generated at: 2026-09-05 13:45:02 UTC

• fix(hooks): ask the NOW range at push, with the gate's own reader #3305 fix(hooks): ask the NOW range at push, with the gate's own reader | Created: 2026-09-05 | Updated: 2026-09-05 | 23 failing / 28 total
• chore(ci)(deps): bump actions/attest-build-provenance from 1 to 4 #3001 chore(ci)(deps): bump actions/attest-build-provenance from 1 to 4 | Created: 2026-09-01 | Updated: 2026-09-05 | 3 failing / 30 total
• chore(ci)(deps): bump softprops/action-gh-release from 2 to 3 #3000 chore(ci)(deps): bump softprops/action-gh-release from 2 to 3 | Created: 2026-09-01 | Updated: 2026-09-05 | 3 failing / 30 total
• chore(ci)(deps): bump github/codeql-action from 3 to 4 #2999 chore(ci)(deps): bump github/codeql-action from 3 to 4 | Created: 2026-09-01 | Updated: 2026-09-05 | 3 failing / 30 total
• Land the formal verification harness on master (it has never run) #2727 Land the formal verification harness on master (it has never run) | Created: 2026-08-27 | Updated: 2026-09-05 | 5 failing / 24 total
• chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 #2693 chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 #2692 chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 33 total
• chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 #2691 chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 #2690 chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 #2689 chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• Unbreak FPGA CI and correct two unbacked hardware claims #2081 Unbreak FPGA CI and correct two unbacked hardware claims | Created: 2026-08-11 | Updated: 2026-08-20 | 5 failing / 27 total

Summary

Status	Count
Total Open PRs	11
PRs with Failing Checks	10
PRs with All Checks Green	1
READY	0
FAILING	10
PENDING	0

Seal Status

• ⚠️ STALE -- sha256(compiler.rs)=ffccfa1a71cf != manifest seal=87e5cbd3ad94.
  The committed NMSE numbers were certified against an older compiler.rs.
  Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

[github-actions]

📓 NotebookLM Notebook linked to this PR

• Notebook ID: b83263109fb055dc
• URL: https://notebooklm.google.com/notebook/b83263109fb055dc

This notebook contains session context, decisions, and artifacts for this work.