@cliangdev/flux-plugin 0.0.0-dev.df9c61f → 0.1.0-dev.588ae42

package/commands/linear.md

@@ -0,0 +1,171 @@
+---
+name: flux:linear
+description: Connect Flux project to Linear for issue tracking
+allowed-tools: mcp__plugin_flux_flux__*, AskUserQuestion
+---
+
+# Linear Integration Setup
+
+Connect a Flux project to Linear using the interactive configuration flow.
+
+## How Interactive Mode Works
+
+The `configure_linear` tool supports progressive discovery:
+
+| Call | Response |
+|------|----------|
+| `{interactive: true}` | Returns `{step: "select_team", teams: [...], user: {...}}` |
+| `{interactive: true, teamId: "xxx"}` | Returns `{step: "select_project", projects: [...], team: {...}}` |
+| `{teamId: "xxx", projectName: "..."}` | Creates new project and configures |
+| `{teamId: "xxx", existingProjectId: "..."}` | Uses existing project and configures |
+
+## Flow
+
+### Step 1: Verify Project
+
+Call `get_project_context`.
+
+- If `initialized: false` → Tell user to run `/flux` first, then exit.
+- If `adapter.type === "linear"` and config exists → Already configured, show info and exit.
+- Otherwise → Continue to Step 2.
+
+### Step 2: Fetch Teams
+
+**IMPORTANT**: Call `configure_linear` with ONLY `interactive: true`. Do NOT pass teamId, projectName, or any other params.
+
+```json
+{"interactive": true}
+```
+
+This is the ONLY parameter needed for the first call. The tool will return available teams.
+
+**If error** (e.g., "Linear API key not found"):
+```
+Linear API key required.
+
+1. Get your key: Linear → Settings → API → Personal API keys
+2. Set it: export LINEAR_API_KEY=lin_api_xxx
+3. Run /flux:linear again
+```
+Then exit.
+
+**If success**, response will be:
+```json
+{
+  "step": "select_team",
+  "user": {"name": "...", "email": "..."},
+  "teams": [
+    {"id": "team-abc", "name": "Engineering", "key": "ENG"},
+    {"id": "team-def", "name": "Product", "key": "PROD"}
+  ]
+}
+```
+
+Display: "Connected as {user.name} ({user.email})"
+
+Use AskUserQuestion to let user select a team:
+```json
+{
+  "questions": [{
+    "question": "Which Linear team should Flux use?",
+    "header": "Team",
+    "options": [
+      {"label": "Engineering (ENG)", "description": "team-abc"},
+      {"label": "Product (PROD)", "description": "team-def"}
+    ],
+    "multiSelect": false
+  }]
+}
+```
+
+Note: Put the team ID in the description field so you can retrieve it from the response.
+
+### Step 3: Fetch Projects
+
+Call `configure_linear` with:
+```json
+{"interactive": true, "teamId": "<selected_team_id>"}
+```
+
+Response will be:
+```json
+{
+  "step": "select_project",
+  "team": {"id": "...", "name": "...", "key": "..."},
+  "projects": [
+    {"id": "proj-123", "name": "Q1 Sprint", "state": "started"},
+    {"id": "proj-456", "name": "Backlog", "state": "planned"}
+  ]
+}
+```
+
+Use AskUserQuestion:
+```json
+{
+  "questions": [{
+    "question": "Which project should Flux sync to?",
+    "header": "Project",
+    "options": [
+      {"label": "Create New Project", "description": "new"},
+      {"label": "Q1 Sprint", "description": "proj-123"},
+      {"label": "Backlog", "description": "proj-456"}
+    ],
+    "multiSelect": false
+  }]
+}
+```
+
+### Step 4: Configure
+
+**If user selected "Create New Project":**
+
+Ask for project name, then call:
+```json
+{
+  "teamId": "<team_id>",
+  "projectName": "<user_provided_name>"
+}
+```
+
+**If user selected existing project:**
+
+Call:
+```json
+{
+  "teamId": "<team_id>",
+  "existingProjectId": "<project_id>"
+}
+```
+
+### Step 5: Success
+
+Response will include:
+```json
+{
+  "success": true,
+  "team": "Engineering",
+  "project": {"id": "...", "name": "..."},
+  "labels": {...},
+  "view": {"created": "...", "setup_hint": "..."}
+}
+```
+
+Display:
+```
+Linear connected!
+
+Team: {team}
+Project: {project.name}
+
+All PRDs, epics, and tasks will sync to Linear.
+Run /flux:prd to create your first PRD.
+```
+
+If `view.setup_hint` exists, show it as a tip.
+
+## Key Points
+
+- Always use `{"interactive": true}` (boolean) not a string
+- The response `step` field tells you what stage you're at
+- Use AskUserQuestion for team/project selection
+- Store the selected IDs from previous responses to use in next calls

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cliangdev/flux-plugin",
-  "version": "0.0.0-dev.df9c61f",
+  "version": "0.1.0-dev.588ae42",
   "description": "Claude Code plugin for AI-first workflow orchestration with MCP server",
   "type": "module",
   "main": "./dist/server/index.js",
@@ -8,8 +8,8 @@
     "flux-plugin": "./bin/install.cjs"
   },
   "files": [
-    "bin/",
-    "dist/",
+    "bin/install.cjs",
+    "src/",
     "skills/",
     "commands/",
     "agents/",
@@ -17,20 +17,20 @@
   ],
   "scripts": {
     "dev": "bun run src/server/index.ts",
-    "build": "bun build src/server/index.ts --outdir dist/server --target node --external better-sqlite3",
-    "postbuild": "node -e \"const fs=require('fs');const f='dist/server/index.js';const c=fs.readFileSync(f,'utf-8');if(!c.startsWith('#!/usr/bin/env node')){fs.writeFileSync(f,'#!/usr/bin/env node\\n'+c)}\"",
-    "build:compile": "bun build --compile --outfile bin/flux-server src/server/index.ts && bun build --compile --outfile bin/flux-status src/status-line/index.ts",
-    "build:compile:server": "bun build --compile --outfile bin/flux-server src/server/index.ts",
-    "build:compile:status": "bun build --compile --outfile bin/flux-status src/status-line/index.ts",
+    "build": "bun build --compile --outfile bin/flux-server src/server/index.ts && bun build --compile --outfile bin/flux-status src/status-line/index.ts",
+    "build:server": "bun build --compile --outfile bin/flux-server src/server/index.ts",
+    "build:status": "bun build --compile --outfile bin/flux-status src/status-line/index.ts",
     "validate": "node scripts/validate-structure.cjs",
-    "prepublishOnly": "bun run validate && bun run build",
+    "test:integration": "bun test scripts/__tests__/integration.test.ts --timeout 120000",
+    "prepublishOnly": "bun run validate && bun run test:integration",
     "test": "bun test",
     "test:linear-description": "bun run src/server/adapters/__tests__/linear-description-test.ts",
     "typecheck": "tsc --noEmit",
     "lint": "biome check .",
     "lint:fix": "biome check --write .",
     "format": "biome format --write .",
-    "verify-release": "bun run scripts/verify-release.ts"
+    "verify-release": "bun run scripts/verify-release.ts",
+    "release": "./scripts/release.sh"
   },
   "repository": {
     "type": "git",
@@ -51,14 +51,12 @@
   "license": "MIT",
   "devDependencies": {
     "@biomejs/biome": "^2.3.11",
-    "@types/better-sqlite3": "^7.6.13",
     "@types/bun": "^1.3.6",
     "typescript": "^5.0.0"
   },
   "dependencies": {
     "@linear/sdk": "^70.0.0",
     "@modelcontextprotocol/sdk": "^1.25.2",
-    "better-sqlite3": "^12.6.2",
     "chalk": "^5.4.1",
     "zod": "^4.3.5"
   },

package/skills/flux-orchestrator/SKILL.md

@@ -6,18 +6,20 @@ user-invocable: false
 
 # Flux Orchestrator Skill
 
-This skill is automatically active when working in a Flux project. It provides context about available tools and workflow patterns.
+This skill is automatically active when working in a Flux project. It provides context about available tools, workflow patterns, and integration options.
 
 ## Available MCP Tools
 
 ### Query Tools
-- `get_project_context` - Check if project initialized, get name/vision/prefix
+- `get_project_context` - Check if project initialized, get name/vision/adapter type
 - `get_stats` - Get PRD/epic/task counts by status
 - `get_entity` - Fetch entity by ref with optional includes (criteria, tasks, dependencies)
 - `query_entities` - Search entities by type, status, parent ref
+- `render_status` - Get formatted project status with progress bars
 
 ### Mutation Tools
 - `init_project` - Initialize new .flux/ directory with project.json and database
+- `configure_linear` - Configure Linear integration (supports interactive mode)
 - `create_prd` - Create a new PRD
 - `create_epic` - Create an epic linked to a PRD
 - `create_task` - Create a task linked to an epic
@@ -31,102 +33,82 @@ This skill is automatically active when working in a Flux project. It provides c
 - `add_criteria` - Add acceptance criterion to epic or task
 - `mark_criteria_met` - Mark criterion as satisfied
 
-## Workflow States
+## Available Commands
 
-The Flux project progresses through these states:
+| Command | Purpose |
+|---------|---------|
+| `/flux` | Project init, status, and workflow routing |
+| `/flux:linear` | Connect project to Linear (interactive setup) |
+| `/flux:prd` | Create or refine PRDs |
+| `/flux:breakdown` | Break approved PRD into epics and tasks |
+| `/flux:implement` | Implement tasks with TDD workflow |
 
-1. **Uninitialized** - No .flux/ directory
-   - Action: Run `/flux` to initialize
+## Workflow States
 
-2. **No PRDs** - Project initialized but empty
-   - Action: Run `/flux:prd` to create first PRD
+```
+Uninitialized → Initialized → PRD Draft → Pending Review → Reviewed → Approved → Breakdown Ready → In Progress → Complete
+                     ↓
+              (optional) Linear Connected
+```
 
-3. **PRD Draft** - PRD created but needs review
-   - Action: Review and submit for approval or refine
+### PRD Status Transitions
+```
+DRAFT → PENDING_REVIEW → REVIEWED → APPROVED → BREAKDOWN_READY → COMPLETED
+          ↓                 ↓
+        DRAFT (revise)    DRAFT (revise)
+```
 
-4. **PRD Pending Review** - PRD submitted for review
-   - Action: Run critique agent, then approve or revise
+### Epic/Task Statuses
+- `PENDING` → `IN_PROGRESS` → `COMPLETED`
+
+## Backend Adapters
 
-5. **PRD Reviewed** - Critique complete
-   - Action: Address feedback, then approve or revise to DRAFT
+Flux supports multiple backends via the adapter pattern:
 
-6. **PRD Approved** - Ready for epic breakdown
-   - Action: Run `/flux:breakdown` to create epics
+| Adapter | Storage | Use Case |
+|---------|---------|----------|
+| `local` | SQLite (.flux/flux.db) | Default, offline-first |
+| `linear` | Linear API | Team collaboration, issue tracking |
 
-7. **Breakdown Ready** - Epics and tasks created
-   - Action: Run `/flux:implement` to start coding
+### Switching to Linear
 
-8. **Implementation In Progress** - Tasks IN_PROGRESS
-   - Action: Continue implementing current task
+Use `configure_linear` with interactive mode:
+1. `{interactive: true}` → returns teams list
+2. `{interactive: true, teamId: "..."}` → returns projects list
+3. `{teamId: "...", projectName/existingProjectId: "..."}` → configures
 
-9. **Complete** - All tasks COMPLETED
-    - Action: Review and create PR
+Or run `/flux:linear` for guided setup.
 
 ## Entity References
 
-All entities have a reference format: `{PREFIX}-{TYPE}{NUMBER}`
+Format: `{PREFIX}-{TYPE}{NUMBER}`
 
 - PRD: `MSA-P1`, `MSA-P2`
 - Epic: `MSA-E1`, `MSA-E2`
 - Task: `MSA-T1`, `MSA-T2`
 
-The prefix is generated from the project name during initialization.
-
-## Status Values
-
-### PRD Statuses (6-stage workflow)
-- `DRAFT` - Initial state, being created/refined
-- `PENDING_REVIEW` - Submitted for critique
-- `REVIEWED` - Critique complete, awaiting approval
-- `APPROVED` - Ready for epic breakdown
-- `BREAKDOWN_READY` - Epics and tasks created
-- `COMPLETED` - All epics done
-
-### Valid PRD Transitions
-```
-DRAFT → PENDING_REVIEW
-PENDING_REVIEW → REVIEWED | DRAFT (revise)
-REVIEWED → APPROVED | DRAFT (revise)
-APPROVED → BREAKDOWN_READY
-BREAKDOWN_READY → COMPLETED
-```
-
-### Epic/Task Statuses
-- `PENDING` - Not started
-- `IN_PROGRESS` - Currently being worked on
-- `COMPLETED` - Done
-
-## Confidence-Based Autonomy
-
-The orchestrator uses confidence levels to determine autonomy:
-
-| Confidence | Behavior | Example |
-|------------|----------|---------|
-| > 80% | Auto-execute, inform user | "I'm creating the epic structure..." |
-| 50-80% | Suggest action, wait for confirmation | "Ready to break down into tasks. Proceed?" |
-| < 50% | Ask clarifying question | "Should we research this technology first?" |
-
-### Confidence Indicators
-- **High confidence (>80%)**: Clear next step, no ambiguity, user has been responsive
-- **Medium confidence (50-80%)**: Reasonable next step, some uncertainty
-- **Low confidence (<50%)**: Multiple valid paths, unclear requirements, unfamiliar tech
-
 ## Available Subagents
 
-### Research Agent
-- **Trigger**: Unfamiliar technology mentioned, confidence < 70%
-- **Purpose**: Gather information about libraries, frameworks, APIs
+### Research Agent (`flux:flux-researcher`)
+- **Trigger**: Unfamiliar technology, confidence < 70%
 - **Tools**: Context7, WebSearch, WebFetch
 
-### Critique Agent
-- **Trigger**: PRD status becomes PENDING_REVIEW
-- **Purpose**: Analyze feasibility, scope, risks
-- **Output**: Structured critique with recommendations
+### Critique Agent (`flux:flux-critic`)
+- **Trigger**: PRD submitted for review
+- **Output**: Feasibility analysis, risks, recommendations
+
+### Coder Agent (`flux:flux-coder`)
+- **Trigger**: Task implementation
+- **Workflow**: TDD - write tests, implement, verify
+
+### Verifier Agent (`flux:flux-verifier`)
+- **Trigger**: After implementation
+- **Purpose**: Verify acceptance criteria coverage
 
 ## Best Practices
 
-1. **Check context first** - Always call `get_project_context` before taking actions
-2. **Use refs, not IDs** - Tools accept human-readable refs like `MSA-E1`
-3. **Validate status transitions** - Use `update_status` which enforces valid transitions
-4. **Include related data** - Use `include` parameter to fetch nested entities in one call
-5. **Handle errors gracefully** - Tools return errors with codes, display user-friendly messages
+1. **Check context first** - Call `get_project_context` before actions
+2. **Use refs, not IDs** - Tools accept `MSA-E1` format
+3. **Use render_status** - For visual project overview
+4. **Validate transitions** - `update_status` enforces valid transitions
+5. **Include related data** - Use `include` param to fetch nested entities

package/src/__tests__/version.test.ts

@@ -0,0 +1,37 @@
+import { describe, expect, test } from "bun:test";
+import { existsSync, readFileSync } from "node:fs";
+import { join } from "node:path";
+
+describe("version module", () => {
+  test("VERSION is exported from src/version.ts", async () => {
+    // Dynamic import to get the VERSION constant
+    const versionModule = await import("../version.js");
+
+    expect(versionModule.VERSION).toBeDefined();
+    expect(typeof versionModule.VERSION).toBe("string");
+  });
+
+  test("VERSION equals package.json version", async () => {
+    // Read package.json version
+    const packageJsonPath = join(process.cwd(), "package.json");
+    expect(existsSync(packageJsonPath)).toBe(true);
+
+    const packageJson = JSON.parse(readFileSync(packageJsonPath, "utf-8"));
+    const packageVersion = packageJson.version;
+
+    expect(packageVersion).toBeDefined();
+    expect(typeof packageVersion).toBe("string");
+
+    // Import VERSION and compare
+    const versionModule = await import("../version.js");
+    expect(versionModule.VERSION).toBe(packageVersion);
+  });
+
+  test("VERSION is a valid semver format", async () => {
+    const versionModule = await import("../version.js");
+
+    // Basic semver format check (e.g., "0.1.0", "1.2.3-beta.1")
+    const semverPattern = /^\d+\.\d+\.\d+(-[\w.]+)?$/;
+    expect(semverPattern.test(versionModule.VERSION)).toBe(true);
+  });
+});

package/src/server/__tests__/config.test.ts

@@ -0,0 +1,163 @@
+import { afterEach, beforeEach, describe, expect, test } from "bun:test";
+import {
+  existsSync,
+  mkdirSync,
+  realpathSync,
+  rmSync,
+  writeFileSync,
+} from "node:fs";
+import { tmpdir } from "node:os";
+
+describe("config", () => {
+  const originalEnv = process.env.FLUX_PROJECT_ROOT;
+  const originalCwd = process.cwd();
+  // Use os.tmpdir() to get the real temp path (handles /tmp -> /private/tmp on macOS)
+  const TEST_DIR = `${realpathSync(tmpdir())}/flux-config-test-${Date.now()}`;
+  const NESTED_DIR = `${TEST_DIR}/subdir/nested`;
+
+  beforeEach(async () => {
+    // Clean up any previous test directory
+    if (existsSync(TEST_DIR)) {
+      rmSync(TEST_DIR, { recursive: true });
+    }
+
+    // Create test directory structure
+    mkdirSync(NESTED_DIR, { recursive: true });
+
+    // Clear the config cache before each test
+    const { config } = await import("../config.js");
+    config.clearCache();
+  });
+
+  afterEach(async () => {
+    // Restore original env
+    if (originalEnv !== undefined) {
+      process.env.FLUX_PROJECT_ROOT = originalEnv;
+    } else {
+      delete process.env.FLUX_PROJECT_ROOT;
+    }
+
+    // Restore original cwd
+    process.chdir(originalCwd);
+
+    // Clear the config cache
+    const { config } = await import("../config.js");
+    config.clearCache();
+
+    // Clean up test directory
+    if (existsSync(TEST_DIR)) {
+      rmSync(TEST_DIR, { recursive: true });
+    }
+  });
+
+  test("uses env var when properly set", async () => {
+    process.env.FLUX_PROJECT_ROOT = "/some/valid/path";
+
+    const { config } = await import("../config.js");
+    config.clearCache();
+
+    expect(config.projectRoot).toBe("/some/valid/path");
+  });
+
+  test("ignores unresolved template variable and walks up directories", async () => {
+    // Create a .flux folder at TEST_DIR
+    mkdirSync(`${TEST_DIR}/.flux`, { recursive: true });
+    writeFileSync(
+      `${TEST_DIR}/.flux/project.json`,
+      JSON.stringify({ name: "test" }),
+    );
+
+    // Simulate Claude Code passing unresolved template variable
+    // biome-ignore lint/suspicious/noTemplateCurlyInString: intentionally testing literal template string
+    process.env.FLUX_PROJECT_ROOT = "${CLAUDE_PROJECT_DIR}";
+
+    // Change to nested directory
+    process.chdir(NESTED_DIR);
+
+    const { config } = await import("../config.js");
+    config.clearCache();
+
+    // Should walk up and find TEST_DIR, not use the literal "${CLAUDE_PROJECT_DIR}"
+    expect(config.projectRoot).not.toContain("${");
+    expect(config.projectRoot).toBe(TEST_DIR);
+  });
+
+  test("walks up directories to find .flux folder", async () => {
+    // Create a .flux folder at TEST_DIR (parent of NESTED_DIR)
+    mkdirSync(`${TEST_DIR}/.flux`, { recursive: true });
+    writeFileSync(
+      `${TEST_DIR}/.flux/project.json`,
+      JSON.stringify({ name: "test" }),
+    );
+
+    // No env var set
+    delete process.env.FLUX_PROJECT_ROOT;
+
+    // Change to nested directory
+    process.chdir(NESTED_DIR);
+
+    const { config } = await import("../config.js");
+    config.clearCache();
+
+    // Should walk up and find TEST_DIR
+    expect(config.projectRoot).toBe(TEST_DIR);
+  });
+
+  test("falls back to cwd when no .flux folder found", async () => {
+    // No .flux folder anywhere in TEST_DIR hierarchy
+    // No env var set
+    delete process.env.FLUX_PROJECT_ROOT;
+
+    // Change to test directory (which has no .flux)
+    process.chdir(TEST_DIR);
+
+    const { config } = await import("../config.js");
+    config.clearCache();
+
+    // Should fall back to cwd
+    expect(config.projectRoot).toBe(TEST_DIR);
+  });
+
+  test("projectExists returns true when project.json exists", async () => {
+    mkdirSync(`${TEST_DIR}/.flux`, { recursive: true });
+    writeFileSync(
+      `${TEST_DIR}/.flux/project.json`,
+      JSON.stringify({ name: "test" }),
+    );
+
+    process.env.FLUX_PROJECT_ROOT = TEST_DIR;
+
+    const { config } = await import("../config.js");
+    config.clearCache();
+
+    expect(config.projectExists).toBe(true);
+  });
+
+  test("projectExists returns false when project.json does not exist", async () => {
+    // No .flux folder
+    process.env.FLUX_PROJECT_ROOT = TEST_DIR;
+
+    const { config } = await import("../config.js");
+    config.clearCache();
+
+    expect(config.projectExists).toBe(false);
+  });
+
+  test("caches project root for performance", async () => {
+    process.env.FLUX_PROJECT_ROOT = "/first/path";
+
+    const { config } = await import("../config.js");
+    config.clearCache();
+
+    // First call caches the value
+    expect(config.projectRoot).toBe("/first/path");
+
+    // Changing env var should not affect cached value
+    process.env.FLUX_PROJECT_ROOT = "/second/path";
+    expect(config.projectRoot).toBe("/first/path");
+
+    // After clearing cache, should use new env var
+    config.clearCache();
+    expect(config.projectRoot).toBe("/second/path");
+  });
+});