ProcessFlow — Work one process (param: process name)

Input: one process name (the arg). Goal: bring it to guardrail-completion. Load processflow-review/references/guardrails.md (Definition of Done + Fehlermuster-Register) and processflow-app (Chrome-MCP + copilot mechanics). If a TodoWrite helps, create one todo per required guard.

0. Locate + load

Find the process by name in data/<company>/processes.json (get its UUID). Pull the current canvas + report + score fresh from Supabase via the Chrome session token (localStorage sb-…-auth-token → access_token; anon apikey) — a colleague may have edited it. Read the relevant transcript passages for THIS process.

1. Transcript-check first (ground truth)

Before reworking, verify the process against the transcript (canvas_wb, transcript, scenario_correct, industry_correct, no_invent): Is it real? Is the SCENARIO right (what actually happens)? Correct industry/products? Any invented tools/brands/devices/ERP names (grep them)? This sets what needs fixing.