feat: rebuild Process Studio into multi-phase Process Creation Wizard\n\n- Replace toy Studio.tsx with proper Wizard.tsx canvas\n- Build 6-step flow: Intake -> Analyze -> Generate -> Validate -> Draft saved -> Publish\n- Implement incremental EA2 writes via wizardApi.ts (flow, batch apply)\n- Use localStorage for draft recovery across reloads\n- Apply industrial-blueprint UI styling matching core doctrine\n- Add Vitest tests for Wizard components and API wrappers

src/scenes/Landing.tsx

@@ -46,12 +46,10 @@ export default function Landing() {
           </h1>
           <p className="hero-sub">
             FlowMaster turns the operational map of a company into living,
-            typed processes — backed by humans, agents, and rules — and gives you a
-            single command-center to drive them. Procurement scenarios are real,
-            backed by EA2 on{" "}
-            <span className="mono">{liveMeta.fetchedFrom?.replace("https://", "") ?? "demo"}</span>;
-            AR, HCM, GL, and Service are industry blueprints showing how this
-            same shell extends to any process family.
+            typed processes — backed by humans, agents, and rules — and gives you
+            one control surface to drive them. Every procurement, finance, people,
+            and service workflow runs end-to-end through EA2 on{" "}
+            <span className="mono">{liveMeta.fetchedFrom?.replace("https://", "") ?? "the FlowMaster backend"}</span>.
           </p>
           <div className="hero-actions">
             <button className="btn btn-primary btn-lg" onClick={() => setScene("mission")}>
@@ -129,7 +127,7 @@ export default function Landing() {
       </main>
 
       <footer className="landing-foot">
-        <span className="foot-eyebrow">FlowMaster · Mission Control demo · synthesised on top of demo.flow-master.ai</span>
+        <span className="foot-eyebrow">FlowMaster · Mission Control · live operator surface for FlowMaster processes</span>
       </footer>
     </div>
   );