sqlew 3.9.1 → 4.0.1

package/docs/TASK_ACTIONS.md

@@ -1,7 +1,7 @@
 # Task Actions Reference
 
-**Version:** 3.2.0
-**Last Updated:** 2025-10-18
+**Version:** 4.0.0
+**Last Updated:** 2025-11-27
 
 ## Table of Contents
 
@@ -48,11 +48,11 @@ Create a new task.
 
 **Optional:**
 - `description`: Full task description (string)
-- `status`: Initial status (string: "todo", "in_progress", "waiting_review", "blocked", "done", "archived") - default: "todo"
+- `status`: Initial status (string: "todo", "in_progress", "waiting_review", "blocked", "done", "archived", "rejected") - default: "todo"
 - `priority`: Priority level (string: "low", "medium", "high", "critical")
-- `assignee`: Agent or user assigned (string)
+- `assignee`: User or agent assigned (string)
 - `tags`: Array of tags (string[])
-- `layer`: Architecture layer (string: "presentation", "business", "data", "infrastructure", "cross-cutting")
+- `layer`: Architecture layer (string: "presentation", "business", "data", "infrastructure", "cross-cutting", "documentation", "planning", "coordination", "review")
 
 ### Examples
 
@@ -72,7 +72,7 @@ Create a new task.
   description: "Add JWT-based authentication with refresh tokens",
   status: "todo",
   priority: "high",
-  assignee: "auth-agent",
+  assignee: "dev-team-1",
   tags: ["security", "authentication"],
   layer: "business"
 }
@@ -154,7 +154,7 @@ Update existing task fields.
 {
   action: "update",
   task_id: 1,
-  assignee: "senior-auth-agent",
+  assignee: "lead-dev",
   priority: "high"
 }
 ```
@@ -288,7 +288,7 @@ List tasks with filtering (metadata only, no descriptions).
 ```javascript
 {
   action: "list",
-  assignee: "auth-agent"
+  assignee: "dev-team-1"
 }
 ```
 
@@ -332,7 +332,7 @@ List tasks with filtering (metadata only, no descriptions).
       title: "Implement JWT authentication",
       status_name: "in_progress",
       priority_name: "high",
-      assignee: "auth-agent",
+      assignee: "dev-team-1",
       layer_name: "business",
       tags: "security,authentication",
       created_ts: 1697545200,
@@ -343,7 +343,7 @@ List tasks with filtering (metadata only, no descriptions).
       title: "Setup OAuth2 provider",
       status_name: "in_progress",
       priority_name: "high",
-      assignee: "auth-agent",
+      assignee: "dev-team-1",
       layer_name: "business",
       tags: "security,oauth2",
       created_ts: 1697545300,
@@ -364,7 +364,7 @@ List tasks with filtering (metadata only, no descriptions).
       title: "Implement JWT authentication",
       status_name: "in_progress",
       priority_name: "high",
-      assignee: "auth-agent",
+      assignee: "dev-team-1",
       layer_name: "business",
       tags: "security,authentication",
       created_ts: 1697545200,
@@ -377,7 +377,7 @@ List tasks with filtering (metadata only, no descriptions).
       title: "Setup OAuth2 provider",
       status_name: "in_progress",
       priority_name: "high",
-      assignee: "auth-agent",
+      assignee: "dev-team-1",
       layer_name: "business",
       tags: "security,oauth2",
       created_ts: 1697545300,
@@ -407,7 +407,10 @@ Move task to new status with validation.
 **Required:**
 - `action`: "move"
 - `task_id`: Task ID (number)
-- `new_status`: Target status (string: "todo", "in_progress", "waiting_review", "blocked", "done", "archived")
+- `status`: Target status (string: "todo", "in_progress", "waiting_review", "blocked", "done", "archived", "rejected")
+
+**Optional:**
+- `rejection_reason`: Reason for rejection (string, only when status="rejected")
 
 ### Examples
 
@@ -416,7 +419,7 @@ Move task to new status with validation.
 {
   action: "move",
   task_id: 1,
-  new_status: "waiting_review"
+  status: "waiting_review"
 }
 ```
 
@@ -425,7 +428,7 @@ Move task to new status with validation.
 {
   action: "move",
   task_id: 1,
-  new_status: "blocked"
+  status: "blocked"
 }
 ```
 
@@ -434,7 +437,17 @@ Move task to new status with validation.
 {
   action: "move",
   task_id: 1,
-  new_status: "done"
+  status: "done"
+}
+```
+
+**Move to Rejected (v4.1.0):**
+```javascript
+{
+  action: "move",
+  task_id: 1,
+  status: "rejected",
+  rejection_reason: "Requirements changed"
 }
 ```
 
@@ -451,22 +464,22 @@ Move task to new status with validation.
 
 ```javascript
 {
-  error: "Invalid status transition from in_progress to archived. Valid transitions: waiting_review, blocked, done"
+  error: "Invalid status transition from archived to todo. Terminal statuses cannot transition."
 }
 ```
 
-### State Machine Validation
+### State Machine Validation (v4.1.0 - Relaxed Rules)
 
 **Valid Transitions:**
 
-| From Status | To Status(es) |
-|-------------|--------------|
-| `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)* |
+| Status Type | Statuses | Can Transition To |
+|-------------|----------|-------------------|
+| **Non-terminal** | todo, in_progress, waiting_review, blocked, done | Any status |
+| **Terminal** | archived, rejected | None |
+
+- Non-terminal statuses can freely transition to any other status
+- Terminal statuses (`archived`, `rejected`) cannot transition
+- `rejected` accepts optional `rejection_reason` parameter
 
 **Auto-Stale Detection:**
 - Runs before move operation
@@ -556,7 +569,7 @@ Link task to decision, constraint, or file.
 }
 ```
 
-**See [TASK_LINKING.md](TASK_LINKING.md) for detailed linking strategies and use cases.**
+**Linking Strategies:** Use decision links for architectural context, constraint links for requirements tracking, and file links for code traceability.
 
 ## Action: archive
 
@@ -615,7 +628,7 @@ Archive completed task (soft delete).
 **Workflow:**
 ```javascript
 // 1. Complete task
-{ action: "move", task_id: 1, new_status: "done" }
+{ action: "move", task_id: 1, status: "done" }
 
 // 2. Archive task
 { action: "archive", task_id: 1 }
@@ -645,13 +658,13 @@ Create multiple tasks atomically or best-effort.
       title: "Setup database schema",
       status: "todo",
       priority: "high",
-      assignee: "db-agent"
+      assignee: "dev-team-1"
     },
     {
       title: "Implement API endpoints",
       status: "todo",
       priority: "medium",
-      assignee: "api-agent"
+      assignee: "dev-team-2"
     }
   ],
   atomic: true  // All succeed or all fail
@@ -667,21 +680,21 @@ Create multiple tasks atomically or best-effort.
       title: "Setup database schema",
       status: "todo",
       priority: "high",
-      assignee: "db-agent",
+      assignee: "dev-team-1",
       tags: ["database", "setup"]
     },
     {
       title: "Implement API endpoints",
       status: "todo",
       priority: "medium",
-      assignee: "api-agent",
+      assignee: "dev-team-2",
       tags: ["api", "development"]
     },
     {
       title: "Write integration tests",
       status: "todo",
       priority: "low",
-      assignee: "test-agent",
+      assignee: "dev-team-3",
       tags: ["testing", "qa"]
     }
   ],
@@ -980,7 +993,7 @@ Returns complete tool documentation including:
 { action: "update", task_id: 1, status: "archived" }
 
 // ✅ CORRECT (validates transition)
-{ action: "move", task_id: 1, new_status: "waiting_review" }
+{ action: "move", task_id: 1, status: "waiting_review" }
 ```
 
 **3. Use `list` Before `get`**
@@ -1034,22 +1047,22 @@ link({
 });
 ```
 
-### For Multi-Agent Workflows
+### For Workflow Coordination
 
 **1. Use Assignee for Coordination**
 ```javascript
-// Agent A creates task for Agent B
+// Create task for specific team/person
 {
   action: "create",
   title: "Implement auth middleware",
-  assignee: "auth-agent",
+  assignee: "dev-team-1",
   tags: ["handoff"]
 }
 
-// Agent B lists assigned tasks
+// List tasks for specific assignee
 {
   action: "list",
-  assignee: "auth-agent",
+  assignee: "dev-team-1",
   status: "todo"
 }
 ```
@@ -1079,21 +1092,21 @@ link({
 
 ## Common Errors
 
-### Error: "Invalid status transition"
+### Error: "Invalid status transition" (Terminal Status)
 
 **Problem:**
 ```javascript
-// Trying to move from in_progress to archived
-{ action: "move", task_id: 1, new_status: "archived" }
+// Trying to move FROM a terminal status (archived/rejected)
+{ action: "move", task_id: 1, status: "todo" }  // Task is already archived
 ```
 
-**Solution:**
+**Error:**
 ```javascript
-// Move to done first
-{ action: "move", task_id: 1, new_status: "done" }
-{ action: "archive", task_id: 1 }
+{ error: "Invalid status transition from archived to todo. Terminal statuses cannot transition." }
 ```
 
+**Note:** In v4.1.0+, non-terminal statuses (todo, in_progress, waiting_review, blocked, done) can freely transition to any status including terminal ones.
+
 ### Error: "Task not found"
 
 **Problem:**
@@ -1133,7 +1146,7 @@ link({
 **Solution:**
 ```javascript
 // Complete task first
-{ action: "move", task_id: 1, new_status: "done" }
+{ action: "move", task_id: 1, status: "done" }
 { action: "archive", task_id: 1 }
 ```
 
@@ -1154,14 +1167,11 @@ link({
 ## Related Documentation
 
 - **[TASK_OVERVIEW.md](TASK_OVERVIEW.md)** - Task system overview and core concepts
-- **[TASK_LINKING.md](TASK_LINKING.md)** - Linking tasks to decisions/constraints/files
-- **[TASK_DEPENDENCIES.md](TASK_DEPENDENCIES.md)** - Dependency management (NEW in 3.2.0)
-- **[TASK_MIGRATION.md](TASK_MIGRATION.md)** - Migrating from decision-based task tracking
-- **[TASK_SYSTEM.md](TASK_SYSTEM.md)** - Complete documentation (original)
+- **[TASK_PRUNING.md](TASK_PRUNING.md)** - Auto-pruning feature for watched files
 - **[AI_AGENT_GUIDE.md](AI_AGENT_GUIDE.md)** - Comprehensive AI agent guide
 
 ---
 
-**Version:** 3.2.0
-**Last Updated:** 2025-10-18
+**Version:** 4.0.0
+**Last Updated:** 2025-11-27
 **Author:** sin5ddd

package/docs/TASK_OVERVIEW.md

@@ -1,6 +1,6 @@
 # Task System Overview - Kanban Task Watcher
 
-**Version:** 3.0.0
+**Version:** 4.0.0
 **Last Updated:** 2025-10-17
 
 ## Table of Contents
@@ -118,72 +118,62 @@ Every task has:
 - Completed tasks no longer active
 - Terminal state (no transitions out)
 
-## State Machine Transitions
+**`rejected`:** (v4.1.0)
+- Cancelled or rejected tasks
+- Terminal state (no transitions out)
+- Accepts optional `rejection_reason` parameter
+
+## State Machine Transitions (v4.1.0 - Relaxed Rules)
 
-### Visual Diagram
+### Simplified Model
 
 ```
-v3.4.0 Git-Aware Workflow:
-todo → in_progress → waiting_review → done → archived
-  ↓         ↓              ↓
-  |     (Quality gates   (Git commits)
-  |      or 2h idle)         ↓
-  |         ↓          (All watched files
-  └──── blocked        committed to Git)
-
-Real-time: .git/index file watcher detects commits
-Periodic: task.list() checks git log
-
-Alternative (with acceptance_criteria):
-todo → in_progress → done → archived
-  ↓         ↓
-  |    (Criteria met,
-  |     skip review)
-  |         ↓
-  └──── blocked
+v4.1.0 Relaxed Workflow:
+
+Non-terminal: todo, in_progress, waiting_review, blocked, done
+    ↓ Can freely transition to any status (including terminal)
+
+Terminal: archived, rejected
+    ↓ Cannot transition (final states)
 ```
 
 ### Valid Transitions
 
-| From Status | To Status(es) | Rationale |
-|-------------|--------------|-----------|
-| `todo` | `in_progress`, `blocked` | Start work or discover blocker |
-| `in_progress` | `waiting_review`, `blocked`, `done` | Quality gates met (v3.4.1), need review, hit blocker, or complete |
-| `waiting_review` | `in_progress`, `todo`, `done` | Resume work, reset to backlog, or approve |
-| `blocked` | `todo`, `in_progress` | Blocker resolved, resume or reset |
-| `done` | `archived` | Archive completed work (auto after 48h in v3.4.1) |
-| `archived` | *(terminal state)* | No transitions allowed |
+| Status Type | Statuses | Can Transition To |
+|-------------|----------|-------------------|
+| **Non-terminal** | todo, in_progress, waiting_review, blocked, done | Any status |
+| **Terminal** | archived, rejected | None |
 
 ### Complete Transition Matrix
 
-| From ↓ / To → | todo | in_progress | waiting_review | blocked | done | archived |
-|---------------|------|-------------|----------------|---------|------|----------|
-| **todo** | - | ✅ | ❌ | ✅ | ❌ | ❌ |
-| **in_progress** | ❌ | - | ✅ | ✅ | ✅ | ❌ |
-| **waiting_review** | ✅ | ✅ | - | ❌ | ✅ | ❌ |
-| **blocked** | ✅ | ✅ | ❌ | - | ❌ | ❌ |
-| **done** | ❌ | ❌ | ❌ | ❌ | - | ✅ |
-| **archived** | ❌ | ❌ | ❌ | ❌ | ❌ | - |
+| From ↓ / To → | todo | in_progress | waiting_review | blocked | done | archived | rejected |
+|---------------|------|-------------|----------------|---------|------|----------|----------|
+| **todo** | - | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| **in_progress** | ✅ | - | ✅ | ✅ | ✅ | ✅ | ✅ |
+| **waiting_review** | ✅ | ✅ | - | ✅ | ✅ | ✅ | ✅ |
+| **blocked** | ✅ | ✅ | ✅ | - | ✅ | ✅ | ✅ |
+| **done** | ✅ | ✅ | ✅ | ✅ | - | ✅ | ✅ |
+| **archived** | ❌ | ❌ | ❌ | ❌ | ❌ | - | ❌ |
+| **rejected** | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | - |
 
 ✅ = Valid transition
-❌ = Invalid transition
+❌ = Invalid transition (terminal statuses)
 \- = Same status (no transition)
 
 ### Validation
 
 - Enforced by `move` action
-- Invalid transitions return error with valid options
-- Use `update` action to bypass validation (use with caution)
+- Only terminal statuses (`archived`, `rejected`) cannot transition
+- `rejected` accepts optional `rejection_reason` parameter
 
-**Example Error:**
+**Example - Moving to rejected:**
 ```javascript
 {
   action: "move",
   task_id: 1,
-  new_status: "archived"  // Task is in_progress
+  status: "rejected",
+  rejection_reason: "Requirements changed, task no longer needed"
 }
-// Error: Invalid status transition from in_progress to archived.
-// Valid transitions: waiting_review, blocked, done
 ```
 
 ## Auto-Stale Detection
@@ -285,37 +275,37 @@ ignore_weekend = true               # Weekend-aware mode (shared setting)
 **Via SQL (Advanced):**
 ```sql
 -- Enable/Disable auto-stale
-UPDATE m_config SET value = '1' WHERE key = 'task_auto_stale_enabled';  -- Enable
-UPDATE m_config SET value = '0' WHERE key = 'task_auto_stale_enabled';  -- Disable
+UPDATE v4_config SET value = '1' WHERE key = 'task_auto_stale_enabled';  -- Enable
+UPDATE v4_config SET value = '0' WHERE key = 'task_auto_stale_enabled';  -- Disable
 
 -- Adjust auto-archive threshold
-UPDATE m_config SET value = '3' WHERE key = 'auto_archive_done_days';  -- 3 days
+UPDATE v4_config SET value = '3' WHERE key = 'auto_archive_done_days';  -- 3 days
 
 -- Adjust stale detection thresholds
-UPDATE m_config SET value = '4' WHERE key = 'task_stale_hours_in_progress';
-UPDATE m_config SET value = '48' WHERE key = 'task_stale_hours_waiting_review';
+UPDATE v4_config SET value = '4' WHERE key = 'task_stale_hours_in_progress';
+UPDATE v4_config SET value = '48' WHERE key = 'task_stale_hours_waiting_review';
 
 -- Check current config
-SELECT key, value FROM m_config WHERE key LIKE 'task_%' OR key LIKE 'auto_%';
+SELECT key, value FROM v4_config WHERE key LIKE 'task_%' OR key LIKE 'auto_%';
 ```
 
 ### Monitoring
 
-Track transitions via `t_activity_log` table:
+Track transitions via `v4_activity_log` table:
 
 ```sql
 -- Recent auto-transitions (including auto-archive)
-SELECT * FROM t_activity_log
+SELECT * FROM v4_activity_log
 WHERE entity_type = 'task' AND action_type = 'status_change'
 ORDER BY ts DESC LIMIT 20;
 
 -- Frequently stale tasks (>2 auto-transitions)
-SELECT task_id, COUNT(*) as stale_count FROM t_activity_log
+SELECT task_id, COUNT(*) as stale_count FROM v4_activity_log
 WHERE entity_type = 'task' AND json_extract(details, '$.new_status') = 3
 GROUP BY task_id HAVING stale_count > 2;
 
 -- Recently auto-archived tasks
-SELECT * FROM t_activity_log
+SELECT * FROM v4_activity_log
 WHERE entity_type = 'task'
   AND action_type = 'status_change'
   AND json_extract(details, '$.new_status') = 6  -- ARCHIVED status
@@ -323,7 +313,7 @@ ORDER BY ts DESC LIMIT 20;
 
 -- Count of archived tasks per day
 SELECT date(ts, 'unixepoch') as day, COUNT(*) as archived_count
-FROM t_activity_log
+FROM v4_activity_log
 WHERE entity_type = 'task'
   AND action_type = 'status_change'
   AND json_extract(details, '$.new_status') = 6
@@ -444,21 +434,19 @@ When `autodelete_ignore_weekend` is enabled (via config.toml or MCP tool):
 {
   action: "move",
   task_id: 1,
-  new_status: "waiting_review"
+  status: "waiting_review"
 }
 ```
 
 ## Related Documentation
 
 - **[TASK_ACTIONS.md](TASK_ACTIONS.md)** - Complete action reference with examples
-- **[TASK_LINKING.md](TASK_LINKING.md)** - Linking tasks to decisions/constraints/files
-- **[TASK_MIGRATION.md](TASK_MIGRATION.md)** - Migrating from decision-based task tracking
-- **[TASK_SYSTEM.md](TASK_SYSTEM.md)** - Complete documentation (original)
+- **[TASK_PRUNING.md](TASK_PRUNING.md)** - Auto-pruning feature for watched files
 - **[AI_AGENT_GUIDE.md](AI_AGENT_GUIDE.md)** - Comprehensive AI agent guide
 - **[README.md](../README.md)** - Project overview
 
 ---
 
-**Version:** 3.0.0
-**Last Updated:** 2025-10-17
+**Version:** 4.0.0
+**Last Updated:** 2025-11-27
 **Author:** sin5ddd

package/docs/TASK_PRUNING.md

@@ -1,4 +1,4 @@
-# Task File Auto-Pruning (v3.5.0)
+# Task File Auto-Pruning (v4.0.0)
 
 **Feature**: Automatic removal of non-existent watched files with audit trail preservation
 
@@ -33,7 +33,7 @@ When these files remain non-existent, tasks cannot transition to `waiting_review
 
 ### The Solution
 
-**v3.5.0 Auto-Pruning** automatically removes non-existent watched files when tasks transition to `waiting_review`, while preserving a complete audit trail for project archaeology.
+**v4.0.0 Auto-Pruning** automatically removes non-existent watched files when tasks transition to `waiting_review`, while preserving a complete audit trail for project archaeology.
 
 ### Key Benefits
 
@@ -65,22 +65,22 @@ Auto-pruning is triggered during the `in_progress → waiting_review` transition
    c. Identify non-existent files
    d. **SAFETY CHECK**: If ALL files non-existent → BLOCK transition
    e. Prune non-existent files
-   f. Record to t_task_pruned_files audit table
-   g. Remove from t_task_file_links
+   f. Record to v4_task_pruned_files audit table
+   g. Remove from v4_task_file_links
    h. Continue with quality gate checks on remaining files
 4. Transition to waiting_review (if quality gates pass)
 ```
 
 ### Database Changes
 
-**Table Created**: `t_task_pruned_files`
+**Table Created**: `v4_task_pruned_files`
 ```sql
-CREATE TABLE t_task_pruned_files (
+CREATE TABLE v4_task_pruned_files (
   id INTEGER PRIMARY KEY AUTOINCREMENT,
-  task_id INTEGER NOT NULL REFERENCES t_tasks(id) ON DELETE CASCADE,
+  task_id INTEGER NOT NULL REFERENCES v4_tasks(id) ON DELETE CASCADE,
   file_path TEXT NOT NULL,
   pruned_ts INTEGER DEFAULT (unixepoch()),
-  linked_decision_id INTEGER REFERENCES t_decisions(id) ON DELETE SET NULL
+  linked_decision_id INTEGER REFERENCES v4_decisions(id) ON DELETE SET NULL
 );
 ```
 
@@ -348,10 +348,10 @@ SELECT
   tpf.file_path,
   datetime(tpf.pruned_ts, 'unixepoch') as pruned_at,
   k.key as decision
-FROM t_task_pruned_files tpf
-JOIN t_tasks t ON tpf.task_id = t.id
-LEFT JOIN t_decisions d ON tpf.linked_decision_id = d.id
-LEFT JOIN m_context_keys k ON d.key_id = k.id
+FROM v4_task_pruned_files tpf
+JOIN v4_tasks t ON tpf.task_id = t.id
+LEFT JOIN v4_decisions d ON tpf.linked_decision_id = d.id
+LEFT JOIN v4_context_keys k ON d.key_id = k.id
 WHERE tpf.pruned_ts >= unixepoch('now', '-7 days')
 ORDER BY tpf.pruned_ts DESC;
 ```
@@ -376,7 +376,7 @@ Auto-pruning runs as part of `detectAndTransitionToReview()`, triggered by:
 mcp-tool config update --key review_idle_minutes --value 5
 
 # Via SQL
-UPDATE m_config SET value = '5' WHERE key = 'review_idle_minutes';
+UPDATE v4_config SET value = '5' WHERE key = 'review_idle_minutes';
 ```
 
 ### Quality Gates
@@ -466,22 +466,22 @@ await task.link_pruned_file({
 
 ```sql
 -- Audit table
-CREATE TABLE t_task_pruned_files (
+CREATE TABLE v4_task_pruned_files (
   id INTEGER PRIMARY KEY AUTOINCREMENT,
-  task_id INTEGER NOT NULL REFERENCES t_tasks(id) ON DELETE CASCADE,
+  task_id INTEGER NOT NULL REFERENCES v4_tasks(id) ON DELETE CASCADE,
   file_path TEXT NOT NULL,
   pruned_ts INTEGER DEFAULT (unixepoch()),
-  linked_decision_id INTEGER REFERENCES t_decisions(id) ON DELETE SET NULL
+  linked_decision_id INTEGER REFERENCES v4_decisions(id) ON DELETE SET NULL
 );
 
 -- Indexes
-CREATE INDEX idx_pruned_task ON t_task_pruned_files(task_id);
-CREATE INDEX idx_pruned_decision ON t_task_pruned_files(linked_decision_id);
+CREATE INDEX idx_pruned_task ON v4_task_pruned_files(task_id);
+CREATE INDEX idx_pruned_decision ON v4_task_pruned_files(linked_decision_id);
 ```
 
 ### Implementation Files
 
-- **Migration**: `src/migrations/add-v3.5.0-pruned-files.ts`
+- **Migration**: `src/database/migrations/v4/20251126000000_v4_bootstrap.ts`
 - **Core Logic**: `src/utils/file-pruning.ts`
 - **Integration**: `src/utils/task-stale-detection.ts`
 - **MCP Actions**: `src/tools/tasks.ts` (getPrunedFiles, linkPrunedFile)
@@ -525,7 +525,7 @@ task.get({ task_id: X, include_dependencies: true })
 ```bash
 # Force check by waiting for idle timeout
 # Or manually query database:
-SELECT * FROM t_task_pruned_files WHERE task_id = X;
+SELECT * FROM v4_task_pruned_files WHERE task_id = X;
 ```
 
 ### Issue: Decision link not working
@@ -545,13 +545,13 @@ task.get_pruned_files({ task_id: X })
 
 ## Migration Notes
 
-### Upgrading from v3.4.x
+### Upgrading from v3.9.x
 
-Auto-pruning is **automatic** in v3.5.0. No configuration required.
+Auto-pruning is **automatic** in v4.0.0. No configuration required.
 
 **Database Migration**:
 - Runs automatically on startup
-- Creates `t_task_pruned_files` table
+- Creates `v4_task_pruned_files` table
 - Idempotent (safe to run multiple times)
 
 **Behavioral Changes**:
@@ -559,11 +559,11 @@ Auto-pruning is **automatic** in v3.5.0. No configuration required.
 - No impact on existing tasks (pruning only affects future transitions)
 
 **Rollback**:
-If needed, downgrade to v3.4.x:
+If needed, downgrade to v3.9.x:
 ```bash
 # Audit table will remain but won't be used
 # No data loss
-git checkout v3.4.1
+git checkout v3.9.0
 npm install
 ```
 
@@ -572,8 +572,7 @@ npm install
 ## Related Documentation
 
 - **TASK_OVERVIEW.md**: Task lifecycle and status transitions
-- **TASK_ACTIONS.md**: All task action references
-- **TASK_LINKING.md**: Linking tasks to decisions/constraints/files
+- **TASK_ACTIONS.md**: All task action references (including linking)
 - **DECISION_CONTEXT.md**: Rich decision documentation
 - **ARCHITECTURE.md**: Database schema details
 
@@ -581,6 +580,12 @@ npm install
 
 ## Changelog
 
+### v4.0.0 (2025-11-27)
+- Updated to v4.0.0 schema with `v4_` table prefix
+- Migrated from legacy table names to unified v4 naming convention
+- Updated migration paths to `src/database/migrations/v4/` structure
+- All SQL examples updated for v4 schema
+
 ### v3.5.0 (2025-10-22)
 - Initial release of Auto-Pruning feature
 - Added `t_task_pruned_files` audit table