node_list.json is packaged but no Comfy nodes are extracted for bv_nodepack

Problem

The Comfy Registry does not list any individual ComfyUI nodes for the custom node package bv_nodepack, although a valid node_list.json has been included in published packages for multiple versions.

Registry page:

https://registry.comfy.org/publishers/blackvortex/nodes/bv_nodepack

Repository:

https://github.com/BlackVortexAI/bv_nodepack

Current behavior

The Registry API returns no extracted nodes:

GET https://api.comfy.org/nodes/bv_nodepack/versions/0.13.0/comfy-nodes?limit=100

{
  "comfy_nodes": null,
  "totalNumberOfPages": 0
}

The same result occurs for versions 0.14.0 and 0.15.0.
Versions 0.14.0 and 0.15.0 are currently also stuck in NodeVersionStatusPending, while 0.13.0 is active.

Verified package contents

The published archives contain node_list.json at the package root:

• 0.13.0: 36 entries
• 0.15.0: node_list.json is present
• The JSON format matches the object format referenced by ComfyUI-Manager:
  "Node name": "Description"

The package also exports NODE_CLASS_MAPPINGS correctly at runtime.

However, the package uses a dynamic loader in its root init.py. It imports modules from py/nodes/*.py and merges their individual NODE_CLASS_MAPPINGS dictionaries into the exported root mapping.

Questions

1. Does the current Registry extraction pipeline support node_list.json as a fallback for dynamically assembled NODE_CLASS_MAPPINGS?
2. Is an explicitly declared mapping in the root init.py required for extraction?
3. Can the extraction status or failure reason for these versions be inspected or retried?
4. Why are versions 0.14.0 and 0.15.0 still pending?

No manual Registry API calls are currently made by the package. Publishing uses the official Comfy-Org/publish-node-action.

Start by tracing the /nodes/bv_nodepack/versions/{version}/comfy-nodes endpoint and the extraction handling for the package-root node_list.json and init.py. Compare versions 0.13.0, 0.14.0, and 0.15.0, then determine whether extraction status or retry information is exposed; done means the cause and supported extraction behavior are established and the pending versions have an identified outcome.