Manual review request: minimax-h3-audio-t8 v1.80.0 flagged and latest stuck at 1.47.0

## Summary

The published version `1.80.0` of `minimax-h3-audio-t8` was uploaded successfully, but the Registry API marks it as `NodeVersionStatusFlagged` with `comfy_node_extract_status: pending`. As a result, the node endpoint still exposes `1.47.0` as `latest_version`, and ComfyUI Manager users cannot receive current releases.

## Node

- Publisher: `t8star`
- Node ID: `minimax-h3-audio-t8`
- Repository: https://github.com/T8mars/comfyui-minimax-h3-audio-T8
- Registry: https://registry.comfy.org/nodes/minimax-h3-audio-t8
- Affected version: `1.80.0`
- Version ID: `3ec4d69f-f787-460e-9c65-d979df4e7611`
- User report: https://github.com/T8mars/comfyui-minimax-h3-audio-T8/issues/19

## Authoritative status

```text
GET https://api.comfy.org/nodes/minimax-h3-audio-t8
latest_version.version = 1.47.0

GET https://api.comfy.org/nodes/minimax-h3-audio-t8/versions?include_status_reason=true
1.80.0.status = NodeVersionStatusFlagged
1.80.0.comfy_node_extract_status = pending
```

The official publish action completed successfully and reported `Upload successful`:
https://github.com/T8mars/comfyui-minimax-h3-audio-T8/actions/runs/34837468112

## Package scope

The repository has a `.comfyignore` which excludes `.github/`, `artifacts/`, `docs/`, `tests/`, `tools/`, caches, bytecode, and local roadmap/skill files. The findings reported for 1.80.0 therefore come from runtime files.

The API currently returns 98 information-level findings. Several are clear pattern-matching false positives, for example:

- ordinary object/signature `.bind(...)` calls are classified as network socket operations;
- 32-character model state-dict hashes are classified as Bitcoin addresses;
- read-only `os.environ.get(...)` calls for documented local paths/API-key environment variables are classified as environment manipulation.

Other findings describe intentional node behavior which may require manual review:

- fixed-argument `subprocess` calls used for FFmpeg, Topaz, DLSS and crash-isolated workers (no `shell=True` command-string execution);
- AST/`compile(..., "exec")` compatibility adapters which rewrite inspected, installed ComfyUI/KJ functions rather than execute workflow-supplied arbitrary code;
- Windows process-liveness inspection for resumable background jobs.

There is also a vendored VRetouchEr fallback containing an upstream model-download request. It is not an exfiltration path, but if this specific behavior must be removed or changed for approval, please identify it explicitly and we will revise it.

## Request

Please:

1. manually review and activate version `1.80.0`, or identify the exact blocking findings that must change;
2. re-run node extraction so the public `latest_version` advances from `1.47.0`;
3. clarify whether intentional compatibility compilation and fixed-argv subprocess workers require a permanent manual-review policy for future versions.

We are not requesting that the scanner be bypassed. We need an actionable review result because the publish action returns success while all recent versions remain unavailable to Manager users.

Start by querying the two Registry API endpoints listed in the issue and inspect the linked publish run and upstream user report. Compare the flagged findings with the package scope in .comfyignore; done means an actionable manual-review decision, any required changes identified, and extraction rerun so latest_version reaches 1.80.0.

Written by the indexing model from the issue text.