Checkpoint creator workspace and adopt NodeKit Caseflow

[HomenShum]

Outcome

NodeVideo now consumes the NodeKit Caseflow lifecycle for its founder-launch creator journey:

Case -> Run -> Stage -> ArtifactVersion -> Proposal -> Approval -> Receipt

The creator thread, messages, canonical versions, proposals, approvals, executor proposals, receipts, and timeline events are Convex-backed. The video-specific canvas, timeline, compiler, local renderer, and executor adapters remain inside NodeVideo.

Verified release evidence

• Exact production build: bce407b7 at https://nodevideo-pi.vercel.app
• Convex production Caseflow: connected with CSP regression coverage
• npm run check: pass
• Vitest: 49 files / 212 tests pass
• NodeKit conformance: pass
• Core production browser journey: pass
• Two production browser sessions: reactive; stale approval fails closed
• Exact Higgsfield quote gate: pass; no provider job submitted and no credits spent
• Live OpenRouter Free route: pass with explicit consent, structured model output, deterministic compilation, and durable proposal
• Local H.264 export: downloaded and reopened
• Desktop/mobile screenshots and accessibility/overflow checks: pass

Trust boundaries

• OpenRouter consent off sends zero external requests and raw media is excluded.
• The free router requires JSON Schema support; output also passes NodeVideo's operation allowlist.
• No proposal approval means no canonical mutation.
• Executor submission requires the currently approved quote digest; a changed quote invalidates approval.
• Executor approval alone does not submit or spend.

Honest remaining boundaries

This remains a draft engineering candidate. It is not ready for Convex component submission and does not claim NodeRoom/NodeSlide runtime parity.

Still required:

1. one separately authorized low-cost Higgsfield submit/poll/import/validate/receipt round trip;
2. an authenticated application wrapper replacing the owner-capability locator for sensitive or multi-user use;
3. a separate empty-directory coding-agent zero-to-proof study with repeated measured runs;
4. the formal revision-bound component submission packet.

See docs/testing/NODEVIDEO_SUBMISSION_READINESS.md and docs/testing/CREATOR_E2E_PROMPTS.md.