sqlew 2.1.0 → 2.1.1

package/README.md

@@ -1,59 +1,146 @@
 # sqlew
+![sqlew_logo](assets/sqlew-logo.png)
 
 [![npm version](https://img.shields.io/npm/v/sqlew.svg)](https://www.npmjs.com/package/sqlew)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
-**sqlew** (SQL Efficient Workflow) is a Model Context Protocol (MCP) server for efficient context sharing between Claude Code sub-agents. Achieve **67% token reduction** through action-based tools while managing structured data through a metadata-driven SQLite database.
+> **SQL Efficient Workflow** - MCP server for efficient context sharing between Claude Code sub-agents
 
-## ⚠️ Version 2.1.0 - Feature Release
+## Overview
 
-**v2.1.0 adds 7 major features** including Activity Log, Smart Defaults, Subscriptions, Advanced Query, Batch Operations, Templates, and CLI Query Tool. This is a feature addition - fully backward compatible with v2.0.0.
+**sqlew** is a Model Context Protocol (MCP) server that enables efficient context sharing between multiple Claude Code agents through a SQLite-backed database. It dramatically reduces token consumption while providing structured data management through metadata-driven organization.
 
-**Database Compatibility:** ✅ **100% compatible** - v2.1 automatically migrates v2.0 databases to add new tables and columns.
+**Current Version:** 2.1.1
 
-**Migration from v2.0:** Automatic on startup - see [CHANGELOG.md](CHANGELOG.md) for details.
+## Benefits
 
-## Why sqlew?
+### 🧠 Organizational Memory for AI Agents
 
-When coordinating multiple Claude Code agents on a complex project, context sharing becomes critical. Traditional JSON-based approaches consume massive amounts of tokens. sqlew solves this with:
+**sqlew solves the "organizational memory" problem that traditional code can't:**
 
-- **96% Token Reduction:** Action-based API eliminates tool duplication (12,848 → 481 tokens)
-- **67% MCP Context Reduction:** From ~13,730 to ~4,482 tokens in MCP server definitions
-- **Structured Metadata:** Tags, layers, scopes, versions, and priorities for intelligent organization
-- **Fast & Reliable:** SQLite-backed with ACID guarantees and automatic cleanup
-- **6 Action-Based Tools:** Comprehensive API for decisions, messaging, file tracking, constraints, config, and stats
-- **Help Actions:** On-demand documentation with zero token cost until called
+| What Traditional Code Provides | What sqlew Adds |
+|-------------------------------|-----------------|
+| ✅ **Git history** - WHAT changed | ✅ **Decisions** - WHY it changed |
+| ✅ **Code comments** - HOW it works | ✅ **Constraints** - WHY it must work this way |
+| ❌ **Architectural decisions** - Missing! | ✅ **Context survival** - Across sessions |
+
+**Real-World Example:**
+```typescript
+// Agent in Session 1 records:
+{
+  key: "loom/duration-constraint",
+  value: "Duration must NOT occur in Loom module",
+  layer: "business",
+  tags: ["architecture", "constraint", "breaking"]
+}
+
+// Agent in Session 2 queries:
+"What are business layer constraints for Loom module?"
+→ Finds: "Duration must NOT occur in Loom"
+→ Avoids introducing the same bug you just fixed!
+```
+
+### 💡 Why This Matters for LLMs
+
+1. **Context Survival**: Next Claude session can query architectural decisions from previous sessions
+2. **Prevents Regression**: Constraints like "Duration must NOT occur in Loom" prevent reintroducing bugs
+3. **Historical Reasoning**: Captures WHY decisions were made, not just WHAT changed
+4. **Knowledge Discovery**: Searchable by layer/tag/scope - "Show me all breaking changes in business layer"
+
+### ⚡ Real-World Token Savings
+
+**Scenario: 5 Agents Working Across 10 Sessions**
+
+| Approach | Token Usage | Details |
+|----------|-------------|---------|
+| **Without sqlew** | ~20,000 tokens | All context re-provided every session |
+| **With sqlew** | ~7,400 tokens | Selective queries, persistent storage |
+| **Savings** | **63% reduction** | Realistic multi-session project |
+
+**Why sqlew Saves Tokens:**
+
+1. **Selective Retrieval** (50-70% savings)
+   - Without: Must read ALL context every time
+   - With: Query only what's needed - `search_layer("business")` returns 5 decisions, not 100
+
+2. **Structured vs Unstructured** (60-85% savings)
+   - Without: "We decided to use JWT because..." (50-200 tokens in prose)
+   - With: `{key: "auth", value: "JWT", layer: "business"}` (20-30 tokens)
+
+3. **Cross-Session Persistence** (80-95% savings)
+   - Without: Context re-provided every new session
+   - With: Query from database, context survives sessions
+
+4. **Search Instead of Scan** (70-90% savings)
+   - Without: Read all 100 decisions to find 5 relevant ones
+   - With: `search_tags(["breaking", "api"])` → only relevant results
+
+**Expected Token Reduction (Typical Multi-Agent Project):**
+- Conservative: 50-65% reduction
+- Realistic: 60-75% reduction
+- Optimal: 70-85% reduction
+
+*Note: Internal architecture improvements (v1.0.0→v2.0.0) achieved 96% tool definition reduction and 67% MCP context reduction. The percentages above reflect real-world usage benefits.*
+
+**Performance:**
+- Query response: 2-50ms
+- Concurrent access: 5+ simultaneous agents
+- Storage efficiency: ~140 bytes per decision
+
+**Reliability:**
+- SQLite ACID transactions
+- 100% backward compatible upgrades
 
 ## Features
 
-- **Context Management:** Record and retrieve decisions with advanced filtering (tags, layers, scopes, versions)
-- **Agent Messaging:** Priority-based messaging system with broadcast support
-- **File Change Tracking:** Layer-based file organization with lock detection
-- **Constraint Management:** Track performance, architecture, and security constraints
-- **Activity Log (v2.1.0):** Automatic tracking of all agent actions with 4 trigger-based monitoring
-- **Smart Defaults (v2.1.0):** Quick decision creation with intelligent layer/tag inference from file paths
-- **Subscriptions (v2.1.0):** Lightweight polling mechanism to check for updates without fetching all data
-- **Advanced Query (v2.1.0):** Complex multi-criteria filtering with full-text search across decisions
-- **Batch Operations (v2.1.0):** Bulk create decisions, messages, and file changes in single transactions
-- **Templates (v2.1.0):** Pre-configured decision templates (5 built-in) with custom template support
-- **CLI Query Tool (v2.1.0):** Standalone CLI commands for fast terminal queries without MCP Inspector
-- **Token Efficient:** Pre-aggregated views and integer enums minimize token consumption
-- **Weekend-Aware Auto-Cleanup:** Smart retention policies that pause during weekends
-- **Configurable Retention:** Adjust cleanup periods via CLI args or MCP tools
-- **Version History:** Track decision evolution over time
-- **Concurrent Access:** Supports multiple agents simultaneously
+### Core Capabilities
+- **Context Management** - Store and retrieve decisions with tags, layers, scopes, and versions
+- **Agent Messaging** - Priority-based messaging system with broadcast support
+- **File Change Tracking** - Layer-based file organization with lock detection
+- **Constraint Management** - Track performance, architecture, and security constraints
+- **Activity Logging** - Automatic tracking of all agent actions (v2.1.0)
+- **Weekend-Aware Auto-Cleanup** - Smart retention policies that pause during weekends
+
+### Advanced Features (v2.1.0)
+- **Smart Defaults** - Auto-infer layer and tags from file paths (60% token reduction)
+- **Batch Operations** - Process up to 50 operations atomically (70% token reduction)
+- **Update Polling** - Lightweight subscription mechanism (95% token reduction)
+- **Advanced Query** - Complex multi-criteria filtering with full-text search
+- **Templates** - 5 built-in templates + custom template support
+- **CLI Tool** - Standalone query commands without MCP server
+
+### 6 Consolidated Tools (26 Actions)
+1. **`decision`** (13 actions) - Context management with metadata
+2. **`message`** (4 actions) - Agent-to-agent messaging
+3. **`file`** (4 actions) - File change tracking
+4. **`constraint`** (3 actions) - Constraint management
+5. **`stats`** (4 actions) - Statistics and cleanup
+6. **`config`** (2 actions) - Configuration management
 
 ## Installation
 
+### Requirements
+- Node.js 18.0.0 or higher
+- npm or npx
+
+### Install from npm
+
 ```bash
 npm install sqlew
 ```
 
+### Quick Test
+
+```bash
+# Test with MCP Inspector
+npx @modelcontextprotocol/inspector npx sqlew
+```
+
 ## Quick Start
 
 ### Add to Claude Desktop
 
-Add sqlew to your Claude Desktop configuration (`claude_desktop_config.json`):
+Add to your Claude Desktop configuration (`claude_desktop_config.json`):
 
 ```json
 {
@@ -66,7 +153,7 @@ Add sqlew to your Claude Desktop configuration (`claude_desktop_config.json`):
 }
 ```
 
-Or with a custom database path:
+### Custom Database Path
 
 ```json
 {
@@ -79,7 +166,7 @@ Or with a custom database path:
 }
 ```
 
-Or with weekend-aware auto-deletion enabled:
+### Weekend-Aware Auto-Deletion
 
 ```json
 {
@@ -97,95 +184,24 @@ Or with weekend-aware auto-deletion enabled:
 }
 ```
 
-### Using with MCP Inspector
-
-Test all tools interactively:
-
-```bash
-npx @modelcontextprotocol/inspector npx sqlew
-```
-
-### CLI Query Tool (v2.1.0)
-
-Query your context database directly from the terminal without MCP Inspector. The CLI provides 4 specialized query commands with rich filtering capabilities.
-
-```bash
-# Query decisions with filtering
-sqlew query decisions --layer business --tags breaking --output table
-sqlew query decisions --search "auth" --status active --limit 10
-sqlew query decisions --key-pattern "api_*" --scope user-service
-
-# Query unread high-priority messages
-sqlew query messages --unread --priority high --output json
-sqlew query messages --to-agent db-agent --msg-type warning
-sqlew query messages --from-agent auth-agent --since 1h
-
-# Query recent file changes (last hour)
-sqlew query files --since 1h --output table
-sqlew query files --layer data --change-type modified
-sqlew query files --agent auth-agent --file-path "*/auth/*"
-
-# Query recent activity from all agents
-sqlew query activity --since 5m --agent '*' --output json
-sqlew query activity --action-type decision_set --since 30m
-sqlew query activity --agent auth-agent --limit 50
-```
-
-**Available Commands:**
-- `decisions` - Query decisions with multi-criteria filtering and full-text search
-- `messages` - Query agent messages with priority, read status, and type filters
-- `files` - Query file changes with layer, change type, and path filtering
-- `activity` - Query activity log with action type and agent filters
-
-**Common Options:**
-- `--output <format>` - Output format: `json` or `table` (default: json)
-- `--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)
-- `--limit <number>` - Limit results (default: 100)
-- `--db-path <path>` - Custom database path
-- `--help` - Show help for available options
-
-**Decision-Specific Options:**
-- `--search <text>` - Full-text search in keys and values
-- `--status <status>` - Filter by status (active, deprecated, draft)
-- `--key-pattern <pattern>` - SQL LIKE pattern for keys
-- `--scope <scope>` - Filter by scope
-
-**Message-Specific Options:**
-- `--unread` - Show only unread messages
-- `--priority <priority>` - Filter by priority (low, medium, high, critical)
-- `--msg-type <type>` - Filter by message type (decision, warning, request, info)
-- `--from-agent <agent>` - Filter by sender agent
-- `--to-agent <agent>` - Filter by recipient agent
-
-**File-Specific Options:**
-- `--change-type <type>` - Filter by change type (created, modified, deleted)
-- `--agent <agent>` - Filter by agent name
-- `--file-path <pattern>` - SQL LIKE pattern for file paths
-
-**Activity-Specific Options:**
-- `--action-type <type>` - Filter by action type (decision_set, message_send, file_record, constraint_add)
-- `--agent <agent>` - Filter by agent name
-
-Run `sqlew query <command> --help` for command-specific documentation.
-
-### Database Location
+### Default Database Location
 
-Default: `.sqlew/sqlew.db` (created in current directory)
+`.sqlew/sqlew.db` (created in current directory)
 
-## Available Tools (v2.1.0)
+## MCP Tools Reference
 
-All tools now use action-based routing. Call any tool with `action: "help"` for comprehensive documentation.
+All tools use action-based routing. Call any tool with `action: "help"` for comprehensive documentation.
 
-### `decision` - Context Management
+### 1. `decision` - Context Management
 
 Manage decisions with metadata (tags, layers, versions, scopes).
 
-**Actions:** `set`, `get`, `list`, `search_tags`, `search_layer`, `versions`, `quick_set`, `search_advanced`, `set_batch`, `set_from_template`, `create_template`, `list_templates`, `has_updates`, `help`
+**Actions:** `set`, `get`, `list`, `search_tags`, `search_layer`, `versions`, `quick_set`, `search_advanced`, `set_batch`, `has_updates`, `set_from_template`, `create_template`, `list_templates`, `help`
+
+**Examples:**
 
 ```typescript
-// Set a decision (standard)
+// Standard set
 {
   action: "set",
   key: "auth_method",
@@ -193,96 +209,59 @@ Manage decisions with metadata (tags, layers, versions, scopes).
   agent: "auth-agent",
   layer: "business",
   tags: ["authentication", "security"],
-  scopes: ["user-service"],
-  version: "1.0.0",
-  status: "active"
+  version: "1.0.0"
 }
 
-// Quick set with smart defaults (v2.1.0)
+// Quick set with smart defaults (auto-infers layer, tags)
 {
   action: "quick_set",
-  key: "database_config",
-  value: "PostgreSQL",
-  agent: "db-agent",
-  file_path: "/src/data/repositories/UserRepository.ts"
-  // Automatically infers: layer="data", tags=["database", "repositories"]
+  key: "api/users/auth",
+  value: "JWT validation updated",
+  agent: "auth-agent"
+  // Auto-infers: layer="presentation", tags=["api", "users", "auth"]
 }
 
-// Advanced search (v2.1.0)
-{
-  action: "search_advanced",
-  search_text: "authentication",
-  layers: ["business", "presentation"],
-  tags: ["security"],
-  status: "active",
-  agent: "auth-agent",
-  scopes: ["user-service"]
-}
-
-// Batch set (v2.1.0)
+// Batch set (up to 50 decisions atomically)
 {
   action: "set_batch",
   decisions: [
-    { key: "api_v1", value: "REST", agent: "api-agent", layer: "presentation" },
-    { key: "api_v2", value: "GraphQL", agent: "api-agent", layer: "presentation" }
-  ]
+    { key: "api_v1", value: "REST", layer: "presentation" },
+    { key: "api_v2", value: "GraphQL", layer: "presentation" }
+  ],
+  atomic: true
 }
 
-// Set from template (v2.1.0)
+// Check for updates (lightweight polling)
 {
-  action: "set_from_template",
-  template_name: "api-endpoint",
-  key: "user_api",
-  agent: "api-agent",
-  overrides: {
-    value: "GET /api/users",
-    scopes: ["user-service"]
-  }
-}
-
-// Create custom template (v2.1.0)
-{
-  action: "create_template",
-  name: "my-template",
-  description: "Custom template",
-  agent: "admin-agent",
-  default_layer: "business",
-  default_tags: ["custom"],
-  default_status: "active"
+  action: "has_updates",
+  agent_name: "my-agent",
+  since_timestamp: "2025-10-15T10:00:00Z"
 }
 
-// List templates (v2.1.0)
+// Advanced search with complex filtering
 {
-  action: "list_templates"
+  action: "search_advanced",
+  layers: ["business", "data"],
+  tags_all: ["security"],
+  search_text: "authentication",
+  status: "active",
+  limit: 20
 }
 
-// Check for updates (v2.1.0)
+// Set from template
 {
-  action: "has_updates",
-  agent: "auth-agent",
-  since: "2025-01-10T12:00:00Z"
+  action: "set_from_template",
+  template: "api-endpoint",
+  key: "user_api",
+  value: "GET /api/users"
 }
 
-// Get decision by key
+// Get decision
 {
   action: "get",
   key: "auth_method"
 }
 
-// List with filtering
-{
-  action: "list",
-  status: "active",
-  layer: "business"
-}
-
-// Search by tags
-{
-  action: "search_tags",
-  tags: ["authentication", "security"],
-  tag_match: "AND"
-}
-
 // Get version history
 {
   action: "versions",
@@ -293,12 +272,14 @@ Manage decisions with metadata (tags, layers, versions, scopes).
 { action: "help" }
 ```
 
-### `message` - Agent Messaging
+### 2. `message` - Agent Messaging
 
-Send and retrieve messages between agents with priority levels.
+Send and retrieve messages with priority levels.
 
 **Actions:** `send`, `get`, `mark_read`, `send_batch`, `help`
 
+**Examples:**
+
 ```typescript
 // Send message
 {
@@ -311,7 +292,7 @@ Send and retrieve messages between agents with priority levels.
   payload: { file: "/src/auth.ts" }
 }
 
-// Send batch messages (v2.1.0)
+// Batch send (up to 50 messages)
 {
   action: "send_batch",
   messages: [
@@ -319,14 +300,14 @@ Send and retrieve messages between agents with priority levels.
       from_agent: "orchestrator",
       to_agent: "auth-agent",
       msg_type: "request",
-      message: "Start authentication setup",
+      message: "Start setup",
       priority: "high"
     },
     {
       from_agent: "orchestrator",
       to_agent: "db-agent",
       msg_type: "request",
-      message: "Initialize database schema",
+      message: "Initialize schema",
       priority: "high"
     }
   ]
@@ -335,6 +316,7 @@ Send and retrieve messages between agents with priority levels.
 // Get messages
 {
   action: "get",
+  agent_name: "agent1",
   unread_only: true,
   priority_filter: "high"
 }
@@ -342,16 +324,19 @@ Send and retrieve messages between agents with priority levels.
 // Mark as read
 {
   action: "mark_read",
+  agent_name: "agent1",
   message_ids: [1, 2, 3]
 }
 ```
 
-### `file` - File Change Tracking
+### 3. `file` - File Change Tracking
 
-Track file modifications with layer assignment and lock detection.
+Track file modifications with layer assignment.
 
 **Actions:** `record`, `get`, `check_lock`, `record_batch`, `help`
 
+**Examples:**
+
 ```typescript
 // Record file change
 {
@@ -363,23 +348,21 @@ Track file modifications with layer assignment and lock detection.
   description: "Updated JWT validation"
 }
 
-// Record batch file changes (v2.1.0)
+// Batch record (up to 50 file changes)
 {
   action: "record_batch",
-  changes: [
+  file_changes: [
     {
       file_path: "/src/auth/jwt.ts",
       agent_name: "auth-agent",
       change_type: "created",
-      layer: "business",
-      description: "Added JWT utility"
+      layer: "business"
     },
     {
       file_path: "/src/auth/validation.ts",
       agent_name: "auth-agent",
       change_type: "created",
-      layer: "business",
-      description: "Added validation logic"
+      layer: "business"
     }
   ]
 }
@@ -387,7 +370,7 @@ Track file modifications with layer assignment and lock detection.
 // Get file changes
 {
   action: "get",
-  since: "2025-01-10T10:00:00Z",
+  since: "2025-10-15T10:00:00Z",
   layer: "business"
 }
 
@@ -399,12 +382,14 @@ Track file modifications with layer assignment and lock detection.
 }
 ```
 
-### `constraint` - Constraint Management
+### 4. `constraint` - Constraint Management
 
 Manage architectural, performance, and security constraints.
 
 **Actions:** `add`, `get`, `deactivate`, `help`
 
+**Examples:**
+
 ```typescript
 // Add constraint
 {
@@ -430,12 +415,14 @@ Manage architectural, performance, and security constraints.
 }
 ```
 
-### `stats` - Statistics & Utilities
+### 5. `stats` - Statistics & Utilities
 
 Get database statistics and manage data cleanup.
 
 **Actions:** `layer_summary`, `db_stats`, `clear`, `activity_log`, `help`
 
+**Examples:**
+
 ```typescript
 // Layer summary
 { action: "layer_summary" }
@@ -446,9 +433,8 @@ Get database statistics and manage data cleanup.
 // Activity log (v2.1.0)
 {
   action: "activity_log",
-  agent: "auth-agent",
-  action_type: "decision_set",
-  since: "2025-01-10T10:00:00Z",
+  since: "1h",
+  agent_names: ["auth-agent"],
   limit: 100
 }
 
@@ -460,12 +446,14 @@ Get database statistics and manage data cleanup.
 }
 ```
 
-### `config` - Configuration
+### 6. `config` - Configuration
 
 Manage auto-deletion and retention settings.
 
 **Actions:** `get`, `update`, `help`
 
+**Examples:**
+
 ```typescript
 // Get config
 { action: "get" }
@@ -479,195 +467,61 @@ Manage auto-deletion and retention settings.
 }
 ```
 
-## v2.1.0 Features
-
-### FR-001: Activity Log
+## CLI Tool (v2.1.0)
 
-Automatic tracking of all agent actions through trigger-based monitoring. Every decision set, message send, file record, and constraint add is logged with timestamps and agent information.
+Query your database directly from terminal without MCP server.
 
-**Use Cases:**
-- Audit trail for debugging agent interactions
-- Performance monitoring and bottleneck identification
-- Historical analysis of agent behavior patterns
+### Available Commands
 
-**Implementation:**
-- `t_activity_log` table with agent_id, action_type, entity_id, and timestamps
-- 4 triggers automatically log actions: `trg_activity_decision_set`, `trg_activity_message_send`, `trg_activity_file_record`, `trg_activity_constraint_add`
-- Query via `stats` tool with `action: "activity_log"` or CLI with `sqlew query activity`
-
-### FR-002: Smart Defaults
-
-Quick decision creation with intelligent layer and tag inference from file paths. Reduces boilerplate by automatically categorizing decisions based on file context.
-
-**Use Cases:**
-- Rapid decision recording during active development
-- Consistent layer/tag assignment without manual specification
-- Reduced cognitive load for agents
-
-**Implementation:**
-- `quick_set` action in `decision` tool
-- Path pattern matching: `/src/data/*` → layer="data", tags=["database"]
-- `/src/presentation/*` → layer="presentation", tags=["ui", "views"]
-- Overridable defaults if explicit values provided
-
-### FR-003: Subscriptions
-
-Lightweight polling mechanism to check for updates without fetching all data. Agents can subscribe to decision changes and efficiently check for updates since last poll.
-
-**Use Cases:**
-- Periodic checks for new decisions without full data retrieval
-- Token-efficient polling for agents monitoring specific contexts
-- Reduced network/token overhead for update detection
-
-**Implementation:**
-- `t_subscriptions` table tracks agent_id and last_check timestamps
-- `has_updates` action in `decision` tool returns boolean and count
-- Agents can poll periodically with minimal token cost
-
-### FR-004: Advanced Query
-
-Complex multi-criteria filtering with full-text search across decisions. Supports AND/OR logic for tags, multiple layer filtering, and text search in keys/values.
-
-**Use Cases:**
-- Cross-layer analysis (e.g., all "security" decisions in "business" and "data" layers)
-- Full-text search for decisions related to specific features
-- Complex filtering scenarios with multiple conditions
-
-**Implementation:**
-- `search_advanced` action in `decision` tool
-- SQL LIKE search for text patterns in keys and values
-- Multiple layer filtering with `layers` array parameter
-- Combines with existing tag/status/scope filters
-
-### FR-005: Batch Operations
-
-Bulk creation of decisions, messages, and file changes in single transactions. Reduces round-trips and ensures atomic operations.
-
-**Use Cases:**
-- Bulk initialization of project decisions
-- Broadcasting messages to multiple agents
-- Recording multiple file changes from refactoring operations
-- Atomic multi-entity operations
-
-**Implementation:**
-- `set_batch` action in `decision` tool (accepts array of decisions)
-- `send_batch` action in `message` tool (accepts array of messages)
-- `record_batch` action in `file` tool (accepts array of file changes)
-- All operations wrapped in transactions for ACID guarantees
-
-### FR-006: Templates
+```bash
+# Query decisions
+npx sqlew-cli query decisions --layer=business --tags=breaking --output=table
 
-Pre-configured decision templates with 5 built-in templates and custom template support. Ensures consistency and reduces setup time.
+# Query messages
+npx sqlew-cli query messages --unread --priority=high --output=json
 
-**Built-in Templates:**
-1. **api-endpoint**: REST/GraphQL endpoint configurations (layer: presentation, tags: api, endpoints)
-2. **database-config**: Database connection and schema settings (layer: data, tags: database, config)
-3. **security-policy**: Authentication, authorization, encryption rules (layer: cross-cutting, tags: security, policy)
-4. **performance-threshold**: Performance metrics and SLA definitions (layer: infrastructure, tags: performance, monitoring)
-5. **feature-flag**: Feature toggle configurations (layer: business, tags: feature-flags, config)
+# Query file changes
+npx sqlew-cli query files --since=1h --layer=data --output=table
 
-**Use Cases:**
-- Consistent decision structure across agents
-- Quick setup for common decision types
-- Team standards enforcement through templates
+# Query activity log
+npx sqlew-cli query activity --since=5m --agent=* --output=json
+```
 
-**Implementation:**
-- `m_templates` table stores template definitions
-- `set_from_template` action applies template with key and overrides
-- `create_template` action for custom templates
-- `list_templates` action to view available templates
+### Common Options
 
-### FR-007: CLI Query Tool
+- `--output <format>` - Output format: `json` or `table` (default: json)
+- `--layer <layer>` - Filter by layer
+- `--tags <tags>` - Filter by tags (comma-separated)
+- `--since <time>` - Time filter (e.g., "5m", "1h", "2d", or ISO timestamp)
+- `--limit <number>` - Limit results
+- `--db-path <path>` - Custom database path
+- `--help` - Show help
 
-Standalone CLI commands for fast terminal queries without MCP Inspector. Provides 4 specialized query commands with rich filtering and table/JSON output formats.
+## Architecture Layers
 
-**Use Cases:**
-- Quick context checks during terminal-based development
-- CI/CD integration for decision validation
-- Shell scripting with JSON output parsing
-- Human-readable table output for debugging
+sqlew organizes code by standard architecture layers:
 
-**Implementation:**
-- `sqlew query decisions|messages|files|activity` commands
-- Rich filtering options per command (see CLI section above)
-- Table output uses `cli-table3` for formatted display
-- JSON output for programmatic consumption
+- **presentation** - UI, API endpoints, views
+- **business** - Business logic, services, use cases
+- **data** - Repositories, database access
+- **infrastructure** - Configuration, external services
+- **cross-cutting** - Logging, security, utilities
 
 ## Database Schema
 
-sqlew uses a normalized SQLite schema (v2.1.0) optimized for token efficiency with category-based table prefixes:
-
-**Master Tables (m_ prefix):** m_agents, m_files, m_context_keys, m_layers, m_tags, m_scopes, m_constraint_categories, m_config, m_templates (v2.1.0)
+**Master Tables (m_ prefix):** Normalization layer (agents, files, keys, layers, tags, scopes, categories, config, templates)
 
-**Transaction Tables (t_ prefix):** t_decisions, t_decisions_numeric, t_decision_history, t_decision_tags, t_decision_scopes, t_agent_messages, t_file_changes, t_constraints, t_constraint_tags, t_activity_log (v2.1.0), t_subscriptions (v2.1.0)
+**Transaction Tables (t_ prefix):** Core data (decisions, history, messages, file changes, constraints, activity log)
 
-**Token-Efficient Views (v_ prefix):** v_tagged_decisions, v_active_context, v_layer_summary, v_unread_messages_by_priority, v_recent_file_changes, v_tagged_constraints
+**Views (v_ prefix):** Token-efficient pre-aggregated queries
 
-**Triggers (trg_ prefix):** trg_record_decision_history, trg_activity_decision_set (v2.1.0), trg_activity_message_send (v2.1.0), trg_activity_file_record (v2.1.0), trg_activity_constraint_add (v2.1.0)
+**Triggers (trg_ prefix):** Automatic version history and activity logging
 
 ### Automatic Migration
 
-**From v2.0 to v2.1:** Automatic migration adds new tables (t_activity_log, t_subscriptions, m_templates) and triggers (4 activity monitoring triggers). Migration runs on startup and is safe - if it fails, the database is unchanged.
-
-**From v1.2.0 to v1.3.0:** The server automatically migrates your database to use the new prefixed table names. The migration is safe and runs in a transaction.
-
-## Token Efficiency
-
-sqlew achieves **96% token reduction** through:
-
-1. **Action-Based Tools (v2.0):** Consolidates 20 tools → 6 tools, eliminating duplication
-2. **ID-Based Normalization:** Strings stored once, referenced by integer IDs
-3. **Integer Enums:** Status, priority, message types use integers (1-4) instead of strings
-4. **Pre-Aggregated Views:** Common queries use pre-computed results
-5. **Type-Based Tables:** Separate storage for numeric vs string values
-6. **Automatic Cleanup:** Prevents database bloat
-
-### v2.0.0 Token Savings
-
-- **Tool Definitions:** 12,848 → 481 tokens (96.3% reduction)
-- **MCP Context Usage:** ~13,730 → ~4,482 tokens (67% reduction)
-
-### Example Comparison
-
-**Traditional JSON (1000 tokens):**
-```json
-{
-  "key": "auth_method",
-  "value": "JWT",
-  "agent": "auth-agent",
-  "layer": "business",
-  "status": "active",
-  "tags": ["authentication", "security"],
-  "scopes": ["user-service"],
-  "updated": "2025-01-10T12:00:00Z"
-}
-```
-
-**sqlew Response (280 tokens):**
-```json
-{
-  "key_id": 42,
-  "value": "JWT",
-  "agent_id": 5,
-  "layer_id": 2,
-  "status": 1,
-  "tag_ids": [1,4],
-  "scope_ids": [3],
-  "ts": 1736510400
-}
-```
-
-**Token Savings: 720 tokens (72%)**
-
-## Architecture Layers
-
-sqlew organizes code by standard architecture layers:
-
-- **presentation:** UI, API endpoints, views
-- **business:** Business logic, services, use cases
-- **data:** Repositories, database access
-- **infrastructure:** Configuration, external services
-- **cross-cutting:** Logging, security, utilities
+- **v1.x → v2.x:** Automatic migration adds table prefixes and new features
+- **v2.0 → v2.1:** Adds activity log and template tables
+- All migrations are safe with rollback protection
 
 ## Development
 
@@ -680,119 +534,76 @@ npm install
 npm run build
 ```
 
-### Running Locally
+### Available Scripts
 
 ```bash
-npm start
+npm start          # Start MCP server
+npm run cli        # Run CLI tool
+npm run inspector  # Test with MCP Inspector
+npm run build      # Build TypeScript
+npm run dev        # Watch mode
+npm run rebuild    # Clean and rebuild
 ```
 
-### Testing
+## Configuration
 
-```bash
-# Use MCP Inspector to test all tools
-npm run inspector
+### Retention Periods (Defaults)
 
-# Or test individual tools via CLI
-npx @modelcontextprotocol/inspector npx sqlew
-```
+- **Messages:** 24 hours (weekend-aware optional)
+- **File Changes:** 7 days (weekend-aware optional)
+- **Decisions:** Permanent (version history preserved)
+- **Constraints:** Permanent (soft delete only)
 
-### Project Structure
+### Weekend-Aware Cleanup
 
-```
-sqlew/
-├── src/
-│   ├── index.ts              # MCP server entry point
-│   ├── database.ts           # Database initialization
-│   ├── schema.ts             # Schema management
-│   ├── types.ts              # TypeScript types
-│   ├── constants.ts          # Constants & enums
-│   └── tools/
-│       ├── context.ts        # Context management
-│       ├── messaging.ts      # Messaging system
-│       ├── files.ts          # File tracking
-│       ├── constraints.ts    # Constraint management
-│       └── utils.ts          # Utilities
-├── dist/                     # Compiled JavaScript
-└── package.json
-```
+When enabled, weekends (Saturday/Sunday) don't count toward retention periods:
 
-## Configuration
+- Message sent Friday 3pm → Deleted Monday 3pm (skips weekend)
+- Message sent Monday 10am → Deleted Tuesday 10am
 
-### Weekend-Aware Auto-Deletion
+Configure via CLI args or MCP tools at runtime.
 
-sqlew supports weekend-aware retention policies that intelligently handle 3-day weekends and holidays:
+## Migration Guide
 
-**How it works:**
-- When `ignoreWeekend: false` (default): Standard time-based deletion
-- When `ignoreWeekend: true`: Weekends (Sat/Sun) don't count toward retention period
+### From v2.1.0 to v2.1.1
 
-**Example:** With 24-hour retention and `ignoreWeekend: true`:
-- Message sent Friday 3pm → Deleted Monday 3pm (skips Sat/Sun)
-- Message sent Monday 10am → Deleted Tuesday 10am (no weekend in between)
+No breaking changes. Only bin command configuration changed:
 
-**Configuration Methods:**
+- **Old:** `npx sqlew` → CLI, `npx sqlew-server` → MCP server
+- **New:** `npx sqlew` → MCP server, `npx sqlew-cli` → CLI
 
-1. **CLI Arguments (at startup):**
-```bash
-npx sqlew \
-  --autodelete-ignore-weekend \
-  --autodelete-message-hours=48 \
-  --autodelete-file-history-days=10
-```
+Update Claude Desktop config if using custom commands.
 
-2. **MCP Tools (runtime):**
-```typescript
-// Get current config
-get_config()
+### From v2.0.0 to v2.1.0
 
-// Update config
-update_config({
-  ignoreWeekend: true,
-  messageRetentionHours: 72,
-  fileHistoryRetentionDays: 14
-})
-```
+No breaking changes. Database migrates automatically on startup.
 
-3. **Database (persisted):**
-Config is stored in the database and travels with the DB file.
+New features are opt-in via new actions.
 
-### Default Retention Periods
+### From v1.x to v2.0.0
 
-- **Messages:** 24 hours (weekend-aware optional)
-- **File Changes:** 7 days (weekend-aware optional)
-- **Decisions:** Permanent (version history preserved)
-- **Constraints:** Permanent (soft delete only)
-
-### Environment Variables
-
-- `DEBUG_SQL`: Set to enable SQL query logging
+Requires migration. See [MIGRATION_v2.md](MIGRATION_v2.md) for details.
 
 ## License
 
 MIT - see [LICENSE](LICENSE) file for details
 
-## Contributing
-
-Contributions welcome! Areas of interest:
+## Links
 
-- Performance optimizations
-- Additional metadata features
-- Enhanced querying capabilities
-- Integration with other MCP tools
+- [npm package](https://www.npmjs.com/package/sqlew)
+- [GitHub repository](https://github.com/sin5ddd/mcp-sqlew)
+- [Changelog](CHANGELOG.md)
+- [Architecture Documentation](ARCHITECTURE.md)
+- [Model Context Protocol](https://modelcontextprotocol.io/)
 
-### Development Guidelines
+## Author
 
-1. Fork the repository
-2. Create a feature branch
-3. Make your changes
-4. Add tests if applicable
-5. Submit a pull request
+**sin5ddd**
 
 ## Support
 
 - **Issues:** [GitHub Issues](https://github.com/sin5ddd/mcp-sqlew/issues)
 - **Documentation:** See [ARCHITECTURE.md](ARCHITECTURE.md) for technical details
-- **Schema Reference:** See source code for complete schema
 
 ## Acknowledgments
 
@@ -800,13 +611,3 @@ Built with:
 - [Model Context Protocol SDK](https://github.com/modelcontextprotocol/sdk)
 - [better-sqlite3](https://github.com/WiseLibs/better-sqlite3)
 - TypeScript
-
-## Author
-
-**sin5ddd**
-
-## Links
-
-- [npm package](https://www.npmjs.com/package/sqlew)
-- [GitHub repository](https://github.com/sin5ddd/mcp-sqlew)
-- [Model Context Protocol](https://modelcontextprotocol.io/)