sequant 1.11.0 → 1.13.0

package/dist/src/lib/workflow/run-log-schema.d.ts

@@ -33,9 +33,9 @@ export type Phase = z.infer<typeof PhaseSchema>;
  * Phase execution status
  */
 export declare const PhaseStatusSchema: z.ZodEnum<{
-    skipped: "skipped";
     success: "success";
     failure: "failure";
+    skipped: "skipped";
     timeout: "timeout";
 }>;
 export type PhaseStatus = z.infer<typeof PhaseStatusSchema>;
@@ -48,6 +48,16 @@ export declare const IssueStatusSchema: z.ZodEnum<{
     partial: "partial";
 }>;
 export type IssueStatus = z.infer<typeof IssueStatusSchema>;
+/**
+ * Valid QA verdicts schema
+ */
+export declare const QaVerdictSchema: z.ZodEnum<{
+    READY_FOR_MERGE: "READY_FOR_MERGE";
+    AC_MET_BUT_NOT_A_PLUS: "AC_MET_BUT_NOT_A_PLUS";
+    AC_NOT_MET: "AC_NOT_MET";
+    NEEDS_VERIFICATION: "NEEDS_VERIFICATION";
+}>;
+export type QaVerdict = z.infer<typeof QaVerdictSchema>;
 /**
  * Log entry for a single phase execution
  */
@@ -66,9 +76,9 @@ export declare const PhaseLogSchema: z.ZodObject<{
     endTime: z.ZodString;
     durationSeconds: z.ZodNumber;
     status: z.ZodEnum<{
-        skipped: "skipped";
         success: "success";
         failure: "failure";
+        skipped: "skipped";
         timeout: "timeout";
     }>;
     error: z.ZodOptional<z.ZodString>;
@@ -76,6 +86,12 @@ export declare const PhaseLogSchema: z.ZodObject<{
     filesModified: z.ZodOptional<z.ZodArray<z.ZodString>>;
     testsRun: z.ZodOptional<z.ZodNumber>;
     testsPassed: z.ZodOptional<z.ZodNumber>;
+    verdict: z.ZodOptional<z.ZodEnum<{
+        READY_FOR_MERGE: "READY_FOR_MERGE";
+        AC_MET_BUT_NOT_A_PLUS: "AC_MET_BUT_NOT_A_PLUS";
+        AC_NOT_MET: "AC_NOT_MET";
+        NEEDS_VERIFICATION: "NEEDS_VERIFICATION";
+    }>>;
 }, z.core.$strip>;
 export type PhaseLog = z.infer<typeof PhaseLogSchema>;
 /**
@@ -105,9 +121,9 @@ export declare const IssueLogSchema: z.ZodObject<{
         endTime: z.ZodString;
         durationSeconds: z.ZodNumber;
         status: z.ZodEnum<{
-            skipped: "skipped";
             success: "success";
             failure: "failure";
+            skipped: "skipped";
             timeout: "timeout";
         }>;
         error: z.ZodOptional<z.ZodString>;
@@ -115,6 +131,12 @@ export declare const IssueLogSchema: z.ZodObject<{
         filesModified: z.ZodOptional<z.ZodArray<z.ZodString>>;
         testsRun: z.ZodOptional<z.ZodNumber>;
         testsPassed: z.ZodOptional<z.ZodNumber>;
+        verdict: z.ZodOptional<z.ZodEnum<{
+            READY_FOR_MERGE: "READY_FOR_MERGE";
+            AC_MET_BUT_NOT_A_PLUS: "AC_MET_BUT_NOT_A_PLUS";
+            AC_NOT_MET: "AC_NOT_MET";
+            NEEDS_VERIFICATION: "NEEDS_VERIFICATION";
+        }>>;
     }, z.core.$strip>>;
     totalDurationSeconds: z.ZodNumber;
 }, z.core.$strip>;
@@ -195,9 +217,9 @@ export declare const RunLogSchema: z.ZodObject<{
             endTime: z.ZodString;
             durationSeconds: z.ZodNumber;
             status: z.ZodEnum<{
-                skipped: "skipped";
                 success: "success";
                 failure: "failure";
+                skipped: "skipped";
                 timeout: "timeout";
             }>;
             error: z.ZodOptional<z.ZodString>;
@@ -205,6 +227,12 @@ export declare const RunLogSchema: z.ZodObject<{
             filesModified: z.ZodOptional<z.ZodArray<z.ZodString>>;
             testsRun: z.ZodOptional<z.ZodNumber>;
             testsPassed: z.ZodOptional<z.ZodNumber>;
+            verdict: z.ZodOptional<z.ZodEnum<{
+                READY_FOR_MERGE: "READY_FOR_MERGE";
+                AC_MET_BUT_NOT_A_PLUS: "AC_MET_BUT_NOT_A_PLUS";
+                AC_NOT_MET: "AC_NOT_MET";
+                NEEDS_VERIFICATION: "NEEDS_VERIFICATION";
+            }>>;
         }, z.core.$strip>>;
         totalDurationSeconds: z.ZodNumber;
     }, z.core.$strip>>;
@@ -253,10 +281,10 @@ export declare function createPhaseLog(phase: Phase, issueNumber: number): Omit<
  *
  * @param phaseLog - Partial phase log
  * @param status - Final status
- * @param options - Additional fields (error, filesModified, etc.)
+ * @param options - Additional fields (error, filesModified, verdict, etc.)
  * @returns Complete PhaseLog
  */
-export declare function completePhaseLog(phaseLog: Omit<PhaseLog, "endTime" | "durationSeconds" | "status">, status: PhaseStatus, options?: Partial<Pick<PhaseLog, "error" | "iterations" | "filesModified" | "testsRun" | "testsPassed">>): PhaseLog;
+export declare function completePhaseLog(phaseLog: Omit<PhaseLog, "endTime" | "durationSeconds" | "status">, status: PhaseStatus, options?: Partial<Pick<PhaseLog, "error" | "iterations" | "filesModified" | "testsRun" | "testsPassed" | "verdict">>): PhaseLog;
 /**
  * Finalize a run log with summary statistics
  *

package/dist/src/lib/workflow/run-log-schema.js

@@ -42,6 +42,15 @@ export const PhaseStatusSchema = z.enum([
  * Issue execution status
  */
 export const IssueStatusSchema = z.enum(["success", "failure", "partial"]);
+/**
+ * Valid QA verdicts schema
+ */
+export const QaVerdictSchema = z.enum([
+    "READY_FOR_MERGE",
+    "AC_MET_BUT_NOT_A_PLUS",
+    "AC_NOT_MET",
+    "NEEDS_VERIFICATION",
+]);
 /**
  * Log entry for a single phase execution
  */
@@ -68,6 +77,8 @@ export const PhaseLogSchema = z.object({
     testsRun: z.number().int().nonnegative().optional(),
     /** Number of tests passed */
     testsPassed: z.number().int().nonnegative().optional(),
+    /** Parsed QA verdict (only for qa phase) */
+    verdict: QaVerdictSchema.optional(),
 });
 /**
  * Complete execution record for a single issue
@@ -195,7 +206,7 @@ export function createPhaseLog(phase, issueNumber) {
  *
  * @param phaseLog - Partial phase log
  * @param status - Final status
- * @param options - Additional fields (error, filesModified, etc.)
+ * @param options - Additional fields (error, filesModified, verdict, etc.)
  * @returns Complete PhaseLog
  */
 export function completePhaseLog(phaseLog, status, options) {

package/dist/src/lib/workflow/state-schema.d.ts

@@ -25,9 +25,9 @@ export declare const WORKFLOW_PHASES: readonly ["spec", "security-review", "exec
  * Phase status - tracks individual phase progress
  */
 export declare const PhaseStatusSchema: z.ZodEnum<{
+    pending: "pending";
     skipped: "skipped";
     completed: "completed";
-    pending: "pending";
     in_progress: "in_progress";
     failed: "failed";
 }>;
@@ -65,9 +65,9 @@ export type Phase = z.infer<typeof PhaseSchema>;
  */
 export declare const PhaseStateSchema: z.ZodObject<{
     status: z.ZodEnum<{
+        pending: "pending";
         skipped: "skipped";
         completed: "completed";
-        pending: "pending";
         in_progress: "in_progress";
         failed: "failed";
     }>;
@@ -198,9 +198,9 @@ export declare const IssueStateSchema: z.ZodObject<{
     }>>;
     phases: z.ZodRecord<z.ZodString, z.ZodObject<{
         status: z.ZodEnum<{
+            pending: "pending";
             skipped: "skipped";
             completed: "completed";
-            pending: "pending";
             in_progress: "in_progress";
             failed: "failed";
         }>;
@@ -286,9 +286,9 @@ export declare const WorkflowStateSchema: z.ZodObject<{
         }>>;
         phases: z.ZodRecord<z.ZodString, z.ZodObject<{
             status: z.ZodEnum<{
+                pending: "pending";
                 skipped: "skipped";
                 completed: "completed";
-                pending: "pending";
                 in_progress: "in_progress";
                 failed: "failed";
             }>;

package/dist/src/lib/workflow/types.d.ts

@@ -40,6 +40,8 @@ export interface ExecutionConfig {
  * Default execution configuration
  */
 export declare const DEFAULT_CONFIG: ExecutionConfig;
+import type { QaVerdict } from "./run-log-schema.js";
+export type { QaVerdict } from "./run-log-schema.js";
 /**
  * Result of executing a single phase
  */
@@ -50,6 +52,8 @@ export interface PhaseResult {
     error?: string;
     /** Captured output from the phase (used for parsing spec recommendations) */
     output?: string;
+    /** Parsed QA verdict (only for qa phase) */
+    verdict?: QaVerdict;
 }
 /**
  * Result of executing all phases for an issue

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sequant",
-  "version": "1.11.0",
+  "version": "1.13.0",
   "description": "Quantize your development workflow - Sequential AI phases with quality gates",
   "type": "module",
   "bin": {
@@ -56,19 +56,24 @@
   "dependencies": {
     "@anthropic-ai/claude-agent-sdk": "^0.2.11",
     "@hono/node-server": "^1.19.9",
+    "boxen": "^8.0.1",
     "chalk": "^5.3.0",
     "chokidar": "^5.0.0",
+    "cli-table3": "^0.6.5",
     "commander": "^12.1.0",
     "diff": "^7.0.0",
+    "gradient-string": "^3.0.0",
     "hono": "^4.11.4",
     "inquirer": "^12.3.2",
     "open": "^11.0.0",
+    "ora": "^8.2.0",
     "yaml": "^2.7.0",
     "zod": "^4.3.5"
   },
   "devDependencies": {
     "@eslint/js": "^9.39.2",
     "@types/diff": "^7.0.0",
+    "@types/gradient-string": "^1.1.6",
     "@types/inquirer": "^9.0.7",
     "@types/node": "^22.10.5",
     "@typescript-eslint/eslint-plugin": "^8.52.0",

package/templates/hooks/pre-tool.sh

@@ -309,6 +309,12 @@ if [[ "$TOOL_NAME" == "Bash" ]] && echo "$TOOL_INPUT" | grep -qE 'git commit'; t
             {
                 echo "HOOK_BLOCKED: Commit must follow conventional commits format"
                 echo "  Expected: type(scope): description"
+                # AC-1 & AC-2 (Issue #198): Detect merge commits and provide helpful suggestion
+                if [[ "$MSG" == Merge\ * ]]; then
+                    echo ""
+                    echo "  💡 For merge commits, use: chore: merge main into feature branch"
+                    echo ""
+                fi
                 echo "  Types: feat|fix|docs|style|refactor|test|chore|ci|build|perf"
                 echo "  Got: $MSG"
             } | tee -a /tmp/claude-hook.log >&2

package/templates/memory/constitution.md

@@ -56,11 +56,7 @@ This document defines the core principles and patterns for AI-assisted developme
 
 ## Stack-Specific Notes
 
-### Astro Projects
-- Astro projects may not have `test` or `lint` scripts configured by default
-- If tests are needed, consider adding Vitest (`npm install -D vitest`)
-- For linting, consider ESLint with the Astro plugin (`npm install -D eslint eslint-plugin-astro`)
-- Build output goes to `dist/` by default
+{{STACK_NOTES}}
 
 ## Project-Specific Notes
 

package/templates/skills/_shared/references/prompt-templates.md

@@ -0,0 +1,350 @@
+# Sub-Agent Prompt Templates
+
+Reference for task-specific prompt templates when spawning sub-agents via the `Task` tool during parallel execution.
+
+## Overview
+
+When spawning sub-agents for implementation tasks, use these templates to provide structured, task-specific guidance. Templates include:
+- Task-specific requirements and constraints
+- Best practices for that task type
+- Expected deliverables and reporting format
+
+## Template Selection
+
+### Automatic Selection (Keywords)
+
+The template is selected based on keywords in the task description:
+
+| Keywords | Template |
+|----------|----------|
+| `component`, `Component`, `React` | [Component Template](#component-template) |
+| `type`, `interface`, `types/` | [Type Definition Template](#type-definition-template) |
+| `CLI`, `command`, `script`, `bin/` | [CLI/Script Template](#cliscript-template) |
+| `test`, `spec`, `.test.` | [Test Template](#test-template) |
+| `refactor`, `restructure`, `migrate` | [Refactor Template](#refactor-template) |
+| (none matched) | [Generic Template](#generic-template) |
+
+### Explicit Annotation Override
+
+You can force a specific template using the `[template: X]` annotation at the start of the task:
+
+```
+[template: component] Create UserCard in components/admin/
+[template: cli] Add export command to scripts/
+[template: type] Define MetricEvent interface
+```
+
+**Annotation takes precedence** over keyword detection.
+
+---
+
+## Task Templates
+
+### Component Template
+
+**Use for:** React components, UI elements, admin panels
+
+```markdown
+## Task: Create React Component
+
+**Component:** [name]
+**Location:** [path]
+
+**Requirements:**
+- [ ] TypeScript with proper prop types (interface or type)
+- [ ] Follow existing component patterns in the codebase
+- [ ] Include displayName for debugging: `Component.displayName = 'ComponentName'`
+- [ ] No inline styles - use existing CSS/Tailwind patterns
+- [ ] Export component as named export
+
+**Best Practices:**
+- Check `components/` for similar components to follow patterns
+- Use existing hooks from `lib/hooks/` if applicable
+- Prefer composition over prop drilling
+- Keep components focused - single responsibility
+
+**Constraints:**
+- Working directory: [worktree path]
+- Do NOT create test files (handled separately)
+- Do NOT add new dependencies without explicit approval
+
+**Deliverable:**
+Report: files created, component name, props interface
+```
+
+---
+
+### Type Definition Template
+
+**Use for:** TypeScript types, interfaces, enums, type utilities
+
+```markdown
+## Task: Create Type Definitions
+
+**File:** [path]
+**Types needed:** [list]
+
+**Requirements:**
+- [ ] Export all types (no internal-only types)
+- [ ] Use strict types - avoid `any`, prefer `unknown` if needed
+- [ ] Add JSDoc comments for complex types explaining purpose
+- [ ] Match database schema if types represent DB entities
+- [ ] Use consistent naming: `PascalCase` for types/interfaces
+
+**Best Practices:**
+- Check `types/` for existing type patterns
+- Prefer interfaces for object shapes (extendable)
+- Use type aliases for unions, intersections, utilities
+- Export from index file if creating new type module
+
+**Constraints:**
+- Working directory: [worktree path]
+- Verify types compile: `npx tsc --noEmit [file]`
+
+**Deliverable:**
+Report: types created, file path, any dependencies on other types
+```
+
+---
+
+### CLI/Script Template
+
+**Use for:** CLI commands, scripts, automation tools
+
+```markdown
+## Task: Implement CLI Command/Script
+
+**Command:** [name]
+**File:** [path]
+
+**Requirements:**
+- [ ] Use commander.js patterns from existing commands (if CLI)
+- [ ] Include descriptive --help text
+- [ ] Handle errors gracefully with appropriate exit codes
+- [ ] Add to command index if this is a new CLI command
+- [ ] Support both programmatic and CLI usage if applicable
+
+**Best Practices:**
+- Check `scripts/` or `src/cli/` for existing patterns
+- Use `process.exit(0)` for success, `process.exit(1)` for errors
+- Log errors to stderr: `console.error()`
+- Provide progress feedback for long-running operations
+
+**Constraints:**
+- Working directory: [worktree path]
+- Scripts should be executable: `chmod +x [file]`
+- Add shebang for shell scripts: `#!/usr/bin/env bash` or `#!/usr/bin/env node`
+
+**Deliverable:**
+Report: script created, command usage, exit codes
+```
+
+---
+
+### Test Template
+
+**Use for:** Unit tests, integration tests, test utilities
+
+```markdown
+## Task: Create Tests
+
+**Test file:** [path]
+**Testing:** [component/module being tested]
+
+**Requirements:**
+- [ ] Use existing test framework patterns (vitest/jest)
+- [ ] Include setup and teardown if needed
+- [ ] Test both success and error cases
+- [ ] Use descriptive test names: `it('should X when Y')`
+- [ ] Mock external dependencies appropriately
+
+**Best Practices:**
+- Check `__tests__/` or `*.test.ts` files for patterns
+- Group related tests with `describe()` blocks
+- Test behavior, not implementation details
+- Aim for meaningful coverage, not 100% line coverage
+
+**Constraints:**
+- Working directory: [worktree path]
+- Run tests after creation: `npm test [file]`
+- Do NOT skip or disable existing tests
+
+**Deliverable:**
+Report: test file created, number of test cases, pass/fail status
+```
+
+---
+
+### Refactor Template
+
+**Use for:** Code restructuring, file reorganization, pattern migrations
+
+```markdown
+## Task: Refactor Code
+
+**Target:** [file or module]
+**Goal:** [what the refactor achieves]
+
+**Requirements:**
+- [ ] Preserve all existing functionality (no behavior changes)
+- [ ] Maintain or improve type safety
+- [ ] Update all imports/exports affected by moves
+- [ ] Ensure tests still pass after refactor
+
+**Best Practices:**
+- Make incremental changes, verify after each step
+- Use IDE rename features when available
+- Update barrel exports (index.ts) if file locations change
+- Check for circular dependencies after restructuring
+
+**Constraints:**
+- Working directory: [worktree path]
+- Run full test suite after refactor: `npm test`
+- Run type check: `npx tsc --noEmit`
+
+**Deliverable:**
+Report: files changed, imports updated, test results
+```
+
+---
+
+### Generic Template
+
+**Use for:** Tasks that don't fit other categories
+
+```markdown
+## Task: [Task Description]
+
+**Goal:** [what needs to be accomplished]
+**Files involved:** [expected files]
+
+**Requirements:**
+- [ ] Complete the task as specified
+- [ ] Follow existing codebase patterns
+- [ ] Maintain type safety
+- [ ] Do not break existing functionality
+
+**Constraints:**
+- Working directory: [worktree path]
+- Run relevant checks after completion
+
+**Deliverable:**
+Report: files created/modified, summary of changes
+```
+
+---
+
+## Error Recovery Template
+
+**Use for:** Retrying failed tasks with enhanced context
+
+When a task fails, use this template to provide diagnostic context for the retry:
+
+```markdown
+## RETRY: Previous Attempt Failed
+
+**Original Task:** [task description]
+**Attempt:** [N] of [max]
+**Previous Error:**
+```
+[error message from TaskOutput]
+```
+
+**Diagnosis Checklist:**
+- [ ] Check imports are correct and files exist
+- [ ] Verify file paths use the worktree directory
+- [ ] Confirm types match expected signatures
+- [ ] Look for typos in identifiers
+- [ ] Check for missing dependencies
+
+**Fix Strategy:**
+1. Read the failing file to understand current state
+2. Identify the specific error location (line number if available)
+3. Apply minimal, targeted fix
+4. Verify fix compiles: `npx tsc --noEmit [file]`
+
+**Critical Constraints (re-emphasized):**
+- You MUST use the worktree path: [worktree path]
+- Do NOT edit files outside the worktree
+- Complete the task with fewer tool calls than previous attempt
+- If the same error occurs, report it clearly rather than retrying
+
+**Deliverable:**
+Report: fix applied, verification result, files changed
+```
+
+---
+
+## Template Customization
+
+### Adding New Templates
+
+To add a custom template:
+
+1. Define the template in this file following the structure above
+2. Add keywords for automatic selection to the keyword table
+3. Document the use case and best practices
+
+### Overriding Templates
+
+Projects can override templates by:
+
+1. Creating `.claude/skills/_shared/references/prompt-templates.local.md`
+2. Defining custom templates with the same headers
+3. Local templates take precedence over defaults
+
+### Template Variables
+
+Templates support these placeholders:
+
+| Variable | Description |
+|----------|-------------|
+| `[name]` | Component/module name from task |
+| `[path]` | File path from task |
+| `[worktree path]` | Current worktree directory |
+| `[task description]` | Original task text |
+
+---
+
+## Usage Example
+
+**Task:** "Create MetricsCard component in components/admin/metrics/"
+
+**Keyword detected:** "component" → Component Template
+
+**Rendered prompt:**
+```markdown
+## Task: Create React Component
+
+**Component:** MetricsCard
+**Location:** components/admin/metrics/MetricsCard.tsx
+
+**Requirements:**
+- [ ] TypeScript with proper prop types (interface or type)
+- [ ] Follow existing component patterns in the codebase
+- [ ] Include displayName for debugging: `MetricsCard.displayName = 'MetricsCard'`
+- [ ] No inline styles - use existing CSS/Tailwind patterns
+- [ ] Export component as named export
+
+**Best Practices:**
+- Check `components/` for similar components to follow patterns
+- Use existing hooks from `lib/hooks/` if applicable
+- Prefer composition over prop drilling
+- Keep components focused - single responsibility
+
+**Constraints:**
+- Working directory: /path/to/worktrees/feature/123-metrics/
+- Do NOT create test files (handled separately)
+- Do NOT add new dependencies without explicit approval
+
+**Deliverable:**
+Report: files created, component name, props interface
+```
+
+---
+
+## References
+
+- [Subagent Types](./subagent-types.md) - Valid subagent types for Task tool
+- `/exec` skill - Parallel execution documentation
+- `/spec` skill - Parallel groups format