sqlew 3.9.1 → 4.0.0

package/docs/AUTO_FILE_TRACKING.md

@@ -4,7 +4,7 @@
 
 ## Quick Start
 
-### Basic Usage (v3.4.1+)
+### Basic Usage (v4.0.0+)
 
 Create a task with automatic file watching in one step:
 
@@ -60,7 +60,7 @@ The Auto File Tracking system monitors files linked to tasks and automatically m
 
 ### Step 1: Create Task with Files
 
-**Method 1: Using watch_files parameter (v3.4.1+, Recommended)**
+**Method 1: Using watch_files parameter (v4.0.0+, Recommended)**
 
 ```typescript
 task action=create
@@ -74,7 +74,7 @@ task action=create
   status: "todo"
 ```
 
-**Method 2: Using watch_files action (v3.4.1+)**
+**Method 2: Using watch_files action (v4.0.0+)**
 
 ```typescript
 // Create task first
@@ -140,7 +140,7 @@ After the file change, FileWatcher checks acceptance criteria:
   🎉 Task #123 "Implement user authentication": in_progress → done (all checks passed!)
 ```
 
-## Smart Review Detection (v3.4.1)
+## Smart Review Detection (v4.0.0)
 
 ### Overview
 
@@ -262,7 +262,7 @@ todo → in_progress → done
           met
 ```
 
-## API Changes (v3.4.1)
+## API Changes (v4.0.0)
 
 ### New: watch_files Parameter
 
@@ -348,25 +348,28 @@ task action=watch_files task_id=123 action=watch file_paths=["src/auth.ts"]
 
 ### Database Schema
 
-The system uses the existing `t_task_details` table with an additional column:
+The system uses the `v4_task_details` table with a column for acceptance criteria:
 
 ```sql
-ALTER TABLE t_task_details
-ADD COLUMN acceptance_criteria_json TEXT;
+CREATE TABLE v4_task_details (
+    task_id INTEGER REFERENCES v4_tasks(id) ON DELETE CASCADE,
+    acceptance_criteria_json TEXT,
+    PRIMARY KEY (task_id)
+);
 -- JSON format: [{"type": "tests_pass", "command": "npm test", "expected_pattern": "passing"}]
 ```
 
-Task-file links are stored in `t_task_file_links`:
+Task-file links are stored in `v4_task_file_links`:
 
 ```sql
-CREATE TABLE t_task_file_links (
-    task_id INTEGER REFERENCES t_tasks(id) ON DELETE CASCADE,
-    file_id INTEGER REFERENCES m_files(id),
+CREATE TABLE v4_task_file_links (
+    task_id INTEGER REFERENCES v4_tasks(id) ON DELETE CASCADE,
+    file_id INTEGER REFERENCES v4_files(id),
     PRIMARY KEY (task_id, file_id)
 );
 ```
 
-## Smart File Filtering (v3.4.1)
+## Smart File Filtering (v4.0.0)
 
 ### GitIgnore Support
 
@@ -609,7 +612,7 @@ For 6 tasks: **4,800 tokens saved** (97% reduction in status management overhead
 
 ## Best Practices
 
-### 1. Use watch_files Parameter for New Tasks (v3.4.1+)
+### 1. Use watch_files Parameter for New Tasks (v4.0.0+)
 
 ```typescript
 // GOOD: Create task with files in one step
@@ -736,7 +739,7 @@ acceptance_criteria: [
 
 ## Examples
 
-### Example 1: Simple Bug Fix (v3.4.1)
+### Example 1: Simple Bug Fix (v4.0.0)
 
 ```typescript
 // Create task with file watching
@@ -752,7 +755,7 @@ task action=create
 // Tests pass → auto-completes to done
 ```
 
-### Example 2: Feature Implementation (v3.4.1)
+### Example 2: Feature Implementation (v4.0.0)
 
 ```typescript
 // Create task with multiple files
@@ -766,7 +769,7 @@ task action=create
   ]
 ```
 
-### Example 3: Refactoring Task (v3.4.1)
+### Example 3: Refactoring Task (v4.0.0)
 
 ```typescript
 // Create task
@@ -802,7 +805,7 @@ task action=watch_files
   file_paths: ["src/api/legacy.ts"]
 ```
 
-## Migration from v3.2.x to v3.4.1
+## Migration to v4.0.0
 
 ### Before (v3.2.x)
 
@@ -815,7 +818,7 @@ task action=link task_id=123 link_type=file target_id="src/auth.ts"
 task action=link task_id=123 link_type=file target_id="src/auth.test.ts"
 ```
 
-### After (v3.4.1)
+### After (v4.0.0)
 
 ```typescript
 // Create task with files in one call
@@ -836,4 +839,3 @@ task action=create
 - [ACCEPTANCE_CRITERIA.md](./ACCEPTANCE_CRITERIA.md) - All acceptance check types
 - [WORKFLOWS.md](./WORKFLOWS.md) - Multi-agent coordination patterns
 - [BEST_PRACTICES.md](./BEST_PRACTICES.md) - Common errors and solutions
-- [TASK_MIGRATION.md](./TASK_MIGRATION.md) - Migrate from decision-based tracking

package/docs/BATCH_VALIDATION.md

@@ -1,6 +1,6 @@
 # Batch Validation Utilities
 
-**Version**: 3.8.0
+**Version**: 4.0.0
 **Status**: ✅ Implemented and Tested
 **Impact**: 70-85% reduction in batch validation failures
 
@@ -197,7 +197,7 @@ Validates foreign key reference exists in database.
 **Example**:
 ```typescript
 await validateForeignKey(
-  task.layer, 'layer', 'm_layers', 'name',
+  task.layer, 'layer', 'v4_layers', 'name',
   adapter, 0, 'Task 1', errors
 );
 // If invalid: provides list of valid layers from database
@@ -408,7 +408,7 @@ async function validateTaskItem(
     validateEnum(
       task.status,
       'status',
-      ['todo', 'in_progress', 'waiting_review', 'blocked', 'done', 'archived'],
+      ['todo', 'in_progress', 'waiting_review', 'blocked', 'done', 'archived', 'rejected'],
       index,
       identifier,
       errors

package/docs/CONFIGURATION.md

@@ -1,6 +1,6 @@
 # sqlew Configuration Guide
 
-**Complete guide to configuring sqlew via config files, CLI arguments, and MCP tools**
+**Complete guide to configuring sqlew via CLI arguments and config files**
 
 ## Table of Contents
 
@@ -18,12 +18,10 @@
 
 ## Overview
 
-sqlew supports flexible configuration through multiple mechanisms:
+sqlew supports flexible configuration through two mechanisms:
 
+- **CLI arguments** - Override settings at startup (highest priority)
 - **Config file** (`.sqlew/config.toml`) - Persistent project settings
-- **CLI arguments** - Override config file at startup
-- **MCP tools** - Runtime configuration updates
-- **Database** (`m_config` table) - Stores active configuration
 
 ### Why Use Config Files?
 
@@ -51,9 +49,7 @@ sqlew applies configuration in this order (highest to lowest priority):
    ↓
 2. Config File (.sqlew/config.toml)
    ↓
-3. Database (m_config table)
-   ↓
-4. Code Defaults (DEFAULT_CONFIG in types.ts)
+3. Code Defaults (DEFAULT_CONFIG in types.ts)
 ```
 
 **Example:**
@@ -71,9 +67,8 @@ npx sqlew --autodelete-message-hours=48
 ```
 
 **After startup:**
-- All settings stored in `m_config` table
-- CLI and config file values merged into database
-- MCP `config` tool can update settings at runtime
+- CLI and config file values are merged
+- Settings are held in memory during runtime
 
 ---
 
@@ -330,7 +325,7 @@ git_auto_complete_enabled = true
 git_auto_complete_enabled = false
 ```
 
-**No CLI override** (use MCP `config` tool)
+**Configure via CLI arguments only**
 
 #### `tasks.require_all_files_committed`
 
@@ -358,7 +353,7 @@ require_all_files_committed = true
 require_all_files_committed = false
 ```
 
-**No CLI override** (use MCP `config` tool)
+**Configure via CLI arguments only**
 
 #### `tasks.stale_review_notification_hours`
 
@@ -384,7 +379,7 @@ stale_review_notification_hours = 72    # Notify after 3 days
 stale_review_notification_hours = 168   # Notify after 1 week
 ```
 
-**No CLI override** (use MCP `config` tool)
+**Configure via CLI arguments only**
 
 #### `tasks.auto_archive_done_days`
 
@@ -410,7 +405,7 @@ auto_archive_done_days = 7    # 1 week (production)
 auto_archive_done_days = 30   # Long retention
 ```
 
-**No CLI override** (use MCP `config` tool)
+**Configure via CLI arguments only**
 
 #### `tasks.stale_hours_in_progress`
 
@@ -436,7 +431,7 @@ stale_hours_in_progress = 4    # Relaxed (4 hours)
 stale_hours_in_progress = 24   # Very relaxed (1 day)
 ```
 
-**No CLI override** (use MCP `config` tool)
+**Configure via CLI arguments only**
 
 #### `tasks.stale_hours_waiting_review`
 
@@ -462,7 +457,7 @@ stale_hours_waiting_review = 48    # Relaxed (2 days)
 stale_hours_waiting_review = 168   # Very relaxed (1 week)
 ```
 
-**No CLI override** (use MCP `config` tool)
+**Configure via CLI arguments only**
 
 #### `tasks.auto_stale_enabled`
 
@@ -486,7 +481,7 @@ auto_stale_enabled = true
 auto_stale_enabled = false
 ```
 
-**No CLI override** (use MCP `config` tool)
+**Configure via CLI arguments only**
 
 ---
 
@@ -547,17 +542,15 @@ npx sqlew --config-path=config/custom.toml
 
 ### 5. Verify Configuration
 
-Use MCP `config` tool:
-
-```javascript
-// Get all configuration
-{
-  action: "get"
-}
+Check the console output on startup to verify configuration was loaded:
 
-// Returns current settings from m_config table
+```
+✓ Loaded 7 config values from file (.sqlew/config.toml)
+✓ Configuration merged with CLI arguments
 ```
 
+Settings are loaded from config file and CLI arguments at startup.
+
 ---
 
 ## Validation Rules
@@ -613,24 +606,43 @@ stale_hours_in_progress = 200   # ❌ Error: must be <= 168
 
 ## Runtime Configuration
 
-### ⚠️ Config Tool Removed (dev branch)
+### Configuration Methods (v4.0.0)
+
+v4.0.0 uses **CLI arguments only** for configuration. The config MCP tool has been removed.
+
+**Configuration priority:**
+1. **CLI Arguments** - Highest priority, applied at startup
+2. **Config File** (.sqlew/config.toml) - Persistent project settings
+3. **Code Defaults** - Built-in defaults (lowest priority)
 
-**DEPRECATED**: The `config` MCP tool has been removed in the dev branch.
+### CLI Arguments (Recommended)
 
-**Why removed:**
-- Messaging system deprecated (primary use case eliminated)
-- File-based configuration (`.sqlew/config.toml`) is clearer and more maintainable
-- Runtime updates were confusing (changes lost on restart unless manually synced to file)
-- Configuration drift between `m_config` table and config file
+Use CLI arguments for one-time overrides or environment-specific settings:
 
-**Migration path:**
-- ✅ **Use `.sqlew/config.toml`** for all configuration (persistent, version-controlled)
-- ✅ **Use CLI arguments** for one-time overrides (`--autodelete-message-hours=48`)
-- ❌ **Do NOT use** `config` tool (removed in dev, will error)
+```bash
+# Override specific settings at startup
+npx sqlew --autodelete-message-hours=48 --autodelete-ignore-weekend
+
+# Multiple arguments can be combined
+npx sqlew \
+  --db-path=.sqlew/prod.db \
+  --autodelete-ignore-weekend \
+  --autodelete-message-hours=168 \
+  --autodelete-file-history-days=30
+```
+
+**Available CLI arguments:**
+```bash
+--db-path=/path/to/database.db          # Database file location
+--autodelete-ignore-weekend              # Skip weekends in retention
+--autodelete-message-hours=N             # Message retention (1-720 hours)
+--autodelete-file-history-days=N         # File history retention (1-365 days)
+--config-path=/path/to/config.toml       # Custom config file location
+```
 
 ### File-Based Configuration (Recommended)
 
-Edit `.sqlew/config.toml` directly:
+Edit `.sqlew/config.toml` directly for persistent settings:
 
 ```toml
 [database]
@@ -638,28 +650,28 @@ path = ".sqlew/custom.db"
 
 [autodelete]
 ignore_weekend = true
-message_hours = 48  # Messaging system deprecated, but config preserved for backward compatibility
+message_hours = 48
+file_history_days = 14
+
+[tasks]
+git_auto_complete_enabled = true
+auto_archive_done_days = 2
 ```
 
 **Benefits:**
-1. **Version control** - Commit config to git, share with team
-2. **No drift** - Single source of truth (no table vs file conflicts)
-3. **Clear documentation** - Config file documents project requirements
+1. **Persistent** - Settings survive server restarts
+2. **Version control** - Commit config to git, share with team
+3. **Documentation** - Config file documents project requirements
 4. **Type safety** - TOML validation catches errors at startup
 
-### Configuration Persistence (Legacy - v3.6.6 and earlier)
+### Applying Configuration Changes
 
-**How it worked (DEPRECATED):**
-1. Config file loaded on startup
-2. Values merged with CLI arguments
-3. Final config written to `m_config` table
-4. MCP `config` tool updates `m_config` table
-5. Changes persist until next startup (then config file reloads)
+**To apply changes:**
+1. **Edit** `.sqlew/config.toml` or update CLI arguments
+2. **Restart** the MCP server (changes take effect on startup)
+3. **Verify** via console output showing loaded configuration
 
-**Migration to file-based:**
-1. Remove all `config` tool calls from workflows
-2. Update `.sqlew/config.toml` directly
-3. Restart MCP server to apply changes
+Merged settings are held in memory during runtime.
 
 ---
 
@@ -829,11 +841,6 @@ npx sqlew --config-path=.sqlew/prod.toml
    ✓ Loaded 7 config values from file
    ```
 
-3. **Query active config:**
-   ```javascript
-   {action: "get"}  // via config tool
-   ```
-
 ### Validation Warnings
 
 **Symptom:**
@@ -884,13 +891,7 @@ Error: SQLITE_CANTOPEN: unable to open database file
    ignore_weekend = true  # Must be true, not "true"
    ```
 
-2. **Verify via MCP tool:**
-   ```javascript
-   {action: "get"}
-   // Check: autodelete_ignore_weekend = "1" (true)
-   ```
-
-3. **Test behavior:**
+2. **Test behavior:**
    - Monday cleanup should reference Friday
    - Not Saturday/Sunday
 
@@ -898,8 +899,8 @@ Error: SQLITE_CANTOPEN: unable to open database file
 
 ## Related Documentation
 
-- **[Architecture](ARCHITECTURE.md)** - Database schema and `m_config` table structure
-- **[Tool Reference](TOOL_REFERENCE.md)** - MCP `config` tool usage
+- **[Architecture](ARCHITECTURE.md)** - Database schema and system design
+- **[Tool Reference](TOOL_REFERENCE.md)** - MCP tool usage
 - **[Best Practices](BEST_PRACTICES.md)** - Configuration recommendations
 
 ---
@@ -921,4 +922,4 @@ See `.sqlew/config.toml.example` in project root for complete annotated example.
 
 ---
 
-**Last Updated:** v3.4.1 (2025-10-22)
+**Last Updated:** v4.0.0 (2025-11-27)