Weekly pin run: say so when a pin cannot be read, and list what is blocked or unchecked

[Matlan1]

Summary

• llama.cpp and ComfyUI no longer read as "nothing newer" when upstream could not be read; the weekly run reports them as inconclusive.
• A confirm script that exits 0 or 1 without a matching receipt is inconclusive, not a pass or a build failure.
• A pin constant that moved or was renamed in this repository reads as inconsistent (red) instead of "could not reach upstream"; a mistyped pin name on the command line exits 3, which the workflow keeps red.
• A tag that merely contains 404 is no longer mistaken for a missing release; four-part versions such as 12.9.2.10 compare correctly; the CUDA wheel age counts only the packages that are behind.
• Pins that are stale for a known reason (marked 16+, the TTS bundle) show as BLOCKED with the reason until 2026-12-31, then turn red again; the newest release inside the pinned major is bumped first so a blocked newest major cannot hold back a safe bump.
• The report lists the builds that are not measured on this machine and every source the registry cannot compare, so none is silently absent.

🤖 Generated with Claude Code