New node updates flagged on Comfy Registry.

### Custom Node Testing

- [ ] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)

### Your question

Hello Comfy Registry team,

I'm Amrendra (publisher ID **`ixmxamar`**) — author of several published Comfy nodes. I'm writing to request manual review of three node versions that have been stuck in `NodeVersionStatusFlagged` status since 2026-05-17, plus pre-emptive review of four versions I just published today which I'd like to surface to users without the typical pending delay.

I've reviewed the code in each pack and have not been able to identify what triggered the automated flag. There are no `eval`/`exec`/`subprocess`/`os.system`/`pickle.loads`/`__import__` calls, no obfuscated code, no calls to non-allowlisted hosts (only `generativelanguage.googleapis.com` for the Gemini packs and the documented Kling AI / ElevenLabs endpoints for the respective wrappers), and all API keys are passed via request headers (not URL query strings — that was explicitly fixed in commit `4cc2b04` of ComfyUI-NanoBanana2 in April).

If the flag was triggered by a specific pattern, I'd really appreciate any concrete detail so I can fix it for future releases.

## Versions blocked since 2026-05-17 (please re-review and approve)

| Node | Version | Version ID | Repository |
|---|---|---|---|
| `nanobanana2` | **2.5.0** | `7b83ecb4-94dd-49d6-99a4-9c628c1dfa01` | https://github.com/IxMxAMAR/ComfyUI-NanoBanana2 |
| `comfyui-nanobanana-faceswap` | **0.2.0** | `38aa7a2d-6765-4b57-a8a5-c7937132360f` | https://github.com/IxMxAMAR/ComfyUI-NanoBanana-FaceSwap |
| `comfyui-elevenlabs-pro` | **2.2.0** | `74a520e7-15b2-4123-9668-52693d46185b` | https://github.com/IxMxAMAR/ComfyUI-ElevenLabs-Pro |

The downstream impact is that `nanobanana2`'s public-facing "latest" pointer currently falls all the way back to v2.4.2 (April 25), and `comfyui-nanobanana-faceswap` has no Active version at all — both packs appear stale on the registry website despite being actively developed.

## Versions published today (please pre-emptively review)

I just published a major update to seven of my packs (adding 244 template workflows across the family — they ship inside each pack's `workflows/` directory and auto-surface in ComfyUI's template browser). The four marked below are at most risk of being auto-flagged because the same May-17 release cycle that triggered the existing flags also touched these packs:

| Node | Version | Version ID | Risk |
|---|---|---|---|
| `nanobanana2` | **2.5.1** | `6b5cb7f9-58a8-487b-98bc-69e6a3647423` | high (same codebase as 2.5.0) |
| `comfyui-nanobanana-faceswap` | **0.2.1** | `63f593d0-9f7f-45ac-98d5-67ec5a853ea9` | high (same codebase as 0.2.0) |
| `comfyui-elevenlabs-pro` | **2.2.1** | `a35db469-807f-4ddb-92d9-37c66d64a481` | high (same codebase as 2.2.0) |
| `comfyui-ixmxamar-masterworks` | **0.1.0** | (first publish — workflow-only pack, zero Python nodes) | low |
| `kling-direct` | **2.1.5** | (currently pending, no prior flag) | low |
| `comfyui-api-toolkit` | **1.6.2** | (currently pending, no prior flag) | low |
| `comfyui-utility-megapack` | **0.3.2** | (currently pending, no prior flag) | low |

## What's in the new releases

The only substantive change in the new versions is the addition of `workflows/*.json` template files — ComfyUI workflow JSONs generated by a small Python tool I wrote (typed recipe DSL → auto-layout → ComfyUI 0.4 workflow JSON). No new Python node code, no new dependencies, no new network endpoints. Each pack's workflow count:

- ComfyUI-NanoBanana2: 39
- ComfyUI-NanoBanana-FaceSwap: 12 (9 pre-existing + 3 new)
- ComfyUI-Kling-Direct: 42
- ComfyUI-ElevenLabs-Pro: 34
- ComfyUI-API-Toolkit: 82
- ComfyUI-Utility-MegaPack: 23
- ComfyUI-IxMxAMAR-Masterworks: 12 (new pack — workflow-only distribution, zero Python nodes, declares no dependencies)

The Masterworks pack is a new lightweight pack that ships only workflow JSON files combining nodes from the other packs. Its `__init__.py` exports `NODE_CLASS_MAPPINGS = {}` and `NODE_DISPLAY_NAME_MAPPINGS = {}` — no Python node code at all.

Happy to provide any additional information needed for review (specific diffs, signed code attestation, etc.).

Thank you for your time,
GitHub: https://github.com/IxMxAMAR
Publisher ID: ixmxamar

### Logs

```powershell

```

### Other

_No response_