comfyui-timesaver: versions 9.2-9.8 stuck on Flagged, registry serves 9.1 as latest

## Pack

- Name: `comfyui-timesaver`
- Publisher: `timesaver`
- Repo: https://github.com/AlexYez/comfyui-timesaver
- Registry page: https://registry.comfy.org/nodes/comfyui-timesaver

## Problem

Every version from **9.2 to 9.8** is in `NodeVersionStatusFlagged`.
The last `NodeVersionStatusActive` version is **9.1.0** (published
2026-05-06), so the registry continues to serve `latest_version =
9.1.0`. ComfyUI Manager users are pinned to 9.1, missing six releases
of fixes and new nodes.

Latest affected version (9.8.0):

- Version ID: `e71160c5-8825-41b9-9b62-e276ddd15e7c`
- Download: https://cdn.comfy.org/timesaver/comfyui-timesaver/9.8.0/node.zip
- Published: 2026-05-13

API confirmation:
GET https://api.comfy.org/nodes/comfyui-timesaver
latest_version.version = 9.1.0
latest_version.status = NodeVersionStatusActive

GET https://api.comfy.org/nodes/comfyui-timesaver/versions
9.8.0 -> NodeVersionStatusFlagged
9.7.0 -> NodeVersionStatusFlagged
9.6.0 -> NodeVersionStatusFlagged
9.5.0 -> NodeVersionStatusFlagged
9.4.0 -> NodeVersionStatusFlagged
9.3.0 -> NodeVersionStatusFlagged
9.2.0 -> NodeVersionStatusFlagged
9.1.0 -> NodeVersionStatusActive

## What I already tried
For 9.8 I added a `.comfyignore` that excludes dev-only paths from
the published archive (`tests/`, `tools/`, `.github/`, internal docs).
I downloaded the actual 9.8 zip from the CDN to confirm — it contains
259 entries with **0** entries from `tests/` or `tools/`, so
`.comfyignore` is honored by `comfy-cli` and the dev tooling is no
longer in the artifact. 9.8 still came back Flagged, so the trigger
must be in the production code.
The production code uses only standard ComfyUI patterns:
- `subprocess` calls to `ffmpeg` / `ffprobe` for audio/video decoding
(`nodes/audio/loader/_audio_helpers.py`,
`nodes/llm/super_prompt/_voice.py`,
`nodes/video/ts_animation_preview.py`).
- `aiohttp` routes for in-node DOM widgets (LamaCleanup retouch,
SAM media loader, audio loader, super-prompt voice button).
- `huggingface_hub.snapshot_download` for model downloads.
The same `subprocess` and download patterns were present in 8.6 – 9.1,
which all shipped as Active. The `aiohttp` route handlers were
introduced gradually across 9.2 – 9.6 alongside new interactive nodes.
## Question
Would you be able to share the scanner reason for 9.8.0 (or any of
9.2 – 9.7)? Knowing the exact pattern that trips the flag would let me
fix the actual issue rather than guess. If the flags are false
positives, could the affected versions be re-reviewed and promoted to
Active so `latest_version` can advance past 9.1?
Happy to refactor any specific pattern that is the trigger. Thanks!

Start by querying the named node and versions API endpoints and compare the statuses for versions 9.1.0 through 9.8.0 with the published artifact details. Trace the registry's scanner or review path from the repository, then identify the exact production pattern causing the flags; done means the reason is documented and the affected versions can be re-reviewed.

Written by the indexing model from the issue text.