@jamesaphoenix/tx-cli 0.4.5 → 0.5.0

package/dist/help.js

@@ -14,19 +14,20 @@ Tasks:
   show <id>               Show task details
   update <id>             Update task
   done <id>               Mark task complete
-  reset <id>              Reset task to ready (recover from stuck)
+  reset <id>              Reset task to ready
   delete <id>             Delete task
+
+Dependencies & Hierarchy:
   block <id> <blocker>    Add blocking dependency
   unblock <id> <blocker>  Remove blocking dependency
   children <id>           List child tasks
   tree <id>               Show task subtree
+
+Attempts:
   try <id> <approach>     Record an attempt on a task
   attempts <id>           List attempts for a task
-  claim                   Claim a task with a lease
-  claim:release           Release a claim on a task
-  claim:renew             Renew the lease on a claim
 
-Context & Learnings:
+Memory:
   learning:add            Add a learning
   learning:search         Search learnings
   learning:recent         List recent learnings
@@ -36,19 +37,29 @@ Context & Learnings:
   learn                   Attach a learning to file/glob pattern
   recall                  Query learnings for a path
 
-Sync:
+Messages:
+  send                    Send a message to a channel
+  inbox                   Read messages from a channel
+  ack                     Acknowledge a message
+  ack:all                 Acknowledge all messages on a channel
+  outbox:pending          Count pending messages on a channel
+  outbox:gc               Garbage collect old messages
+
+Docs:
+  doc <subcommand>        Manage docs (add, edit, show, list, render, lock, version, link, attach, patch, validate, drift)
+  invariant <subcommand>  Manage invariants (list, show, record, sync)
+
+Cycle Scan:
+  cycle                   Run cycle-based issue discovery with sub-agent swarms
+
+Sync & Data:
   sync export             Export tasks to JSONL file
   sync import             Import tasks from JSONL file
   sync status             Show sync status
   sync claude             Sync tasks to Claude Code team directory
-  sync codex              Sync tasks to Codex (coming soon)
-
-Traces:
-  trace list              Show recent runs with event counts
-  trace show              Show metrics events for a run
-  trace transcript        Display raw transcript content
-  trace stderr            Display stderr content
-  trace errors            Show recent errors across all runs
+  compact                 Compact completed tasks and export learnings
+  history                 View compaction history
+  migrate status          Show database migration status
 
 Bulk Operations:
   bulk done <id...>       Complete multiple tasks
@@ -56,36 +67,11 @@ Bulk Operations:
   bulk reset <id...>      Reset multiple tasks to ready
   bulk delete <id...>     Delete multiple tasks
 
-Docs:
-  doc add <kind> <name>   Create a doc (overview, prd, design)
-  doc edit <name>         Open doc YAML in $EDITOR
-  doc show <name>         Show doc details
-  doc list                List all docs
-  doc render [name]       Render MD files + regenerate index
-  doc lock <name>         Lock doc (immutable)
-  doc version <name>      Create new version from locked doc
-  doc link <from> <to>    Link two docs
-  doc attach <task> <doc> Link task to doc
-  doc patch <design> <n>  Create design patch on locked doc
-  doc validate            Warn about unlinked tasks
-  doc drift <name>        Detect drift between doc and tasks
-
-Invariants:
-  invariant list          List all invariants
-  invariant show <id>     Show invariant details
-  invariant record <id>   Record pass/fail check result
-  invariant sync          Sync invariants from doc YAML to DB
-
-Cycle Scan:
-  cycle                   Run cycle-based issue discovery scan
-
-Utilities:
+Tools:
   stats                   Show queue metrics and health overview
   validate                Run pre-flight database health checks
-  migrate status          Show database migration status
-  doctor                  Run system diagnostics for troubleshooting
-  dashboard               Start API server + dashboard and open in browser
-  mcp-server              Start MCP server (JSON-RPC over stdio)
+  doctor                  Run system diagnostics
+  dashboard               Start API server + dashboard
 
 Global Options:
   --json                  Output as JSON
@@ -579,8 +565,9 @@ Examples:
 
 Usage: tx learning:search <query> [options]
 
-Searches learnings using hybrid BM25 + vector search with RRF fusion.
-Returns results ranked by relevance.
+Searches learnings using BM25 full-text search. Returns results ranked by
+relevance (BM25 score) and recency. Supports graph expansion to discover
+related learnings through the knowledge graph.
 
 Arguments:
   <query>  Required. Search query (keywords or phrase)
@@ -588,12 +575,16 @@ Arguments:
 Options:
   -n, --limit <n>      Maximum results (default: 10)
   --min-score <n>      Minimum relevance score 0-1 (default: 0.3)
+  --expand             Enable graph expansion to find related learnings
+  --depth <n>          Graph expansion depth (default: 2)
+  --edge-types <types> Comma-separated edge types to traverse
   --json               Output as JSON
   --help               Show this help
 
 Examples:
   tx learning:search "database transactions"
-  tx learning:search "authentication" -n 5 --json`,
+  tx learning:search "authentication" -n 5 --json
+  tx learning:search "auth" --expand --depth 3`,
     "learning:recent": `tx learning:recent - List recent learnings
 
 Usage: tx learning:recent [options]
@@ -659,8 +650,8 @@ Examples:
 Usage: tx context <task-id> [options]
 
 Retrieves learnings relevant to a specific task based on its title and
-description. Uses hybrid BM25 + vector search with RRF fusion, optional
-re-ranking and MMR diversification.
+description. Uses hybrid BM25 + recency scoring. Supports graph expansion
+to discover related learnings through the knowledge graph.
 
 Arguments:
   <task-id>  Required. Task ID (e.g., tx-a1b2c3d4)
@@ -668,6 +659,9 @@ Arguments:
 Options:
   --json               Output as JSON
   --inject             Write to .tx/context.md for injection
+  --expand             Enable graph expansion to find related learnings
+  --depth <n>          Graph expansion depth (default: 2)
+  --edge-types <types> Comma-separated edge types to traverse
   --retriever <path>   Use custom retriever module (exports Layer<RetrieverService>)
   --help               Show this help
 
@@ -690,6 +684,7 @@ Examples:
   tx context tx-a1b2c3d4
   tx context tx-a1b2c3d4 --json
   tx context tx-a1b2c3d4 --inject
+  tx context tx-a1b2c3d4 --expand --depth 3
   tx context tx-a1b2c3d4 --retriever ./my-retriever.ts`,
     learn: `tx learn - Attach a learning to a file path or glob pattern
 
@@ -742,6 +737,580 @@ Examples:
   tx help           # General help
   tx help add       # Help for 'add' command
   tx add --help     # Same as above`,
+    "graph:verify": `tx graph:verify - Verify anchor validity
+
+Usage: tx graph:verify [file] [--all] [--json]
+
+Verifies that anchors still point to valid code locations. Checks if files
+exist, content hashes match, and symbols are present.
+
+Arguments:
+  [file]     Optional. File path to verify anchors for
+
+Options:
+  --file <path>   File path to verify (alternative to positional arg)
+  --all           Verify all anchors (default if no file specified)
+  --json          Output as JSON
+  --help          Show this help
+
+Examples:
+  tx graph:verify                    # Verify all anchors
+  tx graph:verify src/auth.ts        # Verify anchors for specific file
+  tx graph:verify --json             # Output as JSON`,
+    "graph:invalidate": `tx graph:invalidate - Manually invalidate an anchor
+
+Usage: tx graph:invalidate <anchor-id> [--reason <reason>] [--json]
+
+Marks an anchor as invalid (soft delete). The anchor is kept for history
+but excluded from retrieval. Use graph:restore to undo.
+
+Arguments:
+  <anchor-id>  Required. Anchor ID (number)
+
+Options:
+  --reason <text>  Reason for invalidation (default: "Manual invalidation")
+  --json           Output as JSON
+  --help           Show this help
+
+Examples:
+  tx graph:invalidate 42 --reason "Code removed"
+  tx graph:invalidate 42 --json`,
+    "graph:restore": `tx graph:restore - Restore a soft-deleted anchor
+
+Usage: tx graph:restore <anchor-id> [--json]
+
+Restores an invalid anchor back to valid status. Use this to undo
+accidental invalidations or re-enable an anchor after code is restored.
+
+Arguments:
+  <anchor-id>  Required. Anchor ID (number)
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx graph:restore 42
+  tx graph:restore 42 --json`,
+    "graph:prune": `tx graph:prune - Hard delete old invalid anchors
+
+Usage: tx graph:prune [--older-than <days>] [--json]
+
+Permanently deletes anchors that have been invalid for longer than the
+specified period. Default retention is 90 days.
+
+Options:
+  --older-than <days>  Delete anchors invalid for this many days (default: 90)
+  --json               Output as JSON
+  --help               Show this help
+
+Examples:
+  tx graph:prune                     # Delete anchors invalid > 90 days
+  tx graph:prune --older-than 30     # Delete anchors invalid > 30 days
+  tx graph:prune --json`,
+    "graph:status": `tx graph:status - Show graph health metrics
+
+Usage: tx graph:status [--json]
+
+Shows overall health of the knowledge graph including anchor counts by
+status, pinned anchors, and recent invalidation events.
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx graph:status
+  tx graph:status --json`,
+    "graph:pin": `tx graph:pin - Pin an anchor
+
+Usage: tx graph:pin <anchor-id> [--json]
+
+Pins an anchor to prevent automatic invalidation. Pinned anchors are
+skipped during periodic and on-access verification. Use for anchors
+you want to preserve regardless of code changes.
+
+Arguments:
+  <anchor-id>  Required. Anchor ID (number)
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx graph:pin 42
+  tx graph:pin 42 --json`,
+    "graph:unpin": `tx graph:unpin - Unpin an anchor
+
+Usage: tx graph:unpin <anchor-id> [--json]
+
+Removes the pin from an anchor, allowing automatic invalidation
+during verification.
+
+Arguments:
+  <anchor-id>  Required. Anchor ID (number)
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx graph:unpin 42
+  tx graph:unpin 42 --json`,
+    "hooks:install": `tx hooks:install - Install post-commit hook
+
+Usage: tx hooks:install [options]
+
+Installs a git post-commit hook that automatically triggers anchor
+verification when commits meet certain criteria:
+- More than 10 files changed (configurable)
+- High-value configuration files modified
+
+The hook runs verification in the background to avoid blocking commits.
+Configuration is stored in .txrc.json and can be customized.
+
+Options:
+  --force, -f              Overwrite existing hook
+  --threshold, -t <n>      File count threshold (default: 10)
+  --high-value, -h <list>  Comma-separated list of high-value file patterns
+  --json                   Output as JSON
+  --help                   Show this help
+
+Examples:
+  tx hooks:install                           # Install with defaults
+  tx hooks:install --threshold 5             # Trigger on 5+ files
+  tx hooks:install --high-value "*.config.ts,schema.prisma"
+  tx hooks:install --force                   # Reinstall hook
+  tx hooks:install --json                    # JSON output for scripting`,
+    "hooks:uninstall": `tx hooks:uninstall - Remove post-commit hook
+
+Usage: tx hooks:uninstall [options]
+
+Removes the tx post-commit hook. Only removes hooks that were
+installed by tx (identified by marker comment). Updates .txrc.json
+to disable hook settings.
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx hooks:uninstall
+  tx hooks:uninstall --json                  # JSON output for scripting`,
+    "hooks:status": `tx hooks:status - Show git hook status
+
+Usage: tx hooks:status [--json]
+
+Shows the current status of the tx git hook integration including:
+- Whether a hook is installed
+- Whether hooks are enabled in config
+- Current configuration settings
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx hooks:status
+  tx hooks:status --json`,
+    "test:cache-stats": `tx test:cache-stats - Show LLM cache statistics
+
+Usage: tx test:cache-stats [--json]
+
+Shows statistics about the LLM response cache including:
+- Total number of cache entries
+- Total cache size in bytes
+- Date range of cached entries
+- Breakdown by model
+- Breakdown by cache version
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx test:cache-stats                # Show formatted statistics
+  tx test:cache-stats --json         # Output as JSON`,
+    "test:clear-cache": `tx test:clear-cache - Clear LLM cache entries
+
+Usage: tx test:clear-cache [options]
+
+Clears LLM cache entries based on specified criteria. At least one
+option must be provided to prevent accidental cache deletion.
+
+Options:
+  --all              Clear all cache entries
+  --older-than <n>d  Clear entries older than N days (e.g., 30d, 7d)
+                     Supports: d (days), h (hours), m (minutes), s (seconds)
+  --model <name>     Clear entries for a specific model
+  --version <n>      Clear entries with a specific cache version
+  --json             Output as JSON
+  --help             Show this help
+
+Examples:
+  tx test:clear-cache --all                  # Clear entire cache
+  tx test:clear-cache --older-than 30d       # Clear entries older than 30 days
+  tx test:clear-cache --older-than 2h        # Clear entries older than 2 hours
+  tx test:clear-cache --model claude-haiku   # Clear claude-haiku entries
+  tx test:clear-cache --version 1            # Clear version 1 entries
+  tx test:clear-cache --model claude-sonnet-4 --older-than 7d`,
+    daemon: `tx daemon - Background daemon for learning extraction
+
+Usage: tx daemon <subcommand> [options]
+
+Subcommands:
+  start       Start the background daemon
+  stop        Stop the background daemon
+  status      Show daemon status
+  track       Track a project for learning extraction
+  untrack     Stop tracking a project
+  list        List tracked projects
+  process     Process learning candidates
+  review      Review a learning candidate
+  promote     Promote a candidate to learning
+  reject      Reject a learning candidate
+
+Run 'tx daemon <subcommand> --help' for subcommand-specific help.
+
+Examples:
+  tx daemon start               # Start the daemon
+  tx daemon status              # Show daemon status
+  tx daemon track .             # Track current directory
+  tx daemon list                # List tracked projects`,
+    "daemon start": `tx daemon start - Start the background daemon
+
+Usage: tx daemon start [options]
+
+Starts the background daemon process that monitors tracked projects
+for file changes and extracts learning candidates.
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx daemon start`,
+    "daemon stop": `tx daemon stop - Stop the background daemon
+
+Usage: tx daemon stop [options]
+
+Stops the running background daemon process.
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx daemon stop`,
+    "daemon status": `tx daemon status - Show daemon status
+
+Usage: tx daemon status [options]
+
+Shows the current status of the daemon including:
+- Whether daemon is running
+- PID if running
+- Number of tracked projects
+- Number of pending candidates
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx daemon status
+  tx daemon status --json`,
+    "daemon track": `tx daemon track - Track a project for learning extraction
+
+Usage: tx daemon track <project-path> [options]
+
+Adds a project directory to the daemon's watch list. The daemon will
+monitor file changes and extract learning candidates.
+
+Arguments:
+  <project-path>  Required. Path to the project directory
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx daemon track .              # Track current directory
+  tx daemon track ~/projects/my-app`,
+    "daemon untrack": `tx daemon untrack - Stop tracking a project
+
+Usage: tx daemon untrack <project-path> [options]
+
+Removes a project from the daemon's watch list.
+
+Arguments:
+  <project-path>  Required. Path to the project directory
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx daemon untrack .
+  tx daemon untrack ~/projects/my-app`,
+    "daemon list": `tx daemon list - List tracked projects
+
+Usage: tx daemon list [options]
+
+Lists all projects currently being tracked by the daemon.
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx daemon list
+  tx daemon list --json`,
+    "daemon process": `tx daemon process - Process JSONL files for learning candidates
+
+Usage: tx daemon process [options]
+
+Processes JSONL files to extract learning candidates. By default, processes
+files from tracked projects. Use --path to specify a custom glob pattern.
+
+Options:
+  --path, -p <glob>  Glob pattern for JSONL files to process
+  --json             Output as JSON
+  --help             Show this help
+
+Examples:
+  tx daemon process                              # Process tracked projects
+  tx daemon process --path ~/.claude/**/*.jsonl  # Process specific files`,
+    "daemon review": `tx daemon review - List pending learning candidates
+
+Usage: tx daemon review [options]
+
+Lists pending learning candidates awaiting promotion.
+
+Options:
+  --confidence, -c <levels>  Filter by confidence (comma-separated: high,medium,low)
+  --limit, -l <n>            Maximum candidates to show
+  --json                     Output as JSON
+  --help                     Show this help
+
+Examples:
+  tx daemon review
+  tx daemon review --confidence medium,low
+  tx daemon review --limit 10 --json`,
+    "daemon promote": `tx daemon promote - Promote a candidate to learning
+
+Usage: tx daemon promote <candidate-id> [options]
+
+Promotes a learning candidate to a permanent learning entry.
+
+Arguments:
+  <candidate-id>  Required. Candidate ID
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx daemon promote 42`,
+    "daemon reject": `tx daemon reject - Reject a learning candidate
+
+Usage: tx daemon reject <candidate-id> --reason <reason> [options]
+
+Rejects a learning candidate with a reason.
+
+Arguments:
+  <candidate-id>  Required. Candidate ID
+
+Options:
+  --reason <text>  Required. Reason for rejection
+  --json           Output as JSON
+  --help           Show this help
+
+Examples:
+  tx daemon reject 42 --reason "Not relevant"
+  tx daemon reject 42 --reason "Duplicate of existing learning"`,
+    coordinator: `tx coordinator - Worker coordination primitives
+
+Usage: tx coordinator <subcommand> [options]
+
+Manages the worker coordination system for parallel task processing.
+Provides Kubernetes-style worker health tracking, lease-based claims,
+and automatic orphan detection.
+
+Subcommands:
+  start       Start the coordinator
+  stop        Stop the coordinator
+  status      Show coordinator status
+  reconcile   Force a reconciliation pass
+
+Run 'tx coordinator <subcommand> --help' for subcommand-specific help.
+
+Examples:
+  tx coordinator start               # Start with default settings
+  tx coordinator start --workers 3   # Start with 3 workers
+  tx coordinator status              # Show current status
+  tx coordinator reconcile           # Force orphan detection`,
+    "coordinator start": `tx coordinator start - Start the coordinator
+
+Usage: tx coordinator start [options]
+
+Starts the worker coordination system. The coordinator manages worker
+health via heartbeats, handles lease-based task claims, and runs periodic
+reconciliation to detect dead workers and orphaned tasks.
+
+Options:
+  --workers, -w <n>  Worker pool size (default: 1)
+  --daemon, -d       Run as daemon in background
+  --json             Output as JSON
+  --help             Show this help
+
+Examples:
+  tx coordinator start                  # Start with 1 worker
+  tx coordinator start --workers 3      # Start with 3 workers
+  tx coordinator start -w 5 --daemon    # 5 workers in background`,
+    "coordinator stop": `tx coordinator stop - Stop the coordinator
+
+Usage: tx coordinator stop [options]
+
+Stops the running coordinator. By default, immediately marks all workers
+as dead. With --graceful, signals workers to finish current tasks first.
+
+Options:
+  --graceful, -g  Wait for workers to finish current tasks
+  --json          Output as JSON
+  --help          Show this help
+
+Examples:
+  tx coordinator stop               # Immediate stop
+  tx coordinator stop --graceful    # Wait for workers to finish`,
+    "coordinator status": `tx coordinator status - Show coordinator status
+
+Usage: tx coordinator status [options]
+
+Shows the current status of the coordinator including:
+- Running status (stopped/starting/running/stopping)
+- Process ID if running
+- Worker pool size configuration
+- Heartbeat and lease timing settings
+- Last reconciliation timestamp
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx coordinator status
+  tx coordinator status --json`,
+    "coordinator reconcile": `tx coordinator reconcile - Force reconciliation pass
+
+Usage: tx coordinator reconcile [options]
+
+Runs a single reconciliation pass immediately. Reconciliation:
+- Detects dead workers (missed 2+ heartbeats)
+- Releases expired task claims
+- Recovers orphaned tasks (active but no claim)
+- Fixes state inconsistencies
+
+Normally runs automatically every 60s, but can be triggered manually.
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx coordinator reconcile
+  tx coordinator reconcile --json`,
+    worker: `tx worker - Worker process management
+
+Usage: tx worker <subcommand> [options]
+
+Manages worker processes for the coordination system. Workers claim and
+execute tasks, sending heartbeats to the coordinator.
+
+Subcommands:
+  start       Start a worker process
+  stop        Stop a worker process
+  status      Show worker status
+  list        List all workers
+
+Run 'tx worker <subcommand> --help' for subcommand-specific help.
+
+Examples:
+  tx worker start                           # Start with defaults
+  tx worker start --name my-worker          # Start with custom name
+  tx worker status                          # Show worker summary
+  tx worker list                            # List all workers`,
+    "worker start": `tx worker start - Start a worker process
+
+Usage: tx worker start [options]
+
+Starts a worker process that registers with the coordinator, claims tasks,
+and executes them using Claude. The worker sends periodic heartbeats and
+handles graceful shutdown on SIGTERM/SIGINT.
+
+Options:
+  --name, -n <name>              Worker name (default: worker-<auto>)
+  --capabilities, -c <list>      Comma-separated capabilities (default: tx-implementer)
+  --heartbeat <seconds>          Heartbeat interval in seconds (default: 30)
+  --json                         Output as JSON
+  --help                         Show this help
+
+Examples:
+  tx worker start                                    # Start with defaults
+  tx worker start --name my-worker                   # Custom name
+  tx worker start -c tx-implementer,tx-tester        # Multiple capabilities
+  tx worker start --heartbeat 15                     # Custom heartbeat interval`,
+    "worker stop": `tx worker stop - Stop a worker process
+
+Usage: tx worker stop [options]
+
+Workers are stopped by sending SIGTERM to the worker process. The worker
+will finish its current task (if any) before exiting gracefully.
+
+Options:
+  --graceful, -g  Graceful shutdown (workers already handle this)
+  --json          Output as JSON
+  --help          Show this help
+
+Note: To stop a worker, find its PID with 'tx worker list --json' and
+send SIGTERM:
+
+  kill -SIGTERM <worker-pid>
+
+Examples:
+  tx worker stop                   # Show stop instructions`,
+    "worker status": `tx worker status - Show worker status
+
+Usage: tx worker status [worker-id] [options]
+
+Shows the status of workers. If a worker ID is provided, shows detailed
+status for that specific worker. Otherwise, shows a summary of all workers.
+
+Arguments:
+  [worker-id]   Optional. Show detailed status for this worker
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx worker status                        # Summary of all workers
+  tx worker status worker-abc12345        # Detailed status for one worker
+  tx worker status --json                 # Summary as JSON`,
+    "worker list": `tx worker list - List all workers
+
+Usage: tx worker list [options]
+
+Lists all registered workers with their current status, name, and active task.
+
+Options:
+  --status, -s <list>   Filter by status (comma-separated: starting,idle,busy,stopping,dead)
+  --json                Output as JSON
+  --help                Show this help
+
+Examples:
+  tx worker list                    # List all workers
+  tx worker list --status idle,busy # Only idle and busy workers
+  tx worker list --json             # Output as JSON for scripting`,
     trace: `tx trace - Execution tracing for debugging run failures
 
 Usage: tx trace <subcommand> [options]
@@ -899,6 +1468,47 @@ Fails if:
 Examples:
   tx claim:renew tx-abc123 worker-def456
   tx claim:renew tx-abc123 worker-def456 --json`,
+    compact: `tx compact - Compact completed tasks and export learnings
+
+Usage: tx compact [options]
+
+Compacts completed tasks older than a specified date and exports learnings
+to a markdown file (default: CLAUDE.md). Uses LLM to generate summaries
+and extract actionable learnings from completed work.
+
+Options:
+  --before <date>    Compact tasks before this date (default: 7 days ago)
+                     Formats: YYYY-MM-DD or Nd (e.g., 7d for 7 days ago)
+  --output, -o <file>  Output file for learnings (default: CLAUDE.md)
+  --dry-run, --preview Preview without compacting (no API key needed)
+  --json               Output as JSON
+  --help               Show this help
+
+Requirements:
+  - ANTHROPIC_API_KEY environment variable must be set for actual compaction
+  - --dry-run works without an API key
+
+Examples:
+  tx compact                           # Compact tasks older than 7 days
+  tx compact --before 2024-01-15       # Compact tasks before Jan 15
+  tx compact --before 30d              # Compact tasks older than 30 days
+  tx compact --dry-run                 # Preview what would be compacted
+  tx compact --output agents.md        # Export learnings to agents.md
+  tx compact --json                    # Output as JSON`,
+    history: `tx history - View compaction history
+
+Usage: tx history [options]
+
+Shows the history of past compaction operations including dates,
+task counts, and where learnings were exported.
+
+Options:
+  --json   Output as JSON
+  --help   Show this help
+
+Examples:
+  tx history
+  tx history --json`,
     validate: `tx validate - Database health checks
 
 Usage: tx validate [options]
@@ -1009,57 +1619,126 @@ Examples:
   tx dashboard              # Start and open in Brave/Chrome
   tx dashboard --no-open    # Start without opening browser
   tx dashboard --port 3002  # Custom API port`,
-    doc: `tx doc - Docs as primitives (DD-023)
+    send: `tx send - Send a message to a channel
+
+Usage: tx send <channel> <content> [options]
+
+Options:
+  --sender <s>       Sender name (default: "cli")
+  --task <id>        Associate with a task ID
+  --ttl <seconds>    Time-to-live in seconds
+  --correlation <id> Correlation ID for request/reply
+  --metadata '{}'    JSON metadata object
+  --json             Output as JSON
+
+Examples:
+  tx send worker-3 "Review PR #42" --sender orchestrator
+  tx send broadcast "v2.3.0 deployed" --sender ci --ttl 3600
+  tx send errors "OOM at step 4" --sender worker-3 --task tx-abc123
+  tx send orchestrator "Done" --correlation 550e8400-e29b`,
+    inbox: `tx inbox - Read messages from a channel
+
+Usage: tx inbox <channel> [options]
+
+Read-only: does NOT modify message status. Use tx ack to acknowledge.
+Use --after for cursor-based reading (each reader tracks their own position).
+
+Options:
+  --after <id>       Only messages with ID > this value (cursor)
+  --limit <n>        Max messages to return (default: 50)
+  --sender <s>       Filter by sender
+  --correlation <id> Filter by correlation ID
+  --include-acked    Include already-acknowledged messages
+  --json             Output as JSON
+
+Examples:
+  tx inbox worker-3                    # Read pending messages
+  tx inbox broadcast --after 42        # Cursor-based fan-out
+  tx inbox orchestrator --json         # JSON output
+  tx inbox errors --include-acked      # Include acked messages`,
+    ack: `tx ack - Acknowledge a message
+
+Usage: tx ack <message-id> [--json]
+
+Transitions a message from pending to acked.
+
+Examples:
+  tx ack 42
+  tx ack 42 --json`,
+    "ack:all": `tx ack:all - Acknowledge all pending messages on a channel
+
+Usage: tx ack:all <channel> [--json]
+
+Examples:
+  tx ack:all worker-3
+  tx ack:all errors --json`,
+    "outbox:pending": `tx outbox:pending - Count pending messages
+
+Usage: tx outbox:pending <channel> [--json]
+
+Examples:
+  tx outbox:pending errors
+  tx outbox:pending worker-3 --json`,
+    "outbox:gc": `tx outbox:gc - Garbage collect old messages
+
+Usage: tx outbox:gc [--acked-older-than <hours>] [--json]
+
+Deletes expired messages (past TTL) and optionally old acked messages.
+
+Options:
+  --acked-older-than <hours>  Delete acked messages older than N hours
+
+Examples:
+  tx outbox:gc                         # Delete expired only
+  tx outbox:gc --acked-older-than 24   # Also clean acked > 24h old`,
+    doc: `tx doc - Manage docs-as-primitives
 
 Usage: tx doc <subcommand> [options]
 
 Subcommands:
-  add <kind> <name>     Create a doc (overview, prd, design)
-  edit <name>           Open doc YAML in $EDITOR
-  show <name>           Show doc details (--md for rendered markdown)
-  list                  List all docs (--kind, --status filters)
-  render [name]         Render MD files + regenerate index
-  lock <name>           Lock doc (immutable after locking)
-  version <name>        Create new version from locked doc (copies content)
-  link <from> <to>      Link two docs (auto-infers link type)
-  attach <task> <doc>   Link task to doc (--type implements|references)
-  patch <design> <name> Create design patch on locked doc
-  validate              Warn about tasks not linked to docs
-  drift <name>          Detect drift between doc and linked tasks
+  add <kind> <name>         Create a new doc (overview, prd, design)
+  edit <name>               Open doc YAML in $EDITOR
+  show <name>               Show doc details
+  list                      List all docs
+  render [name]             Render YAML to Markdown (all docs if no name)
+  lock <name>               Lock a doc version (immutable)
+  version <name>            Create new version from locked doc
+  link <from> <to>          Link two docs
+  attach <task-id> <name>   Attach a doc to a task
+  patch <design> <patch>    Create a design patch doc
+  validate                  Check all tasks are linked to docs
+  drift <name>              Detect hash/link drift for a doc
 
 Run 'tx doc <subcommand> --help' for subcommand-specific help.
 
 Examples:
-  tx doc add overview system-design
-  tx doc add design DD-023 --title "Docs as Primitives"
+  tx doc add prd auth-flow --title "Authentication Flow"
+  tx doc show auth-flow --json
+  tx doc list --kind design --status changing
+  tx doc lock auth-flow
+  tx doc version auth-flow
   tx doc render
-  tx doc lock DD-023
-  tx doc version DD-023
-  tx doc validate`,
+  tx doc attach tx-abc123 auth-flow
+  tx doc drift auth-flow`,
     "doc add": `tx doc add - Create a new doc
 
-Usage: tx doc add <kind> <name> [--title <title>]
+Usage: tx doc add <kind> <name> [--title <title>] [--json]
 
-Creates a new doc with template YAML content. The file is written to
-.tx/docs/<kind>/<name>.yml (overview docs go to .tx/docs/<name>.yml).
+Creates a new doc with generated YAML template on disk and metadata in DB.
 
 Arguments:
-  <kind>    Required. Doc kind: overview, prd, design
-  <name>    Required. Doc name (e.g., DD-023-docs-as-primitives)
+  <kind>    Required. Doc kind: overview, prd, or design
+  <name>    Required. Doc name (alphanumeric with dashes/dots)
 
 Options:
-  --title, -t <title>   Doc title (defaults to name)
-  --json                Output as JSON
-  --help                Show this help
-
-Notes:
-  - Only ONE overview doc is allowed per project
-  - YAML content is the source of truth; MD is generated via 'tx doc render'
+  --title, -t <title>  Doc title (defaults to name)
+  --json               Output as JSON
+  --help               Show this help
 
 Examples:
-  tx doc add overview system-design --title "System Design & Invariants"
-  tx doc add prd PRD-023 --title "Docs as Primitives"
-  tx doc add design DD-023 --title "Docs as Primitives"`,
+  tx doc add prd auth-flow --title "Authentication Flow"
+  tx doc add design auth-impl -t "Auth Implementation"
+  tx doc add overview system-overview`,
     "doc edit": `tx doc edit - Open doc YAML in editor
 
 Usage: tx doc edit <name>
@@ -1070,66 +1749,66 @@ Arguments:
   <name>    Required. Doc name
 
 Examples:
-  tx doc edit DD-023
-  EDITOR=code tx doc edit DD-023`,
+  tx doc edit auth-flow
+  EDITOR=code tx doc edit auth-flow`,
     "doc show": `tx doc show - Show doc details
 
 Usage: tx doc show <name> [--md] [--json]
 
-Shows metadata for a doc. Use --md to display rendered markdown content.
+Shows doc metadata. With --md, renders and displays Markdown content.
 
 Arguments:
   <name>    Required. Doc name
 
 Options:
-  --md      Show rendered markdown content instead of metadata
+  --md      Render and display Markdown content
   --json    Output as JSON
   --help    Show this help
 
 Examples:
-  tx doc show DD-023
-  tx doc show DD-023 --md
-  tx doc show DD-023 --json`,
+  tx doc show auth-flow
+  tx doc show auth-flow --md
+  tx doc show auth-flow --json`,
     "doc list": `tx doc list - List all docs
 
-Usage: tx doc list [--kind <k>] [--status <s>] [--json]
+Usage: tx doc list [--kind <kind>] [--status <status>] [--json]
 
-Lists all docs with their kind, version, status, and title.
+Lists all docs, optionally filtered by kind or status.
 
 Options:
-  --kind, -k <kind>     Filter by kind (overview, prd, design)
-  --status, -s <status> Filter by status (changing, locked)
-  --json                Output as JSON
-  --help                Show this help
+  --kind, -k <kind>      Filter by kind (overview, prd, design)
+  --status, -s <status>  Filter by status (changing, locked)
+  --json                 Output as JSON
+  --help                 Show this help
 
 Examples:
   tx doc list
   tx doc list --kind design
   tx doc list --status locked --json`,
-    "doc render": `tx doc render - Render MD files from YAML
+    "doc render": `tx doc render - Render YAML to Markdown
 
 Usage: tx doc render [name] [--json]
 
-Reads YAML source files and generates markdown. Always regenerates
-index.yml and index.md alongside any specific doc.
+Renders doc YAML to Markdown files. If no name given, renders all docs.
+Also regenerates index.yml and index.md.
 
 Arguments:
-  [name]    Optional. Specific doc to render (default: all)
+  [name]    Optional. Doc name (renders all if omitted)
 
 Options:
   --json    Output as JSON
   --help    Show this help
 
 Examples:
-  tx doc render           # Render all docs + index
-  tx doc render DD-023    # Render specific doc + index`,
-    "doc lock": `tx doc lock - Lock a doc
+  tx doc render                # Render all docs
+  tx doc render auth-flow      # Render specific doc
+  tx doc render --json`,
+    "doc lock": `tx doc lock - Lock a doc version
 
 Usage: tx doc lock <name> [--json]
 
-Locks a doc, making it immutable. Renders final MD. To make changes
-to a locked doc, create a new version (tx doc version) or a patch
-(tx doc patch).
+Locks a doc, making it immutable. Also renders final Markdown.
+Use 'tx doc version' to create a new editable version from a locked doc.
 
 Arguments:
   <name>    Required. Doc name
@@ -1139,13 +1818,13 @@ Options:
   --help    Show this help
 
 Examples:
-  tx doc lock DD-023`,
+  tx doc lock auth-flow
+  tx doc lock auth-flow --json`,
     "doc version": `tx doc version - Create new version from locked doc
 
 Usage: tx doc version <name> [--json]
 
-Creates a new version (v2, v3, etc.) by copying the locked doc's content.
-The new version starts in 'changing' status and can be edited.
+Creates a new editable version of a locked doc. The doc must be locked first.
 
 Arguments:
   <name>    Required. Doc name (must be locked)
@@ -1155,70 +1834,66 @@ Options:
   --help    Show this help
 
 Examples:
-  tx doc version DD-023    # Creates DD-023 v2 from locked v1`,
+  tx doc version auth-flow`,
     "doc link": `tx doc link - Link two docs
 
 Usage: tx doc link <from-name> <to-name> [--type <link-type>]
 
-Creates a link between two docs. Link type is auto-inferred from
-doc kinds (overview->prd, prd->design, etc.) unless overridden.
+Creates a directed link between two docs. Link type is auto-inferred
+from doc kinds if not specified.
 
 Arguments:
-  <from-name>   Required. Source doc name
-  <to-name>     Required. Target doc name
+  <from-name>    Required. Source doc name
+  <to-name>      Required. Target doc name
 
 Options:
-  --type <type>   Link type (overview_to_prd, overview_to_design,
-                  prd_to_design, design_patch). Auto-inferred if omitted.
-  --json          Output as JSON
-  --help          Show this help
+  --type <type>  Link type (overview_to_prd, overview_to_design, prd_to_design, design_patch)
+  --json         Output as JSON
+  --help         Show this help
 
 Examples:
-  tx doc link system-design PRD-023
-  tx doc link PRD-023 DD-023`,
-    "doc attach": `tx doc attach - Link task to doc
+  tx doc link system-overview auth-prd
+  tx doc link auth-prd auth-impl --type prd_to_design`,
+    "doc attach": `tx doc attach - Attach a doc to a task
 
-Usage: tx doc attach <task-id> <doc-name> [--type <link-type>]
+Usage: tx doc attach <task-id> <doc-name> [--type implements|references]
 
-Links a task to a doc. Allowed even on locked docs (Class A bugs
-can reference locked designs).
+Creates a link between a task and a doc.
 
 Arguments:
   <task-id>     Required. Task ID (e.g., tx-a1b2c3d4)
   <doc-name>    Required. Doc name
 
 Options:
-  --type <type>   Link type: implements (default) or references
-  --json          Output as JSON
-  --help          Show this help
+  --type <type>  Link type: implements (default) or references
+  --json         Output as JSON
+  --help         Show this help
 
 Examples:
-  tx doc attach tx-abc123 DD-023
-  tx doc attach tx-abc123 DD-023 --type references`,
-    "doc patch": `tx doc patch - Create design patch on locked doc
+  tx doc attach tx-abc123 auth-flow
+  tx doc attach tx-abc123 auth-flow --type references`,
+    "doc patch": `tx doc patch - Create a design patch doc
 
 Usage: tx doc patch <design-name> <patch-name> [--title <title>]
 
-Creates a new design doc linked as a patch to a locked design doc.
-Use for Class B bug fixes on locked designs.
+Creates a new design doc that patches an existing design doc.
 
 Arguments:
-  <design-name>   Required. Name of locked design doc to patch
-  <patch-name>    Required. Name for the patch doc
+  <design-name>  Required. Parent design doc name
+  <patch-name>   Required. New patch doc name
 
 Options:
-  --title, -t <title>   Patch title (defaults to patch name)
-  --json                Output as JSON
-  --help                Show this help
+  --title, -t <title>  Patch title (defaults to patch name)
+  --json               Output as JSON
+  --help               Show this help
 
 Examples:
-  tx doc patch DD-023 DD-023-patch-1 --title "Fix rendering edge case"`,
-    "doc validate": `tx doc validate - Warn about unlinked tasks
+  tx doc patch auth-impl auth-impl-v2 --title "Auth v2 Migration"`,
+    "doc validate": `tx doc validate - Check task-doc coverage
 
 Usage: tx doc validate [--json]
 
-Checks all tasks and warns about any that are not linked to a design doc.
-Does not block operations (warn-only enforcement).
+Checks that all tasks are linked to at least one doc.
 
 Options:
   --json    Output as JSON
@@ -1227,12 +1902,12 @@ Options:
 Examples:
   tx doc validate
   tx doc validate --json`,
-    "doc drift": `tx doc drift - Detect drift between doc and tasks
+    "doc drift": `tx doc drift - Detect drift for a doc
 
 Usage: tx doc drift <name> [--json]
 
-Checks for drift between a doc and its linked tasks. Reports tasks
-that are linked but may not be covered in the doc's work breakdown.
+Checks for drift between the DB metadata and the YAML file on disk.
+Reports hash mismatches, missing files, and unlinked design docs.
 
 Arguments:
   <name>    Required. Doc name
@@ -1242,93 +1917,113 @@ Options:
   --help    Show this help
 
 Examples:
-  tx doc drift DD-023
-  tx doc drift DD-023 --json`,
-    invariant: `tx invariant - Manage structured invariants (DD-023)
+  tx doc drift auth-flow
+  tx doc drift auth-flow --json`,
+    invariant: `tx invariant - Manage machine-checkable invariants
 
 Usage: tx invariant <subcommand> [options]
 
 Subcommands:
-  list                  List all invariants (--subsystem, --enforcement filters)
-  show <id>             Show invariant details
-  record <id>           Record pass/fail check result
-  sync                  Sync invariants from doc YAML files to DB
+  list                List all invariants
+  show <id>           Show invariant details
+  record <id>         Record a check result (--passed or --failed)
+  sync                Sync invariants from doc YAML files into DB
 
 Run 'tx invariant <subcommand> --help' for subcommand-specific help.
 
 Examples:
   tx invariant list
-  tx invariant list --subsystem docs
-  tx invariant show INV-DOC-001
-  tx invariant record INV-DOC-001 --passed
-  tx invariant sync`,
+  tx invariant list --subsystem auth --enforcement integration_test
+  tx invariant show INV-AUTH-001
+  tx invariant record INV-AUTH-001 --passed
+  tx invariant sync
+  tx invariant sync --doc auth-flow`,
     "invariant list": `tx invariant list - List all invariants
 
-Usage: tx invariant list [--subsystem <s>] [--enforcement <e>] [--json]
+Usage: tx invariant list [options]
 
-Lists all invariants with their rule, enforcement type, and status.
+Lists all invariants, optionally filtered by subsystem or enforcement type.
 
 Options:
-  --subsystem, -s <sub>     Filter by subsystem (e.g., docs, task-management)
-  --enforcement, -e <type>  Filter by enforcement type (integration_test, linter, llm_as_judge)
-  --json                    Output as JSON
-  --help                    Show this help
+  --subsystem, -s <name>      Filter by subsystem
+  --enforcement, -e <type>    Filter by enforcement (integration_test, linter, llm_as_judge)
+  --json                      Output as JSON
+  --help                      Show this help
 
 Examples:
   tx invariant list
-  tx invariant list --subsystem docs
-  tx invariant list --enforcement integration_test --json`,
+  tx invariant list --subsystem auth
+  tx invariant list --enforcement linter --json`,
     "invariant show": `tx invariant show - Show invariant details
 
 Usage: tx invariant show <id> [--json]
 
 Shows full details for an invariant including rule, enforcement type,
-subsystem, test/lint/prompt references, and status.
+subsystem, test/lint/prompt references, and creation date.
 
 Arguments:
-  <id>    Required. Invariant ID (e.g., INV-001, INV-DOC-001)
+  <id>    Required. Invariant ID (e.g., INV-AUTH-001)
 
 Options:
   --json    Output as JSON
   --help    Show this help
 
 Examples:
-  tx invariant show INV-001
-  tx invariant show INV-DOC-001 --json`,
-    "invariant record": `tx invariant record - Record invariant check result
+  tx invariant show INV-AUTH-001
+  tx invariant show INV-AUTH-001 --json`,
+    "invariant record": `tx invariant record - Record a check result
 
-Usage: tx invariant record <id> --passed|--failed [--details <text>]
+Usage: tx invariant record <id> --passed|--failed [--details <text>] [--json]
 
-Manually records the result of checking an invariant. In v1, all
-checks are manual. Automated runners (test, lint, LLM) are v2.
+Records whether an invariant check passed or failed. Creates an audit
+trail entry for compliance tracking.
 
 Arguments:
-  <id>    Required. Invariant ID (e.g., INV-001)
+  <id>    Required. Invariant ID (e.g., INV-AUTH-001)
 
 Flags (one required):
-  --passed    Record a passing check
-  --failed    Record a failing check
+  --passed     Record a passing check
+  --failed     Record a failing check
 
 Options:
-  --details, -d <text>  Additional details about the check
+  --details, -d <text>  Additional details about the check result
   --json                Output as JSON
   --help                Show this help
 
 Examples:
-  tx invariant record INV-001 --passed
-  tx invariant record INV-DOC-001 --failed --details "Missing test coverage"
-  tx invariant record INV-001 --passed --json`,
-    cycle: `tx cycle - Run cycle-based issue discovery scan
+  tx invariant record INV-AUTH-001 --passed
+  tx invariant record INV-AUTH-001 --failed --details "Missing null check"
+  tx invariant record INV-AUTH-001 --passed --json`,
+    "invariant sync": `tx invariant sync - Sync invariants from YAML
+
+Usage: tx invariant sync [--doc <name>] [--json]
+
+Syncs invariants from doc YAML files into the database. If a doc name
+is given, syncs only that doc's invariants. Otherwise syncs all docs.
+
+Options:
+  --doc <name>  Sync invariants from a specific doc only
+  --json        Output as JSON
+  --help        Show this help
+
+Examples:
+  tx invariant sync                  # Sync all docs
+  tx invariant sync --doc auth-flow  # Sync specific doc
+  tx invariant sync --json`,
+    cycle: `tx cycle - Cycle-based issue discovery with sub-agent swarms
 
 Usage: tx cycle --task-prompt <text|file> [options]
 
-Dispatches sub-agent swarms to scan for codebase issues, deduplicates
-findings against known issues using LLM-as-judge, and optionally fixes them.
-Repeats in rounds within each cycle until convergence.
+Dispatches parallel sub-agent swarms to scan for codebase issues,
+deduplicates findings across rounds, and optionally fixes them.
+Uses a convergence loop: scan → dedup → score → repeat until no new
+issues are found (loss stabilizes).
+
+Arguments:
+  --task-prompt <text|file>  Required. Area/work being reviewed
 
 Options:
-  --task-prompt <text|file>   Area/work being reviewed (required)
-  --scan-prompt <text|file>   What sub-agents look for (optional)
+  --scan-prompt <text|file>  What sub-agents look for (default: bugs, anti-patterns, security)
   --name <text>              Cycle name (shown in dashboard)
   --description <text>       Cycle description
   --cycles <N>               Number of cycles (default: 1)
@@ -1340,27 +2035,16 @@ Options:
   --dry-run                  Report only, no DB writes
   --score <N>                Base score for new tasks (default: 500)
   --json                     Output as JSON
+  --help                     Show this help
 
-Examples:
-  tx cycle --task-prompt "Review core services" --scan-prompt "Find bugs"
-  tx cycle --task-prompt "Auth module" --scan-only --name "Auth review"
-  tx cycle --task-prompt "Review core" --agents 2 --model claude-sonnet-4-5-20250929
-  tx cycle --task-prompt "Full review" --cycles 3 --fix`,
-    "invariant sync": `tx invariant sync - Sync invariants from doc YAML to DB
-
-Usage: tx invariant sync [--doc <name>] [--json]
-
-Parses invariant definitions from doc YAML files and upserts them
-into the database. Invariants removed from YAML are deprecated.
-
-Options:
-  --doc <name>   Only sync invariants from a specific doc
-  --json         Output as JSON
-  --help         Show this help
+Loss Calculation:
+  loss = 3 * HIGH + 2 * MEDIUM + 1 * LOW
+  Convergence: loss drops to 0 or stops decreasing between rounds
 
 Examples:
-  tx invariant sync                    # Sync all docs
-  tx invariant sync --doc DD-023       # Sync specific doc
-  tx invariant sync --json`
+  tx cycle --task-prompt "Review core services"
+  tx cycle --task-prompt "Review auth module" --scan-prompt "Find security issues"
+  tx cycle --task-prompt "Audit API" --agents 5 --max-rounds 5 --fix
+  tx cycle --task-prompt prompt.md --dry-run --json`
 };
 //# sourceMappingURL=help.js.map