Check 4 tried .comfyignore on 22 hand-picked paths with its own
gitignore matcher. With git it now lists what comfy-cli packs - tracked
files minus the ones .comfyignore matches - and fails when anything
outside the runtime allowlist ships, when .comfyignore drops a runtime
file, when an allowlist entry, js/docs/ or example_workflows/inputs/
ships empty, or when the archive grows past 12 MB (201 files and 7.1 MB
today). A copy without its own git repository keeps the sample-path
check.
The README's images and GIFs were 7.3 MB of a 14.4 MB archive, and only
GitHub shows them; nothing in the pack loads assets/. The editor
swap-file patterns and the one for a local copy of the brand skill
matched no tracked file, and comfy-cli packs tracked files only, so
they are gone.
todo2 was a finished checklist that rode along with the 2.1.0 release
commit. The ignore files listed personal note names one by one, including
several that no longer exist; local notes now follow one rule instead.
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