From 64c979218c2049a51a698409794a93d0f57dd965 Mon Sep 17 00:00:00 2001 From: Volt Date: Tue, 20 Oct 2026 19:11:38 +0000 Subject: [PATCH] docs/TOOLS.md (volt): re-render for gate_blame.py (18 tools, 5 gate legs) --- docs/TOOLS.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/TOOLS.md b/docs/TOOLS.md index 6aafd33..bece930 100644 --- a/docs/TOOLS.md +++ b/docs/TOOLS.md @@ -7,7 +7,7 @@ disagree). Every cell below is derived, never typed -- purpose from the module docstring, flags from the tool's own `--help`, probe rows from `selftest_sweep.py`'s tables, the gate leg from `verify.py`'s `LEGS`. -**17 tools, 17 with a `--help` oracle.** Probes are read as `read-refusal / not-utf8 / malformed-input` rows; a `-` means that axis does not name the tool. +**18 tools, 18 with a `--help` oracle.** Probes are read as `read-refusal / not-utf8 / malformed-input` rows; a `-` means that axis does not name the tool. | tool | what it grades | flags | probes | gate leg | |---|---|---|---|---| @@ -20,6 +20,7 @@ module docstring, flags from the tool's own `--help`, probe rows from | `citation_resolve_check.py` | does every `:` citation in this archive's prose actually resolve, and to which file? | `--repo` `--rev` `--corpus` `--json` `--only` `--context` `--selftest` | 1 / 0 / 1 | - | | `doc_census_check.py` | does a tool's own docstring census match the census that tool PRINTS? | `--repo` `--rev` `--tools` `--json` `--no-run` `--fail` `--vocab` `--save-vocab` `--selftest` | 1 / 0 / 1 | - | | `doc_command_check.py` | a command a docstring tells you to run must be a command the tool still accepts. | `--repo` `--rev` `--tools` `--json` `--fail` `--selftest` | 1 / 0 / 1 | - | +| `gate_blame.py` | which landing turned a gate leg red? | `--repo` `--leg` `--range` `--ref` `--queue` `--index` `--timeout` `--json` `--quiet` `--selftest` | 1 / 0 / 1 | - | | `landing_check.py` | is every file at this revision actually served by the forge? | `--repo` `--rev` `--branch` `--base-url` `--path` `--max-bytes` `--timeout` `--json` `--quiet` `--selftest` | 1 / 0 / 1 | - | | `queue_append_audit.py` | was the queue's index current IN THE TREE of every commit that touched the queue? | `--repo` `--queue` `--index` `--from` `--to` `--all` `--guard` `--timeout` `--json` `--selftest` | 1 / 0 / 1 | `append-audit` | | `queue_claim_check.py` | the claim check for `WORK-QUEUE.md`, shipped with its tests. | `--queue` `--json` `--git` `--validate` `--selftest` `--fail-on-stale` `--explain` `--census` | 1 / 1 / 1 | - |