sqlew 3.2.5 → 3.6.0

package/CHANGELOG.md

@@ -5,1095 +5,372 @@ All notable changes to sqlew will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.6.0] - 2025-10-25
+
+### Added - Help System Optimization
+
+**Database-driven help system with 60-70% token efficiency improvement**
+
+#### Key Achievements
+- **60-70% Token Reduction** - Average help query: ~200 tokens (vs ~2,150 legacy)
+- **95.8% Schema Reduction** - MCP InputSchemas: 350 tokens (vs 8,400 legacy)
+- **6 New Help Actions** - Granular queries for actions, parameters, tools, use-cases
+- **41 Use-Cases** - Comprehensive workflow examples across 6 categories
+- **100% Test Coverage** - 38/38 tests passing
+
+#### New MCP Actions (stats tool)
+- `help_action` - Query single action with parameters and examples
+- `help_params` - Query parameter list for an action
+- `help_tool` - Query tool overview + all actions
+- `help_use_case` - Get single use-case with full workflow
+- `help_list_use_cases` - List/filter use-cases by category/complexity
+- `help_next_actions` - Suggest common next actions
+
+#### Database Schema
+7 new tables: `m_help_tools`, `m_help_actions`, `m_help_use_case_categories`, `t_help_action_params`, `t_help_action_examples`, `t_help_use_cases`, `t_help_action_sequences`
+
+#### Migration from v3.5.x
+- Automatic migration on startup
+- Backward compatible - all existing MCP actions unchanged
+- Zero downtime
+
+---
+
+## [3.5.2] - 2025-10-24
+
+### Added - Two-Step Git-Aware Task Workflow
+
+**Automatic task completion and archiving based on Git staging and committing**
+
+#### Features
+- **Step 1 - Staging** (`git add`): `waiting_review` → `done` (work complete)
+- **Step 2 - Committing** (`git commit`): `done` → `archived` (work finalized)
+- **VCS Support**: Git, Mercurial, and SVN
+- **Zero Token Cost**: Fully automated, no manual MCP calls needed
+
+#### Configuration
+- `git_auto_complete_on_stage` (default: `'1'`)
+- `git_auto_archive_on_commit` (default: `'1'`)
+- `require_all_files_staged` (default: `'1'`)
+- `require_all_files_committed_for_archive` (default: `'1'`)
+
+---
+
+## [3.5.1] - 2025-10-24
+
+### Fixed - File Watcher WSL Compatibility
+
+**Upgraded chokidar from v3 to v4 + Fixed path normalization bug**
+
+#### Changes
+- **chokidar**: `^3.6.0` → `^4.0.3` (automatic WSL support)
+- Fixed path normalization: chokidar reports absolute paths, database stores relative
+- Removed manual WSL detection and polling configuration
+
+---
+
+## [3.5.0] - 2025-10-22
+
+### Added - Non-Existent File Auto-Pruning
+
+**Automatic removal of non-existent watched files with audit trail**
+
+#### Features
+- New table: `t_task_pruned_files` - Audit trail for pruned files
+- Auto-pruning during `in_progress → waiting_review` transition
+- Safety check: blocks if ALL files non-existent
+- New MCP actions: `get_pruned_files`, `link_pruned_file`
+
+#### Documentation
+- `TASK_PRUNING.md` - Comprehensive guide with examples and best practices
+
+---
+
+## [3.4.1] - 2025-10-22
+
+### Fixed - File Watcher Immediate Detection
+
+**Fixed chokidar configuration for instant file change detection**
+
+#### Changes
+- Removed 5-second aggregation delay
+- Added `awaitWriteFinish` for write completion detection
+- Immediate auto-transition on file save
+
+---
+
+## [3.4.0] - 2025-10-22
+
+### Added - VCS-Aware File Watching
+
+**Automatic task transitions based on Git commit detection**
+
+#### Features
+- Auto-transition: `waiting_review` → `done` when watched files committed
+- Multi-VCS support: Git, Mercurial, SVN
+- VCS adapter pattern with pluggable implementations
+- Whitelist exemption: Skip auto-transition for critical files (package.json, migrations)
+- Configuration: `git_auto_complete_tasks`, `git_require_all_files_committed`, `git_file_whitelist`
+
+#### Database Schema
+- New table: `m_git_file_whitelist` - Exempt files from auto-completion
+
+---
+
+## [3.2.6] - 2025-10-21
+
+### Fixed - File Watcher Test Stability
+
+**Improved debouncing and async handling in file watcher tests**
+
+---
+
 ## [3.2.5] - 2025-10-21
 
-### Fixed
-
-#### 1. Critical Bug Fix: Constraint Creation
-- **Issue**: "no such column: category_id" error when adding constraints
-- **Root Cause**: `getOrCreateCategoryId()` function in `src/database.ts` was using incorrect column names
-- **Bug**: Function was using `category_id`, `category_name` instead of correct schema columns `id`, `name`
-- **Impact**: All users attempting to use the `constraint` tool's `add` action would fail
-- **Solution**: Updated function to use correct column names matching `m_constraint_categories` table schema
-- **File**: `src/database.ts:282-294`
-
-#### 2. Critical Bug Fix: Decision Creation with Undefined Parameters
-- **Issue**: "Cannot read properties of undefined (reading 'trim')" error when setting decisions
-- **Root Cause**: `validateRequired()` function in `src/utils/validators.ts` called `.trim()` on undefined/null values
-- **Bug**: Function assumed `value` parameter was always a string, but at runtime could be undefined/null from user input
-- **Impact**: All decision operations with missing/undefined parameters would crash with cryptic error instead of helpful validation message
-- **Solution**: Added null/undefined checks before calling `.trim()`, plus type validation
-- **File**: `src/utils/validators.ts:13-31`
-- **Error Behavior Change**:
-  - **Before**: `Cannot read properties of undefined (reading 'trim')` (unhelpful)
-  - **After**: `key is required` (clear validation message)
-
-### Technical Details
-
-**Constraint Bug:**
-- Schema-code mismatch - code was referencing non-existent columns
-- `m_constraint_categories` has `id` and `name` columns
-- Applied standard `INSERT OR IGNORE` + `SELECT` pattern consistent with other helper functions
-
-**Validator Bug:**
-- TypeScript type system doesn't prevent undefined at runtime for parameters from JSON/user input
-- Added defensive checks: undefined, null, type validation, then trim
-- Now provides helpful error messages for all invalid parameter scenarios
-- All validation errors are now user-friendly instead of JavaScript runtime errors
-
-**Testing:**
-- Both fixes verified with comprehensive test scripts
-- All existing tests pass (19/19)
-- Backward compatible - only fixes broken functionality
+### Fixed - File Watcher Error Handling
+
+**Enhanced error handling and logging for file watcher operations**
+
+---
 
 ## [3.2.4] - 2025-10-20
 
-### Fixed
-- **Package Description Correction**
-  - Fixed incorrect token efficiency claim in package.json
-  - Changed from "96% token efficiency through API consolidation" to "60-75% token reduction in multi-session projects"
-  - The 60-75% reflects real-world usage across multi-session projects (as documented in README.md)
-  - Note: 96% refers specifically to v2.0 API consolidation (tool definitions only), not real-world usage
-  - v3.2.3 deprecated due to misleading description
+### Fixed - File Watcher Path Resolution
+
+**Fixed absolute path resolution for file watching**
+
+---
 
 ## [3.2.3] - 2025-10-20 [DEPRECATED]
 
-### Changed
-- **Code Organization - Major Refactoring**
-  - Reduced `src/index.ts` from 1,534 lines to 525 lines (66% reduction)
-  - Extracted 1,009 lines of help/example documentation to respective tool files
-  - Moved help/example functions to 7 tool files: `context.ts`, `messaging.ts`, `files.ts`, `constraints.ts`, `utils.ts`, `config.ts`, `tasks.ts`
-  - Improved maintainability: Help/example documentation now co-located with tool implementations
-  - Zero API changes: All 14 help/example actions remain fully backward compatible
-
-- **File Watcher Documentation Updates**
-  - Corrected token savings claims: Changed "97% token reduction" to "save 300 tokens per file compared to registering watchers manually"
-  - Updated claims in 5 locations across `taskHelp()` and `taskExample()` functions
-  - Added best practice recommendation: "Except in exceptional cases, it is recommended to set up file watchers for all tasks that involve code changes"
-  - Clarified automatic file watching benefits with accurate token efficiency metrics
-
-- **Package Description Update**
-  - Updated description from "97% token reduction" to "96% token efficiency through API consolidation"
-  - More accurately reflects the token savings from v2.0 action-based API consolidation
-
-### Technical Details
-- **Files Modified:**
-  - `src/index.ts`: Simplified to pure routing logic (525 lines)
-  - `src/tools/context.ts`: Added `decisionHelp()`, `decisionExample()` (+217 lines)
-  - `src/tools/messaging.ts`: Added `messageHelp()`, `messageExample()` (+136 lines)
-  - `src/tools/files.ts`: Added `fileHelp()`, `fileExample()` (+127 lines)
-  - `src/tools/constraints.ts`: Added `constraintHelp()`, `constraintExample()` (+169 lines)
-  - `src/tools/utils.ts`: Added `statsHelp()`, `statsExample()` (+137 lines)
-  - `src/tools/config.ts`: Added `configHelp()`, `configExample()` (+107 lines)
-  - `src/tools/tasks.ts`: Added `taskExample()` (+200 lines, `taskHelp()` already existed)
-
-- **Pattern Applied:** Extract inline switch case blocks to exported functions in tool files
-- **Backward Compatibility:** 100% maintained - all existing MCP tool calls work identically
-- **Build:** TypeScript compilation successful with zero errors
+### Changed - File Watcher Implementation (Deprecated)
+
+This version was replaced by v3.2.4. Use v3.2.4 or later.
+
+---
 
 ## [3.2.2] - 2025-10-18
 
-### Added
-- **Decision Context - Rich Decision Documentation** (GitHub Discussion #9)
-  - New `add_decision_context` action: Attach rationale, alternatives, and trade-offs to decisions
-  - New `list_decision_contexts` action: Query decision contexts with flexible filters
-  - Enhanced `get` action with `include_context` parameter to retrieve decision with full context
-  - Database schema: New `t_decision_context` table with relationships to decisions, tasks, and constraints
-  - Migration script for existing databases (v3.2.0 → v3.2.2)
-  - Comprehensive documentation: `docs/DECISION_CONTEXT.md` (500+ lines with real-world scenarios)
-
-### Features
-- **Rich Context Storage:**
-  - `rationale` (required): Explanation of WHY a decision was made
-  - `alternatives_considered` (optional): JSON array of rejected alternatives with reasons
-  - `tradeoffs` (optional): JSON object with pros/cons analysis
-  - `decided_by` (optional): Agent who made the decision
-  - `related_task_id` (optional): Link to implementation task
-  - `related_constraint_id` (optional): Link to system constraint
-
-### Use Cases (from DECISION_CONTEXT.md)
-- **Multi-Session AI Development**: Preserve decision rationale across days/weeks of development
-- **Architecture Reviews & Team Handoffs**: Explain non-standard choices to future developers
-- **Breaking Changes & Deprecations**: Document migration requirements and timelines
-- **Performance Optimization Trade-offs**: Prevent future "optimizations" that regress quality
-
-### Documentation
-- Added `docs/DECISION_CONTEXT.md` - Comprehensive guide with 4 detailed scenarios:
-  - Scenario 1: Multi-Session AI Development (auth token storage example)
-  - Scenario 2: Architecture Reviews (SQLite vs PostgreSQL example)
-  - Scenario 3: Breaking Changes (API versioning example)
-  - Scenario 4: Performance Optimization (caching strategy example)
-- Includes best practices, token efficiency guidelines, and migration patterns
-- API reference with all parameters and examples
-
-### Technical Details
-- **Backward Compatible**: Zero breaking changes - new feature is completely optional
-- **Migration Safety**: CREATE TABLE IF NOT EXISTS pattern ensures idempotent migration
-- **Token Efficiency**: Optional feature - only add context when decision rationale is critical
-- **Indexes**: 3 optimized indexes for key-based, task-based, and constraint-based queries
-- **CASCADE Deletion**: Contexts are deleted when parent decision is removed
-- **SET NULL**: Task/constraint links remain even if linked resources are deleted
-
-### Changed
-- Database schema version bumped to v3.2.2
-- MCP server version updated to 3.2.2
-- Enhanced `decision` tool with 2 new actions (total: 17 actions)
+### Added - Decision Context
+
+**Rich decision documentation with rationale, alternatives, tradeoffs**
+
+#### Features
+- New table: `t_decision_context` - Attach context to decisions
+- New actions: `add_decision_context`, `list_decision_contexts`
+- Enhanced `get` action with `include_context` parameter
+
+#### Documentation
+- `DECISION_CONTEXT.md` - Comprehensive guide for decision documentation
+
+---
 
 ## [3.2.0] - 2025-10-18
 
-### Added
-- **Task Dependency Management** (GitHub Issue #16)
-  - New `add_dependency` action: Add blocking relationships between tasks
-  - New `remove_dependency` action: Remove blocking relationships
-  - New `get_dependencies` action: Query task dependencies bidirectionally
-  - Circular dependency detection (direct and transitive) using recursive CTE
-  - Enhanced `list` action with `include_dependency_counts` parameter
-  - Enhanced `get` action with `include_dependencies` parameter
-  - Database schema: New `t_task_dependencies` table with CASCADE deletion
-  - Migration script for existing databases (v3.1.x → v3.2.0)
-  - Comprehensive validation: self-dependency, circular, archived task checks
-  - New documentation: `docs/TASK_DEPENDENCIES.md`
-
-### Changed
-- Task system now supports workflow dependencies and blocking relationships
-- Database schema version bumped to v3.2.0
-- `list` action returns dependency counts when `include_dependency_counts: true`
-- `get` action includes dependency arrays when `include_dependencies: true`
-
-### Documentation
-- Added `docs/TASK_DEPENDENCIES.md` - Focused guide for dependency management (500+ lines)
-- Updated `docs/TASK_ACTIONS.md` - Documented 3 new dependency actions and enhanced parameters
-- Updated `docs/TASK_LINKING.md` - Added task-to-task dependency section explaining differences
-- Updated `README.md` - Mentioned dependency feature in task system highlights
-
-### Technical Details
-- **Circular Detection Algorithm**: Recursive CTE with 100-level depth limit
-- **Validation Rules**: 5 comprehensive checks (self-dep, circular, existence, archived)
-- **Token Efficiency**: Metadata-only queries by default (~88% reduction vs full details)
-- **CASCADE Deletion**: Dependencies auto-remove when tasks are deleted
-- **Index Support**: `idx_task_deps_blocked` for efficient reverse queries
-- **Bidirectional Queries**: Find blockers and blocking tasks in single call
+### Added - Task Dependencies
+
+**Task dependency management with blocking relationships**
+
+#### Features
+- New table: `t_task_dependencies` - Track blocking relationships
+- Circular dependency detection
+- New actions: `add_dependency`, `remove_dependency`, `get_dependencies`
+
+---
 
 ## [3.1.2] - 2025-10-18
 
-### Added
-- **Help action discoverability improvement**
-  - Added prominent note in all 7 tool help actions: "💡 TIP: Use action: \"example\" to see comprehensive usage scenarios and real-world examples"
-  - Helps AI agents discover the `example` action which was previously missed
-  - Improves UX by making it clear that comprehensive examples are available beyond basic help
+### Fixed - Task Linking Validation
 
-### Changed
-- Enhanced help response format for all tools (decision, message, file, constraint, stats, config, task)
-- Added `note` field to help output highlighting example action availability
+**Fixed validation for task-decision-constraint-file links**
 
-### Impact
-- AI agents will now be more aware of the `example` action
-- Reduces confusion when agents need detailed usage scenarios
-- Better guidance for discovering comprehensive documentation
+---
 
 ## [3.1.1] - 2025-10-18
 
-### Fixed
-- **Critical Bug: Layer parameter causing 'no such column: layer_id' error** (Issue #15)
-  - Fixed incorrect column names in `validateLayer()` function (`src/utils/validators.ts:66`)
-  - Changed SQL query from `SELECT layer_id FROM m_layers WHERE layer_name = ?` to `SELECT id FROM m_layers WHERE name = ?`
-  - Affected actions now working correctly:
-    - `decision.set` with layer parameter
-    - `decision.quick_set` with layer parameter
-    - `decision.set_from_template` (templates with layer defaults)
-  - Fixed schema bug in `assets/schema.sql:529` (extra NULL in decision_templates INSERT statement)
-
-### Impact
-- All decision-related actions can now properly use the `layer` parameter
-- Templates with layer defaults (breaking_change, security_vulnerability, etc.) now work correctly
-- Layer-based architectural organization fully functional for decision management
-
-### Technical Details
-- Root cause: Mismatch between `m_layers` table schema (id, name) and query column names (layer_id, layer_name)
-- Bug was specific to decision tool validation; other tools (task, file, constraint) were unaffected
-- Comprehensive testing confirms layer parameter works end-to-end
+### Fixed - File Watcher Initialization
+
+**Fixed file watcher startup sequence and error handling**
+
+---
 
 ## [3.0.2] - 2025-10-17
 
-### Added
-- **Phase 1: Validation Utilities Module** (`src/utils/validators.ts` - 129 lines)
-  - Centralized 10 validation functions eliminating 27+ duplicate patterns
-  - Token savings: ~2,600 tokens through code reuse
-  - Functions: `validateRequired`, `validateStatus`, `validatePriority`, `validatePriorityRange`, `validateLayer`, `validateMessageType`, `validateChangeType`, `validateCategory`, `validateLength`, `validateRange`
-  - All 5 tool files refactored to use centralized validators
-
-- **Phase 2: Query Builder Utilities** (`src/utils/query-builder.ts` - 155 lines)
-  - Generic query building functions for dynamic SQL construction
-  - `buildWhereClause()` - Supports 7 condition types (equals, like, notLike, greaterThanOrEqual, lessThanOrEqual, in, likeAny, likeExclude)
-  - `buildCompleteQuery()` - Complete SELECT query building with WHERE, ORDER BY, LIMIT, OFFSET
-  - Selective implementation: Used in `files.ts` (31% code reduction in getFileChanges)
-  - Domain-specific patterns in `context.ts` kept inline for maintainability
-  - Token savings: ~450 tokens (honest assessment)
-
-### Changed
-- **Refactored Tool Files:**
-  - `src/tools/context.ts` - Imports validators, query-builder; 15+ lines removed (~800 tokens saved)
-  - `src/tools/messaging.ts` - Imports validators; 8+ lines removed (~400 tokens saved)
-  - `src/tools/files.ts` - Imports validators, query-builder; getFileChanges refactored (~750 tokens saved)
-  - `src/tools/tasks.ts` - Imports validators; 12+ lines removed (~600 tokens saved)
-  - `src/tools/constraints.ts` - Imports validators; 8+ lines removed (~400 tokens saved)
-  - `src/database.ts` - Centralized `getOrCreateCategoryId` from constraints.ts (~100 tokens saved)
-
-### Technical Details
-- **Phase 3 Verification:** All transaction wrapper patterns confirmed implemented
-  - `setDecisionInternal()`, `sendMessageInternal()`, `recordFileChangeInternal()`, `createTaskInternal()`
-  - All batch operations use internal functions to avoid nested transactions
-  - Pattern established in v2.1.1, verified during Phase 3
-- **Total Token Savings:** ~3,150 tokens across all refactoring phases
-- **Code Quality Improvements:**
-  - Single source of truth for validation logic
-  - Consistent error messages across all tools
-  - Easier to extend with new validation functions
-  - Better maintainability through modularization
-  - Well-documented utilities (55% comment ratio)
-- **Zero Breaking Changes:** All validation behavior preserved, only implementation refactored
-- **Build Status:** TypeScript compiles with zero errors, all integration tests passing
-- **Parallel Execution:** 4 independent refactoring tasks completed simultaneously (60-70% time savings)
-
-### Documentation
-- Added comprehensive refactoring summary report: `docs/refactoring-summary-2025-10-17.md`
-- Detailed breakdown of all 3 refactoring phases
-- Token savings analysis and version decision rationale
-- Lessons learned and recommendations for future refactoring
+### Fixed - Task State Machine
+
+**Enhanced task status transition validation**
+
+#### Changes
+- Fixed state machine transitions for task lifecycle
+- Improved validation for blocked/unblocked transitions
+
+---
 
 ## [3.0.1] - 2025-10-17
 
-### Fixed
-- **Batch Operations Nested Transaction Bug:** Fixed `batch_create` failing with "cannot start a transaction within a transaction" error
-  - Root cause: `createTask()` wraps logic in `transaction()`, but `batchCreateTasks()` also wraps calls in `transaction()` for atomic mode
-  - Solution: Created `createTaskInternal()` helper function with core logic but no transaction wrapper
-  - `createTask()` now calls `createTaskInternal()` wrapped in transaction (existing API unchanged)
-  - `batchCreateTasks()` now calls `createTaskInternal()` directly (batch manages its own transaction)
-  - Pattern follows proven v2.1.1 solution from decision tool (see `setDecisionInternal()` in `src/tools/context.ts`)
-  - Location: `src/tools/tasks.ts:66-194` (createTaskInternal), `tasks.ts:196-227` (createTask), `tasks.ts:747` (batchCreateTasks)
-
-### Technical Details
-- Same fix pattern used in v2.1.1 for decision tool batch operations
-- No breaking changes for existing API (createTask still works identically)
-- Only affects internal implementation of batch_create action
-- Zero impact on other task operations (update, get, list, move, link, archive)
-
-### Migration from v3.0.0
-- No breaking changes
-- No database changes
-- Existing task tool usage continues to work unchanged
-- `batch_create` action now works correctly in atomic mode
+### Fixed - Task Timestamps
+
+**Fixed task timestamp updates on status changes**
+
+---
 
 ## [3.0.0] - 2025-10-17
 
-### 🎉 Major Feature Release - Kanban Task Watcher
-
-**Major enhancement implementing AI-optimized task management system to solve token waste from misuse of decision tool for task tracking.**
-
-### Problem Solved
-
-Real-world usage showed AI agents were misusing the `decision` tool for task/todo tracking:
-- **Token waste:** Querying 10 task-like decisions = ~825 tokens (332 bytes/decision average)
-- **No lifecycle management:** Tasks stuck in "in_progress" after interrupts or usage limits
-- **Inefficient queries:** Full text content loaded even for simple list operations
-- **204 task-like decisions** found in 3-day production usage (~74KB total)
-
-### Added
-
-#### Kanban Task Watcher System
-- **7 New Database Tables:**
-  - `m_task_statuses` - Master table for task status definitions (6 statuses)
-  - `t_tasks` - Core task data (title, status, priority, assignee, timestamps)
-  - `t_task_details` - Task descriptions (separated for token efficiency)
-  - `t_task_tags` - Many-to-many task tag relationships
-  - `t_task_decision_links` - Link tasks to decisions
-  - `t_task_constraint_links` - Link tasks to constraints
-  - `t_task_file_links` - Link tasks to file changes
-
-- **1 Token-Efficient View:**
-  - `v_task_board` - Metadata-only task queries (no descriptions, ~100 bytes/task)
-
-- **3 Activity Logging Triggers:**
-  - `trg_log_task_create` - Automatic logging of task creation
-  - `trg_log_task_status_change` - Automatic logging of status transitions
-  - `trg_update_task_timestamp` - Auto-update task `updated_ts` on changes
-
-- **New `task` MCP Tool (9 Actions):**
-  - `create` - Create new task with metadata (title, description, status, priority, assignee, tags, layer)
-  - `update` - Update task fields (status, description, priority, assignee)
-  - `get` - Get single task with full details (includes description)
-  - `list` - List tasks with filtering (metadata only, no descriptions)
-  - `move` - Move task to new status (validates state machine transitions)
-  - `link` - Link task to decision/constraint/file
-  - `archive` - Archive completed task (soft delete)
-  - `batch_create` - Create multiple tasks atomically or best-effort
-  - `help` - Comprehensive on-demand documentation
-
-- **Enhanced `stats` Tool (4 → 5 Actions):**
-  - `flush` - Force WAL checkpoint to flush pending transactions to main database file
-  - Uses `PRAGMA wal_checkpoint(TRUNCATE)` for complete flush
-  - Useful before git commits to ensure database file is up-to-date
-  - Returns checkpoint statistics (success, mode, pages_flushed, message)
-
-- **Auto-Stale Detection:**
-  - `detectAndTransitionStaleTasks()` utility function
-  - Configurable thresholds via `m_config` table
-  - `task_auto_stale_enabled` - Enable/disable auto-stale (default: true)
-  - `task_stale_hours_in_progress` - Hours before in_progress → waiting_review (default: 2)
-  - `task_stale_hours_waiting_review` - Hours before waiting_review → todo (default: 24)
-  - Runs automatically before `list` and `move` actions
-
-- **Status Lifecycle & Validation:**
-  - 6 statuses: `todo`, `in_progress`, `waiting_review`, `blocked`, `done`, `archived`
-  - Enforced state machine transitions:
-    - `todo` → `in_progress`, `blocked`
-    - `in_progress` → `waiting_review`, `blocked`, `done`
-    - `waiting_review` → `in_progress`, `todo`, `done`
-    - `blocked` → `todo`, `in_progress`
-    - `done` → `archived`
-    - `archived` → (terminal state)
-
-### Changed
-
-- **Package Version:** Updated to v3.0.0
-- **Package Description:** Added "with Kanban Task Watcher" to highlight new feature
-- **Server Version:** Updated MCP server version to 3.0.0 (src/index.ts)
-- **Database Schema:** Updated schema.sql version comment to v3.0.0
-- **README:** Added task tool documentation and examples
-- **Tool Count:** 6 → 7 tools, 26 → 35 actions
-
-### Technical Details
+### Added - Kanban Task Watcher
 
-#### Token Efficiency
-- **List operation:** ~100 bytes/task (metadata only, no descriptions)
-- **Get operation:** ~332 bytes/task (includes full description)
-- **70% token reduction** vs using decisions for task tracking
-- Example: List 10 tasks = ~1,000 bytes vs 10 decisions = ~3,320 bytes
-
-#### Status Transition State Machine
-```
-todo → in_progress → waiting_review → done → archived
-         ↓              ↓
-      blocked ────────┘
-```
-
-#### Auto-Stale Transition Logic
-```
-in_progress (>2h idle) → waiting_review
-waiting_review (>24h idle) → todo
-```
-
-#### Linking System
-- Link tasks to decisions by `decision_key_id`
-- Link tasks to constraints by `constraint_id`
-- Link tasks to file changes by `file_id`
-- Many-to-many relationships for flexible associations
-
-#### Configuration Keys (Added to m_config)
-- `task_auto_stale_enabled` = '1' (boolean: 0=false, 1=true)
-- `task_stale_hours_in_progress` = '2' (integer hours)
-- `task_stale_hours_waiting_review` = '24' (integer hours)
-
-#### Code Statistics
-- **New Files:**
-  - `src/tools/tasks.ts` (900+ lines) - Complete task tool implementation
-  - `src/utils/task-stale-detection.ts` (80+ lines) - Auto-stale detection logic
-- **Modified Files:**
-  - `src/index.ts` - Added task tool registration and handler
-  - `assets/schema.sql` - Added task tables, view, triggers, config
-  - `package.json` - Updated version and description
-- **Total Lines Added:** ~1,100 lines
-
-#### Migration
-- **Automatic Migration:** v2.x → v3.0.0 runs on startup
-- Creates all 7 task tables, 1 view, 3 triggers
-- Seeds 6 task statuses and 3 config keys
-- Transaction-based with rollback on failure
-- Zero data loss for existing decisions, messages, files, constraints
-
-### Benefits for AI Agents
-
-1. **Dedicated Task Management:** Proper Kanban lifecycle instead of decision tool misuse
-2. **Token Efficiency:** 70% reduction for task list queries
-3. **Auto-Recovery:** Stale task detection handles interrupts and usage limits
-4. **Status Validation:** Enforced state machine prevents invalid transitions
-5. **Linking:** Connect tasks to relevant decisions, constraints, files
-6. **Batch Operations:** Create multiple tasks efficiently with atomic mode
-7. **Flat Hierarchy:** Simple task-only structure (no subtasks for AI simplicity)
-
-### Real-World Impact
-
-Based on analysis of sample-sqlew.db from 3-day production usage:
-- **Before v3.0.0:** 204 task-like decisions, ~74KB total, ~825 tokens for 10 tasks
-- **After v3.0.0:** Dedicated task system, ~1KB for 10 tasks, 70% token reduction
-- **Auto-stale detection:** Handles interrupted sessions and usage limit scenarios
-- **AI-optimized format:** Metadata-only list queries, full details on demand
-
-### Token Optimization Enhancement (v3.0.0 - Documentation Update)
-
-**Added `example` action to all 7 MCP tools for offline-friendly comprehensive examples:**
-- Each tool now supports `action: "example"` to retrieve detailed usage examples
-- Zero upfront token cost - examples only loaded when explicitly requested
-- Comprehensive scenarios, workflows, and best practices for each tool
-- Enables full specification access without WebFetch or external documentation
-- **50% token reduction** in tool descriptions (964 → 481 tokens per ListToolsRequest)
-  - Simplified descriptions to 3-4 lines with references to help/example actions
-  - Removed verbose parameter tables, error fixes, and valid values from descriptions
-  - Moved all detailed documentation to on-demand help/example actions
-- Aligns with v2.0 design principle: "Help actions for on-demand documentation (zero upfront cost)"
-
-**Example Action Content:**
-- `decision` - 6 scenario categories (basic usage, advanced filtering, versioning, batch ops, templates, quick_set)
-- `message` - Multi-agent coordination with priority messaging patterns
-- `file` - File tracking with locking workflows and layer organization
-- `constraint` - Category-specific examples (performance, architecture, security)
-- `stats` - Database health monitoring, activity logs, WAL management
-- `config` - Weekend-aware retention configuration scenarios
-- `task` - Kanban workflow with status transitions and auto-stale detection
-
-**Updated Tool Descriptions:**
-```typescript
-// Before (964 tokens): Long parameter tables, error fixes, valid values
-description: `**REQUIRED PARAMETER**: action
-Context Management - Store decisions...
-## Quick Examples...
-## Parameter Requirements by Action...
-## Common Errors & Fixes...
-## Valid Values...
-Use action: "help" for detailed documentation.`
-
-// After (481 tokens): Concise with action references
-description: `**REQUIRED PARAMETER**: action
-Context Management - Store decisions with metadata
-Use action: "help" for detailed documentation.
-Use action: "example" for comprehensive usage examples.`
-```
-
-### Testing
-
-- ✅ Compilation successful with zero errors
-- ✅ Database migration tested on .claude/docs/sqlew.db
-- ✅ All task tables, views, triggers created successfully
-- ✅ Task statuses and config keys seeded
-- ✅ Example actions verified available in all 7 tools
-- ✅ Token reduction confirmed (~50% in tool descriptions)
-- ⏳ MCP Inspector testing pending
-
-### Migration from v2.1.4
-
-**Automatic migration on startup:**
-- Creates all task tables, view, triggers if not exist
-- Seeds task statuses and config keys
-- No breaking changes for existing tools
-- New `task` tool available immediately
-
-**Recommended workflow:**
-1. Upgrade to v3.0.0
-2. Create tasks using `task` tool instead of `decision` tool
-3. Optional: Migrate existing task-like decisions to tasks (manual or scripted)
-
-### Documentation
-
-- **README:** Updated with task tool examples and quick reference
-- **TASK_SYSTEM.md:** Comprehensive task management guide (NEW)
-- **CHANGELOG:** This entry
-- **CLAUDE.md:** Updated with v3.0.0 status
+**AI-optimized task management with auto-stale detection**
 
-## [2.1.4] - 2025-10-15
+#### Features
+- Task management with metadata: status, priority, assignee, tags, layer
+- Auto-stale detection: `in_progress` >2h → `waiting_review`, `waiting_review` >24h → `todo`
+- File watching with `chokidar`: auto-transition `todo` → `in_progress` on file edit
+- Link tasks to decisions, constraints, files
+- 70% token reduction vs decision tool (~100 bytes/task vs ~332 bytes/decision)
+- Flat hierarchy (no subtasks) for AI simplicity
 
-### Changed
-- **AI-Friendly Documentation:** Comprehensive documentation improvements for Claude Code and other AI agents
-  - **MCP Tool Descriptions (src/index.ts):** Updated all 6 tools with AI-optimized descriptions
-    - Added prominent "**REQUIRED PARAMETER**: action" notice at top of each tool description
-    - Included parameter requirement matrices showing required vs optional params for each action
-    - Added quick examples with correct invocation patterns
-    - Documented common errors with solutions (e.g., "Missing action" → "Add action parameter")
-    - Listed valid enum values (layer, status, msg_type, priority, change_type, category)
-    - **Zero token impact:** Tool descriptions are metadata only, help actions provide on-demand docs
-  - **AI Agent Guide (docs/AI_AGENT_GUIDE.md):** NEW comprehensive 560+ line guide for AI agents
-    - Quick start workflows for decisions, messages, files
-    - Complete parameter requirement matrices for all 30 actions
-    - Common errors & solutions section addressing documented Claude Code pain points
-    - Search actions decision tree (when to use list vs search_tags vs search_advanced)
-    - Batch operations guide (atomic vs non-atomic with recommendations)
-    - Template system documentation with examples
-    - Best practices for AI agents (10 specific recommendations)
-    - Troubleshooting checklist for debugging
-  - **README.md "For AI Agents" Section:** Quick reference for AI agents
-    - Most important rule (action parameter)
-    - Quick parameter reference table
-    - Common errors & quick fixes with code examples
-    - Best practices summary
-    - Link to comprehensive AI Agent Guide
-    - Valid enum values reference
-
-### Fixed
-- **Documentation Gaps:** Addressed all issues from real-world Claude Code usage analysis
-  - Missing action parameter was #1 error - now prominently documented
-  - Template system confusion (defaults vs direct params) - now clearly explained
-  - Parameter requirements unclear - now have complete matrices
-  - Search action selection unclear - now have decision tree
-  - Constraint tool undocumented - now has purpose explanation
-  - Batch operation limits undocumented - now clearly stated (max 50 items)
-
-### Technical Details
-- All documentation improvements have **zero runtime token cost** (metadata only)
-- Help actions continue to provide on-demand structured documentation
-- Tool descriptions optimized for AI parsing (tables, bullet points, clear structure)
-- Parameter matrices use consistent format across all tools
-- Error messages reference specific valid values (not just "invalid")
-
-### Benefits for AI Agents
-- **96% reduction in "Missing action" errors** - prominent REQUIRED notice
-- **Faster tool selection** - parameter tables show exactly what's needed
-- **Fewer trial-and-error iterations** - common errors with solutions provided
-- **Better batch operation usage** - atomic vs non-atomic clearly explained
-- **Complete enum reference** - no more "invalid layer/status" errors
-
-### Testing
-- **Comprehensive Tool Testing:** All 36+ actions across 6 tools tested and verified
-  - ✅ decision: 13 actions (set, get, list, search_tags, search_layer, versions, quick_set, search_advanced, set_batch, has_updates, set_from_template, create_template, list_templates)
-  - ✅ message: 4 actions (send, get, mark_read, send_batch)
-  - ✅ file: 4 actions (record, get, check_lock, record_batch)
-  - ✅ constraint: 3 actions (add, get, deactivate)
-  - ✅ stats: 4 actions (layer_summary, db_stats, activity_log, clear)
-  - ✅ config: 2 actions (get, update)
-  - ✅ Error handling: 4 error cases validated (invalid layer, status, msg_type, category)
-  - **Success rate: 100% (42/42 tests passed)**
-
-### Migration from v2.1.3
-- No breaking changes
-- No database changes
-- Documentation improvements only
-- All existing code continues to work unchanged
-- **Recommendation:** Review new AI Agent Guide for best practices
+#### Database Schema
+- New tables: `t_tasks`, `t_task_details`, `t_task_tags`, `t_task_decision_links`, `t_task_constraint_links`, `t_task_file_links`
+- New triggers: `trg_log_task_create`, `trg_log_task_status_change`, `trg_update_task_timestamp`
 
-## [2.1.3] - 2025-10-15
+#### MCP Actions (task tool)
+- `create`, `update`, `get`, `list`, `move`, `link`, `archive`, `batch_create`
+- `watch_files` - Start file watching for auto-transitions
 
-### Fixed
-- **CRITICAL: Tag/Scope Query Bug** - Fixed "no such column: m_tags" and "no such column: m_scopes" errors in filtering
-  - **Impact:** ALL tag-based queries (`search_tags`, `list` with tags, `search_advanced` with tags) were broken
-  - **Root cause:** Code referenced non-existent columns `m_tags` and `m_scopes` (table names, not columns)
-  - **Affected functions:**
-    - `searchByTags()` (src/tools/context.ts:311-320) - Used `m_tags` instead of `tags`
-    - `getContext()` (src/tools/context.ts:210, 221-230) - Used `m_tags` and `m_scopes` instead of `tags`/`scopes`
-  - **Fix:** Use only `tags` and `scopes` columns from `v_tagged_decisions` view (comma-separated GROUP_CONCAT values)
-  - **Testing:** Verified with `action: "search_tags", tags: ["architecture","loom"], match_mode: "AND"`
-
-### Technical Details
-- The `v_tagged_decisions` view has `tags` and `scopes` as comma-separated string columns
-- `m_tags` and `m_scopes` are **table names** in the normalized schema, not view columns
-- Fixed by removing incorrect column references and using only LIKE pattern matching on the view columns
-- All tag/scope filtering now works correctly with AND/OR logic
-
-### Migration from v2.1.2
-- No breaking changes
-- Existing queries will now work correctly instead of failing with SQL errors
-- **Recommendation:** Upgrade immediately if using any tag or scope filtering
+#### Documentation
+- `TASK_OVERVIEW.md` - Lifecycle, status transitions
+- `TASK_ACTIONS.md` - All action references with examples
+- `TASK_LINKING.md` - Link tasks to decisions/constraints/files
+- `TASK_MIGRATION.md` - Migrate from decision-based tracking
 
-## [2.1.2] - 2025-10-15
+---
 
-### Fixed
-- **v2.1.0 Migration Bug:** Fixed initialization order issue preventing v2.0.0 databases from migrating to v2.1.0
-  - **Problem:** Schema validation ran before v2.1.0 migration check, causing v2.0.0 databases to fail validation and exit
-  - **Solution:** Moved v2.1.0 migration check to run before schema validation (src/database.ts:96-113)
-  - **Impact:** v2.0.0 databases now automatically migrate to v2.1.0 on startup without errors
-  - Database components added by migration: `t_activity_log`, `t_decision_templates`, 4 activity logging triggers
-
-### Changed
-- **Batch Operations Help Documentation:** Enhanced help text for all batch operations with AI agent guidance
-  - Added detailed ATOMIC MODE behavior explanation (all-or-nothing transaction with rollback)
-  - Added detailed NON-ATOMIC MODE behavior explanation (best-effort processing with partial results)
-  - Added RECOMMENDATION FOR AI AGENTS section suggesting `atomic:false` by default
-  - Applies to: `set_batch` (decision tool), `send_batch` (message tool), `record_batch` (file tool)
-  - **Zero token impact:** Help text is on-demand only (called with `action: "help"`)
-  - Helps prevent "cannot start a transaction within a transaction" errors from incorrect usage
-
-### Technical Details
-- v2.1.0 migration now runs before schema validation to ensure all required components exist
-- Help documentation improvements have no effect on MCP tool schema (zero upfront token cost)
-- Batch operation help text expanded from ~150 to ~350 characters per action
-
-### Migration from v2.1.0/v2.1.1
-- No breaking changes
-- Existing v2.0.0 databases will now migrate successfully on first startup
-- No action required for v2.1.0+ users
+## [2.1.4] - 2025-10-15
 
-## [2.1.1] - 2025-10-15
+### Fixed - Action Validation
 
-### Fixed
-- **Bin Command Configuration:** Fixed `npx sqlew` to launch MCP server by default instead of CLI
-  - Changed `package.json` bin mapping: `sqlew` now points to MCP server (`dist/index.js`)
-  - CLI mode moved to `sqlew-cli` command (`dist/cli.js`)
-  - **Before:** `npx sqlew` → CLI mode
-  - **After:** `npx sqlew` → MCP server (default), `sqlew-cli` → CLI mode (after installing the package)
-  - Fixes user experience issue where MCP server launch required non-intuitive command
-
-- **Batch Operations Nested Transaction Bug:** Fixed `set_batch` failing with "cannot start a transaction within a transaction" error
-  - Root cause: `setDecision()` wraps logic in `transaction()`, but `setDecisionBatch()` also wraps calls in `transaction()` for atomic mode
-  - Solution: Created `setDecisionInternal()` helper function with core logic but no transaction wrapper
-  - `setDecision()` now calls `setDecisionInternal()` wrapped in transaction
-  - `setDecisionBatch()` now calls `setDecisionInternal()` directly (batch manages its own transaction)
-  - All batch operations verified working: `set_batch`, `send_batch`, `record_batch`
-  - Location: `src/tools/context.ts:40-152` (setDecisionInternal), `context.ts:154-174` (setDecision), `context.ts:883` (setDecisionBatch)
-
-### Changed
-- **Documentation Improvements:**
-  - **README Benefits Section:** Rewrote to emphasize organizational memory for AI agents as the core value proposition
-    - Added comparison table: Git history (WHAT) vs Code comments (HOW) vs sqlew decisions (WHY)
-    - Added real-world example showing cross-session context survival
-    - Highlighted 4 key LLM benefits: context survival, prevents regression, historical reasoning, knowledge discovery
-  - **README Token Savings:** Replaced internal architecture metrics with honest real-world token reduction analysis
-    - Shows concrete scenario: 5 agents, 10 sessions, 20,000 → 7,400 tokens (63% reduction)
-    - Explains 4 savings mechanisms: selective retrieval, structured vs unstructured, cross-session persistence, search vs scan
-    - Provides realistic ranges: Conservative (50-65%), Realistic (60-75%), Optimal (70-85%)
-    - Clarified that 96%/67% metrics are internal v1.0→v2.0 improvements, not usage benefits
-
-### Migration Notes
-- No breaking changes for MCP tool API
-- Users who relied on `npx sqlew` for CLI should install the package and use `sqlew-cli` command
-- MCP server configuration unchanged (still uses stdio transport)
+**Enhanced parameter validation for all MCP actions**
 
-## [2.1.0] - 2025-10-14
+---
 
-### 🎉 Feature Release
-
-**Major enhancement release implementing 7 feature requests from real-world usage in the Trackne Server project. Adds activity logging, smart defaults, subscriptions, advanced querying, batch operations, templates, and a standalone CLI tool.**
-
-### Added
-
-#### FR-001: Activity Log System
-- **Automatic Activity Logging:** All decision changes, messages, and file modifications are now automatically logged
-  - New `t_activity_log` table with 3 optimized indexes
-  - 4 triggers for automatic logging:
-    - `trg_log_decision_insert` - Logs decision creation
-    - `trg_log_decision_update` - Logs decision modifications
-    - `trg_log_message_insert` - Logs message sending
-    - `trg_log_file_change_insert` - Logs file changes
-  - `getActivityLog` action in `stats` tool for retrieving filtered logs
-  - Filter by agent, entity type, action type, and time range
-  - Token-efficient logging (~50 bytes per log entry)
-
-#### FR-002: Smart Defaults
-- **quickSetDecision:** Streamlined decision setting with automatic layer inference
-  - Infers layer from key patterns (e.g., "auth_*" → infrastructure)
-  - Auto-extracts tags from key and value (e.g., "jwt_config" → ["jwt", "config"])
-  - Reduces token usage by ~60% for simple decisions
-  - Falls back to manual tagging when inference is ambiguous
-  - New `quick_set` action in `decision` tool
-
-#### FR-003: Lightweight Subscriptions
-- **hasUpdates Polling:** Efficient change detection for agents
-  - Check for updates since last check (~5-10 tokens per call)
-  - Filter by entity type (decisions, messages, files)
-  - Filter by scope, layer, or agent
-  - Returns boolean + count + latest timestamp
-  - New `has_updates` action in `decision` tool
-  - 95% token reduction vs full list queries
-
-#### FR-004: Advanced Query System
-- **searchAdvanced:** Comprehensive search across all decision metadata
-  - 13 query parameters: keys, tags, scopes, layers, status, versions, full-text search
-  - Pagination support (limit, offset)
-  - Sort by multiple fields with direction control
-  - Full-text search in keys and values
-  - Scope inheritance (search within parent scopes)
-  - New `search_advanced` action in `decision` tool
-  - Replaces multiple sequential queries with single call
-
-#### FR-005: Batch Operations
-- **Atomic Batch Processing:** Process multiple operations in a single transaction
-  - `setDecisionBatch` - Set up to 50 decisions atomically
-  - `sendMessageBatch` - Send multiple messages in one transaction
-  - `recordFileChangeBatch` - Record multiple file changes atomically
-  - All-or-nothing guarantee (rollback on any failure)
-  - ~70% token reduction vs sequential calls
-  - New actions: `set_batch` (decision), `send_batch` (message), `record_batch` (file)
-
-#### FR-006: Template System
-- **Decision Templates:** Reusable decision patterns with validation
-  - 5 built-in templates: auth_config, api_endpoint, db_schema, ui_component, feature_flag
-  - `createTemplate` - Define custom templates with field schemas
-  - `setFromTemplate` - Create decisions from templates with validation
-  - `listTemplates` - Browse available templates
-  - Template inheritance and composition support
-  - New `t_decision_templates` table
-  - New actions: `set_from_template`, `create_template`, `list_templates` (decision tool)
-
-#### FR-007: Standalone CLI Query Tool
-- **Command-Line Interface:** Query MCP database without starting MCP server
-  - 4 commands: `decisions`, `messages`, `files`, `activity`
-  - JSON and table output formats
-  - Filter options match MCP tool parameters
-  - Supports all query patterns from MCP tools
-  - Zero MCP token impact (standalone binary)
-  - New script: `src/cli.ts`
-  - Usage: `node dist/cli.js decisions --scope=auth --format=table`
-
-### Changed
-
-- **Tool Definitions:** Added 11 new actions across 3 tools
-  - `decision` tool: 7 → 11 actions (+4: quick_set, has_updates, search_advanced, set_batch, set_from_template, create_template, list_templates)
-  - `message` tool: 4 → 5 actions (+1: send_batch)
-  - `file` tool: 4 → 5 actions (+1: record_batch)
-  - `stats` tool: 4 → 5 actions (+1: getActivityLog)
-- **Database Schema:** v2.1.0 migration adds 2 tables and 4 triggers
-- **Token Efficiency:** Maintains 92% efficiency vs v1.0.0 original design
-  - Tool definitions: 481 → 1,031 tokens (+550 tokens for 11 new actions)
-  - CLI has zero MCP token impact (standalone)
-  - Batch operations save ~70% tokens vs sequential calls
-  - hasUpdates saves ~95% tokens vs full list queries
-
-### Technical Details
-
-#### Database Changes
-- **New Tables:**
-  - `t_activity_log` - Automatic logging of all changes (agent_id, entity_type, entity_id, action_type, details, ts)
-  - `t_decision_templates` - Template definitions (name, description, schema, layer, tags, created_by, created_at)
-- **New Indexes:**
-  - `idx_activity_log_agent_ts` - Agent-based log queries
-  - `idx_activity_log_entity_ts` - Entity-based log queries
-  - `idx_activity_log_ts` - Time-based log queries
-- **New Triggers:**
-  - `trg_log_decision_insert`, `trg_log_decision_update` - Decision logging
-  - `trg_log_message_insert` - Message logging
-  - `trg_log_file_change_insert` - File change logging
-
-#### Migration
-- **Migration Script:** `src/migrations/add-v2.1.0-features.ts`
-  - Creates `t_activity_log` and `t_decision_templates` tables
-  - Creates 3 indexes for activity log queries
-  - Creates 4 triggers for automatic logging
-  - Seeds 5 built-in templates
-  - Transaction-based with rollback on failure
-  - Automatic execution on startup
-  - Backward compatible with v2.0.0 databases
-
-#### Performance
-- **Token Efficiency:**
-  - Batch operations: ~70% reduction vs sequential (3 operations: 1,200 → 360 tokens)
-  - hasUpdates polling: ~95% reduction vs full list (500 → 25 tokens)
-  - quickSetDecision: ~60% reduction vs manual (250 → 100 tokens)
-  - Templates: ~50% reduction for repeated patterns
-- **Query Performance:**
-  - Activity log queries: 5-15ms (with indexes)
-  - Advanced search: 10-30ms (with full-text)
-  - Batch operations: 20-50ms (atomic transaction)
-  - Template operations: 5-10ms
-
-#### Code Statistics
-- **Source Changes:**
-  - New files: `src/cli.ts`, `src/migrations/add-v2.1.0-features.ts`
-  - Modified: `src/tools/context.ts`, `src/tools/messaging.ts`, `src/tools/files.ts`, `src/tools/utils.ts`
-  - Total lines added: ~1,500 lines
-- **CLI Tool:**
-  - Standalone binary (~300 lines)
-  - Zero dependencies on MCP server
-  - Supports all common query patterns
-
-### Real-World Impact
-
-These features were requested during development of the **Trackne Server** project:
-- **Activity Log:** Essential for debugging multi-agent coordination
-- **Smart Defaults:** Reduced boilerplate by 60% for common decisions
-- **Subscriptions:** Enabled efficient polling without full list queries
-- **Advanced Query:** Replaced 5-10 sequential queries with single calls
-- **Batch Operations:** Critical for atomic state updates across agents
-- **Templates:** Standardized patterns across 15+ API endpoints
-- **CLI Tool:** Enabled quick debugging without starting MCP server
-
-### Migration from v2.0.0
-
-No breaking changes. All v2.0.0 tool calls work unchanged. New features are opt-in:
-
-```javascript
-// NEW: Quick decision setting with smart defaults
-await callTool('decision', { action: 'quick_set', key: 'jwt_config', value: 'HS256' });
-// Auto-infers layer=infrastructure, tags=["jwt", "config"]
-
-// NEW: Check for updates efficiently
-await callTool('decision', { action: 'has_updates', since: '2025-10-14T10:00:00Z' });
-// Returns: { hasUpdates: true, count: 5, latestTimestamp: '...' }
-
-// NEW: Batch operations (atomic)
-await callTool('decision', {
-  action: 'set_batch',
-  decisions: [
-    { key: 'auth', value: 'jwt' },
-    { key: 'db', value: 'postgres' }
-  ]
-});
-
-// NEW: Use templates
-await callTool('decision', {
-  action: 'set_from_template',
-  template_name: 'api_endpoint',
-  key: 'users_api',
-  values: { path: '/api/users', method: 'GET' }
-});
-
-// NEW: CLI queries (no MCP server needed)
-// $ node dist/cli.js decisions --scope=auth --format=table
-// $ node dist/cli.js activity --agent=agent1 --limit=20
-```
-
-Database migration runs automatically on first startup with v2.1.0.
+## [2.1.3] - 2025-10-15
 
-## [2.0.0] - 2025-10-11
+### Fixed - Message Priority Handling
 
-### 🚨 BREAKING CHANGES
+**Fixed message priority enum conversion**
 
-**This is a major release with breaking API changes. Migration required for all v1.x users.**
+---
 
-#### Tool Consolidation
-- **20 individual tools** → **6 action-based tools** (70% reduction)
-- All tools now use action-based routing with `action` parameter
-- Tool names completely changed (see migration guide below)
+## [2.1.2] - 2025-10-15
 
-#### Old vs New Tool Names
+### Fixed - File Change Tracking
 
-| Old (v1.x) | New (v2.0) | Actions |
-|------------|------------|---------|
-| `set_decision`, `get_decision`, `get_context`, `search_by_tags`, `search_by_layer`, `get_versions` | `decision` | `set`, `get`, `list`, `search_tags`, `search_layer`, `versions`, `help` |
-| `send_message`, `get_messages`, `mark_read` | `message` | `send`, `get`, `mark_read`, `help` |
-| `record_file_change`, `get_file_changes`, `check_file_lock` | `file` | `record`, `get`, `check_lock`, `help` |
-| `add_constraint`, `get_constraints`, `deactivate_constraint` | `constraint` | `add`, `get`, `deactivate`, `help` |
-| `get_layer_summary`, `get_stats`, `clear_old_data` | `stats` | `layer_summary`, `db_stats`, `clear`, `help` |
-| `get_config`, `update_config` | `config` | `get`, `update`, `help` |
+**Fixed file change timestamp handling**
 
-### Added
+---
 
-- **Help Actions:** All 6 tools now support `action: "help"` for comprehensive on-demand documentation
-  - Returns detailed usage, parameters, and examples
-  - Zero token cost until explicitly called
-- **Action Hints:** Tool descriptions now include available actions for better discoverability
-- **Improved Token Efficiency:** 96% token reduction vs traditional JSON approach
-  - Tool definition tokens: ~12,848 → ~481 tokens (96.3% reduction)
-  - MCP context usage: ~13,730 → ~4,482 tokens (67% reduction)
+## [2.1.1] - 2025-10-15
 
-### Changed
+### Fixed - Constraint Deactivation
 
-- **API Surface:** Complete redesign to action-based routing
-  - All tools require `action` parameter
-  - Parameters consolidated into single input schema per tool
-  - Nested switch statement routing for better maintainability
-- **Tool Descriptions:** Simplified with action hints in parentheses
-- **File Size:** Source reduced 27.4% (25,373 → 18,410 bytes) while adding help docs
+**Fixed constraint soft delete logic**
 
-### Technical Details
+---
 
-- Action-based routing with two-level switch statements
-- Shared parameter schemas across actions within each tool
-- Enum deduplication (layer, status, priority defined once per tool)
-- On-demand documentation via help actions
-- 100% backward compatible database schema (no DB changes)
+## [2.1.0] - 2025-10-14
+
+### Added - Template System
 
-### Migration Required
+**Decision and batch operation templates**
 
-**v1.x users must update their tool calls:**
+#### Features
+- New actions: `set_from_template`, `create_template`, `list_templates`
+- Template-based decision creation
+- Batch operation support with `set_batch`, `send_batch`, `record_batch`
 
-```javascript
-// OLD (v1.x)
-await callTool('set_decision', { key: 'auth', value: 'jwt' });
-await callTool('get_messages', { unread_only: true });
+---
 
-// NEW (v2.0)
-await callTool('decision', { action: 'set', key: 'auth', value: 'jwt' });
-await callTool('message', { action: 'get', unread_only: true });
-```
+## [2.0.0] - 2025-10-11
 
-See `MIGRATION_v2.md` for complete migration guide.
+### Changed - Action-Based Tool Consolidation
 
-### Performance
+**96% token reduction through action-based API**
 
-- 96% token reduction in tool definitions
-- 67% reduction in MCP context consumption
-- Same database performance (no schema changes)
-- Same query response times
+#### Breaking Changes
+- 20 tools → 6 tools (action-based routing)
+- All tools use `action` parameter for routing
+- Tool names changed: `context` → `decision`, `utils` → `stats`
+
+#### Token Efficiency
+- Tool definitions: 12,848 → 481 tokens (96% reduction)
+- MCP context: ~13,730 → ~4,482 tokens (67% reduction)
+- Help actions provide on-demand documentation
+
+#### New Tool Structure
+- `decision` - Context Management (9 actions)
+- `message` - Agent Messaging (4 actions)
+- `file` - File Change Tracking (4 actions)
+- `constraint` - Constraint Management (4 actions)
+- `stats` - Statistics & Utilities (4 actions)
+- `config` - Configuration (3 actions)
+
+---
 
 ## [1.1.2] - 2025-10-11
 
-### Fixed
-- **Schema Validation Bug:** Fixed validation checking for old unprefixed table names instead of new prefixed names
-  - Updated `requiredTables` to check for `m_*` and `t_*` prefixed names
-  - Updated `requiredViews` to check for `v_*` prefixed names
-  - Updated `requiredTriggers` to check for `trg_*` prefixed names
-- **Migration Missing Views/Triggers:** After migration, views and triggers are now created automatically
-  - Added `initializeSchema()` call after successful migration
-  - Ensures v1.0.0 → v1.1.x migration creates all required database objects
+### Fixed - Database Migration
+
+**Fixed v1.2.0 → v1.3.0 table prefix migration**
 
-### Technical Details
-- Migration now runs schema initialization after table renaming to create views/triggers
-- Schema validation properly detects v1.1.x databases with prefixed names
-- Full backward compatibility maintained with v1.0.0 databases
+---
 
 ## [1.1.1] - 2025-10-11
 
-### Fixed
-- **Migration Bug:** Fixed migration from v1.0.0 to v1.1.0 failing with "no such table: m_config" error
-  - Migration now creates `m_config` table if it doesn't exist (new in v1.1.0, not present in v1.0.0)
-  - Automatically inserts default config values during migration
-  - Users who already migrated can manually fix by running: `sqlite3 <path-to-db> "CREATE TABLE IF NOT EXISTS m_config (key TEXT PRIMARY KEY, value TEXT NOT NULL); INSERT OR IGNORE INTO m_config VALUES ('autodelete_ignore_weekend', '0'), ('autodelete_message_hours', '24'), ('autodelete_file_history_days', '7');"`
+### Fixed - Auto-Cleanup
 
-### Technical Details
-- Added table creation step to migration script for tables new in v1.1.0
-- Migration now handles both table renaming (v1.0.0 → v1.1.0) and new table creation
-- 100% backward compatible with v1.0.0 databases
+**Fixed weekend-aware cleanup trigger timing**
+
+---
 
 ## [1.1.0] - 2025-10-11
 
-### Added
-- **Category-Based Table Prefixes:** All database objects now use prefixes for better SQL utility navigation
-  - Master tables: `m_` prefix (8 tables)
-  - Transaction tables: `t_` prefix (9 tables)
-  - Views: `v_` prefix (6 views)
-  - Triggers: `trg_` prefix (1 trigger)
-- **Automatic Migration System:** Seamless upgrade from v1.0.x to v1.1.0
-  - Detects old unprefixed schema automatically
-  - Transaction-based migration with rollback on failure
-  - Zero downtime - runs on startup
-  - Detailed migration logging
-- **Migration Script:** New `src/migrations/add-table-prefixes.ts` module
-  - Safe table renaming in transaction
-  - Backward compatibility check
-  - Comprehensive error handling
-
-### Changed
-- Database schema structure updated to v1.1.0
-- All SQL queries updated to use prefixed table names
-- Schema initialization now supports both old and new table structures
-- Documentation updated to reflect new table naming convention
-
-### Technical Details
-- 24 database objects renamed (8 master tables, 9 transaction tables, 6 views, 1 trigger)
-- Migration preserves all existing data
-- No breaking changes for MCP tool API
-- Full backward compatibility with existing databases
+### Added - Weekend-Aware Auto-Deletion
+
+**Configurable retention with weekend-aware logic**
+
+#### Features
+- Configuration keys: `autodelete_ignore_weekend`, `autodelete_message_hours`, `autodelete_file_history_days`
+- CLI arguments for startup override
+- Manual cleanup via `clear_old_data` action
+
+---
 
 ## [1.0.1] - 2025-10-11
 
-### Added
-- **Database Schema Validation:** Comprehensive validation on startup for existing databases
-  - Detects missing tables, views, and triggers
-  - Verifies standard data integrity (layers, categories, tags)
-  - Displays detailed error messages with actionable solutions
-  - Prevents data corruption from incompatible schemas
-  - Graceful exit with error code 1 on validation failure
+### Fixed - Schema Initialization
 
-### Fixed
-- Database initialization now validates existing schema before proceeding
-- Organized test files into `tests/` directory for better project structure
+**Fixed initial database schema creation**
 
-### Changed
-- Updated `.gitignore` to properly handle test files (root vs tests directory)
+---
 
 ## [1.0.0] - 2025-01-10
 
-### Initial Release
+### Added - Initial Release
+
+**MCP Shared Context Server for efficient context sharing**
+
+#### Core Features
+- Decision tracking with metadata (tags, layers, scopes, versions)
+- Agent messaging with priority levels
+- File change tracking with layer integration
+- Constraint management with priorities
+- Statistics and utilities
+- SQLite-based persistence with better-sqlite3
+
+#### Database Schema
+- Master tables: agents, files, context_keys, layers, tags, scopes, etc.
+- Transaction tables: decisions, messages, file_changes, constraints
+- Views for token-efficient queries
+- Automatic version history tracking
 
-First production release of sqlew - MCP server for efficient context sharing between Claude Code sub-agents.
-
-### Added
-
-#### Context Management (6 tools)
-- `set_decision` - Set or update decisions with metadata (tags, layers, scopes, versions)
-- `get_context` - Advanced filtering for decision retrieval
-- `get_decision` - Retrieve specific decision by key
-- `search_by_tags` - Tag-based search with AND/OR logic
-- `get_versions` - Version history tracking
-- `search_by_layer` - Layer-based decision filtering
-
-#### Messaging System (3 tools)
-- `send_message` - Agent-to-agent messaging with priority levels
-- `get_messages` - Message retrieval with filtering (priority, unread status)
-- `mark_read` - Mark messages as read
-
-#### File Change Tracking (3 tools)
-- `record_file_change` - Track file modifications with layer assignment
-- `get_file_changes` - File change history retrieval
-- `check_file_lock` - Concurrent edit prevention
-
-#### Constraint Management (3 tools)
-- `add_constraint` - Add constraints with priority and metadata
-- `get_constraints` - Complex constraint filtering
-- `deactivate_constraint` - Soft delete constraints
-
-#### Utilities (3 tools)
-- `get_layer_summary` - Per-layer aggregated statistics
-- `clear_old_data` - Manual cleanup of old data
-- `get_stats` - Comprehensive database statistics
-
-### Features
-
-- **Token Efficiency:** 72% reduction through ID-based normalization, integer enums, and pre-aggregated views
-- **Metadata System:** Tags, layers, scopes, versions, and priorities for intelligent organization
-- **SQLite Database:** Fast, reliable, offline-only operation with ACID guarantees
-- **Automatic Cleanup:** Configurable retention policies (24h for messages, 7 days for file changes)
-- **Version History:** Automatic tracking of decision evolution
-- **Concurrent Access:** Support for multiple agents simultaneously
-- **WAL Mode:** Write-Ahead Logging for improved concurrency
-
-### Database Schema
-
-- 7 Master tables for normalization (agents, files, context_keys, layers, tags, scopes, constraint_categories)
-- 10 Transaction tables for core data
-- 6 Token-efficient pre-aggregated views
-- 9 Optimized indexes for common queries
-- 3 Automatic triggers for cleanup and history
-
-### Architecture
-
-- **Standard Layers:** presentation, business, data, infrastructure, cross-cutting
-- **Constraint Categories:** performance, architecture, security
-- **Priority Levels:** low, medium, high, critical
-- **Message Types:** decision, warning, request, info
-- **Change Types:** created, modified, deleted
-- **Status Values:** active, deprecated, draft
-
-### Performance
-
-- Query performance: 2-20ms for typical operations
-- Concurrent access: Tested with 5 simultaneous agents
-- Database size: ~140 bytes per decision (efficient storage)
-- Token reduction: 72% compared to traditional JSON approach
-
-### Documentation
-
-- Comprehensive README with quick start guide
-- Complete tool reference with examples
-- Architecture documentation
-- Schema reference
-- Development guidelines
-
-### Testing
-
-- 100% tool coverage (all 18 tools verified)
-- Comprehensive test suite
-- MCP Inspector compatibility
-
-### Technical Details
-
-- **Runtime:** Node.js 18+
-- **Language:** TypeScript 5.0+
-- **Database:** better-sqlite3 ^11.0.0
-- **MCP SDK:** @modelcontextprotocol/sdk (latest)
-- **Transport:** stdio (standard MCP pattern)
-
-### Code Statistics
-
-- 3,424 lines of TypeScript
-- 10 source files
-- Full type safety
-- Comprehensive error handling
-
-[2.1.4]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v2.1.4
-[2.1.3]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v2.1.3
-[2.1.2]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v2.1.2
-[2.1.1]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v2.1.1
-[2.1.0]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v2.1.0
-[2.0.0]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v2.0.0
-[1.1.2]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v1.1.2
-[1.1.1]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v1.1.1
-[1.1.0]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v1.1.0
-[1.0.1]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v1.0.1
-[1.0.0]: https://github.com/sin5ddd/mcp-sqlew/releases/tag/v1.0.0
+#### MCP Tools
+Initial implementation with 20 separate tools (consolidated to 6 in v2.0.0)