Hermes Agent 97cb771d89 checker: fall back to unauthenticated HTTPS when gh is unusable ...

Found by the first real run of the weekly job: on a GitHub runner 'gh' is present
but unauthenticated, so every GitHub-sourced row (Ghidra, binwalk, WABT, apktool,
pwndbg, ida-pro-mcp and the three action majors - 9 rows) reported 'unknown'
instead of being checked. A row that cannot be checked is not a pass, and a
weekly job that quietly proves nothing is worse than no job.

The fetch path now tries 'gh api' (authenticated, higher limit), then plain
HTTPS, and reports both reasons when both fail. The workflow also passes
GH_TOKEN=github.token, warns explicitly when any row is unverifiable, and echoes
the counts so the log states what it proved.

Verified all three paths give identical results locally: authenticated gh, no gh
on PATH at all, and gh present with a broken token (0 unknown, 6 actionable
either way).

2026-10-15 20:34:04 +00:00

..

build.yml

add a version-drift checker and the update procedure

2026-10-15 20:30:28 +00:00

updates.yml

checker: fall back to unauthenticated HTTPS when gh is unusable

2026-10-15 20:34:04 +00:00