v0.4.0-rc.2

v0.4.0-rc.2 is a controlled-testing artifact. The stable v0.4.0 release is not published yet. Do not describe the candidate as a stable or generally available release.

Install this exact candidate

cd /path/to/ComfyUI/custom_nodes
git clone --branch v0.4.0-rc.2 --depth 1 \
  https://github.com/trypluribus/comfyui-pluribus

Restart ComfyUI and confirm the Pluribus panel contains no demo people, projects, or permission records.

Controlled coverage

The controlled rehearsal began from clean state on the previous release candidate. After that candidate exposed a false-offline timeout, v0.4.0-rc.2 replaced it in the same isolated state, recovered the existing work, and completed the remaining checks. This was not a complete zero-state run performed entirely on v0.4.0-rc.2.

Across that controlled rehearsal, the core producer and recipient record path exercised:

• Clean plugin state without bundled people or fixture permission records
• Explicit individual workspace setup
• Multiple workflow stages associated with one project
• Creating and reusing a project person across sources
• Linking sources and persisting source dispositions across restart
• Saving and reloading a complete intended-use brief
• Secure-link and email confirmation paths for tested outcomes
• Recipient responses syncing without changing internal review
• Material source changes making an older response display Scope changed — request again
• Unrelated graph-note changes preserving the current rights manifest
• Restart recovery, returning-owner recovery, and server-confirmed disconnect

Open caveats

Fresh-signup email placement

Fresh-signup inbox placement has not been certified for this candidate. Check Spam before retrying or changing the address. Do not infer broad deliverability from one already-authenticated or provider-specific path.

Marker-only rehearsal coverage

The controlled rehearsal used marker-only character-sheet and storyboard workflows. It did not certify a supported non-marker production or final graph, downstream AI-action inference, real-media handling, generation, or rendering.

Slow writes

Some writes and recipient submissions can take several seconds. Wait for a definitive result before retrying. Progress and reconciliation behavior still need broader production coverage.

Link-only retry identity

An ambiguous link-only request keeps its stable retry ID in the open dialog. Reloading or closing that dialog can lose the client-held retry identity. If the dialog is lost, refresh canonical project state and reconcile the existing request instead of creating another one blindly.

Remaining production coverage

Before a stable tag, the exact final artifact still needs broader coverage for:

• Fresh signup and confirmation email placement across owned providers
• The internal-review handoff in the canonical workspace
• A privacy-inspected supported non-marker production and final workflow
• Normalized AI actions in a render-relevant graph
• Remaining recipient outcomes and multi-person source coverage
• Slow-write progress and safe reconciliation
• A complete zero-state journey using only the exact final artifact

What not to infer

Automated allow-list tests do not by themselves prove that no unexpected data leaves every custom production stack. Marker-only coverage does not certify production, final, or render paths. A recipient response does not complete internal review.

Use the production handoff checklist and keep these caveats visible during controlled testing.