Request manual review: bonfire@0.1.0 stuck NodeVersionStatusFlagged (clean archive)

## Description

### Custom Node Testing
- [x] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://github.com/ltdrdata/ComfyUI-Manager#how-to-disable-nodes) if you need help)

### Your question

Requesting a manual review of **bonfire** version **0.1.0**, which has been `NodeVersionStatusFlagged` since publish on 2026-09-14.

This is a first publish for publisher `@bonfire`. The node pack itself is `NodeStatusActive`, but there is **no Active version**, so Manager / registry search cannot surface an installable latest.

### API status

- Node: https://api.comfy.org/nodes/bonfire (`NodeStatusActive`)
- Version: https://api.comfy.org/nodes/bonfire/versions — `0.1.0` is `NodeVersionStatusFlagged`
- Active/Pending versions: **none** (`GET .../versions?statuses=NodeVersionStatusActive&statuses=NodeVersionStatusPending` returns `[]`)
- Version ID: `989af62d-7436-49f2-b8d2-fbc25d5cb21a`
- Repository: https://github.com/DaemonSK/ComfyUI-Bonfire
- Publisher: `bonfire`

### What we already checked

The published zip (26 files, runtime only; tests/docs/CI/CLAUDE.md excluded via `.comfyignore`) contains no:

- `eval` / `exec`
- `subprocess` / `os.system`
- `pickle` / `__import__`
- runtime `pip install`
- network calls from the node pack

`comfy node publish` reported `All validation checks passed successfully` before the registry marked the version flagged.

If a specific scanner pattern triggered this, I would like to know so later versions do not stay hidden from Manager.

Please re-review and, if it passes, clear the flag so `latest_version` is `0.1.0`.

Start with the node and version API responses linked in the issue, especially version ID 989af62d-7436-49f2-b8d2-fbc25d5cb21a and the active/pending status query. Review why bonfire 0.1.0 is flagged despite the reported clean archive and passed publish validation. Done means the flag is cleared and latest_version becomes 0.1.0, or the triggering scanner pattern is identified.

Written by the indexing model from the issue text.