purple-ai 0.0.4 → 0.0.6

package/mcp-server/dist/index.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Purple MCP Server
+ *
+ * This MCP server provides status update tools for Claude Code agents
+ * to communicate their progress back to the Purple CLI status bar.
+ *
+ * Tools provided:
+ * - purple_update_status: Full status update with all fields
+ * - purple_set_phase: Quick helper to set just the phase
+ * - purple_report_progress: Report ticket progress during implementation
+ *
+ * Communication flow:
+ * Claude Agent -> MCP Server (stdio) -> HTTP POST localhost:7685 -> Purple CLI
+ *
+ * Changelog:
+ * - 2026-01-12: Initial implementation
+ */
+export {};

package/mcp-server/dist/index.js

@@ -0,0 +1,299 @@
+/**
+ * Purple MCP Server
+ *
+ * This MCP server provides status update tools for Claude Code agents
+ * to communicate their progress back to the Purple CLI status bar.
+ *
+ * Tools provided:
+ * - purple_update_status: Full status update with all fields
+ * - purple_set_phase: Quick helper to set just the phase
+ * - purple_report_progress: Report ticket progress during implementation
+ *
+ * Communication flow:
+ * Claude Agent -> MCP Server (stdio) -> HTTP POST localhost:7685 -> Purple CLI
+ *
+ * Changelog:
+ * - 2026-01-12: Initial implementation
+ */
+import { Server } from "@modelcontextprotocol/sdk/server/index.js";
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
+import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js";
+// Purple CLI status server endpoints
+const PURPLE_STATUS_URL = "http://127.0.0.1:7685/status";
+const PURPLE_STANDARDS_COMPLETE_URL = "http://127.0.0.1:7685/standards-complete";
+// Tool definitions
+const TOOLS = [
+    {
+        name: "purple_update_status",
+        description: "Update the Purple CLI status bar with current progress. Use this to keep users informed of agent activity without requiring them to read your output.",
+        inputSchema: {
+            type: "object",
+            properties: {
+                phase: {
+                    type: "string",
+                    description: 'Current phase (e.g., "0 - Validation", "1 - Product Spec", "2 - Engineering", "3 - Implementation", "4 - Review")',
+                },
+                agent: {
+                    type: "string",
+                    description: 'Active agent name (e.g., "orchestrator", "senior-engineer", "spec-writer")',
+                },
+                currentTicket: {
+                    type: "number",
+                    description: "Current ticket number being worked on (1-indexed)",
+                },
+                totalTickets: {
+                    type: "number",
+                    description: "Total number of tickets in the implementation",
+                },
+                mode: {
+                    type: "string",
+                    enum: ["plan", "execute", "review"],
+                    description: 'Current working mode: "plan" (analyzing/planning), "execute" (writing code), "review" (verifying work)',
+                },
+                tool: {
+                    type: "string",
+                    description: 'Currently active tool being used (e.g., "Edit", "Grep", "Read", "Bash")',
+                },
+                activeFile: {
+                    type: "string",
+                    description: "File currently being worked on (e.g., src/components/Button.tsx)",
+                },
+            },
+            additionalProperties: false,
+        },
+    },
+    {
+        name: "purple_set_phase",
+        description: "Quick helper to set just the current phase. Use this when transitioning between major workflow phases.",
+        inputSchema: {
+            type: "object",
+            properties: {
+                phase: {
+                    type: "string",
+                    description: 'Phase name (e.g., "0 - Validation", "1 - Product Spec", "2 - Engineering", "3 - Implementation", "4 - Review")',
+                },
+            },
+            required: ["phase"],
+            additionalProperties: false,
+        },
+    },
+    {
+        name: "purple_report_progress",
+        description: "Report ticket progress during implementation. Call this at the start of each ticket to update the progress indicator.",
+        inputSchema: {
+            type: "object",
+            properties: {
+                current: {
+                    type: "number",
+                    description: "Current ticket number (1-indexed)",
+                },
+                total: {
+                    type: "number",
+                    description: "Total number of tickets",
+                },
+            },
+            required: ["current", "total"],
+            additionalProperties: false,
+        },
+    },
+    {
+        name: "purple_ticket_status",
+        description: "Update ticket progress with phase information. Use this to show progress like '5/12 tickets done' in the status bar. Call this whenever starting a new ticket or completing one.",
+        inputSchema: {
+            type: "object",
+            properties: {
+                phase: {
+                    type: "string",
+                    description: 'Current phase name (e.g., "Phase 3: Implementation", "Phase 4: Review")',
+                },
+                completed: {
+                    type: "number",
+                    description: "Number of tickets completed so far",
+                },
+                total: {
+                    type: "number",
+                    description: "Total number of tickets",
+                },
+                currentTicketName: {
+                    type: "string",
+                    description: 'Name or description of the current ticket being worked on (e.g., "AUTH-001: User Login")',
+                },
+            },
+            required: ["completed", "total"],
+            additionalProperties: false,
+        },
+    },
+    {
+        name: "purple_standards_complete",
+        description: "Signal that standards creation/update is complete. Call this when the create-standards agent has finished writing all standards files. This triggers automatic upload of standards to the Purple database.",
+        inputSchema: {
+            type: "object",
+            properties: {
+                message: {
+                    type: "string",
+                    description: 'Optional completion message (e.g., "Created 12 standards files")',
+                },
+            },
+            additionalProperties: false,
+        },
+    },
+];
+/**
+ * Sends a status update to the Purple CLI via HTTP POST.
+ * Gracefully handles failures since Purple may not be running.
+ */
+async function sendStatusUpdate(payload) {
+    try {
+        const response = await fetch(PURPLE_STATUS_URL, {
+            method: "POST",
+            headers: {
+                "Content-Type": "application/json",
+            },
+            body: JSON.stringify(payload),
+        });
+        if (!response.ok) {
+            // Log but don't throw - Purple might be busy or restarting
+            console.error(`Status update failed with HTTP ${response.status}: ${response.statusText}`);
+        }
+    }
+    catch (error) {
+        // Non-fatal - Purple CLI might not be running
+        // This is expected when running Claude Code standalone
+        console.error("Failed to send status update (Purple may not be active):", error);
+    }
+}
+/**
+ * Sends a standards complete signal to the Purple CLI.
+ * This triggers the CLI to upload all standards to the database.
+ */
+async function sendStandardsComplete(payload) {
+    try {
+        const response = await fetch(PURPLE_STANDARDS_COMPLETE_URL, {
+            method: "POST",
+            headers: {
+                "Content-Type": "application/json",
+            },
+            body: JSON.stringify(payload),
+        });
+        if (!response.ok) {
+            console.error(`Standards complete signal failed with HTTP ${response.status}: ${response.statusText}`);
+        }
+    }
+    catch (error) {
+        console.error("Failed to send standards complete signal (Purple may not be active):", error);
+    }
+}
+/**
+ * Main function to initialize and run the MCP server
+ */
+async function main() {
+    // Create MCP server instance
+    const server = new Server({
+        name: "purple-status",
+        version: "1.0.0",
+    }, {
+        capabilities: {
+            tools: {},
+        },
+    });
+    // Register tools/list handler
+    server.setRequestHandler(ListToolsRequestSchema, async () => {
+        return {
+            tools: TOOLS,
+        };
+    });
+    // Register tools/call handler
+    server.setRequestHandler(CallToolRequestSchema, async (request) => {
+        const { name, arguments: args } = request.params;
+        // Build payload based on tool called
+        let payload;
+        switch (name) {
+            case "purple_update_status": {
+                const typedArgs = args;
+                payload = {
+                    tool: name,
+                    phase: typedArgs.phase,
+                    agent: typedArgs.agent,
+                    currentTicket: typedArgs.currentTicket,
+                    totalTickets: typedArgs.totalTickets,
+                    mode: typedArgs.mode,
+                    activeTool: typedArgs.tool,
+                    activeFile: typedArgs.activeFile,
+                };
+                break;
+            }
+            case "purple_set_phase": {
+                const typedArgs = args;
+                payload = {
+                    tool: name,
+                    phase: typedArgs.phase,
+                };
+                break;
+            }
+            case "purple_report_progress": {
+                const typedArgs = args;
+                payload = {
+                    tool: name,
+                    currentTicket: typedArgs.current,
+                    totalTickets: typedArgs.total,
+                };
+                break;
+            }
+            case "purple_ticket_status": {
+                const typedArgs = args;
+                payload = {
+                    tool: name,
+                    phase: typedArgs.phase,
+                    // completed means how many are done, so current ticket is completed + 1
+                    currentTicket: typedArgs.completed + 1,
+                    totalTickets: typedArgs.total,
+                    activeFile: typedArgs.currentTicketName, // Use activeFile to show ticket name
+                };
+                break;
+            }
+            case "purple_standards_complete": {
+                const typedArgs = args;
+                // Send standards complete signal (separate endpoint)
+                await sendStandardsComplete({ message: typedArgs.message });
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: "Standards upload triggered",
+                        },
+                    ],
+                };
+            }
+            default:
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: `Unknown tool: ${name}`,
+                        },
+                    ],
+                    isError: true,
+                };
+        }
+        // Send status update to Purple CLI
+        await sendStatusUpdate(payload);
+        return {
+            content: [
+                {
+                    type: "text",
+                    text: "Status updated",
+                },
+            ],
+        };
+    });
+    // Create stdio transport and connect
+    const transport = new StdioServerTransport();
+    await server.connect(transport);
+    // Log startup (to stderr to avoid interfering with stdio protocol)
+    console.error("Purple MCP server started");
+}
+// Run the server
+main().catch((error) => {
+    console.error("Fatal error in MCP server:", error);
+    process.exit(1);
+});

package/mcp-server/node_modules/@hono/node-server/README.md

@@ -0,0 +1,357 @@
+# Node.js Adapter for Hono
+
+This adapter `@hono/node-server` allows you to run your Hono application on Node.js.
+Initially, Hono wasn't designed for Node.js, but with this adapter, you can now use Hono on Node.js.
+It utilizes web standard APIs implemented in Node.js version 18 or higher.
+
+## Benchmarks
+
+Hono is 3.5 times faster than Express.
+
+Express:
+
+```txt
+$ bombardier -d 10s --fasthttp http://localhost:3000/
+
+Statistics        Avg      Stdev        Max
+  Reqs/sec     16438.94    1603.39   19155.47
+  Latency        7.60ms     7.51ms   559.89ms
+  HTTP codes:
+    1xx - 0, 2xx - 164494, 3xx - 0, 4xx - 0, 5xx - 0
+    others - 0
+  Throughput:     4.55MB/s
+```
+
+Hono + `@hono/node-server`:
+
+```txt
+$ bombardier -d 10s --fasthttp http://localhost:3000/
+
+Statistics        Avg      Stdev        Max
+  Reqs/sec     58296.56    5512.74   74403.56
+  Latency        2.14ms     1.46ms   190.92ms
+  HTTP codes:
+    1xx - 0, 2xx - 583059, 3xx - 0, 4xx - 0, 5xx - 0
+    others - 0
+  Throughput:    12.56MB/s
+```
+
+## Requirements
+
+It works on Node.js versions greater than 18.x. The specific required Node.js versions are as follows:
+
+- 18.x => 18.14.1+
+- 19.x => 19.7.0+
+- 20.x => 20.0.0+
+
+Essentially, you can simply use the latest version of each major release.
+
+## Installation
+
+You can install it from the npm registry with `npm` command:
+
+```sh
+npm install @hono/node-server
+```
+
+Or use `yarn`:
+
+```sh
+yarn add @hono/node-server
+```
+
+## Usage
+
+Just import `@hono/node-server` at the top and write the code as usual.
+The same code that runs on Cloudflare Workers, Deno, and Bun will work.
+
+```ts
+import { serve } from '@hono/node-server'
+import { Hono } from 'hono'
+
+const app = new Hono()
+app.get('/', (c) => c.text('Hono meets Node.js'))
+
+serve(app, (info) => {
+  console.log(`Listening on http://localhost:${info.port}`) // Listening on http://localhost:3000
+})
+```
+
+For example, run it using `ts-node`. Then an HTTP server will be launched. The default port is `3000`.
+
+```sh
+ts-node ./index.ts
+```
+
+Open `http://localhost:3000` with your browser.
+
+## Options
+
+### `port`
+
+```ts
+serve({
+  fetch: app.fetch,
+  port: 8787, // Port number, default is 3000
+})
+```
+
+### `createServer`
+
+```ts
+import { createServer } from 'node:https'
+import fs from 'node:fs'
+
+//...
+
+serve({
+  fetch: app.fetch,
+  createServer: createServer,
+  serverOptions: {
+    key: fs.readFileSync('test/fixtures/keys/agent1-key.pem'),
+    cert: fs.readFileSync('test/fixtures/keys/agent1-cert.pem'),
+  },
+})
+```
+
+### `overrideGlobalObjects`
+
+The default value is `true`. The Node.js Adapter rewrites the global Request/Response and uses a lightweight Request/Response to improve performance. If you don't want to do that, set `false`.
+
+```ts
+serve({
+  fetch: app.fetch,
+  overrideGlobalObjects: false,
+})
+```
+
+### `autoCleanupIncoming`
+
+The default value is `true`. The Node.js Adapter automatically cleans up (explicitly call `destroy()` method) if application is not finished to consume the incoming request. If you don't want to do that, set `false`.
+
+If the application accepts connections from arbitrary clients, this cleanup must be done otherwise incomplete requests from clients may cause the application to stop responding. If your application only accepts connections from trusted clients, such as in a reverse proxy environment and there is no process that returns a response without reading the body of the POST request all the way through, you can improve performance by setting it to `false`.
+
+```ts
+serve({
+  fetch: app.fetch,
+  autoCleanupIncoming: false,
+})
+```
+
+## Middleware
+
+Most built-in middleware also works with Node.js.
+Read [the documentation](https://hono.dev/middleware/builtin/basic-auth) and use the Middleware of your liking.
+
+```ts
+import { serve } from '@hono/node-server'
+import { Hono } from 'hono'
+import { prettyJSON } from 'hono/pretty-json'
+
+const app = new Hono()
+
+app.get('*', prettyJSON())
+app.get('/', (c) => c.json({ 'Hono meets': 'Node.js' }))
+
+serve(app)
+```
+
+## Serve Static Middleware
+
+Use Serve Static Middleware that has been created for Node.js.
+
+```ts
+import { serveStatic } from '@hono/node-server/serve-static'
+
+//...
+
+app.use('/static/*', serveStatic({ root: './' }))
+```
+
+If using a relative path, `root` will be relative to the current working directory from which the app was started.
+
+This can cause confusion when running your application locally.
+
+Imagine your project structure is:
+
+```
+my-hono-project/
+  src/
+    index.ts
+  static/
+    index.html
+```
+
+Typically, you would run your app from the project's root directory (`my-hono-project`),
+so you would need the following code to serve the `static` folder:
+
+```ts
+app.use('/static/*', serveStatic({ root: './static' }))
+```
+
+Notice that `root` here is not relative to `src/index.ts`, rather to `my-hono-project`.
+
+### Options
+
+#### `rewriteRequestPath`
+
+If you want to serve files in `./.foojs` with the request path `/__foo/*`, you can write like the following.
+
+```ts
+app.use(
+  '/__foo/*',
+  serveStatic({
+    root: './.foojs/',
+    rewriteRequestPath: (path: string) => path.replace(/^\/__foo/, ''),
+  })
+)
+```
+
+#### `onFound`
+
+You can specify handling when the requested file is found with `onFound`.
+
+```ts
+app.use(
+  '/static/*',
+  serveStatic({
+    // ...
+    onFound: (_path, c) => {
+      c.header('Cache-Control', `public, immutable, max-age=31536000`)
+    },
+  })
+)
+```
+
+#### `onNotFound`
+
+The `onNotFound` is useful for debugging. You can write a handle for when a file is not found.
+
+```ts
+app.use(
+  '/static/*',
+  serveStatic({
+    root: './non-existent-dir',
+    onNotFound: (path, c) => {
+      console.log(`${path} is not found, request to ${c.req.path}`)
+    },
+  })
+)
+```
+
+#### `precompressed`
+
+The `precompressed` option checks if files with extensions like `.br` or `.gz` are available and serves them based on the `Accept-Encoding` header. It prioritizes Brotli, then Zstd, and Gzip. If none are available, it serves the original file.
+
+```ts
+app.use(
+  '/static/*',
+  serveStatic({
+    precompressed: true,
+  })
+)
+```
+
+## ConnInfo Helper
+
+You can use the [ConnInfo Helper](https://hono.dev/docs/helpers/conninfo) by importing `getConnInfo` from `@hono/node-server/conninfo`.
+
+```ts
+import { getConnInfo } from '@hono/node-server/conninfo'
+
+app.get('/', (c) => {
+  const info = getConnInfo(c) // info is `ConnInfo`
+  return c.text(`Your remote address is ${info.remote.address}`)
+})
+```
+
+## Accessing Node.js API
+
+You can access the Node.js API from `c.env` in Node.js. For example, if you want to specify a type, you can write the following.
+
+```ts
+import { serve } from '@hono/node-server'
+import type { HttpBindings } from '@hono/node-server'
+import { Hono } from 'hono'
+
+const app = new Hono<{ Bindings: HttpBindings }>()
+
+app.get('/', (c) => {
+  return c.json({
+    remoteAddress: c.env.incoming.socket.remoteAddress,
+  })
+})
+
+serve(app)
+```
+
+The APIs that you can get from `c.env` are as follows.
+
+```ts
+type HttpBindings = {
+  incoming: IncomingMessage
+  outgoing: ServerResponse
+}
+
+type Http2Bindings = {
+  incoming: Http2ServerRequest
+  outgoing: Http2ServerResponse
+}
+```
+
+## Direct response from Node.js API
+
+You can directly respond to the client from the Node.js API.
+In that case, the response from Hono should be ignored, so return `RESPONSE_ALREADY_SENT`.
+
+> [!NOTE]
+> This feature can be used when migrating existing Node.js applications to Hono, but we recommend using Hono's API for new applications.
+
+```ts
+import { serve } from '@hono/node-server'
+import type { HttpBindings } from '@hono/node-server'
+import { RESPONSE_ALREADY_SENT } from '@hono/node-server/utils/response'
+import { Hono } from 'hono'
+
+const app = new Hono<{ Bindings: HttpBindings }>()
+
+app.get('/', (c) => {
+  const { outgoing } = c.env
+  outgoing.writeHead(200, { 'Content-Type': 'text/plain' })
+  outgoing.end('Hello World\n')
+
+  return RESPONSE_ALREADY_SENT
+})
+
+serve(app)
+```
+
+## Listen to a UNIX domain socket
+
+You can configure the HTTP server to listen to a UNIX domain socket instead of a TCP port.
+
+```ts
+import { createAdaptorServer } from '@hono/node-server'
+
+// ...
+
+const socketPath ='/tmp/example.sock'
+
+const server = createAdaptorServer(app)
+server.listen(socketPath, () => {
+  console.log(`Listening on ${socketPath}`)
+})
+```
+
+## Related projects
+
+- Hono - <https://hono.dev>
+- Hono GitHub repository - <https://github.com/honojs/hono>
+
+## Author
+
+Yusuke Wada <https://github.com/yusukebe>
+
+## License
+
+MIT

package/mcp-server/node_modules/@hono/node-server/dist/conninfo.d.mts

@@ -0,0 +1,10 @@
+import { GetConnInfo } from 'hono/conninfo';
+
+/**
+ * ConnInfo Helper for Node.js
+ * @param c Context
+ * @returns ConnInfo
+ */
+declare const getConnInfo: GetConnInfo;
+
+export { getConnInfo };

package/mcp-server/node_modules/@hono/node-server/dist/conninfo.d.ts

@@ -0,0 +1,10 @@
+import { GetConnInfo } from 'hono/conninfo';
+
+/**
+ * ConnInfo Helper for Node.js
+ * @param c Context
+ * @returns ConnInfo
+ */
+declare const getConnInfo: GetConnInfo;
+
+export { getConnInfo };