Studio Delivery Sheet

A turnover is just a pile of files until someone writes down what's in it. MKRStudioDeliverySheet is the node that writes it down: give it a delivery_plan_json from MKRStudioDeliveryPlan, and it generates the rows of a delivery/turnover sheet - the file list with paths, names, and context that tells the next department or the client exactly what they're receiving and why.

Mechanically it takes the plan's metadata, combines it with optional selection context, and emits both a structured JSON list of rows and a ready-to-share Markdown table. The delivery_sheet_md output is the one you'll paste into an email, a ticket, or a shared doc - it's a human-readable handoff sheet with zero formatting effort.

The inputs

• delivery_plan_json (required) - from MKRStudioDeliveryPlan. This is the spine; without it there's nothing to enumerate.
• root_folder - the base path the delivered files will live under, so the sheet shows real paths instead of abstract names.
• include_optional_files - include the optional/support files in the list (default true).
• include_selection_context - fold in the selection context (default true).
• selection_manifest_json (optional) - from MKRStudioSelectionSet, so the sheet can reference which frames were picked and their statuses.

What comes out

• delivery_rows_json - the rows as structured JSON, for anything programmatic.
• delivery_sheet_md - the Markdown table, ready to drop into a doc. This is the output you'll actually look at.
• summary_json - a summary of what the sheet contains.
• row_count - an INT, the number of rows. Handy if you want downstream logic to branch on "is this delivery empty?"

Installing it

In criskb/MKRShift_Nodes from Cris K B. ComfyUI Manager search "MKRShift_Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/criskb/MKRShift_Nodes

Restart. No pip requirements, no models.

Where it fits

This node assumes you've already built the plan - it's a renderer for the plan's data, not a place to type shot names. The workflow that makes it sing: MKRStudioDeliveryPlan → this → paste the Markdown into the client ticket. It won't move files or write to disk (the pack has publish/save nodes for that); it produces the description of the delivery, which is exactly what's usually missing at 5pm on handoff day.