sqlew 3.9.1 → 4.0.1

package/assets/sample-commands/sqw-scrum.md

@@ -1,4 +1,30 @@
-# Sqlew Scrum Master Agent
+---
+description: Break down plans into tasks, manage dependencies, and coordinate parallel execution
+---
+
+# Sqlew Scrum Master Workflow
+
+Task management workflow for breaking down work, managing dependencies, and coordinating execution.
+
+## Agent Invocation
+
+This workflow uses the specialized scrum-master agent:
+
+```
+Task tool → subagent_type: "scrum-master" (sonnet)
+```
+
+**Example:**
+```typescript
+Task({
+  subagent_type: "scrum-master",
+  prompt: "Break down the following work into tasks: [user requirement]. Create tasks with proper layers, priorities, and dependencies."
+})
+```
+
+---
+
+**Agent Instructions (for scrum-master):**
 
 You are an expert Scrum Master specializing in agile task planning, coordination, and dependency management using the sqlew MCP shared context server.
 
@@ -12,7 +38,7 @@ Break down work into manageable tasks, establish dependencies, coordinate agent
   - **create**: Create new tasks with metadata (priority, layer, file_actions, tags)
   - **update**: Modify task details
   - **get**: Retrieve task details
-  - **list**: Query tasks with filters (status, agent, layer, tags, priority)
+  - **list**: Query tasks with filters (status, layer, tags, priority)
   - **move**: Transition task status (todo → in_progress → waiting_review → done → archived)
   - **link**: Connect tasks to decisions, constraints, or files
   - **archive**: Archive completed tasks
@@ -21,6 +47,10 @@ Break down work into manageable tasks, establish dependencies, coordinate agent
   - **get_dependencies**: Visualize dependency graph
   - **watcher**: Check file watcher status
 
+- **mcp__sqlew__suggest**: Find related items before linking (v4.0)
+  - **by_context** with `target: "constraint"`: Find constraints to link to tasks
+  - **by_tags** with `target: "constraint"`: Find constraints by tags
+
 ## Workflow
 
 ### 1. Task Planning & Execution
@@ -203,6 +233,10 @@ Connect tasks to architectural context:
 
 2. **Link to constraints** addressed:
    ```typescript
+   // Find related constraints first (v4.0)
+   suggest({ action: "by_context", target: "constraint", text: "authentication", tags: ["security"] })
+
+   // Then link
    task({
      action: "link",
      task_id: 15,
@@ -261,7 +295,7 @@ The command automatically detects whether to use Mode A or Mode B based on your
 7. **Use file_actions: []** - allowed for planning tasks in code layers
 8. **Omit file_actions** - allowed for planning/coordination/review layers only
 
-### Layer Selection (v3.8.0)
+### Layer Selection (v4.0)
 
 **FILE_REQUIRED Layers** (must include file_actions or []):
 - **presentation**: UI components, views, templates

package/dist/adapters/mysql-adapter.js

@@ -627,9 +627,9 @@ export class MySQLAdapter extends BaseAdapter {
     async tableExists(tableName) {
         const knex = this.getKnex();
         const database = this.config.connection.database;
-        const result = await knex.raw(`SELECT TABLE_NAME
-       FROM INFORMATION_SCHEMA.TABLES
-       WHERE TABLE_SCHEMA = ?
+        const result = await knex.raw(`SELECT TABLE_NAME
+       FROM INFORMATION_SCHEMA.TABLES
+       WHERE TABLE_SCHEMA = ?
          AND TABLE_NAME = ?`, [database, tableName]);
         return result[0].length > 0;
     }

package/dist/adapters/postgresql-adapter.js

@@ -318,9 +318,9 @@ export class PostgreSQLAdapter extends BaseAdapter {
     async tableExists(tableName) {
         const knex = this.getKnex();
         const database = this.config.connection.database;
-        const result = await knex.raw(`SELECT table_name
-       FROM information_schema.tables
-       WHERE table_catalog = ?
+        const result = await knex.raw(`SELECT table_name
+       FROM information_schema.tables
+       WHERE table_catalog = ?
          AND table_name = ?`, [database, tableName]);
         return result.rows.length > 0;
     }

package/dist/cli/db-dump.js

@@ -9,79 +9,79 @@ import { loadConfigFile } from '../config/loader.js';
  * Show help message for db:dump command
  */
 export function showDbDumpHelp() {
-    console.log(`
-sqlew db:dump - Generate SQL dump for database migration
-
-USAGE:
-  npx sqlew db:dump --format=<format> [options]
-
-REQUIRED OPTIONS:
-  --format <format>        Target database format: mysql, postgresql, or sqlite
-
-OPTIONS:
-  --from <database>        Source database: sqlite, mysql, or postgresql (default: sqlite)
-  --output <file>          Output file path (default: stdout)
-  --tables <tables>        Comma-separated list of tables to dump (default: all)
-  --chunk-size <number>    Rows per INSERT statement (default: 100)
-  --max-statements <num>   Max statements per file - splits into multiple files if exceeded
-                           (default: unlimited, recommended: 900 for MariaDB batch mode)
-  --on-conflict <mode>     Duplicate key handling: error, ignore, replace (default: error)
-                           - error: Standard INSERT (fails on duplicates)
-                           - ignore: Skip duplicate rows (INSERT IGNORE/ON CONFLICT DO NOTHING)
-                           - replace: Update existing rows (ON DUPLICATE KEY UPDATE/ON CONFLICT DO UPDATE)
-  --exclude-schema         Exclude CREATE TABLE statements (data-only dump)
-                           By default, schema is included for complete migration
-  --db-path <path>         SQLite database file path (overrides config file)
-  --config <path>          Config file path (default: auto-detect .sqlew/config.toml or config.toml)
-  --help                   Show this help message
-
-CONFIG FILE:
-  The command automatically loads database settings from config.toml.
-  Priority: CLI args > config file > environment variables > defaults
-
-ENVIRONMENT VARIABLES (for MySQL/PostgreSQL sources):
-  MYSQL_HOST               MySQL host (default: 127.0.0.1)
-  MYSQL_PORT               MySQL port (default: 3306)
-  MYSQL_USER               MySQL username
-  MYSQL_PASSWORD           MySQL password
-  MYSQL_DATABASE           MySQL database name
-
-  PG_HOST                  PostgreSQL host (default: localhost)
-  PG_PORT                  PostgreSQL port (default: 5432)
-  PG_USER                  PostgreSQL username
-  PG_PASSWORD              PostgreSQL password
-  PG_DATABASE              PostgreSQL database name
-
-EXAMPLES:
-  # SQLite → MySQL (default source)
-  npx sqlew db:dump --format mysql --output dump-mysql.sql
-
-  # MySQL → SQLite (reverse migration)
-  npx sqlew db:dump --from mysql --format sqlite --output dump-sqlite.sql
-
-  # PostgreSQL → MySQL (cross-database)
-  npx sqlew db:dump --from postgresql --format mysql --output dump-mysql.sql
-
-  # MySQL → PostgreSQL (cross-database)
-  npx sqlew db:dump --from mysql --format postgresql --output dump-pg.sql
-
-  # Dump specific tables from PostgreSQL
-  npx sqlew db:dump --from postgresql --format sqlite --tables t_decisions,t_tasks
-
-  # Split dump for MariaDB batch mode (1000 statement limit)
-  npx sqlew db:dump --format mysql --output dump.sql --max-statements=900
-
-MIGRATION WORKFLOW:
-  1. Create schema on target database:
-     npm run migrate:latest --env=<target>
-
-  2. Generate SQL dump from source:
-     npx sqlew db:dump --from=<source> --format=<target> --output=dump.sql
-
-  3. Import data into target database:
-     mysql < dump.sql    # for MySQL
-     psql -f dump.sql    # for PostgreSQL
-     sqlite3 db.db < dump.sql    # for SQLite
+    console.log(`
+sqlew db:dump - Generate SQL dump for database migration
+
+USAGE:
+  npx sqlew db:dump --format=<format> [options]
+
+REQUIRED OPTIONS:
+  --format <format>        Target database format: mysql, postgresql, or sqlite
+
+OPTIONS:
+  --from <database>        Source database: sqlite, mysql, or postgresql (default: sqlite)
+  --output <file>          Output file path (default: stdout)
+  --tables <tables>        Comma-separated list of tables to dump (default: all)
+  --chunk-size <number>    Rows per INSERT statement (default: 100)
+  --max-statements <num>   Max statements per file - splits into multiple files if exceeded
+                           (default: unlimited, recommended: 900 for MariaDB batch mode)
+  --on-conflict <mode>     Duplicate key handling: error, ignore, replace (default: error)
+                           - error: Standard INSERT (fails on duplicates)
+                           - ignore: Skip duplicate rows (INSERT IGNORE/ON CONFLICT DO NOTHING)
+                           - replace: Update existing rows (ON DUPLICATE KEY UPDATE/ON CONFLICT DO UPDATE)
+  --exclude-schema         Exclude CREATE TABLE statements (data-only dump)
+                           By default, schema is included for complete migration
+  --db-path <path>         SQLite database file path (overrides config file)
+  --config <path>          Config file path (default: auto-detect .sqlew/config.toml or config.toml)
+  --help                   Show this help message
+
+CONFIG FILE:
+  The command automatically loads database settings from config.toml.
+  Priority: CLI args > config file > environment variables > defaults
+
+ENVIRONMENT VARIABLES (for MySQL/PostgreSQL sources):
+  MYSQL_HOST               MySQL host (default: 127.0.0.1)
+  MYSQL_PORT               MySQL port (default: 3306)
+  MYSQL_USER               MySQL username
+  MYSQL_PASSWORD           MySQL password
+  MYSQL_DATABASE           MySQL database name
+
+  PG_HOST                  PostgreSQL host (default: localhost)
+  PG_PORT                  PostgreSQL port (default: 5432)
+  PG_USER                  PostgreSQL username
+  PG_PASSWORD              PostgreSQL password
+  PG_DATABASE              PostgreSQL database name
+
+EXAMPLES:
+  # SQLite → MySQL (default source)
+  npx sqlew db:dump --format mysql --output dump-mysql.sql
+
+  # MySQL → SQLite (reverse migration)
+  npx sqlew db:dump --from mysql --format sqlite --output dump-sqlite.sql
+
+  # PostgreSQL → MySQL (cross-database)
+  npx sqlew db:dump --from postgresql --format mysql --output dump-mysql.sql
+
+  # MySQL → PostgreSQL (cross-database)
+  npx sqlew db:dump --from mysql --format postgresql --output dump-pg.sql
+
+  # Dump specific tables from PostgreSQL
+  npx sqlew db:dump --from postgresql --format sqlite --tables t_decisions,t_tasks
+
+  # Split dump for MariaDB batch mode (1000 statement limit)
+  npx sqlew db:dump --format mysql --output dump.sql --max-statements=900
+
+MIGRATION WORKFLOW:
+  1. Create schema on target database:
+     npm run migrate:latest --env=<target>
+
+  2. Generate SQL dump from source:
+     npx sqlew db:dump --from=<source> --format=<target> --output=dump.sql
+
+  3. Import data into target database:
+     mysql < dump.sql    # for MySQL
+     psql -f dump.sql    # for PostgreSQL
+     sqlite3 db.db < dump.sql    # for SQLite
 `);
 }
 /**

package/dist/cli/db-export.js

@@ -12,56 +12,56 @@ import { loadConfigFile } from '../config/loader.js';
  * Show help message for db:export command
  */
 export function showDbExportHelp() {
-    console.log(`
-sqlew db:export - Export project data to JSON format
-
-USAGE:
-  npx sqlew db:export [options]
-
-OPTIONS:
-  --project <name>         Export specific project by name (required for multi-project databases)
-                           If not specified, exports all projects
-  --output <file>          Output file path (default: stdout)
-  --db-path <path>         SQLite database file path (overrides config file)
-  --config <path>          Config file path (default: auto-detect .sqlew/config.toml or config.toml)
-  --help                   Show this help message
-
-CONFIG FILE:
-  The command automatically loads database settings from config.toml.
-  Priority: CLI args > config file > environment variables > defaults
-
-EXAMPLES:
-  # Export specific project to file
-  npx sqlew db:export --project=visualizer --output=visualizer-data.json
-
-  # Export all projects
-  npx sqlew db:export --output=full-backup.json
-
-  # Export to stdout (pipe to file or another command)
-  npx sqlew db:export --project=myproject
-
-  # Export with explicit database path
-  npx sqlew db:export --project=myproject --db-path=.sqlew/sqlew.db --output=data.json
-
-EXPORT FORMAT:
-  The exported JSON contains:
-  - Project metadata
-  - Master tables (agents, files, tags, etc.) - only entries used by project
-  - Transaction tables (decisions, tasks, constraints, etc.) - filtered by project_id
-  - Statistics (decision count, task count, etc.)
-
-IMPORT WORKFLOW:
-  1. Export data from source database:
-     npx sqlew db:export --project=visualizer --output=data.json
-
-  2. Copy JSON file to target project directory
-
-  3. Import data into target database:
-     npx sqlew db:import --source=data.json --project-name=visualizer-v2
-
-SEE ALSO:
-  npx sqlew db:dump --help    # SQL export with schema (for full database migration)
-  npx sqlew db:import --help  # Import JSON data (append to existing database)
+    console.log(`
+sqlew db:export - Export project data to JSON format
+
+USAGE:
+  npx sqlew db:export [options]
+
+OPTIONS:
+  --project <name>         Export specific project by name (required for multi-project databases)
+                           If not specified, exports all projects
+  --output <file>          Output file path (default: stdout)
+  --db-path <path>         SQLite database file path (overrides config file)
+  --config <path>          Config file path (default: auto-detect .sqlew/config.toml or config.toml)
+  --help                   Show this help message
+
+CONFIG FILE:
+  The command automatically loads database settings from config.toml.
+  Priority: CLI args > config file > environment variables > defaults
+
+EXAMPLES:
+  # Export specific project to file
+  npx sqlew db:export --project=visualizer --output=visualizer-data.json
+
+  # Export all projects
+  npx sqlew db:export --output=full-backup.json
+
+  # Export to stdout (pipe to file or another command)
+  npx sqlew db:export --project=myproject
+
+  # Export with explicit database path
+  npx sqlew db:export --project=myproject --db-path=.sqlew/sqlew.db --output=data.json
+
+EXPORT FORMAT:
+  The exported JSON contains:
+  - Project metadata
+  - Master tables (agents, files, tags, etc.) - only entries used by project
+  - Transaction tables (decisions, tasks, constraints, etc.) - filtered by project_id
+  - Statistics (decision count, task count, etc.)
+
+IMPORT WORKFLOW:
+  1. Export data from source database:
+     npx sqlew db:export --project=visualizer --output=data.json
+
+  2. Copy JSON file to target project directory
+
+  3. Import data into target database:
+     npx sqlew db:import --source=data.json --project-name=visualizer-v2
+
+SEE ALSO:
+  npx sqlew db:dump --help    # SQL export with schema (for full database migration)
+  npx sqlew db:import --help  # Import JSON data (append to existing database)
 `);
 }
 /**

package/dist/cli/db-import.js

@@ -12,57 +12,57 @@ import { loadConfigFile } from '../config/loader.js';
  * Show help message for db:import command
  */
 export function showDbImportHelp() {
-    console.log(`
-sqlew db:import - Import project data from JSON export
-
-USAGE:
-  npx sqlew db:import --source=<file> [options]
-
-OPTIONS:
-  --source <file>          JSON export file path (required)
-  --project-name <name>    Target project name (default: use name from JSON)
-  --skip-if-exists         Skip import if project exists (default: true)
-  --dry-run                Validate only, don't import (default: false)
-  --db-path <path>         SQLite database file path (overrides config file)
-  --config <path>          Config file path (default: auto-detect .sqlew/config.toml)
-  --help                   Show this help message
-
-CONFIG FILE:
-  The command automatically loads database settings from config.toml.
-  Priority: CLI args > config file > environment variables > defaults
-
-EXAMPLES:
-  # Import from JSON export
-  npx sqlew db:import --source=visualizer-data.json
-
-  # Import with custom project name
-  npx sqlew db:import --source=data.json --project-name=visualizer-v2
-
-  # Dry run validation
-  npx sqlew db:import --source=data.json --dry-run
-
-  # Import to specific database
-  npx sqlew db:import --source=data.json --db-path=.sqlew/target.db
-
-IMPORT BEHAVIOR:
-  - Always creates new IDs (no ID preservation from source)
-  - Skips import if project name already exists (prevents conflicts)
-  - Uses topological sort for task dependencies
-  - Wraps entire import in transaction (atomic all-or-nothing)
-  - Smart merge for project-scoped tables (files, tags, scopes)
-
-WORKFLOW:
-  1. Export data from source database:
-     npx sqlew db:export --project=myproject --output=data.json
-
-  2. Copy JSON file to target project directory
-
-  3. Import data into target database:
-     npx sqlew db:import --source=data.json
-
-SEE ALSO:
-  npx sqlew db:export --help    # Export project data to JSON
-  npx sqlew db:dump --help      # SQL export with schema (for database migration)
+    console.log(`
+sqlew db:import - Import project data from JSON export
+
+USAGE:
+  npx sqlew db:import --source=<file> [options]
+
+OPTIONS:
+  --source <file>          JSON export file path (required)
+  --project-name <name>    Target project name (default: use name from JSON)
+  --skip-if-exists         Skip import if project exists (default: true)
+  --dry-run                Validate only, don't import (default: false)
+  --db-path <path>         SQLite database file path (overrides config file)
+  --config <path>          Config file path (default: auto-detect .sqlew/config.toml)
+  --help                   Show this help message
+
+CONFIG FILE:
+  The command automatically loads database settings from config.toml.
+  Priority: CLI args > config file > environment variables > defaults
+
+EXAMPLES:
+  # Import from JSON export
+  npx sqlew db:import --source=visualizer-data.json
+
+  # Import with custom project name
+  npx sqlew db:import --source=data.json --project-name=visualizer-v2
+
+  # Dry run validation
+  npx sqlew db:import --source=data.json --dry-run
+
+  # Import to specific database
+  npx sqlew db:import --source=data.json --db-path=.sqlew/target.db
+
+IMPORT BEHAVIOR:
+  - Always creates new IDs (no ID preservation from source)
+  - Skips import if project name already exists (prevents conflicts)
+  - Uses topological sort for task dependencies
+  - Wraps entire import in transaction (atomic all-or-nothing)
+  - Smart merge for project-scoped tables (files, tags, scopes)
+
+WORKFLOW:
+  1. Export data from source database:
+     npx sqlew db:export --project=myproject --output=data.json
+
+  2. Copy JSON file to target project directory
+
+  3. Import data into target database:
+     npx sqlew db:import --source=data.json
+
+SEE ALSO:
+  npx sqlew db:export --help    # Export project data to JSON
+  npx sqlew db:dump --help      # SQL export with schema (for database migration)
 `);
 }
 /**

package/dist/cli.js

@@ -94,58 +94,58 @@ function formatTable(data, headers) {
  * Show help message
  */
 function showHelp() {
-    console.log(`
-sqlew CLI - Query and database migration tool for mcp-sqlew
-
-USAGE:
-  sqlew <command> [subcommand] [options]
-
-COMMANDS:
-  query      Query context data (decisions, messages, files)
-  db:dump    Generate SQL dump for database migration (schema + data)
-  db:export  Export project data to JSON format (data-only, for append-import)
-  db:import  Import project data from JSON export (append to existing database)
-
-QUERY SUBCOMMANDS:
-  decisions  Query decisions with filtering
-  messages   Query agent messages
-  files      Query file changes
-
-QUERY OPTIONS:
-  --layer <layer>          Filter by layer (presentation, business, data, infrastructure, cross-cutting)
-  --tags <tags>            Filter by tags (comma-separated)
-  --since <time>           Time filter (e.g., "5m", "1h", "2d", or ISO timestamp)
-  --unread                 Show only unread messages (messages only)
-  --priority <priority>    Filter by priority (low, medium, high, critical)
-  --agent <agent>          Filter by agent name
-  --limit <number>         Limit number of results
-  --output <format>        Output format: json or table (default: json)
-  --db-path <path>         Database file path (default: .sqlew/sqlew.db)
-  --help                   Show this help message
-
-EXAMPLES:
-  # Query active decisions with breaking changes
-  sqlew query decisions --layer=business --tags=breaking --output=table
-
-  # Query unread high-priority messages
-  sqlew query messages --unread --priority=high --output=json
-
-  # Generate MySQL dump for database migration
-  sqlew db:dump --format=mysql --output=dump-mysql.sql
-
-  # Generate PostgreSQL dump
-  sqlew db:dump --format=postgresql --output=dump-pg.sql
-
-  # Export project data to JSON (for merging data across databases)
-  sqlew db:export --project=visualizer --output=data.json
-
-  # Import project data from JSON export
-  sqlew db:import --source=data.json --project-name=visualizer-v2
-
-For more information on commands, run:
-  sqlew db:dump --help
-  sqlew db:export --help
-  sqlew db:import --help
+    console.log(`
+sqlew CLI - Query and database migration tool for mcp-sqlew
+
+USAGE:
+  sqlew <command> [subcommand] [options]
+
+COMMANDS:
+  query      Query context data (decisions, messages, files)
+  db:dump    Generate SQL dump for database migration (schema + data)
+  db:export  Export project data to JSON format (data-only, for append-import)
+  db:import  Import project data from JSON export (append to existing database)
+
+QUERY SUBCOMMANDS:
+  decisions  Query decisions with filtering
+  messages   Query agent messages
+  files      Query file changes
+
+QUERY OPTIONS:
+  --layer <layer>          Filter by layer (presentation, business, data, infrastructure, cross-cutting)
+  --tags <tags>            Filter by tags (comma-separated)
+  --since <time>           Time filter (e.g., "5m", "1h", "2d", or ISO timestamp)
+  --unread                 Show only unread messages (messages only)
+  --priority <priority>    Filter by priority (low, medium, high, critical)
+  --agent <agent>          Filter by agent name
+  --limit <number>         Limit number of results
+  --output <format>        Output format: json or table (default: json)
+  --db-path <path>         Database file path (default: .sqlew/sqlew.db)
+  --help                   Show this help message
+
+EXAMPLES:
+  # Query active decisions with breaking changes
+  sqlew query decisions --layer=business --tags=breaking --output=table
+
+  # Query unread high-priority messages
+  sqlew query messages --unread --priority=high --output=json
+
+  # Generate MySQL dump for database migration
+  sqlew db:dump --format=mysql --output=dump-mysql.sql
+
+  # Generate PostgreSQL dump
+  sqlew db:dump --format=postgresql --output=dump-pg.sql
+
+  # Export project data to JSON (for merging data across databases)
+  sqlew db:export --project=visualizer --output=data.json
+
+  # Import project data from JSON export
+  sqlew db:import --source=data.json --project-name=visualizer-v2
+
+For more information on commands, run:
+  sqlew db:dump --help
+  sqlew db:export --help
+  sqlew db:import --help
 `);
 }
 // ============================================================================