shields.io's dynamic TOML badge reads the version straight out of
pyproject.toml on main at view time, so the badge cannot go stale by
construction - no third version string to bump. Preflight check 3 flips
from comparing a hardcoded number to guarding the mechanism: the dynamic
badge must be present and a hardcoded release-X.Y.Z badge fails the
check. AGENTS.md's release step 1 goes back to two version strings.
The README badge advertised 1.0.0 through two releases, and the registry
side had two silent failure modes nobody was watching:
- release_preflight.py check 3: the README release badge must name the
pyproject version, so the three places a version lives (pyproject,
AUSBOSS_JS_VERSION, badge) can never disagree again. Badge bumped to
1.2.0; README also names the real ComfyUI-floor key (requires-comfyui).
- AGENTS.md release step 4: the push-triggered publish run has failed
before (1.2.0's run died; the version only shipped via a manual
dispatch) - a red run is an unpublished release until re-run.
- AGENTS.md release step 5: verify the version AND its status on the
registry. Every version this pack has published sits in
NodeVersionStatusFlagged - the automated scan holding it for human
review - and flagged versions are invisible in Manager's Select
Version picker and set no last-update, which is exactly the empty
picker on the live install. Ask the Comfy team for review; do not
re-publish.
ausboss