[PR #3] feat: add manifest.json for external tool consumption #1

New issue

Open

opened 2026-10-26 22:15:42 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-26 22:15:42 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/ComfyUI-test-framework/pull/3
Author: @WASasquatch
Created: 3/23/2026
Status: 🔄 Open

Base: main ← Head: was/add-manifest

📝 Commits (1)

40996c4 feat: add manifest.json for external tool consumption

📊 Changes

2 files changed (+329 additions, -0 deletions)

View changed files

➕ manifest.json (+121 -0)
➕ scripts/generate_manifest.py (+208 -0)

📄 Description

Summary

Add manifest.json — a generated file exposing node metadata (node_id, display_name, is_output_node, category, description) for external tools
Add scripts/generate_manifest.py — generates the manifest from node define_schema() definitions, with a --check flag for CI sync validation

Why

External tools (like workflow validators) need to know which test framework nodes are output nodes, without requiring a running ComfyUI instance. Previously, tools had to hardcode node names or rely on object_info.json from a live server. The manifest provides a static, always-available source of truth that stays in sync with the code via CI.

Test plan

python scripts/generate_manifest.py generates manifest with all 17 nodes
python scripts/generate_manifest.py --check passes when manifest is up to date
Cloud repo's validate_workflow.py successfully reads the manifest and recognizes test framework output nodes

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/ComfyUI-test-framework/pull/3 **Author:** [@WASasquatch](https://github.com/WASasquatch) **Created:** 3/23/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `was/add-manifest` --- ### 📝 Commits (1) - [`40996c4`](https://github.com/Comfy-Org/ComfyUI-test-framework/commit/40996c4a002dea1b1eb8f225305afeb5b5263326) feat: add manifest.json for external tool consumption ### 📊 Changes **2 files changed** (+329 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `manifest.json` (+121 -0) ➕ `scripts/generate_manifest.py` (+208 -0) </details> ### 📄 Description ## Summary - Add `manifest.json` — a generated file exposing node metadata (node_id, display_name, is_output_node, category, description) for external tools - Add `scripts/generate_manifest.py` — generates the manifest from node `define_schema()` definitions, with a `--check` flag for CI sync validation ## Why External tools (like workflow validators) need to know which test framework nodes are output nodes, without requiring a running ComfyUI instance. Previously, tools had to hardcode node names or rely on `object_info.json` from a live server. The manifest provides a static, always-available source of truth that stays in sync with the code via CI. ## Test plan - [x] `python scripts/generate_manifest.py` generates manifest with all 17 nodes - [x] `python scripts/generate_manifest.py --check` passes when manifest is up to date - [x] Cloud repo's `validate_workflow.py` successfully reads the manifest and recognizes test framework output nodes 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-26 22:15:42 +00:00

bsakaguchi referenced this issue

2026-10-26 22:15:42 +00:00

[PR #1] [MERGED] Flag all nodes as dev-only #2