@sureshdsk/devflow-mcp 3.0.0 → 3.0.2

package/.next/standalone/devflow/specs/precommit/tasks.md

@@ -0,0 +1,283 @@
+# Tasks: Setup automatic linting & formatting on git commit
+
+## 1. Delivery Overview
+
+### 1.1 Objective
+
+Add a pre-commit hook pipeline that automatically lints and formats staged files on every `git commit`, ensuring consistent code quality without manual effort.
+
+### 1.2 In-Scope Outcomes
+
+- Husky pre-commit hook installed automatically on `npm install`
+- lint-staged runs ESLint + Prettier on staged files
+- Prettier config and ignore file in place
+- Full codebase formatted in a baseline commit
+
+### 1.3 Non-Goals
+
+- CI pipeline changes
+- Commit message linting (commitlint)
+- Pre-push hooks (tests, typecheck)
+- Changing existing ESLint rules
+
+### 1.4 Global Constraints
+
+- Must not break the existing `postinstall` script
+- Must skip hook installation gracefully in CI (`CI=true`)
+
+### 1.5 Shared References
+
+- Proposal: `devflow/specs/precommit/proposal.md`
+- Design: `devflow/specs/precommit/design.md`
+- Specs: `devflow/specs/precommit/specs.md`
+- `package.json`
+
+## 2. Task Cards
+
+**Execution Plan**
+
+1. npm install --save-dev husky lint-staged prettier\n2. Add prepare script and lint-staged config to package.json\n3. Validate
+
+### 2.1 Task: Install dependencies and configure package.json
+
+- [ ] **Status**
+- **Task ID:** `T1`
+- **Owner Type:** `agent`
+- **Priority:** `P0`
+- **Depends On:** `none`
+
+**Goal**
+Install husky, lint-staged, and prettier as devDependencies and add the required scripts and config to package.json.
+
+**Context**
+The project already has ESLint configured. The `postinstall` script exists and must not be affected. Husky v9 uses a `prepare` script (not `postinstall`) to set up hooks.
+
+**Scope**
+
+- In scope:
+  - `npm install --save-dev husky lint-staged prettier`
+  - Add `"prepare": "husky"` to scripts
+  - Add `lint-staged` config block to package.json
+- Out of scope:
+  - Creating hook files (T2)
+  - Prettier config files (T3)
+
+**Implementation Targets**
+
+- Files to create/update:
+  - `package.json`
+
+**Execution Steps**
+
+1. Run `npm install --save-dev husky lint-staged prettier`
+2. Add `"prepare": "husky"` to the `scripts` section of package.json
+3. Add lint-staged config to package.json:
+   ```json
+   "lint-staged": {
+     "*.{ts,tsx}": ["eslint --fix", "prettier --write"],
+     "*.{js,json,css,md}": ["prettier --write"]
+   }
+   ```
+
+**Validation**
+
+- Commands to run:
+  - `npm ls husky lint-staged prettier` — all three listed
+  - `node -e "const p=require('./package.json'); console.log(p.scripts.prepare, p['lint-staged'])"` — outputs expected values
+
+**Acceptance Criteria**
+
+- husky, lint-staged, prettier are in devDependencies
+- `prepare` script is `"husky"`
+- lint-staged config matches the design spec
+
+**Task Summary**
+
+- Completed: yes
+- What was done: Installed husky, lint-staged, and prettier as devDependencies. Added prepare script and lint-staged config to package.json.
+- Files changed: package.json, package-lock.json
+- Issues encountered: None
+- Follow-ups: None
+  **Execution Plan**
+
+1. Run npx husky init\n2. Replace .husky/pre-commit contents with npx lint-staged\n3. Validate
+
+### 2.2 Task: Initialize husky and create pre-commit hook
+
+- [ ] **Status**
+- **Task ID:** `T2`
+- **Owner Type:** `agent`
+- **Priority:** `P0`
+- **Depends On:** `T1`
+
+**Goal**
+Initialize husky and create the `.husky/pre-commit` hook that runs lint-staged.
+
+**Context**
+Husky v9 uses `npx husky init` which creates `.husky/pre-commit` with a default command. We need to replace it with `npx lint-staged`.
+
+**Scope**
+
+- In scope:
+  - Run `npx husky init`
+  - Set `.husky/pre-commit` contents to `npx lint-staged`
+- Out of scope:
+  - Other hook types (pre-push, commit-msg)
+
+**Implementation Targets**
+
+- Files to create/update:
+  - `.husky/pre-commit`
+
+**Execution Steps**
+
+1. Run `npx husky init`
+2. Replace `.husky/pre-commit` contents with `npx lint-staged`
+
+**Validation**
+
+- Commands to run:
+  - `cat .husky/pre-commit` — should contain `npx lint-staged`
+  - `ls -la .husky/` — pre-commit file exists
+
+**Acceptance Criteria**
+
+- `.husky/pre-commit` exists and contains `npx lint-staged`
+- Hook is executable
+
+**Task Summary**
+
+- Completed: yes
+- What was done: Initialized husky and set .husky/pre-commit to run npx lint-staged.
+- Files changed: .husky/pre-commit
+- Issues encountered: None
+- Follow-ups: None
+  **Execution Plan**
+
+1. Create .prettierrc\n2. Create .prettierignore\n3. Validate with npx prettier --check src/
+
+### 2.3 Task: Add Prettier configuration files
+
+- [ ] **Status**
+- **Task ID:** `T3`
+- **Owner Type:** `agent`
+- **Priority:** `P0`
+- **Depends On:** `none`
+
+**Goal**
+Create `.prettierrc` and `.prettierignore` with project defaults.
+
+**Context**
+No Prettier config exists yet. The design specifies: single quotes, trailing commas, 2-space indent, 100 char print width, semicolons enabled.
+
+**Scope**
+
+- In scope:
+  - Create `.prettierrc`
+  - Create `.prettierignore`
+- Out of scope:
+  - Running Prettier on the codebase (T4)
+
+**Implementation Targets**
+
+- Files to create/update:
+  - `.prettierrc`
+  - `.prettierignore`
+
+**Execution Steps**
+
+1. Create `.prettierrc`:
+   ```json
+   {
+     "semi": true,
+     "singleQuote": true,
+     "trailingComma": "all",
+     "tabWidth": 2,
+     "printWidth": 100
+   }
+   ```
+2. Create `.prettierignore`:
+   ```
+   node_modules
+   .next
+   dist
+   drizzle
+   ```
+
+**Validation**
+
+- Commands to run:
+  - `npx prettier --check src/` — runs without config errors (files may not pass yet)
+
+**Acceptance Criteria**
+
+- `.prettierrc` exists with the specified settings
+- `.prettierignore` excludes node_modules, .next, dist, drizzle
+
+**Task Summary**
+
+- Completed: yes
+- What was done: Created .prettierrc with project defaults and .prettierignore excluding node_modules, .next, dist, drizzle.
+- Files changed: .prettierrc, .prettierignore
+- Issues encountered: None
+- Follow-ups: None
+
+**Execution Plan**
+
+1. Run npx prettier --write .\n2. Verify with npx prettier --check .\n3. Report results — user will commit when ready
+
+### 2.4 Task: Run baseline formatting on the full codebase
+- [ ] **Status**
+- **Task ID:** `T4`
+- **Owner Type:** `agent`
+- **Priority:** `P1`
+- **Depends On:** `T1, T3`
+
+**Goal**
+Run Prettier across the entire codebase and commit all formatting changes in a single commit, so subsequent commits aren't polluted with formatting noise.
+
+**Context**
+The existing code was not written with Prettier. Running it for the first time will touch many files. This must be a standalone commit before the hook is active for the team.
+
+**Scope**
+- In scope:
+  - Run `npx prettier --write .`
+  - Commit all changes as "chore: format codebase with prettier"
+- Out of scope:
+  - Fixing any ESLint errors surfaced by formatting
+
+**Implementation Targets**
+- Files to create/update:
+  - All `.ts`, `.tsx`, `.js`, `.json`, `.css`, `.md` files in the project
+
+**Execution Steps**
+1. Run `npx prettier --write .`
+2. Review the diff to ensure no unexpected file changes
+3. Stage and commit: `git add -A && git commit -m "chore: format codebase with prettier"`
+
+**Validation**
+- Commands to run:
+  - `npx prettier --check .` — should pass with no errors after formatting
+
+**Acceptance Criteria**
+- `npx prettier --check .` exits 0
+- All formatting changes are in a single commit
+
+**Task Summary**
+- Completed: yes
+- What was done: Ran npx prettier --write . across the full codebase. All files now pass npx prettier --check.
+- Files changed: 52+ files across src/, scripts/, devflow/, docs/, config files
+- Issues encountered: CONTRIBUTING.md needed a second pass
+- Follow-ups: User should commit all changes and verify npm run lint still passes
+
+## 3. Cross-Task Verification
+- [ ] `git commit` on a file with formatting issues auto-fixes and commits successfully
+- [ ] `git commit` on a file with a non-fixable ESLint error blocks the commit
+- [ ] `npm install` in a fresh clone installs husky hooks automatically
+- [ ] All scenarios from specs.md are satisfied
+
+## 4. Completion Gate
+- [ ] All task cards are checked complete
+- [ ] `npx prettier --check .` passes
+- [ ] `npm run lint` passes
+- [ ] Pre-commit hook is functional end-to-end

package/.next/standalone/docs/custom-schemas.md

@@ -0,0 +1,117 @@
+# Custom Schemas
+
+Schemas define the artifact workflow for a spec — which documents are required,
+their dependencies, and quality rules.
+
+## Built-in Schemas
+
+DevFlow ships with several schemas: `spec-driven`, `backend-api`,
+`frontend-product`, `data-engineering`, and `devops-platform`. List them with
+the `list_schemas` MCP tool.
+
+## Creating a Custom Schema
+
+### Using `/df:schema` (recommended)
+
+Run the `/df:df-schema` skill in Claude Code. It will interactively ask about
+your project type, workflow stages, and quality preferences, then create the
+schema files for you.
+
+### Manual Creation
+
+Create a directory under `devflow/schemas/<name>/` with:
+
+```
+devflow/schemas/my-schema/
+├── schema.yaml
+└── templates/
+    ├── proposal.md
+    ├── design.md
+    └── tasks.md
+```
+
+### schema.yaml Structure
+
+```yaml
+name: my-schema # Must match directory name
+version: 1
+artifacts:
+  - id: proposal # Unique identifier
+    generates: proposal.md
+    description: Change intent and scope
+    template: proposal.md # File in templates/ dir
+    requires: [] # No dependencies — this is a root artifact
+  - id: design
+    generates: design.md
+    description: Technical approach
+    template: design.md
+    requires: [proposal] # Blocked until proposal is approved
+  - id: tasks
+    generates: tasks.md
+    description: Implementation tasks
+    template: tasks.md
+    requires: [design]
+qualityRules:
+  requireRfc2119: true # Enforce MUST/SHOULD/MAY keywords
+  minScenariosPerRequirement: 1 # Min test scenarios per requirement
+apply:
+  requires: [tasks] # Which artifacts gate promotion to Kanban tasks
+```
+
+### Key Concepts
+
+- **Artifact DAG**: Artifacts form a directed acyclic graph via `requires`.
+  An artifact is "blocked" until all its dependencies are approved.
+- **Quality rules**: Optional enforcement of RFC 2119 language and scenario
+  coverage in specs.
+- **Apply gate**: The `apply.requires` field controls which artifacts must be
+  approved before a spec can be promoted to Kanban tasks via `promote_spec`.
+
+### Using the `create_schema` MCP Tool
+
+You can also create schemas programmatically:
+
+```
+create_schema({
+  name: "ml-pipeline",
+  artifacts: [
+    { id: "proposal", generates: "proposal.md", description: "Problem statement", template: "proposal.md", requires: [] },
+    { id: "data-spec", generates: "data-spec.md", description: "Data requirements", template: "data-spec.md", requires: ["proposal"] },
+    { id: "model-design", generates: "model-design.md", description: "Model architecture", template: "model-design.md", requires: ["data-spec"] },
+    { id: "tasks", generates: "tasks.md", description: "Implementation tasks", template: "tasks.md", requires: ["model-design"] }
+  ],
+  qualityRules: { requireRfc2119: true },
+  apply: { requires: ["tasks"] },
+  templates: {
+    "proposal": "# Proposal\n\n## Problem Statement\n...",
+    "data-spec": "# Data Specification\n\n## Sources\n...",
+    "model-design": "# Model Design\n\n## Architecture\n...",
+    "tasks": "# Tasks\n\n- [ ] Task 1\n..."
+  }
+})
+```
+
+## Project-local vs Bundled Schemas
+
+- **Bundled**: Ship with DevFlow in `src/schemas/`. Cannot be modified by users.
+- **Project-local**: Live in `devflow/schemas/`. Override bundled schemas if
+  names conflict. Created by `create_schema` or `/df:df-schema`.
+
+## Template Authoring Tips
+
+- Use clear section headers that guide the author
+- Include HTML comments (`<!-- ... -->`) with instructions
+- Reference the artifact's purpose from `schema.yaml` description
+- Keep templates focused — each artifact should have a single responsibility
+
+## Setting a Default Schema
+
+Create or edit `devflow/project-config.json`:
+
+```json
+{
+  "defaultSchema": "my-schema"
+}
+```
+
+New specs created without an explicit `schema` parameter will use this schema.

package/.next/standalone/docs/local-dev-guide.md

@@ -0,0 +1,73 @@
+# Local Development Guide
+
+## Prerequisites
+
+- Node.js 20+
+- Bun 1.0+ (required for the MCP server)
+
+## Build & Install Locally
+
+### 1. Clone & install dependencies
+
+```bash
+git clone https://github.com/sureshdsk/devflow-mcp.git
+cd devflow-mcp
+npm install
+```
+
+### 2. Build
+
+```bash
+npm run build
+```
+
+This runs `next build` and produces the `.next/standalone` output.
+
+### 3. Install globally (link)
+
+```bash
+npm link
+```
+
+This symlinks the package globally, making `devflow` and `devflow-mcp` commands available in your terminal.
+
+### 4. Use it
+
+```bash
+devflow init          # Initialize the database
+devflow dev           # Start the web UI (default port 3000)
+devflow mcp           # Start the MCP server
+```
+
+### Development mode (hot reload)
+
+```bash
+npm run dev
+```
+
+Starts Next.js dev server with hot reload on port 3000.
+
+### Custom ports
+
+```bash
+DEVFLOW_PORT=4000 DEVFLOW_WS_PORT=4001 devflow dev
+```
+
+## Uninstall
+
+```bash
+# From the project directory
+npm unlink
+```
+
+Or if that doesn't work:
+
+```bash
+npm unlink -g @sureshdsk/devflow-mcp
+```
+
+To verify it's removed:
+
+```bash
+which devflow  # should return nothing
+```

package/.next/standalone/drizzle.config.ts

@@ -1,12 +1,12 @@
-import type { Config } from "drizzle-kit";
-import { join } from "path";
-import { homedir } from "os";
+import type { Config } from 'drizzle-kit';
+import { join } from 'path';
+import { homedir } from 'os';
 
 export default {
-  schema: "./src/db/schema.ts",
-  out: "./drizzle",
-  dialect: "turso",
+  schema: './src/db/schema.ts',
+  out: './drizzle',
+  dialect: 'turso',
   dbCredentials: {
-    url: `file:${join(homedir(), ".devflow", "devflow.db")}`,
+    url: `file:${join(homedir(), '.devflow', 'devflow.db')}`,
   },
 } satisfies Config;

package/.next/standalone/eslint.config.mjs

@@ -1,9 +1,9 @@
-import nextConfig from "eslint-config-next";
+import nextConfig from 'eslint-config-next';
 
 const eslintConfig = [
   ...nextConfig,
   {
-    ignores: ["node_modules/**"],
+    ignores: ['node_modules/**'],
   },
 ];
 

package/.next/standalone/instrumentation.ts

@@ -1,10 +1,8 @@
 export async function register() {
   // Only run on Node.js server, not during build or on edge runtime
-  if (process.env.NEXT_RUNTIME === "nodejs") {
-    const { startWebSocketServer } = await import("./src/websocket/server");
-    const port = process.env.DEVFLOW_WS_PORT
-      ? parseInt(process.env.DEVFLOW_WS_PORT, 10)
-      : 3001;
+  if (process.env.NEXT_RUNTIME === 'nodejs') {
+    const { startWebSocketServer } = await import('./src/websocket/server');
+    const port = process.env.DEVFLOW_WS_PORT ? parseInt(process.env.DEVFLOW_WS_PORT, 10) : 3001;
     await startWebSocketServer(port);
   }
 }

package/.next/standalone/next.config.ts

@@ -1,7 +1,16 @@
-import type { NextConfig } from "next";
+import type { NextConfig } from 'next';
 
 const nextConfig: NextConfig = {
-  output: "standalone",
+  output: 'standalone',
+  images: {
+    unoptimized: true,
+  },
+  env: {
+    NEXT_PUBLIC_DEVFLOW_WS_PORT: process.env.DEVFLOW_WS_PORT || '3001',
+  },
+  outputFileTracingExcludes: {
+    '*': ['./node_modules/typescript/**', './node_modules/sharp/**', './node_modules/@img/**'],
+  },
 };
 
 export default nextConfig;

package/.next/standalone/node_modules/{sharp → libsql}/node_modules/detect-libc/package.json

@@ -1,6 +1,6 @@
 {
   "name": "detect-libc",
-  "version": "2.1.2",
+  "version": "2.0.2",
   "description": "Node.js module to detect the C standard library (libc) implementation family and version",
   "main": "lib/detect-libc.js",
   "files": [
@@ -8,14 +8,13 @@
     "index.d.ts"
   ],
   "scripts": {
-    "test": "semistandard && nyc --reporter=text --check-coverage --branches=100 ava test/unit.js",
-    "changelog": "conventional-changelog -i CHANGELOG.md -s",
+    "test": "semistandard && nyc --reporter=lcov --check-coverage --branches=100 ava test/unit.js",
     "bench": "node benchmark/detect-libc",
     "bench:calls": "node benchmark/call-familySync.js && sleep 1 && node benchmark/call-isNonGlibcLinuxSync.js && sleep 1 && node benchmark/call-versionSync.js"
   },
   "repository": {
     "type": "git",
-    "url": "git://github.com/lovell/detect-libc.git"
+    "url": "git://github.com/lovell/detect-libc"
   },
   "keywords": [
     "libc",
@@ -31,14 +30,11 @@
   "devDependencies": {
     "ava": "^2.4.0",
     "benchmark": "^2.1.4",
-    "conventional-changelog-cli": "^5.0.0",
-    "eslint-config-standard": "^13.0.1",
     "nyc": "^15.1.0",
     "proxyquire": "^2.1.3",
     "semistandard": "^14.2.3"
   },
   "engines": {
     "node": ">=8"
-  },
-  "types": "index.d.ts"
+  }
 }