@wonderwhy-er/desktop-commander 0.2.38 → 0.2.40

package/dist/ui/shared/widget-state.d.ts

@@ -23,6 +23,11 @@ export declare function isChatGPT(): boolean;
  * Create a widget state storage adapter.
  *
  * On ChatGPT: Uses window.openai.widgetState for persistence
- * On other hosts: Returns no-op adapter (state comes from ui/notifications/tool-result)
+ * On other hosts: Uses sessionStorage as a fallback so the preview can survive
+ *   transient interruptions (page refresh on hosts that don't re-send tool_result,
+ *   visibility/focus loss, etc.).
+ *   The fallback cache key is scoped by app pathname and a per-frame widget id
+ *   persisted in window.name, so different widgets in the same origin/session
+ *   do not overwrite one another's cached state.
  */
 export declare function createWidgetStateStorage<T>(validator?: (state: unknown) => boolean): WidgetStateStorage<T>;

package/dist/ui/shared/widget-state.js

@@ -9,6 +9,71 @@
  * - ChatGPT: Uses window.openai.widgetState
  * - Other hosts: No-op (rely on standard ui/notifications/tool-result)
  */
+const FALLBACK_WIDGET_STATE_KEY_PREFIX = 'desktop-commander:widget-state';
+const FALLBACK_WIDGET_INSTANCE_MARKER = '__dc_widget_id__:';
+function createWidgetInstanceId() {
+    const cryptoObject = typeof globalThis.crypto === 'object' ? globalThis.crypto : undefined;
+    if (typeof cryptoObject?.randomUUID === 'function') {
+        return cryptoObject.randomUUID();
+    }
+    return `widget-${Date.now().toString(36)}-${Math.random().toString(36).slice(2, 10)}`;
+}
+function readWidgetInstanceIdFromWindowName(windowName) {
+    const markerIndex = windowName.indexOf(FALLBACK_WIDGET_INSTANCE_MARKER);
+    if (markerIndex === -1) {
+        return undefined;
+    }
+    const encodedValue = windowName
+        .slice(markerIndex + FALLBACK_WIDGET_INSTANCE_MARKER.length)
+        .split('|', 1)[0];
+    if (!encodedValue) {
+        return undefined;
+    }
+    try {
+        return decodeURIComponent(encodedValue);
+    }
+    catch {
+        return encodedValue;
+    }
+}
+function getFallbackWidgetInstanceId() {
+    if (typeof window === 'undefined') {
+        return 'unknown-instance';
+    }
+    const currentWindowName = typeof window.name === 'string' ? window.name : '';
+    const existingInstanceId = readWidgetInstanceIdFromWindowName(currentWindowName);
+    if (existingInstanceId) {
+        return existingInstanceId;
+    }
+    const instanceId = createWidgetInstanceId();
+    const marker = `${FALLBACK_WIDGET_INSTANCE_MARKER}${encodeURIComponent(instanceId)}`;
+    try {
+        window.name = currentWindowName ? `${currentWindowName}|${marker}` : marker;
+    }
+    catch {
+        // Ignore window.name write failures and fall back to the in-memory id.
+    }
+    return instanceId;
+}
+function getFallbackWidgetStateKey() {
+    if (typeof window === 'undefined') {
+        return `${FALLBACK_WIDGET_STATE_KEY_PREFIX}:unknown`;
+    }
+    const appPath = window.location.pathname || 'unknown';
+    const instanceId = getFallbackWidgetInstanceId();
+    return `${FALLBACK_WIDGET_STATE_KEY_PREFIX}:${appPath}:${encodeURIComponent(instanceId)}`;
+}
+function getSessionStorage() {
+    if (typeof window === 'undefined') {
+        return undefined;
+    }
+    try {
+        return window.sessionStorage;
+    }
+    catch {
+        return undefined;
+    }
+}
 /**
  * Check if we're running in ChatGPT (has special widget state API)
  */
@@ -20,14 +85,47 @@ export function isChatGPT() {
  * Create a widget state storage adapter.
  *
  * On ChatGPT: Uses window.openai.widgetState for persistence
- * On other hosts: Returns no-op adapter (state comes from ui/notifications/tool-result)
+ * On other hosts: Uses sessionStorage as a fallback so the preview can survive
+ *   transient interruptions (page refresh on hosts that don't re-send tool_result,
+ *   visibility/focus loss, etc.).
+ *   The fallback cache key is scoped by app pathname and a per-frame widget id
+ *   persisted in window.name, so different widgets in the same origin/session
+ *   do not overwrite one another's cached state.
  */
 export function createWidgetStateStorage(validator) {
     if (!isChatGPT()) {
-        // Other hosts don't have widget state persistence - return no-op
+        const storage = getSessionStorage();
+        const storageKey = getFallbackWidgetStateKey();
         return {
-            read: () => undefined,
-            write: () => { }
+            read() {
+                if (!storage)
+                    return undefined;
+                try {
+                    const raw = storage.getItem(storageKey);
+                    if (!raw)
+                        return undefined;
+                    const parsed = JSON.parse(raw);
+                    const payload = parsed?.payload;
+                    if (payload === undefined)
+                        return undefined;
+                    if (validator && !validator(payload))
+                        return undefined;
+                    return payload;
+                }
+                catch {
+                    return undefined;
+                }
+            },
+            write(state) {
+                if (!storage)
+                    return;
+                try {
+                    storage.setItem(storageKey, JSON.stringify({ payload: state }));
+                }
+                catch {
+                    // Ignore storage failures
+                }
+            }
         };
     }
     // ChatGPT-specific implementation

package/dist/utils/capture.js

@@ -381,7 +381,7 @@ export const capture_call_tool = async (event, properties) => {
     const GA_NEW_URL = `https://www.google-analytics.com/mp/collect?measurement_id=${GA_NEW_ID}&api_secret=${GA_NEW_SECRET}`;
     // Route highest-volume tools to new property, rest to old
     const HIGH_VOLUME_TOOLS = ['start_process', 'track_ui_event'];
-    const toolName = properties?.name;
+    const toolName = properties?.tool_name ?? properties?.name;
     const gaUrl = HIGH_VOLUME_TOOLS.includes(toolName) ? GA_NEW_URL : GA_OLD_URL;
     // Build properties once, send to GA4 + telemetry proxy in parallel
     const eventProperties = await buildEventProperties(properties);

package/dist/utils/files/base.d.ts

@@ -87,6 +87,8 @@ export interface FileResult {
 export interface FileMetadata {
     /** For images */
     isImage?: boolean;
+    /** For directories (read_file fallback to listDirectory) */
+    isDirectory?: boolean;
     /** For binary files */
     isBinary?: boolean;
     /** For Excel files */

package/dist/utils/open-browser.js

@@ -24,7 +24,7 @@ export async function openBrowser(url) {
                 break;
             case 'win32':
                 // Windows 'start' is a shell builtin, use spawn with shell but pass URL as separate arg
-                spawn('cmd', ['/c', 'start', '', url], { shell: false }).on('close', (code) => {
+                spawn('cmd', ['/c', 'start', '', url], { shell: false, windowsHide: true }).on('close', (code) => {
                     code === 0 ? resolve() : reject(new Error(`Exit code ${code}`));
                 });
                 break;

package/dist/utils/toolHistory.d.ts

@@ -12,6 +12,8 @@ interface FormattedToolCallRecord extends Omit<ToolCallRecord, 'timestamp'> {
 declare class ToolHistory {
     private history;
     private readonly MAX_ENTRIES;
+    private readonly MAX_HISTORY_FILE_SIZE_BYTES;
+    private readonly HISTORY_FILE_TRIM_TARGET_BYTES;
     private readonly historyFile;
     private writeQueue;
     private isWriting;
@@ -21,6 +23,17 @@ declare class ToolHistory {
      * Load history from disk (all instances share the same file)
      */
     private loadFromDisk;
+    /**
+     * Trim the on-disk history file to stay under the size cap by dropping the
+     * oldest entries (lines) until the kept tail fits within the trim target.
+     * Returns true only when the file was actually rewritten with a smaller
+     * tail, so callers can fall through to their normal path on failure or
+     * no-op rather than mutating in-memory state.
+     *
+     * Always keeps at least the most recent entry, even if a single record
+     * exceeds the trim target — there is no useful state below that.
+     */
+    private trimHistoryFileIfTooLarge;
     /**
      * Trim history file to prevent it from growing indefinitely
      */

package/dist/utils/toolHistory.js

@@ -18,6 +18,11 @@ class ToolHistory {
     constructor() {
         this.history = [];
         this.MAX_ENTRIES = 1000;
+        this.MAX_HISTORY_FILE_SIZE_BYTES = 5 * 1024 * 1024;
+        // When the file exceeds the cap we trim it down to this target instead of
+        // all the way to zero, so a single overflow doesn't cause every subsequent
+        // flush to re-trim.
+        this.HISTORY_FILE_TRIM_TARGET_BYTES = 4 * 1024 * 1024;
         this.writeQueue = [];
         this.isWriting = false;
         // Store history in same directory as config to keep everything together
@@ -41,6 +46,9 @@ class ToolHistory {
             if (!fs.existsSync(this.historyFile)) {
                 return;
             }
+            // If the file is over the cap, trim it down before reading so we
+            // load a bounded amount.
+            this.trimHistoryFileIfTooLarge();
             const content = fs.readFileSync(this.historyFile, 'utf-8');
             const lines = content.trim().split('\n').filter(line => line.trim());
             // Parse each line as JSON
@@ -64,6 +72,58 @@ class ToolHistory {
             // Silently fail
         }
     }
+    /**
+     * Trim the on-disk history file to stay under the size cap by dropping the
+     * oldest entries (lines) until the kept tail fits within the trim target.
+     * Returns true only when the file was actually rewritten with a smaller
+     * tail, so callers can fall through to their normal path on failure or
+     * no-op rather than mutating in-memory state.
+     *
+     * Always keeps at least the most recent entry, even if a single record
+     * exceeds the trim target — there is no useful state below that.
+     */
+    trimHistoryFileIfTooLarge() {
+        let stats;
+        try {
+            if (!fs.existsSync(this.historyFile)) {
+                return false;
+            }
+            stats = fs.statSync(this.historyFile);
+            if (stats.size <= this.MAX_HISTORY_FILE_SIZE_BYTES) {
+                return false;
+            }
+        }
+        catch (error) {
+            return false;
+        }
+        try {
+            const content = fs.readFileSync(this.historyFile, 'utf-8');
+            const lines = content.split('\n').filter(line => line.length > 0);
+            if (lines.length === 0) {
+                return false;
+            }
+            // Walk lines from newest to oldest, accumulating bytes (line + '\n'),
+            // and keep as many as fit within the trim target. Always keep at
+            // least the last line.
+            const kept = [];
+            let bytes = 0;
+            for (let i = lines.length - 1; i >= 0; i--) {
+                const lineBytes = Buffer.byteLength(lines[i], 'utf-8') + 1; // +1 for '\n'
+                if (kept.length > 0 && bytes + lineBytes > this.HISTORY_FILE_TRIM_TARGET_BYTES) {
+                    break;
+                }
+                kept.push(lines[i]);
+                bytes += lineBytes;
+            }
+            kept.reverse();
+            fs.writeFileSync(this.historyFile, kept.join('\n') + '\n', 'utf-8');
+            return true;
+        }
+        catch (error) {
+            // Trim failed; do not claim the file was changed.
+            return false;
+        }
+    }
     /**
      * Trim history file to prevent it from growing indefinitely
      */
@@ -101,6 +161,11 @@ class ToolHistory {
         const toWrite = [...this.writeQueue];
         this.writeQueue = [];
         try {
+            // If the on-disk file has grown past the cap, trim it down to the
+            // target size (keeping the most recent entries) before appending.
+            // The in-memory cache is unaffected — it is already bounded by
+            // MAX_ENTRIES via addCall.
+            this.trimHistoryFileIfTooLarge();
             // Append to file (atomic append operation)
             const lines = toWrite.map(entry => JSON.stringify(entry)).join('\n') + '\n';
             fs.appendFileSync(this.historyFile, lines, 'utf-8');

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const VERSION = "0.2.38";
+export declare const VERSION = "0.2.40";

package/dist/version.js

@@ -1 +1 @@
-export const VERSION = '0.2.38';
+export const VERSION = '0.2.40';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wonderwhy-er/desktop-commander",
-  "version": "0.2.38",
+  "version": "0.2.40",
   "description": "MCP server for terminal operations and file editing",
   "mcpName": "io.github.wonderwhy-er/desktop-commander",
   "license": "MIT",
@@ -53,6 +53,7 @@
     "release:dry": "node scripts/publish-release.cjs --dry-run",
     "release:mcp": "node scripts/publish-release.cjs --mcp-only",
     "release:alpha": "node scripts/publish-release.cjs --npm-only --alpha",
+    "release:skip-mcp": "node scripts/publish-release.cjs --skip-mcp",
     "logs:view": "npm run build && node scripts/view-fuzzy-logs.js",
     "logs:analyze": "npm run build && node scripts/analyze-fuzzy-logs.js",
     "logs:clear": "npm run build && node scripts/clear-fuzzy-logs.js",
@@ -86,6 +87,14 @@
     "@modelcontextprotocol/sdk": "^1.9.0",
     "@opendocsg/pdf2md": "^0.2.2",
     "@supabase/supabase-js": "^2.89.0",
+    "@tiptap/core": "^3.22.3",
+    "@tiptap/extension-image": "^3.22.3",
+    "@tiptap/extension-table": "^3.22.4",
+    "@tiptap/extension-table-cell": "^3.22.4",
+    "@tiptap/extension-table-header": "^3.22.4",
+    "@tiptap/extension-table-row": "^3.22.4",
+    "@tiptap/pm": "^3.22.3",
+    "@tiptap/starter-kit": "^3.22.3",
     "@vscode/ripgrep": "^1.15.9",
     "cross-fetch": "^4.1.0",
     "exceljs": "^4.4.0",
@@ -103,6 +112,7 @@
     "remark-gfm": "^4.0.1",
     "remark-parse": "^11.0.0",
     "sharp": "^0.34.5",
+    "tiptap-markdown": "^0.9.0",
     "unified": "^11.0.5",
     "unpdf": "^1.4.0",
     "zod": "^3.24.1",
@@ -118,6 +128,7 @@
     "commander": "^13.1.0",
     "esbuild": "^0.27.2",
     "js-tiktoken": "^1.0.21",
+    "jsdom": "^24.1.3",
     "nexe": "^5.0.0-beta.4",
     "nodemon": "^3.0.2",
     "shx": "^0.3.4",

package/dist/data/spec-kit-prompts.json

@@ -1,123 +0,0 @@
-{
-  "version": "1.0.0",
-  "description": "Spec-Kit prompts for specification-driven development workflows",
-  "prompts": [
-    {
-      "id": "spec_001",
-      "title": "Initialize Spec-Kit Project",
-      "description": "Set up a new project with spec-driven development workflow including templates, scripts, and AI agent integration.",
-      "prompt": "Let's initialize a new spec-driven development project! 🎯\n\n**Project Setup Process:**\n\n1. **Check Current Environment**: I'll verify if we're already in a spec-kit project (look for `.specify` folder)\n2. **Initialize New Project**: Set up project structure with `specify init <project-name>`\n3. **Configure AI Integration**: Choose your preferred AI agent (claude, copilot, gemini, cursor, etc.)\n4. **Explain Workflow**: Show you the available slash commands and methodology\n\n**What's the name of your new project?**\n\n*Example: `my-photo-app` or `user-auth-service`*\n\nOnce initialized, you'll have access to the complete spec-driven workflow:\n• `/constitution` - Define project principles\n• `/specify` - Create feature specifications\n• `/plan` - Generate technical plans\n• `/tasks` - Break down into actionable tasks\n• `/implement` - Execute implementation\n\nReady to get started?",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Setup",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "Rocket",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    },
-    {
-      "id": "spec_002",
-      "title": "Create Project Constitution",
-      "description": "Define project principles and governance that will guide all development decisions and ensure consistency across features.",
-      "prompt": "Let's establish your project constitution - the foundational principles that will guide all development! 📜\n\n**Constitution Creation Process:**\n\n1. **Analyze Current Context**: I'll check if you already have a constitution and understand your project\n2. **Define Core Principles**: Create non-negotiable rules for your development process\n3. **Set Governance**: Establish how principles are updated and enforced\n4. **Sync Dependencies**: Ensure all templates align with your new principles\n\n**What principles should guide your project?**\n\n*Examples:*\n• Code quality standards (testing requirements, review processes)\n• User experience consistency (accessibility-first, performance targets)\n• Technical constraints (preferred frameworks, deployment requirements)\n• Security requirements (authentication standards, data protection)\n\n**Tell me about your project's core values and constraints:**\n\nI'll create a comprehensive constitution that includes:\n• Principle definitions with clear rationale\n• Amendment procedures and versioning\n• Compliance review expectations\n• Template synchronization\n\nThis becomes the foundation for all future specifications and technical decisions!",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Setup",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "BookOpen",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    },
-    {
-      "id": "spec_003",
-      "title": "Create Feature Specification",
-      "description": "Generate a comprehensive feature specification from natural language description using spec-kit methodology and templates.",
-      "prompt": "Let's create a detailed feature specification using the spec-kit methodology! 📋\n\n**Specification Process:**\n\n1. **Create Feature Branch**: I'll run the create-new-feature script to set up a new branch and spec file\n2. **Generate Comprehensive Spec**: Use the spec-kit template to create:\n   • User scenarios and testing approaches\n   • Functional requirements (testable and unambiguous)\n   • Key entities and data models\n   • Success criteria and acceptance criteria\n3. **Mark Clarifications**: Highlight any areas that need more detail with [NEEDS CLARIFICATION] markers\n4. **Review Checklist**: Validate completeness and business alignment\n\n**What feature do you want to build?**\n\n*Be as detailed as possible about WHAT and WHY, avoid HOW:*\n\n*Examples:*\n• \"User authentication system with login, logout, and password reset\"\n• \"Photo album management with drag-and-drop organization\"\n• \"Real-time chat with message history and user presence\"\n• \"Task management with projects, assignments, and Kanban boards\"\n\n**Feature Description:**\n\nI'll focus on:\n✅ What users need and why\n✅ Business requirements and user scenarios\n✅ Testable functional requirements\n❌ Technical implementation details (saved for planning phase)\n\nReady to create your specification?",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Specification",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "FileText",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    },
-    {
-      "id": "spec_004",
-      "title": "Clarify Specification Requirements",
-      "description": "Run structured clarification workflow to resolve ambiguous requirements and ensure specification completeness before planning.",
-      "prompt": "Let's clarify any ambiguous areas in your specification before moving to technical planning! 🔍\n\n**Clarification Workflow:**\n\n1. **Analyze Current Spec**: I'll read your feature specification and identify areas marked with [NEEDS CLARIFICATION]\n2. **Structured Questioning**: Ask targeted questions about:\n   • User types and permissions\n   • Data retention and deletion policies\n   • Performance targets and scale requirements\n   • Error handling behaviors\n   • Integration requirements\n3. **Document Answers**: Record all clarifications in the specification\n4. **Validate Completeness**: Ensure all requirements are testable and unambiguous\n\n**Current clarification areas in your spec:**\n\nI'll systematically work through each unclear aspect:\n• Who are the users and what are their roles?\n• What are the data and storage requirements?\n• What are the performance and scale expectations?\n• How should errors and edge cases be handled?\n• What integrations or external dependencies exist?\n\n**Ready to clarify your specification?**\n\n*This step is crucial for reducing rework during planning and implementation phases.*\n\nOnce clarified, your specification will be ready for technical planning with `/plan`!",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Specification",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "HelpCircle",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    },
-    {
-      "id": "spec_005",
-      "title": "Generate Technical Implementation Plan",
-      "description": "Create detailed technical plan from specification including architecture, tech stack, data models, and implementation strategy.",
-      "prompt": "Let's create a comprehensive technical implementation plan for your feature! 🏗️\n\n**Planning Process:**\n\n1. **Analyze Specification**: I'll read your feature spec and understand all requirements\n2. **Check Constitution**: Ensure alignment with project principles and constraints\n3. **Generate Implementation Plan**: Create detailed technical plan including:\n   • Architecture and tech stack decisions\n   • Data models based on key entities\n   • API contracts and interfaces\n   • Research for technical decisions\n   • Quickstart validation scenarios\n4. **Validate Against Gates**: Check simplicity, anti-abstraction, and constitutional compliance\n\n**What's your preferred technology approach?**\n\n*Specify your tech stack and architectural preferences:*\n\n*Examples:*\n• \"React with TypeScript, Node.js backend, PostgreSQL database\"\n• \"Vanilla HTML/CSS/JavaScript, SQLite for local storage\"\n• \"Python FastAPI, Redis for caching, Docker deployment\"\n• \"Vue.js frontend, .NET Core API, SQL Server database\"\n\n**Technical Context:**\n\nI'll generate:\n📋 **Implementation Plan** - Architecture and approach\n🗄️ **Data Model** - Entities and relationships\n🔌 **API Contracts** - Endpoints and specifications\n🔬 **Research Notes** - Technical decisions and rationale\n⚡ **Quickstart Guide** - Key validation scenarios\n\nReady to create your technical plan?",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Planning",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "Blueprint",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    },
-    {
-      "id": "spec_006",
-      "title": "Generate Implementation Tasks",
-      "description": "Break down technical plan into actionable, dependency-ordered tasks ready for execution with parallel execution markers.",
-      "prompt": "Let's break down your implementation plan into actionable tasks! ✅\n\n**Task Generation Process:**\n\n1. **Analyze Design Artifacts**: I'll read your plan.md, data-model.md, contracts/, and other design documents\n2. **Generate Task Breakdown**: Create specific tasks organized by phases:\n   • **Setup Tasks**: Project init, dependencies, configuration\n   • **Test Tasks [P]**: Contract tests, integration scenarios (parallel)\n   • **Core Tasks**: Models, services, CLI commands, endpoints\n   • **Integration Tasks**: Database, middleware, logging\n   • **Polish Tasks [P]**: Unit tests, performance, docs (parallel)\n3. **Order Dependencies**: Ensure proper execution sequence (TDD approach)\n4. **Mark Parallelization**: Identify tasks that can run simultaneously with [P]\n\n**Task Generation Rules:**\n• Each contract → test task marked [P]\n• Each entity → model creation task marked [P]\n• Each endpoint → implementation task\n• Different files = parallel [P]\n• Same files = sequential\n• Tests before implementation (TDD)\n\n**Additional context for task generation:**\n\n*Any specific requirements or preferences for the implementation approach?*\n\nI'll create a `tasks.md` file with:\n📝 **Numbered Tasks** (T001, T002, etc.)\n📁 **File Paths** for each task\n🔗 **Dependencies** clearly marked\n⚡ **Parallel Groups** for efficient execution\n\nReady to generate your implementation tasks?",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Planning",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "CheckSquare",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    },
-    {
-      "id": "spec_007",
-      "title": "Execute Feature Implementation",
-      "description": "Execute all implementation tasks following the task breakdown with TDD approach, dependency management, and progress tracking.",
-      "prompt": "Let's implement your feature following the spec-driven task breakdown! 🚀\n\n**Implementation Process:**\n\n1. **Load Implementation Context**: I'll read all your design documents:\n   • tasks.md (execution plan)\n   • plan.md (architecture and tech stack)\n   • data-model.md (entities and relationships)\n   • contracts/ (API specifications)\n   • research.md (technical decisions)\n\n2. **Execute Phase-by-Phase**:\n   • **Setup**: Project structure, dependencies, configuration\n   • **Tests**: Contract tests and integration scenarios (TDD)\n   • **Core**: Models, services, CLI commands, endpoints\n   • **Integration**: Database, middleware, logging\n   • **Polish**: Unit tests, performance, documentation\n\n3. **Follow Execution Rules**:\n   • Respect task dependencies (sequential vs parallel)\n   • Tests before implementation (TDD approach)\n   • File-based coordination (same file = sequential)\n   • Mark completed tasks with [X]\n\n4. **Progress Tracking**: Report after each completed task with validation\n\n**Implementation preferences:**\n\n*Any specific notes for the implementation (deployment targets, testing frameworks, etc.)?*\n\nI'll execute tasks systematically:\n✅ **Validate Prerequisites** - All documents ready\n📋 **Phase-by-Phase Execution** - Setup → Tests → Core → Integration → Polish\n🔄 **Real-time Progress** - Track completion and handle errors\n🎯 **Final Validation** - Ensure specs match implementation\n\nReady to build your feature?",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Implementation",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "Play",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    },
-    {
-      "id": "spec_008",
-      "title": "Analyze Spec-Kit Project Status",
-      "description": "Comprehensive analysis of current spec-kit project state including features, phases, and recommended next steps.",
-      "prompt": "Let me analyze your spec-kit project and show you the current state! 📊\n\n**Project Analysis Process:**\n\n1. **Project Structure Review**: I'll examine your `.specify` directory and validate:\n   • Templates and scripts availability\n   • Project constitution and principles\n   • Current branch and feature context\n\n2. **Feature Inventory**: Scan the `specs/` directory to identify:\n   • All features and their completion status\n   • Current phase (specification, planning, tasks, implementation)\n   • Missing or incomplete artifacts\n\n3. **Health Check**: Verify project follows spec-kit best practices:\n   • All required templates present\n   • Script permissions and functionality\n   • Git branch structure and workflow\n\n4. **Progress Assessment**: For the current feature:\n   • What phase are you in?\n   • What files exist vs. what's missing?\n   • What's the logical next step?\n\n**Current Project Overview:**\n\nI'll provide:\n📋 **Feature Status Matrix** - All features and their phases\n🎯 **Current Focus** - Active feature and next steps\n⚙️ **Configuration Health** - Templates and scripts status\n📈 **Recommendations** - Suggested workflow continuations\n\n**Any specific areas you'd like me to focus on?**\n\n*Examples: \"Focus on feature completion status\" or \"Check for any configuration issues\"*\n\nLet me give you a complete project status report!",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Analysis",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "BarChart3",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    },
-    {
-      "id": "spec_009",
-      "title": "Validate Spec-Kit Workflow Compliance",
-      "description": "Check project adherence to spec-kit methodology and constitutional requirements with recommendations for improvements.",
-      "prompt": "Let's validate your project's compliance with spec-kit methodology and constitutional requirements! ✅\n\n**Compliance Validation Process:**\n\n1. **Constitutional Compliance**: I'll check if your features align with project constitution:\n   • Principle adherence in specifications\n   • Technical decisions follow governance\n   • Implementation respects constraints\n\n2. **Methodology Validation**: Verify proper spec-kit workflow:\n   • Specifications focus on WHAT/WHY (not HOW)\n   • Technical plans follow from specifications\n   • Tasks properly break down implementation\n   • Test-driven development approach\n\n3. **Quality Assessment**: Review specification and planning quality:\n   • Requirements are testable and unambiguous\n   • No [NEEDS CLARIFICATION] markers remain\n   • Success criteria are measurable\n   • Technical decisions have clear rationale\n\n4. **Process Adherence**: Check workflow execution:\n   • Proper phase progression (spec → plan → tasks → implement)\n   • Branch management and version control\n   • Documentation completeness\n\n**Compliance Report:**\n\nI'll generate:\n📋 **Constitutional Alignment** - Principle compliance score\n🔄 **Workflow Adherence** - Methodology following assessment\n📝 **Quality Metrics** - Specification and planning quality\n⚠️ **Issue Identification** - Areas needing attention\n🎯 **Recommendations** - Specific improvement actions\n\n**Any specific compliance areas you're concerned about?**\n\nReady for a complete compliance assessment?",
-      "categories": ["spec-kit"],
-      "secondaryTag": "Analysis",
-      "votes": 0,
-      "gaClicks": 0,
-      "icon": "Shield",
-      "author": "GitHub Spec-Kit",
-      "verified": true
-    }
-  ]
-}

package/dist/handlers/macos-control-handlers.d.ts

@@ -1,16 +0,0 @@
-import { ServerResult } from '../types.js';
-export declare function handleMacosAxStatus(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxListApps(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxListElements(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxFind(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxGetState(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxFindAndClick(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxClick(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxType(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxKey(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxActivate(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxWaitFor(args: unknown): Promise<ServerResult>;
-export declare function handleMacosAxBatch(args: unknown): Promise<ServerResult>;
-export declare function handleElectronDebugAttach(args: unknown): Promise<ServerResult>;
-export declare function handleElectronDebugEval(args: unknown): Promise<ServerResult>;
-export declare function handleElectronDebugDisconnect(args: unknown): Promise<ServerResult>;

package/dist/handlers/macos-control-handlers.js

@@ -1,81 +0,0 @@
-import { MacosAxStatusArgsSchema, MacosAxListAppsArgsSchema, MacosAxListElementsArgsSchema, MacosAxFindArgsSchema, MacosAxGetStateArgsSchema, MacosAxFindAndClickArgsSchema, MacosAxClickArgsSchema, MacosAxTypeArgsSchema, MacosAxKeyArgsSchema, MacosAxActivateArgsSchema, MacosAxWaitForArgsSchema, MacosAxBatchArgsSchema, ElectronDebugAttachArgsSchema, ElectronDebugEvalArgsSchema, ElectronDebugDisconnectArgsSchema, } from '../tools/schemas.js';
-import { macosControlOrchestrator } from '../tools/macos-control/orchestrator.js';
-function toServerResult(result) {
-    if (!result?.ok) {
-        const message = result?.error?.message || 'macOS control request failed';
-        const code = result?.error?.code ? ` (${result.error.code})` : '';
-        return {
-            content: [{
-                    type: 'text',
-                    text: `Error${code}: ${message}`,
-                }],
-            isError: true,
-        };
-    }
-    return {
-        content: [{
-                type: 'text',
-                text: JSON.stringify(result.data ?? {}, null, 2),
-            }],
-    };
-}
-export async function handleMacosAxStatus(args) {
-    MacosAxStatusArgsSchema.parse(args || {});
-    return toServerResult(await macosControlOrchestrator.axStatus());
-}
-export async function handleMacosAxListApps(args) {
-    MacosAxListAppsArgsSchema.parse(args || {});
-    return toServerResult(await macosControlOrchestrator.axListApps());
-}
-export async function handleMacosAxListElements(args) {
-    const parsed = MacosAxListElementsArgsSchema.parse(args || {});
-    return toServerResult(await macosControlOrchestrator.axListElements(parsed));
-}
-export async function handleMacosAxFind(args) {
-    const parsed = MacosAxFindArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axFind(parsed));
-}
-export async function handleMacosAxGetState(args) {
-    const parsed = MacosAxGetStateArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axGetState(parsed));
-}
-export async function handleMacosAxFindAndClick(args) {
-    const parsed = MacosAxFindAndClickArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axFindAndClick(parsed));
-}
-export async function handleMacosAxClick(args) {
-    const parsed = MacosAxClickArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axClick(parsed));
-}
-export async function handleMacosAxType(args) {
-    const parsed = MacosAxTypeArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axType(parsed.text));
-}
-export async function handleMacosAxKey(args) {
-    const parsed = MacosAxKeyArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axKey(parsed.key, parsed.modifiers ?? []));
-}
-export async function handleMacosAxActivate(args) {
-    const parsed = MacosAxActivateArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axActivate(parsed.app));
-}
-export async function handleMacosAxWaitFor(args) {
-    const parsed = MacosAxWaitForArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axWaitFor(parsed));
-}
-export async function handleMacosAxBatch(args) {
-    const parsed = MacosAxBatchArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.axBatch(parsed.commands, parsed.stopOnError));
-}
-export async function handleElectronDebugAttach(args) {
-    const parsed = ElectronDebugAttachArgsSchema.parse(args || {});
-    return toServerResult(await macosControlOrchestrator.electronDebugAttach(parsed));
-}
-export async function handleElectronDebugEval(args) {
-    const parsed = ElectronDebugEvalArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.electronDebugEval(parsed));
-}
-export async function handleElectronDebugDisconnect(args) {
-    const parsed = ElectronDebugDisconnectArgsSchema.parse(args);
-    return toServerResult(await macosControlOrchestrator.electronDebugDisconnect(parsed));
-}

package/dist/handlers/node-handlers.d.ts

@@ -1,6 +0,0 @@
-import { ServerResult } from '../types.js';
-/**
- * Handle execute_node command
- * Executes Node.js code using the same Node runtime as the MCP
- */
-export declare function handleExecuteNode(args: unknown): Promise<ServerResult>;