feat: desktop terminal-action bridge (Push, Add datasource, New project)

.gitignore

@@ -63,3 +63,4 @@ Approved_rights/
 **/.profiles/
 # PowerCodex local build/compile scratch dirs
 .tmp-*
+.superpowers/

desktop/scripts/sync-lifecycle.js

@@ -23,19 +23,30 @@ fs.cpSync(src, dst, {
 
 console.log('synced lifecycle →', path.relative(process.cwd(), dst));
 
-// The published starter is the canonical scaffold for desktop "Create a new app"
-// (decision D5). Vendor it beside the engine so desktop-born projects get the full
-// harness / e2e / data layout; scaffold.js resolves it at vendor/templates/starter.
-const tplSrc = path.resolve(__dirname, '..', '..', 'templates', 'starter');
-const tplDst = path.resolve(__dirname, '..', 'vendor', 'templates', 'starter');
-if (fs.existsSync(tplSrc)) {
-  fs.rmSync(tplDst, { recursive: true, force: true });
-  fs.mkdirSync(path.dirname(tplDst), { recursive: true });
-  fs.cpSync(tplSrc, tplDst, {
-    recursive: true,
-    filter: (s) => !SKIP.test(s),
-  });
-  console.log('synced starter →', path.relative(process.cwd(), tplDst));
+// Vendor the whole templates/ tree (starter + github OPSX prompts/skills + the fixed
+// openspec/config.yaml) and bin/create-powercodex.js, so "✨ New project" inside the
+// packaged app can spawn the exact same full scaffold the `powercodex` CLI produces
+// (one CLI, two entry points — decision D5, extended). scaffold-cli.js resolves the
+// vendored bin at vendor/bin/create-powercodex.js, which in turn resolves its own
+// template root at vendor/templates/ relative to itself — no path changes needed
+// inside create-powercodex.js itself.
+const templatesSrc = path.resolve(__dirname, '..', '..', 'templates');
+const templatesDst = path.resolve(__dirname, '..', 'vendor', 'templates');
+if (fs.existsSync(templatesSrc)) {
+  fs.rmSync(templatesDst, { recursive: true, force: true });
+  fs.mkdirSync(path.dirname(templatesDst), { recursive: true });
+  fs.cpSync(templatesSrc, templatesDst, { recursive: true, filter: (s) => !SKIP.test(s) });
+  console.log('synced templates →', path.relative(process.cwd(), templatesDst));
 } else {
-  console.warn('starter template not found at', tplSrc, '— desktop scaffold will fall back to the generic template');
+  console.warn('templates/ not found at', templatesSrc, '— desktop scaffold will fall back to the generic template, and "New project" will be unavailable');
+}
+
+const binSrc = path.resolve(__dirname, '..', '..', 'bin', 'create-powercodex.js');
+const binDst = path.resolve(__dirname, '..', 'vendor', 'bin', 'create-powercodex.js');
+if (fs.existsSync(binSrc)) {
+  fs.mkdirSync(path.dirname(binDst), { recursive: true });
+  fs.copyFileSync(binSrc, binDst);
+  console.log('synced create-powercodex.js →', path.relative(process.cwd(), binDst));
+} else {
+  console.warn('bin/create-powercodex.js not found — "New project" will be unavailable in this build');
 }

docs/superpowers/specs/2026-07-13-desktop-terminal-action-bridge-design.md

@@ -0,0 +1,69 @@
+# Desktop terminal-action bridge
+
+**Status:** approved (design), not yet planned/implemented
+**Date:** 2026-07-13
+**Author:** Manfred Siew (design session with Claude Code)
+
+## Problem
+
+The PowerCodex desktop app (`desktop/`) wraps the lifecycle chat UI (`tools/lifecycle/assets/chat.html`) in an Electron shell. The chat UI already bridges one terminal action end-to-end — "⚡ Build this" — through `Controller.action()` in `tools/lifecycle/lib/control.js`. Three more terminal actions a Code Apps maker regularly needs are **not** bridged:
+
+- **Push** — `pac code push` exists as a working wrapper (`pushCodeApp()` in `tools/lifecycle/lib/pac-init.js`) and as a CLI subcommand (`code-push`), but `Controller.action()` has no case for it, so the chat UI can't call it.
+- **Add datasource** — `pac code add-data-source` is only referenced as guidance text for the AI agent (`CODEAPPS['dataverse-specialist']` / `CODEAPPS['connector-integrator']` in `tools/lifecycle/lib/harness.js`). No wrapper function exists anywhere.
+- **Create new project** — the full scaffold (starter template, OpenSpec, all 11 OPSX prompts/skills, npm install, git init) is `bin/create-powercodex.js`, a separate top-level CLI (`powercodex my-app`). The desktop app only has "📂 Open project" (pick an existing folder) — nothing scaffolds a new one from inside the app.
+
+The user should not need to leave the app or touch a terminal for these three actions. Clicking a button (or asking in chat) should be enough.
+
+## Goal
+
+Bridge all three actions into the chat UI using the same mechanism the app already uses for "Build this": a `Controller.action()` case that both a toolbar button and the chat agent call identically, streaming progress into the existing activity feed.
+
+## Non-goals (explicitly skipped for v1)
+
+- **No connector browser for non-Dataverse sources.** Free-text connector id only, until there's a real `pac connection list` wrapper to build a picker from.
+- **No solution-aware push (`--solutionName`).** `alm-engineer` guidance mentions solutions as the unit of movement, but wiring Push to a specific solution is a distinct feature. v1 pushes to the default target the same way `pushCodeApp()` does today.
+- **No rollback UI for Add-datasource.** Dataverse schema changes aren't cleanly reversible via the CLI anyway; the `allowPush` consent gate is the safety net, not an undo button.
+
+## Design
+
+### Core pattern
+
+Every new action is one more `case` in `Controller.action()` (`tools/lifecycle/lib/control.js:44`) — the same switch that already handles `intake` / `approve` / `propose-mvp` / etc. This gives the button and the chat agent a single code path for free:
+
+- The button calls `api('push', {...})` (the same `api()` helper `chat.html` already uses for every other action).
+- The chat agent, when it recognizes intent in a typed message, calls the identical action.
+
+No duplicated logic between "clicked" and "typed" — one implementation, two entry points.
+
+### 1. Push (`case 'push'`)
+
+- Wraps the existing `pushCodeApp()` from `tools/lifecycle/lib/pac-init.js`.
+- Runs `npm run build` first if the workspace has a `build` script, then `pac code push`.
+- Streams `pac` stdout/stderr into the activity feed via `emit()`, the same pattern `applySchema` already uses for Dataverse table creation.
+- **Gate:** reuses the existing `allowPush` rights flag (the rights panel's "Publish to my environment" toggle). The button is disabled/tooltipped when `allowPush` is off; the chat path returns the same "Push is off — turn on Publish to my environment first" message the gate already produces elsewhere.
+- **UI:** new "🚀 Push" toolbar button next to "⚡ Build this".
+- **Chat intent:** recognizes phrases like "push", "deploy", "publish".
+
+### 2. Add datasource (`case 'add-datasource'`)
+
+- New module `tools/lifecycle/lib/datasource.js`, same spawn/emit shape as `pac-init.js`, wrapping `pac code add-data-source -a <api> -t <table>`.
+- Unlike Push, this needs a parameter — no zero-input path:
+  - **Dataverse:** button opens a small panel listing tables already created via the Rule 1 browser flow, read from `.powercodex/dataverse.json` (`dataverse-schema.js`'s existing state file).
+  - **Other connectors:** free-text connector id field (see Non-goals — no picker yet).
+- **Chat intent:** e.g. "add a datasource for the Orders table" — the agent extracts the table name and calls the same action. If it can't confidently identify a table/connector, it asks a clarifying question in chat rather than guessing.
+- Guidance surfaced to the agent reuses the existing `CODEAPPS['dataverse-specialist']` / `CODEAPPS['connector-integrator']` text in `harness.js` — no new guidance text is authored.
+- **Gate:** reuses `allowPush` (schema/data-source wiring is a live-environment change too).
+
+### 3. Create new project (`case 'create-project'`)
+
+- Spawns `node bin/create-powercodex.js <name>` as a child process into a folder the user picks via the existing native picker (`pcDesktop.pickFolder()`).
+- Streams the CLI's real step names ("Copy starter template", "Initialize OpenSpec", "Finalize OPSX assets", etc. — from `create-powercodex.js`'s own `runStep()` calls) into the activity feed.
+- On success, the app re-opens the new folder as the active workspace automatically (reusing the existing "open project" flow) — usable immediately, no extra step.
+- **No gate** — purely local scaffolding, touches no live environment.
+- **Chat intent:** e.g. "start a new project called Orders Tracker" — same action; if no name is given, asks for one (reusing `create-powercodex.js`'s existing `validateProjectName` error messages for consistency, rather than re-implementing validation).
+
+## Cross-cutting notes
+
+- All three actions follow the existing `emit()`-per-step convention, so the activity feed is the single "what happened" surface — no new progress UI to build.
+- All three are exposed at the same `Controller.action()` switch, keeping button and chat-agent entry points identical.
+- Skill guidance (the `CODEAPPS` object in `harness.js`) is already loaded into the agent's context for relevant tasks; these actions reuse that wiring rather than duplicating guidance text.

templates/starter/tools/lifecycle/assets/chat.html

@@ -288,6 +288,9 @@
       <button class="iconbtn" id="openVSCodeBtn" title="Open this project in VS Code">⧉ VS Code</button>
       <button class="provchip" id="provChip" title="Which AI is answering — click to switch"><span class="br">🧠</span><span class="nm" id="provName">…</span><span style="color:var(--faint)">▾</span></button>
       <button class="iconbtn" id="canvasToggle" title="Show the canvas">🖼️ Canvas</button>
+      <button class="iconbtn" id="newProjectBtn" title="Create a brand-new PowerCodex project">✨ New project</button>
+      <button class="iconbtn" id="datasourceBtn" title="Wire up a Dataverse table or connector">🧩 Add datasource</button>
+      <button class="iconbtn" id="pushBtn" title="npm run build && pac code push" disabled>🚀 Push</button>
       <button class="statusbtn" id="statusBtn"><span class="d"></span><span class="stg" id="stStage">Starting…</span><span class="cv" id="stHint">status ▾</span></button>
     </div>
   </header>
@@ -377,6 +380,16 @@
     </div>
   </div>
 
+  <!-- add datasource -->
+  <div class="overlay" id="dsOverlay">
+    <div class="modal" id="dsPanel">
+      <div class="mh"><span>🧩</span><span class="t">Add a data source</span><button type="button" class="x" id="dsClose">✕</button></div>
+      <div class="fpbar"><select id="dsTableSelect"><option value="">— pick a Dataverse table —</option></select></div>
+      <div class="fpbar"><input id="dsConnectorInput" type="text" placeholder="…or a connector id, e.g. shared_sharepointonline" /></div>
+      <div class="mf"><span class="hint">Dataverse tables come from what's already been created via the browser flow. Other connectors need to exist in make.powerapps.com first.</span><button type="button" class="btn go" id="dsGo">Add data source</button></div>
+    </div>
+  </div>
+
   <!-- AI sign-in gate (no silent degrade) -->
   <div class="overlay" id="setupOverlay">
     <div class="modal">
@@ -640,6 +653,9 @@
     $('spCoverage').textContent = state.test && state.test.coverage!=null ? state.test.coverage+'%' : (state.intake && state.intake.compliance!=null ? state.intake.compliance+'%' : '—');
     $('spIssues').textContent = state.stopped ? 'needs you' : String((state.notifications||[]).filter(n=>n.kind==='approval').length);
     $('spLast').textContent = (state.feed && state.feed[0] && state.feed[0].message) ? state.feed[0].message.slice(0,42) : '—';
+    const rights = (state.intake && state.intake.rights) || {};
+    $('pushBtn').disabled = rights.allowPush !== true;
+    $('datasourceBtn').title = rights.allowPush === true ? 'Wire up a Dataverse table or connector' : 'Turn on "Publish to my environment" first';
   }
 
   // ---------- canvas ----------
@@ -995,6 +1011,54 @@
   $('treeRefresh').onclick = ()=> loadTree();
   makeSplit($('splitTree'),'left'); makeSplit($('splitCanvas'),'right');
   $('openVSCodeBtn').onclick = openInVSCode;
+
+  // ---------- Push ----------
+  $('pushBtn').onclick = async () => {
+    $('pushBtn').disabled = true;
+    bubble('me', 'Push 🚀');
+    const r = await api('push', {});
+    bubble('ai', r.ok ? '✅ Pushed to your environment.' : '⚠️ ' + esc(r.error || 'Push failed'));
+    if(app.treeRoot) loadTree();
+  };
+
+  // ---------- Add datasource ----------
+  async function openDatasourcePanel(){
+    $('dsOverlay').classList.add('open');
+    const sel = $('dsTableSelect');
+    sel.innerHTML = '<option value="">— pick a Dataverse table —</option>';
+    try {
+      const state = await (await fetch('/api/dataverse-state', {cache:'no-store'})).json();
+      (state.tables||[]).forEach(t => { if(t.logicalName){ const o=document.createElement('option'); o.value=t.logicalName; o.textContent=t.displayName+' ('+t.logicalName+')'; sel.appendChild(o); } });
+    } catch { /* picker still usable via the free-text connector field */ }
+  }
+  $('datasourceBtn').onclick = openDatasourcePanel;
+  $('dsClose').onclick = () => $('dsOverlay').classList.remove('open');
+  $('dsOverlay').onclick = (e) => { if(e.target===$('dsOverlay')) $('dsOverlay').classList.remove('open'); };
+  $('dsGo').onclick = async () => {
+    const table = $('dsTableSelect').value;
+    const connector = $('dsConnectorInput').value.trim();
+    $('dsOverlay').classList.remove('open');
+    bubble('me', table ? 'Add datasource: '+esc(table) : (connector ? 'Add datasource: '+esc(connector) : 'Add datasource'));
+    const r = await api('add-datasource', table ? {api:'dataverse', table} : {api: connector});
+    bubble('ai', r.ok ? '✅ Data source added.' : '⚠️ ' + esc(r.error || 'Could not add that data source'));
+  };
+
+  // ---------- Create new project ----------
+  $('newProjectBtn').onclick = async () => {
+    const name = prompt('Project name:');
+    if(!name) return;
+    let targetDir = null;
+    if(window.pcDesktop && window.pcDesktop.pickFolder) targetDir = await window.pcDesktop.pickFolder();
+    if(!targetDir) targetDir = prompt('Folder to create it in (absolute path):');
+    if(!targetDir) return;
+    bubble('me', 'New project: '+esc(name));
+    const typing = showTyping();
+    const r = await api('scaffold-project', {targetDir, name});
+    typing.remove();
+    bubble('ai', r.ok ? '✅ Created "'+esc(name)+'" and switched to it. It’s ready to build.' : '⚠️ ' + esc(r.error || 'Could not create the project'));
+    if(r.ok){ loadTree(); }
+  };
+
   $('setupRecheck').onclick = recheckSetup;
   $('setupSkip').onclick = ()=>{ app.skippedSetup=true; closeSetup(); };
   $('setupOverlay').onclick = (e)=>{ if(e.target===$('setupOverlay')){ app.skippedSetup=true; closeSetup(); } };