fix(v0.6.2): async classifier — kill the fork-bomb

ingest-hook ran the classifier (nested `claude -p`) synchronously,
blocking each Claude Code hook 5-30s. PostToolUse fired faster than
the classifier finished, so ingest-hook procs piled up. The nested
claude also loaded every installed plugin, including task-journal
itself, spawning extra task-journal-mcp servers per call. After a
few minutes WSL2 died on `EAGAIN: pthread_create`.

Fix:
- Real-classifier ingest-hook now writes an enriched pending entry
  (schema v2: kind/text/project_hash/events_path/backend) and spawns
  a detached `task-journal classify-worker` child. Hook returns
  <100ms instead of 5-30s. Mock path stays sync (tests rely on it);
  TJ_INGEST_SYNC=1 forces sync mode for the real path too.
- Hidden `classify-worker` subcommand drains v2 pending entries.
  Holds project-scoped file lock at
  `state_dir/classifier-<project_hash>.lock` — at most one worker
  per project. Stale locks (dead PID via `kill(pid, 0)`) are
  reclaimed automatically.
- Bare `claude` invocations now get `--strict-mcp-config --mcp-config
  '{"mcpServers":{}}'` injected. Inner haiku-claude no longer spawns
  task-journal-mcp (or any other MCP server) per classification.
  Wrappers like `aimux run dt` are detected via non-empty base args
  and left untouched. `--bare` not used because it breaks
  subscription auth (claude-memory-0kk); `--no-plugins` does not
  exist in claude 2.1.x.

Tests: 259 passed, 0 failed. Three new tests cover async hook speed,
worker behavior on classifier failure, and lockfile contention.

Closes claude-memory-9ty.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: Shahinyanm

.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "Task Journal — append-only reasoning chain memory for AI-coding tasks",
-    "version": "0.6.1"
+    "version": "0.6.2"
   },
   "plugins": [
     {
       "name": "task-journal",
       "source": "./plugin",
       "description": "Append-only journal of AI-coding task reasoning chains. Captures hypotheses, decisions, rejections, evidence — renders compact resume packs so an agent can pick up a 2-week-old task with full context.",
-      "version": "0.6.1",
+      "version": "0.6.2",
       "author": {
         "name": "Digital-Threads"
       },

CHANGELOG.md

@@ -7,6 +7,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.2] - 2026-05-09
+
+Fork-bomb fix. Synchronous classifier in `ingest-hook` was blocking
+each Claude Code hook for 5-30s while spawning a nested
+`claude -p` that loaded all installed plugins (including
+task-journal-mcp itself), so within minutes ~19 stale
+`task-journal ingest-hook` and `task-journal-mcp` processes piled up
+and WSL2 died on `EAGAIN: pthread_create`.
+
+### Fixed
+- `ingest-hook` no longer blocks on the classifier. Real-classifier
+  events are queued to `pending/<id>.json` (schema "v2") and a
+  detached `task-journal classify-worker` child drains them in the
+  background. Hook returns in <100ms instead of 5-30s. Mock-classifier
+  path stays synchronous (tests rely on it); set `TJ_INGEST_SYNC=1`
+  to force sync mode for the real path too.
+- `tj_core::classifier::cli::ClaudeCliClassifier` injects
+  `--strict-mcp-config --mcp-config '{"mcpServers":{}}'` automatically
+  when the configured command is bare `claude` (no wrapper). Wrappers
+  like `aimux run dt claude` are detected by non-empty base args and
+  left alone — wrappers may not pass through unknown flags. Stops the
+  inner haiku-claude from spawning task-journal-mcp (and ~24 other MCP
+  servers) per classification. `--bare` not used because it breaks
+  subscription auth (claude-memory-0kk); `--no-plugins` does not exist
+  in claude 2.1.x CLI.
+- New project-scoped worker lockfile at
+  `state_dir/classifier-<project_hash>.lock` caps in-flight
+  classifier workers at 1 per project. PID is written to the lockfile
+  on acquire; stale lockfiles (dead PID) are reclaimed automatically.
+
+### Added
+- Hidden `task-journal classify-worker --backend <cli|api>`
+  subcommand. Internal — spawned by `ingest-hook`. Not stable API.
+
+### Changed (internal)
+- `pending/<id>.json` gained a `"schema"` field. v2 entries carry
+  `kind`, `text`, `project_hash`, `events_path`, `backend` and route
+  through `classify-worker`. v1 entries (legacy `text`+`error` shape)
+  still parse and route through the existing `pending retry` path.
+
 ## [0.6.1] - 2026-05-08
 
 Branch-name regex was too greedy and captured the next word after any

Cargo.lock

@@ -7,7 +7,7 @@ members = [
 ]
 
 [workspace.package]
-version = "0.6.1"
+version = "0.6.2"
 edition = "2021"
 rust-version = "1.88"
 license = "MIT"

Cargo.toml

@@ -16,7 +16,7 @@ name = "task-journal"
 path = "src/main.rs"
 
 [dependencies]
-tj-core = { package = "task-journal-core", version = "0.6.1", path = "../tj-core" }
+tj-core = { package = "task-journal-core", version = "0.6.2", path = "../tj-core" }
 anyhow = { workspace = true }
 clap = { workspace = true }
 tracing = { workspace = true }
@@ -30,6 +30,9 @@ ratatui = { workspace = true }
 crossterm = { workspace = true }
 tempfile = { workspace = true }
 
+[target.'cfg(unix)'.dependencies]
+libc = "0.2"
+
 [dev-dependencies]
 assert_fs = { workspace = true }
 predicates = { workspace = true }