#!/bin/sh
# 2026-10-30 tool_map drift repair -- CHECK (bounded rebuild).
#
# The first version of this script ran `tools/verify.py` un-flagged, i.e. with
# the selftest-sweep leg, and measured 107.93s wall on a clean tree. Inside the
# caller's harness it was killed just after printing this section's header, so
# the script read as a failure while every graded property in it was green
# (the un-flagged gate, run by hand on the same tree, reads 9/9 and rc 0).
# A CHECK that cannot finish inside its own harness is not a check.
#
# So each leg now has an explicit `timeout`, the sweep is out of the budget
# (it is a wrapper over the same cells this script grades directly -- the
# drift guard IS the selftest cell that caught the stale render), and the
# total is printed. Budget: <45s measured, 60s per leg worst case.
#
# rc 0 = docs/TOOLS.md is the render of this tree at HEAD and in the WORKTREE,
#        every cell of tool_map's selftest passed (cells == passed, 0 failed),
#        and the repo gate's fast legs are green with 0 fault / 0 ungradable.
#        The two counts are graded as STRUCTURE -- "pass + skipped == legs" and
#        "cells == passed" -- not as numerals a reader must remember to bump;
#        the numerals went stale when the gate grew from 9 legs to 12 and
#        tool_map from 20 cells to 23, and this entry point read FAIL beside
#        green evidence for it (Q145).
# rc 1 = a leg graded red.  rc 2 = the repo does not resolve.  rc 124 = a leg
#        outlived its timeout (a hang is not a pass).
set -u
REPO="$(cd "$(dirname "$0")/../.." 2>/dev/null && pwd)" || exit 2
cd "$REPO" || exit 2
T0=$(date +%s)
OUT="${TMPDIR:-/tmp}/toolsmd-drift.$$"

fail() { tail -16 "$OUT" 2>/dev/null; rm -f "$OUT"; echo "TOOLSMD FAIL: $1" >&2; exit 1; }

echo "== 1. tool_map drift guard (HEAD) =="
timeout 120 python3 tools/tool_map.py --repo . --rev HEAD --check docs/TOOLS.md \
    >"$OUT" 2>&1 || fail "drift guard at HEAD"
[ -s "$OUT" ] && tail -2 "$OUT" || echo "   CURRENT: document matches the render of HEAD"
rm -f "$OUT"

echo "== 2. tool_map drift guard (WORKTREE) =="
timeout 120 python3 tools/tool_map.py --repo . --rev WORKTREE --check docs/TOOLS.md \
    >"$OUT" 2>&1 || fail "drift guard in the WORKTREE"
[ -s "$OUT" ] && tail -2 "$OUT" || echo "   CURRENT: document matches the render of the WORKTREE"
rm -f "$OUT"

echo "== 3. tool_map --selftest (every cell passed, incl. the currency cell) =="
timeout 180 python3 tools/tool_map.py --repo . --rev HEAD --selftest >"$OUT" 2>&1 \
    || fail "tool_map selftest graded red"
# Consistency, not a literal. This leg used to demand the exact string
# "selftest: 20 cells, 20 passed, 0 failed" and read FAIL beside a green
# "23 cells, 23 passed, 0 failed" once tool_map grew cells: the count is a
# fact about tool_map, not about the drift this entry point grades (Q145).
awk '/^selftest: /{ if ($2 == $4 && $6 == 0 && $2 + 0 >= 20) ok = 1 }
     END { exit ok ? 0 : 1 }' "$OUT" \
    || fail "selftest did not read cells == passed, 0 failed"
grep -qE "^  ok +HEAD: .*the drift guard" "$OUT" \
    || fail "the currency cell is not among the passes"
grep "selftest: " "$OUT"; rm -f "$OUT"

echo "== 4. repo gate, fast legs (sweep skipped by design) =="
timeout 240 python3 tools/verify.py --repo . --fast >"$OUT" 2>&1 \
    || fail "a graded gate leg ran red"
grep -q "gate: OK" "$OUT" || fail "gate did not read OK"
# Structural, not a tally someone must remember to bump: the legs must add up
# (pass + skip == legs, since a skipped leg is neither a pass nor a fault) and
# no leg may have faulted or gone ungradable. The old literal
# "9 legs, 8 pass, 0 fault, 0 ungradable, 1 skipped" went stale at 12 legs.
awk '/^verify: /{ if ($6 == 0 && $8 == 0 && ($4 + $10) == $2) ok = 1 }
     END { exit ok ? 0 : 1 }' "$OUT" \
    || fail "the gate tally is not (0 fault, 0 ungradable, pass + skipped == legs)"
grep -E "verify: |gate: " "$OUT"; rm -f "$OUT"

echo "TOOLSMD OK: drift 0 at HEAD and WORKTREE; tool_map selftest all cells passed; gate fast legs all green ($(( $(date +%s) - T0 ))s)"