servicemap 0.1.45 → 0.1.47

package/SKILL.md

@@ -34,10 +34,13 @@ If no website can be found, create a desktop app fallback at `servicemap-desktop
     Do not deploy unless the user explicitly says yes.
     If they approve, use the project's existing deployment path, preferring `npm run deploy` when present, then provider-specific project configuration such as Vercel or Netlify.
 11. Report the page or desktop app path, service count, validation run, any services marked low or medium confidence, whether requested email access was enforced, and whether deployment was skipped or completed.
-12. If a desktop app was created and the chat client supports Codex inline follow-ups, end the final response with this button, replacing `<absolute-desktop-app-path>` with the generated app's actual absolute path:
-    `- :codex-followup[Launch Service Map]{prompt="Open a terminal in <absolute-desktop-app-path>, run npm run tauri dev, keep the process running, and tell me when the desktop app opens."}`
-    The button sends a follow-up request to Codex; do not claim that it executes the command directly.
-    If inline follow-ups are unavailable, report the absolute app path and the equivalent `npm run tauri dev` command instead.
+12. If a desktop app was created, launch the native desktop app after validation instead of relying on chat follow-up buttons.
+    Open a terminal in the generated app directory and run `npm run tauri dev`.
+    Keep that process running.
+    Report whether the native desktop app opened.
+    If Tauri, Rust, platform prerequisites, or another local issue prevents the native app from launching, report the exact failure and include this fallback command:
+    `cd <absolute-desktop-app-path> && npm run tauri dev`.
+    Do not claim the app is open unless the launch succeeds.
 
 ## Safety Rules
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "servicemap",
-  "version": "0.1.45",
+  "version": "0.1.47",
   "description": "Generate an internal service map page or desktop app for a software project.",
   "type": "module",
   "bin": {

package/scripts/generate-page.mjs

@@ -1051,7 +1051,7 @@ export default function InternalServiceMapPage() {
           <>
             <div className="map-plane" style={{ '--zoom': zoom, '--pan-x': \`\${pan.x}px\`, '--pan-y': \`\${pan.y}px\` } as CSSProperties}>
               <Connections nodes={nodes} selectedId={selectedId} />
-              <button type="button" className={\`hub \${selectedId === 'project' ? 'is-selected' : ''}\`} onClick={() => setSelectedId('project')} aria-label={\`Trace \${graph.project?.name ?? 'Project'} child services\`}><div className="hub-inner"><ProjectMark /></div></button>
+              <button type="button" className={\`hub \${selectedId === 'project' ? 'is-selected' : ''}\`} onClick={() => setSelectedId((current) => current === 'project' ? null : 'project')} aria-label={selectedId === 'project' ? \`Stop tracing \${graph.project?.name ?? 'Project'} child services\` : \`Trace \${graph.project?.name ?? 'Project'} child services\`} aria-pressed={selectedId === 'project'}><div className="hub-inner"><ProjectMark /></div></button>
               {nodes.map((service) => {
                 const isHighlightedChild = highlightedChildIds.has(service.id);
                 const isRelated = descendantIds.has(service.id) || selected?.parentId === service.id || isHighlightedChild;