diff --git a/AGENTS.md b/AGENTS.md
index e31b362b..f928363d 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -120,7 +120,7 @@ WorldScript-Studio/
 │   ├── unit/               # Vitest tests (co-located naming convention)
 │   ├── e2e/                # Playwright specs (CI-only)
 │   └── setup.ts            # Global Vitest setup
-├── workers/                # Web Workers: inference, duckdb, plugin, v2 inference/duckdb
+├── workers/                # Web Workers: plugin.worker.ts; v2/ is the sole worker generation since ADR-0015 (inference, duckdb, webllm)
 ├── scripts/                # Build/deploy helpers (i18n bundle, SW version sync, bundle budget, edge build)
 ├── infra/low-end-ci/       # Local CI stack for constrained hardware
 ├── src-tauri/              # Tauri 2 desktop app (Rust)
@@ -425,7 +425,7 @@ Edge builds run `scripts/build-edge.mjs` which sets `DEPLOY_TARGET=edge` and pat
 ### Local Inference
 
 - 4-layer stack: WebLLM → ONNX Runtime Web → Transformers.js → heuristics fallback.
-- `services/localAiFacade.ts` wraps WebLLM via `packages/ai-core` + `workers/inference.worker.ts`.
+- `services/localAiFacade.ts` wraps WebLLM via `packages/ai-core` + `workers/v2/inference.worker.ts`.
 - Tab-leader election via BroadcastChannel prevents multi-tab GPU contention.
 - **Adaptive AI Engine** (`services/ai/adaptiveAiEngine.ts`) — runtime hardware-aware backend/model selection. Gated by `enableAdaptiveAiEngine` flag.
 - **Device Profiler** (`services/ai/localAiDeviceProfiler.ts`) — WebGPU/WebNN/NPU/battery detection, 30s TTL cache.
@@ -448,19 +448,20 @@ Edge builds run `scripts/build-edge.mjs` which sets `DEPLOY_TARGET=edge` and pat
 
 ### WorkerBus v2
 
-Central orchestration layer for all background worker tasks. Messages use short kind literals (`TASK`, `CANCEL`, `PING`, `PONG`, `PROGRESS`, `RESULT`) validated by Zod.
+Central orchestration layer for all background worker tasks — since ADR-0015, the **sole** worker generation (v1's `workers/duckdbWorker.ts`/`workers/inference.worker.ts` deleted). Messages use short kind literals (`TASK`, `CANCEL`, `PING`, `PONG`, `PROGRESS`, `RESULT`) validated by Zod.
 
-- `packages/worker-bus/src/` — WorkerBus, WorkerPool, PriorityTaskQueue, CircuitBreaker, DeadLetterQueue, ProtocolHandler, workerBootstrap, constants, schemas.
-- `services/workerBusManager.ts` — singleton lifecycle; registers `inference` and `duckdb` pools.
+- `packages/worker-bus/src/` — WorkerBus (`hasPool()`/`terminatePool()` for scoped pool lifecycle), WorkerPool, PriorityTaskQueue (`critical > high > normal > low`, no `background` tier), CircuitBreaker, DeadLetterQueue, ProtocolHandler (unused by the live `runTask()` path), workerBootstrap (`WorkerHandlerContext.emitProgress(stage, progress, message?)` — a flat function, not `context.progress.emit(...)`), constants, schemas.
+- `services/workerBusManager.ts` — singleton lifecycle; registers `inference`, `duckdb`, `webllm`, `plugin` pools. `ensureDuckDbPool()`/`ensureInferencePool()`/`ensureWebLlmPool()` force-init and re-register a pool removed via `terminatePool()`, decoupled from `enableWorkerBusV2` (these are core features, not experimental infra).
 - `services/hybridRouter.ts` — routes to Web Worker pool or Rust TaskSupervisor (Tauri only) when `enableRustCompute` is on.
 - `services/legacyWorkerBusAdapter.ts` — shims old `@domain/ai-core` WorkerBus API onto v2.
 - `services/tauriTaskBridge.ts` — `invokeRustTask()`, `isRustComputeAvailable()` (60s TTL ping cache).
 - Feature flags: `enableWorkerBusV2` (on by default), `enableRustCompute` (on by default; effective on Tauri desktop only).
-- v2 workers: `workers/v2/inference.worker.ts` (text + embed via Hugging Face transformers), `workers/v2/duckdb.worker.ts` (init/query/exec/shutdown).
+- Workers: `workers/v2/inference.worker.ts` (text + embed via Hugging Face transformers, prepared-statement-free), `workers/v2/duckdb.worker.ts` (init/query/exec/shutdown, binds params via DuckDB-WASM prepared statements), `workers/v2/webllm.worker.ts` (WebGPU, ADR-0005), `workers/plugin.worker.ts` (sandboxed plugin execution, outside `v2/` but on the same protocol).
+- **Known gap:** `timeoutMs` is not enforced anywhere in the live `runTask()` path (no timer rejects a hung task) — pre-existing, tracked in ADR-0015/TODO.md.
 
 ### DuckDB Analytics
 
-- `workers/duckdbWorker.ts` runs DuckDB-WASM off main thread (OPFS persistence → in-memory fallback).
+- `workers/v2/duckdb.worker.ts` runs DuckDB-WASM off main thread via the shared `duckdb` pool (OPFS persistence → in-memory fallback). `duckdbClient.ts` is an adapter over `ensureDuckDbPool()`/`bus.enqueue()` that auto-reinits on a respawned worker's "not initialized" error.
 - `services/duckdb/duckdbClient.ts` is a singleton proxy with AbortSignal and init retry.
 - Schema (`duckdbSchema.ts`): 10 tables + 5 views including `rag_chunks` (FLOAT[384]), `cross_project_index`, `codex_*`.
 - Gated behind `featureFlagsSlice.enableDuckDbAnalytics` (on by default).
diff --git a/AUDIT.md b/AUDIT.md
index 3a9f45da..8a75b5fc 100644
--- a/AUDIT.md
+++ b/AUDIT.md
@@ -39,10 +39,10 @@ change landed — all 14 findings CONFIRMED, no baseline drift, base SHA `f5f9c1
 | F-08 | 🟠 P1 | Tauri `connect-src` missing LanguageTool's port and the Hugging Face hosts WebLLM/Transformers.js resolve models from | Fixed; scope widened during verification — the LanguageTool port was missing on **all 5** surfaces, not just Tauri; the real weight-file CDN (`us.aws.cdn.hf.co`) traced empirically via `curl`, not guessed |
 | F-09 | 🟠 P1 | DuckDB-WASM loaded from an unversioned, floating-`latest` third-party CDN — already unreachable under the (correctly-scoped) `worker-src` CSP, so this was dead code, not just a supply-chain risk | Self-hosted from the pinned npm dependency via `scripts/copy-duckdb-assets.mjs` (gitignored, ~72 MB, never committed) |
 | F-10 | 🟡 P2 | Two conflicting production URLs; the in-app link and the Italian locale pointed at a dead domain | Empirically resolved (live 200 vs. 404 check) — no maintainer input needed. Unified into a `PRODUCTION_URL` constant + new drift gate |
-| F-11 | 🟡 P2 | Release/tag drift — `v1.24.1` tag 5 commits behind `HEAD` | Version bumped to `1.24.2` in this sprint (WS-7); tag/release publish remains a maintainer action |
+| F-11 | 🟡 P2 | Release/tag drift — `v1.24.1` tag 5 commits behind `HEAD` | Version bumped to `1.24.2` in this sprint (WS-7); `v1.24.2` tagged and published 2026-07-29 |
 | F-12 | 🟡 P2 | Storybook built 3× per CI run; `ci.yml` header still said "StoryCraft Studio" | Deduped to 1×, header fixed. Bonus: the Storybook test-runner's flags were invalid for the installed CLI version, so it had never actually executed a single story on any prior CI run — fixed, and its `\|\| true` (which was itself hiding the failure) replaced with `continue-on-error: true` |
 | F-13 | 🟡 P2 | Coverage ratchet stale since 2026-06-06; 4 non-blocking CI gates with no stated exit criterion | Ratchet raised to CI-measured values (see quality-gate line above); `docs/CI.md` gained an exit-criteria table for all 4 |
-| F-14 | 🟡 P2 | Two live worker generations (v1 + WorkerBus v2) for DuckDB/inference, confirmed via real call-site tracing | Documented, not consolidated — [ADR-0014](docs/adr/0014-worker-generation-duplication.md); a dedicated migration sprint is the correct scope for consolidation |
+| F-14 | 🟡 P2 | Two live worker generations (v1 + WorkerBus v2) for DuckDB/inference, confirmed via real call-site tracing | **Resolved.** Consolidated as the dedicated migration sprint [ADR-0014](docs/adr/0014-worker-generation-duplication.md) called for — [ADR-0015](docs/adr/0015-worker-generation-consolidation.md), PRs #286–288/#290. Both v1 files deleted; correction loops on the migration PRs also caught and fixed 4 real bugs the untested v2 files had drifted on (dropped SQL params, pool-termination hangs, respawn connection loss, a missing export that broke production builds) |
 
 ### Post-mortem: why no gate caught F-01 for two months
 
diff --git a/CHANGELOG.md b/CHANGELOG.md
index eb4c64cd..6fe70a2c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,6 +5,51 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+> Worker-generation consolidation sprint: the v1/WorkerBus-v2 duplication [ADR-0014](docs/adr/0014-worker-generation-duplication.md)
+> deferred is now closed out. Executed as 4 stacked PRs (#286–288, #290); see
+> [ADR-0015](docs/adr/0015-worker-generation-consolidation.md) for the full decision record.
+
+### Changed
+
+- **DuckDB analytics and local inference (embeddings + NLP) now route through WorkerBus v2**,
+  replacing dedicated `new Worker(...)` instances per service. `services/duckdb/duckdbClient.ts`,
+  `services/ai/localEmbeddingService.ts`, and `services/ai/localNlpService.ts` keep their exact
+  public APIs — an adapter pattern, not a consumer rewrite, so none of their real callers needed
+  changes. `ensureDuckDbPool()`/`ensureInferencePool()` added to `services/workerBusManager.ts`,
+  decoupled from `enableWorkerBusV2` (mirrors the existing `ensureWebLlmPool()` pattern — these are
+  core features, not experimental infra).
+- The shared `inference` WorkerBus pool's `maxWorkers` capped at 2 (was 4) — each replica
+  independently loads its own transformers.js pipeline with no cross-replica cache sharing, so 4
+  concurrent workers under a burst could mean 4x the model memory footprint.
+
+### Fixed
+
+- **DuckDB query/exec parameters were silently dropped**, executing an unbound query — already live
+  and breaking `services/ai/telemetryService.ts`'s parameterized `INSERT` writes. Fixed via
+  DuckDB-WASM prepared statements.
+- **`WorkerBus.terminatePool()` could leave tasks hanging forever** — removing a pool didn't settle
+  tasks already routed to it. Fixed by tracking task→pool assignment and cancelling matching tasks
+  before removal; a pool removed this way is now also transparently re-registered on next use
+  instead of failing every subsequent call.
+- **A respawned DuckDB worker lost its connection**, failing every query after an idle timeout with
+  "DuckDB not initialized." Fixed by transparently re-initializing once and retrying.
+- **DuckDB's OPFS-unavailable fallback silently swallowed the failure**, giving users no warning
+  their analytics wouldn't persist across reloads (private browsing, old Safari) — restored via the
+  existing progress channel. A follow-up fix made the fallback's own cleanup step best-effort, so a
+  secondary failure there can no longer block the fallback path itself.
+- **A missing `ensureInferencePool` export broke production builds** on Vercel (rolldown's
+  `[MISSING_EXPORT]`) — not caught by Vitest (the consumer test mocks the whole module) or by local
+  `tsgo` typecheck. Root-caused by reproducing Vercel's *exact* build command
+  (`pnpm run build:edge`, which differs from the plain `pnpm run build` used for an earlier,
+  misleading local repro attempt) and fixed by adding the missing function.
+
+### Removed
+
+- `workers/duckdbWorker.ts` and `workers/inference.worker.ts` (the v1 worker generation) — both
+  workloads now exclusively use `workers/v2/duckdb.worker.ts` and `workers/v2/inference.worker.ts`.
+
 ## [1.24.2] — 2026-07-29
 
 > CSP functional-truth, desktop crypto, and documentation-truth hardening sprint
diff --git a/CLAUDE.md b/CLAUDE.md
index d8ee4dfd..a89858f3 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -107,8 +107,9 @@ locales/          → i18n source JSON — 19 locales (de/en/es/fr/it/ar/he/el/j
 tests/            → unit/ (Vitest) + e2e/ (Playwright); shared E2E helpers in tests/e2e/helpers.ts
 types/            → Supplemental TypeScript definitions (duckdb-wasm-worker.d.ts, tauri-plugins.d.ts)
 types.ts          → Core shared interfaces and types (root level)
-workers/          → inference.worker.ts (@huggingface/transformers v3), duckdbWorker.ts (DuckDB-WASM)
-                     v2/ → WorkerBus v2 workers: inference.worker.ts, duckdb.worker.ts, webllm.worker.ts (P1-1, @mlc-ai/web-llm)
+workers/          → plugin.worker.ts (sandboxed plugin execution, P0-2)
+                     v2/ → sole worker generation since ADR-0015: inference.worker.ts (@huggingface/transformers v3),
+                     duckdb.worker.ts (DuckDB-WASM), webllm.worker.ts (P1-1, @mlc-ai/web-llm)
 infra/low-end-ci/ → Local CI stack: Forgejo + act + systemd units + bash scripts
 scripts/          → Build/deploy helpers (sync-deploy-base, cf-pages-deploy, graphify-update, etc.)
 ```
@@ -188,7 +189,7 @@ Wrap each major view root with `components/ui/ViewErrorBoundary.tsx` — provide
 
 ### DuckDB Analytics
 
-`workers/duckdbWorker.ts` off main thread (OPFS → in-memory fallback). `duckdbClient.ts`: singleton, init retry 3× backoff. Schema: 10 tables + 5 views incl. `rag_chunks` (FLOAT[384]). Gate all paths behind `enableDuckDbAnalytics`. Dual-write via `duckdbListenerLoader.ts` (dynamically imported). `ragVectorMigration.ts`: FLOAT[64]→FLOAT[384] upgrade. `useDuckDb.ts` 30s timeout; `useAnalytics.ts` parallelizes 4 queries.
+`workers/v2/duckdb.worker.ts` off main thread via the shared WorkerBus v2 `duckdb` pool (OPFS → in-memory fallback, ADR-0015). `duckdbClient.ts`: adapter over `ensureDuckDbPool()`/`bus.enqueue()`, auto-reinits on a respawned worker's "not initialized" error. Schema: 10 tables + 5 views incl. `rag_chunks` (FLOAT[384]). Gate all paths behind `enableDuckDbAnalytics`. Dual-write via `duckdbListenerLoader.ts` (dynamically imported). `ragVectorMigration.ts`: FLOAT[64]→FLOAT[384] upgrade. `useDuckDb.ts` 30s timeout; `useAnalytics.ts` parallelizes 4 queries.
 
 ### Logging
 
@@ -218,7 +219,7 @@ Real-time P2P via Yjs + `packages/collab-transport`. Signaling AES-256-GCM/PBKDF
 
 ### WorkerBus v2 (`packages/worker-bus`)
 
-Central orchestration layer for all background tasks. Key files: `workerBus.ts` (orchestrator, priority queue + circuit breakers), `workerPool.ts` (auto-scaling `MIN`→`MAX_WORKERS_INFERENCE`, idle timeout), `taskQueue.ts` (heap: `critical > high > normal > low > background`), `circuitBreaker.ts` (per-worker health gate), `deadLetterQueue.ts`, `protocolHandler.ts` (typed postMessage + version negotiation), `workerBootstrap.ts` (`registerTaskHandler` inside worker scripts, `WorkerHandlerContext.progress.emit`).
+Central orchestration layer for all background tasks — since ADR-0015, the **sole** worker generation (no more v1/v2 duplication). Key files: `workerBus.ts` (orchestrator, priority queue + circuit breakers, `hasPool()`/`terminatePool()` for scoped pool lifecycle), `workerPool.ts` (auto-scaling `MIN`→`MAX_WORKERS_INFERENCE`, idle timeout), `taskQueue.ts` (priority queue: `critical > high > normal > low` — no `background` tier), `circuitBreaker.ts` (per-worker health gate), `deadLetterQueue.ts`, `protocolHandler.ts` (typed postMessage + version negotiation, currently unused by the live `runTask()` path — not wired up), `workerBootstrap.ts` (`registerTaskHandler` inside worker scripts; handlers receive `WorkerHandlerContext.emitProgress(stage, progress, message?)`, a flat function, not `context.progress.emit(...)`).
 
 **All constants** re-exported from `constants.ts`. **Schemas** (Zod) in `schemas.ts` gate cross-thread messages. After changes: `pnpm exec vitest run tests/unit/workerBus`.
 
@@ -405,7 +406,8 @@ Feature-specific implementation patterns (Plot Board, ProForge Pipeline, scene-l
 
 See `AUDIT.md` and `TODO.md`. Key items:
 - `app/listenerMiddleware.ts` — redux-undo `StateWithHistory` typing at boundaries.
-- `workers/inference.worker.ts` — `@huggingface/transformers` v3 path alias in `tsconfig.json`; if alias breaks, restore `@ts-expect-error`.
+- `workers/v2/inference.worker.ts` (v1 deleted, ADR-0015) — `@huggingface/transformers` v3 path alias in `tsconfig.json`; if the alias breaks, fix the path alias or the package's type declaration directly — do not suppress with `@ts-expect-error` (conflicts with the suppression-ratchet policy above).
+- **`WorkerBus.runTask()` doesn't enforce `timeoutMs`** — confirmed via inspection, no timer on either the bus or worker-side rejects a hung task. Pre-existing, tracked in ADR-0015/TODO.md, not yet fixed.
 - **DS-5:** Delete legacy bridge block from `index.css` — deferred until DS-1 verified in production.
 - **B-1 (IDB encryption):** Passphrase UX complete (`IdbUnlockModal`, `PassphraseModal`). Actual IDB read/write integration for stores is Phase 4 (service-layer only currently).
 - **B-2 (Voice WASM):** Engine + download UI shipped. Remaining: E2E integration test coverage.
diff --git a/TODO.md b/TODO.md
index 16856070..04ee4221 100644
--- a/TODO.md
+++ b/TODO.md
@@ -23,13 +23,19 @@ Status: 🔄 in progress | ⬜ open | ✅ done
 - ✅ **DuckDB-WASM self-hosted** — replaced an unversioned, already-CSP-dead third-party CDN.
 - ✅ **Doc-truth fixes** — fabricated `tauri-plugin-stronghold` claim removed; canonical Vercel URL unified with a new drift gate; CI Storybook 3×→1× + a genuinely broken test-runner invocation fixed.
 - ✅ **Coverage ratchet** raised to CI-measured values (L79/F72/B65/S77).
-- ⬜ **Worker-generation consolidation (F-14, new this sprint)** — both a v1 and a WorkerBus-v2
-  generation of the DuckDB and local-inference workers are live simultaneously
-  (`docs/adr/0014-worker-generation-duplication.md`). Needs a dedicated migration sprint: decide
-  the target generation (v2, per `CLAUDE.md`'s own architecture framing), plan the 3 v1 call-site
-  migrations (`services/duckdb/duckdbClient.ts`, `services/ai/localNlpService.ts`,
-  `services/ai/localEmbeddingService.ts`), then remove the v1 worker files. Until then, any worker-
-  level fix (CSP, protocol, error handling) must be checked against **both** generations.
+- ✅ **Worker-generation consolidation (F-14)** — the dedicated migration sprint
+  `docs/adr/0014-worker-generation-duplication.md` deferred, executed as 4 stacked PRs:
+  #286 (parity gate + real handler tests for the previously-untested v2 workers), #287 (DuckDB —
+  `duckdbClient.ts` migrated, `workers/duckdbWorker.ts` deleted), #288 (embeddings —
+  `localEmbeddingService.ts` migrated), #290 (NLP — `localNlpService.ts` migrated,
+  `workers/inference.worker.ts` deleted, closing out v1 entirely). Decision record:
+  `docs/adr/0015-worker-generation-consolidation.md` (supersedes 0014). Correction loops on #287/#288
+  surfaced and fixed real bugs the original v2 files had never been exercised against: DuckDB
+  `params` were silently dropped (already live in `telemetryService.ts`'s parameterized writes),
+  `terminatePool()` could leave tasks hanging forever, a respawned DuckDB worker lost its
+  connection, and `ensureInferencePool()` was imported but never defined (broke Vercel's prod
+  build — see the entry below). **Merge status:** #286 merged; #287/#288/#290 open, stacked, CI
+  green — merge in order before the next release.
 - ✅ **Pre-existing, unrelated E2E a11y finding surfaced during this sprint's CI runs** —
   `tests/e2e/a11y.spec.ts` "writer version control panel has no serious axe violations" failed
   deterministically (`color-contrast` 4.47 vs. 4.5 required, `--sc-accent` `#92400e` over its own
@@ -38,8 +44,8 @@ Status: 🔄 in progress | ⬜ open | ✅ done
   active-toggle classes reused `--sc-accent` for both background tint and text instead of the
   already-vetted `--nav-background-active`/`--nav-text-active` token pair; switched all 3
   occurrences (Writer VC desktop/mobile + mobile ProForge, same shared pattern).
-- ⬜ **Tag `v1.24.2` + publish the GitHub Release** — maintainer action (STOP-AND-ASK per this
-  sprint's own hard rules); the version-bump commit is in, the tag/release is not.
+- ✅ **Tag `v1.24.2` + publish the GitHub Release** — stale entry, already done (verified via
+  `git tag`/`gh release list`: `v1.24.2` tagged and published 2026-07-29T11:25:42Z).
 
 
 ## v1.24 — Post-release feature-flag refinement (2026-06-21)
diff --git a/docs/adr/0014-worker-generation-duplication.md b/docs/adr/0014-worker-generation-duplication.md
index bd08a051..24086609 100644
--- a/docs/adr/0014-worker-generation-duplication.md
+++ b/docs/adr/0014-worker-generation-duplication.md
@@ -1,6 +1,6 @@
 # ADR 0014 — Two live worker generations (v1 and WorkerBus v2)
 
-- **Status:** Accepted (documented as known debt — consolidation explicitly out of scope this sprint)
+- **Status:** Superseded by [[0015-worker-generation-consolidation]] — migrated 2026-07-29
 - **Date:** 2026-07-29
 - **Deciders:** Maintainer + Claude Code
 - **Context tags:** workers, architecture, tech-debt
diff --git a/docs/adr/0015-worker-generation-consolidation.md b/docs/adr/0015-worker-generation-consolidation.md
new file mode 100644
index 00000000..cc54f7b1
--- /dev/null
+++ b/docs/adr/0015-worker-generation-consolidation.md
@@ -0,0 +1,99 @@
+# ADR 0015 — Worker-generation consolidation: v1 retired, WorkerBus v2 is the sole generation
+
+- **Status:** Accepted (shipped)
+- **Date:** 2026-07-29
+- **Deciders:** Maintainer + Claude Code
+- **Context tags:** workers, architecture, tech-debt
+- **Supersedes:** [[0014-worker-generation-duplication]]
+
+## Context
+
+[[0014-worker-generation-duplication]] documented, but deliberately deferred, consolidating two
+live worker generations (legacy `workers/*.worker.ts` vs. WorkerBus v2's `workers/v2/*.worker.ts`)
+for the same two workloads — DuckDB analytics and local inference (embeddings/NLP). That ADR named
+the target generation (v2, per the codebase's own architecture framing) and the exact 3 v1 call
+sites to migrate, but explicitly scoped the actual migration out as "a dedicated migration sprint."
+This ADR is that migration, executed as 4 stacked PRs.
+
+## Decision
+
+**v2 is now the sole worker generation for DuckDB analytics and local inference.** Both legacy
+files are deleted:
+
+| Workload | v1 file (deleted) | v2 file (sole generation) | Migrated in |
+|---|---|---|---|
+| DuckDB analytics | `workers/duckdbWorker.ts` | `workers/v2/duckdb.worker.ts` | PR #287 |
+| Embeddings | `workers/inference.worker.ts` | `workers/v2/inference.worker.ts` (`inference.embed`) | PR #288 |
+| Local NLP | `workers/inference.worker.ts` | `workers/v2/inference.worker.ts` (`inference.text`) | PR #290 |
+
+Each of the 3 v1 call sites (`services/duckdb/duckdbClient.ts`, `services/ai/localEmbeddingService.ts`,
+`services/ai/localNlpService.ts`) kept its exact public API — an adapter pattern, not a consumer
+rewrite — so none of their real callers (`useDuckDb.ts`, `duckdbAnalytics.ts`, `duckdbMigration.ts`,
+`ragVectorMigration.ts`, `telemetryService.ts`, `localRagService.ts`, `crossProjectIndexService.ts`,
+`ragPromptAssembly.ts`, `proForgeMemoryBank.ts`, `loraEvaluationService.ts`, `loraDatasetBuilder.ts`,
+`inferenceGateway.ts`) needed any changes. `services/workerBusManager.ts` gained
+`ensureDuckDbPool()`/`ensureInferencePool()`, mirroring `ensureWebLlmPool()`'s decoupling from
+`enableWorkerBusV2` (ADR-0005) — these are core features (DuckDB analytics defaults on; RAG/
+cross-project search are permanent core behaviour), not experimental infra, so toggling that flag
+off must not silently break them.
+
+### Parity gaps found and fixed before cutover (not assumed away)
+
+The v2 worker files had zero production callers before this migration — registered as live pools
+but never exercised by real traffic — and had genuinely drifted from v1 in ways a parity-test PR
+(#286) and two review-comment correction loops caught before they could reach users:
+
+1. **`initDuckDb()`'s OPFS-unavailable catch block silently swallowed the failure**, unlike v1's
+   out-of-band `OPFS_FALLBACK` message that lets the UI warn users their analytics won't persist.
+   Fixed by threading `emitProgress` into `initDuckDb()` and emitting an `'opfs-fallback'` progress
+   stage; a follow-up review pass found the fix itself could abort the fallback path if the
+   partial connection's `close()` rejected — wrapped in its own best-effort try/catch.
+2. **`handleQuery`/`handleExec` silently dropped `params`**, executing an unbound query — already
+   live and breaking `telemetryService.ts`'s parameterized `INSERT` (a real, shipping bug caught
+   only by this migration, not a hypothetical). Fixed via DuckDB-WASM prepared statements
+   (`connection.prepare(sql)` → `stmt.query(...params)` → `stmt.close()`).
+3. **A respawned duckdb-pool worker had no `connection`** (the pool's `minWorkers:0` lets it
+   idle-terminate; a fresh worker's module state starts blank), so any QUERY/EXEC after a respawn
+   failed with "DuckDB not initialized." Fixed by transparently re-sending INIT once and retrying
+   the original call when `duckdbClient.ts` sees that specific error.
+4. **`WorkerBus.terminatePool()` had no lifecycle contract** — removing a pool didn't settle tasks
+   already routed to it (their result promises would await a RESULT message from a worker that no
+   longer exists), and `ensureDuckDbPool()` assumed a non-null bus always has every pool, so any
+   call after `duckdbClient.terminate()` would fail with `NO_POOL` forever. Fixed by tracking
+   task→pool assignment and cancelling matching tasks on `terminatePool()`, plus a re-registration
+   path (`reRegisterDuckDbPool()`/`reRegisterInferencePool()`) shared with initial registration.
+5. **`ensureInferencePool()` was imported by `localEmbeddingService.ts` but never defined** — a
+   genuine missing-export regression that broke production builds (caught by Vercel's build, not
+   by Vitest, since the consumer test fully mocks the module, or by local `tsgo` typecheck, for
+   reasons not fully understood). Fixed by adding the function; see the "not yet resolved" item
+   below and `TODO.md`'s incident write-up.
+
+### Deliberately not changed
+
+WebLLM's worker-first-with-main-thread-fallback shape (ADR-0005) was **not** extended to DuckDB or
+embedding/NLP — that shape exists because a real main-thread fallback engine exists for WebLLM
+(`runLocalTextGeneration`'s ONNX→Transformers.js→heuristic chain). No such fallback exists for
+DuckDB-WASM or transformers.js pipelines in this repo; failures still surface as errors and callers
+degrade exactly as they did against v1 (empty query results, heuristic sentiment/summary fallback).
+
+## Consequences
+
+- **Positive:** the "any worker-level fix must be checked against both generations" tax ADR-0014
+  described is retired — `workers/duckdbWorker.ts` and `workers/inference.worker.ts` no longer
+  exist. `packages/worker-bus`'s generic `WorkerPool` health-check also replaced ~70 lines of
+  hand-rolled ping/backoff duplicated per v1 service.
+- **Negative (accepted):** the `inference` pool's `maxWorkers` was capped at 2 (was
+  `MAX_WORKERS_INFERENCE`=4) because each pool replica independently loads its own transformers.js
+  pipeline with no cross-replica cache sharing — a resource tradeoff to revisit from WorkerBus's own
+  telemetry (`peakLatencyMs`/`errorRate`) if it proves too conservative.
+- **Not yet resolved:** `WorkerBus.runTask()`'s live path does not enforce `timeoutMs` — confirmed
+  via code inspection, no timer anywhere rejects a hung task, on either the bus or the worker-side
+  bootstrap. Pre-existing (not introduced by this migration), tracked as a follow-up in `TODO.md`
+  rather than expanded into this migration's scope.
+
+## References
+
+- [[0014-worker-generation-duplication]] — the deferred decision this ADR completes
+- [[0005-webllm-worker-offload]] — the `ensureXPool()`/worker-first pattern this migration reused
+- PRs #286 (parity gate), #287 (DuckDB), #288 (embeddings), #290 (NLP + v1 deletion)
+- `TODO.md`'s "Vercel deployment failures root-caused + fixed" entry — the missing-export incident
diff --git a/docs/adr/README.md b/docs/adr/README.md
index 802d88b7..14e4d557 100644
--- a/docs/adr/README.md
+++ b/docs/adr/README.md
@@ -15,6 +15,12 @@ than editing history.
 | [0007](0007-plugin-sandbox-model.md) | Plugin Sandbox Model | Accepted |
 | [0008](0008-local-first-data-model.md) | Local-first data model: Yjs document as source of truth | Accepted |
 | [0009](0009-xstate-workflow-orchestration.md) | XState for complex workflow orchestration (Redux + RTK Query + XState) | Accepted |
+| [0010](0010-languagetool-self-hosted.md) | Self-hosted LanguageTool grammar checking via the editor overlay | Accepted |
+| [0011](0011-ai-heuristic-fallbacks.md) | AI heuristic fallbacks via a registry + provider-layer seam | Accepted |
+| [0012](0012-local-server-connectivity-tauri-http.md) | Local AI server connectivity: route localhost HTTP through the Tauri HTTP plugin | Accepted |
+| [0013](0013-csp-wasm-and-blob-frames.md) | CSP `'wasm-unsafe-eval'` and `frame-src blob:` | Accepted |
+| [0014](0014-worker-generation-duplication.md) | Two live worker generations (v1 and WorkerBus v2) | Superseded by 0015 |
+| [0015](0015-worker-generation-consolidation.md) | Worker-generation consolidation: v1 retired, WorkerBus v2 is the sole generation | Accepted |
 
 **Format:** Context → Decision → Consequences (incl. rejected alternatives). Keep each ADR to one
 decision. Link related records with `[[slug]]`.
diff --git a/docs/audit/WS-RUN-LOG-2026-07-29-worker-consolidation.md b/docs/audit/WS-RUN-LOG-2026-07-29-worker-consolidation.md
new file mode 100644
index 00000000..20983a1b
--- /dev/null
+++ b/docs/audit/WS-RUN-LOG-2026-07-29-worker-consolidation.md
@@ -0,0 +1,100 @@
+# WS Run Log — 2026-07-29 Worker-Generation Consolidation Sprint
+
+Tracks execution of the deferred [ADR-0014](../adr/0014-worker-generation-duplication.md) migration
+(F-14 from the CSP/crypto/doc-truth sprint's finding table), completed the same day as `v1.24.2`'s
+release. Decision record: [ADR-0015](../adr/0015-worker-generation-consolidation.md).
+
+## Baseline
+
+- **HEAD at start:** `dc14bc09` (`chore: reconcile stale TODO.md entry + add Renovate storybook
+  grouping (#285)`), tag `v1.24.2` already published at this point.
+- **Plan file:** `.claude/plans/worker-generation-v1-vs-enumerated-fox.md`.
+- **Scope handed off from ADR-0014:** target generation v2 (per the repo's own architecture
+  framing); 3 named v1 call sites (`services/duckdb/duckdbClient.ts`,
+  `services/ai/localNlpService.ts`, `services/ai/localEmbeddingService.ts`); no migration plan or
+  timeline beyond "a dedicated migration sprint."
+
+## Execution — 4 stacked PRs
+
+| PR | Branch | Scope | Status at log time |
+|---|---|---|---|
+| #286 | `feat/worker-v2-parity-gate` | Export v2 `duckdb`/`inference` worker handlers, add handler-level tests exercising real logic (previously untested — zero production callers before this sprint), fix a real OPFS-fallback-signal gap found in the process | **Merged** (squash, `ea879e41`) |
+| #287 | `feat/worker-v2-duckdb-migration` | Migrate `duckdbClient.ts` onto WorkerBus v2; delete `workers/duckdbWorker.ts`; add `WorkerBus.terminatePool()`/`hasPool()` | Open, CI green, correction loop quiescent |
+| #288 | `feat/worker-v2-embedding-migration` | Migrate `localEmbeddingService.ts`; cap `inference` pool `maxWorkers` at 2 | Open, CI green (after the missing-export incident below) |
+| #290 | `feat/worker-v2-nlp-migration` | Migrate `localNlpService.ts`; delete `workers/inference.worker.ts` (v1 fully retired); consolidate a duplicate test file | Open, CI green |
+
+Each PR kept the migrated service's public API stable (adapter pattern) — no consumer call site
+outside the 3 named services needed changes across the whole sprint.
+
+## Correction-loop findings (CodeRabbit), all confirmed real and fixed before merge
+
+**PR #286** (2 waves):
+1. QNBS-v3 comment-format nitpicks (multi-line → required single bracketed line) — 3 files.
+2. **Major:** `initDuckDb()`'s OPFS-unavailable catch block silently swallowed the failure instead
+   of surfacing it (v1 had an out-of-band `OPFS_FALLBACK` message; v2 had none). Fixed via the
+   existing progress channel.
+3. **Major** (second wave, outside-diff-range comment on the PR#286 fix itself): the new
+   `opfsConnection?.close()` cleanup could itself reject and abort the fallback path, undoing the
+   fix it was part of. Fixed by making cleanup best-effort (its own try/catch).
+
+**PR #287** (1 wave, 4 findings):
+1. **Critical:** `handleQuery`/`handleExec` silently dropped `params` — an already-live bug
+   breaking `services/ai/telemetryService.ts`'s parameterized `INSERT`. Fixed via DuckDB-WASM
+   prepared statements.
+2. **Major:** a respawned `duckdb` pool worker had no `connection` (fresh module state after
+   `minWorkers:0` idle-termination), failing every query with "DuckDB not initialized." Fixed via
+   transparent re-init-and-retry.
+3. **Major:** `WorkerBus.terminatePool()` didn't settle tasks already routed to the removed pool —
+   their result promises would await forever. Fixed via task→pool tracking + cancellation.
+4. **Major:** `ensureDuckDbPool()` assumed a non-null bus always has every pool, so any call after
+   `terminatePool('duckdb')` would fail `NO_POOL` permanently. Fixed via `hasPool()` +
+   re-registration.
+
+**PR #288 → production incident (not a review-bot finding — a real deployment failure):**
+`services/ai/localEmbeddingService.ts` imported `ensureInferencePool` from `workerBusManager.ts`,
+which was never actually defined there. Invisible to Vitest (the consumer test mocks the whole
+module) and to local `tsgo` typecheck (root cause not fully understood — flagged as a follow-up).
+Two consecutive Vercel deployments failed with only a generic error; the first local repro attempt
+(`pnpm run build`) misleadingly succeeded because **it is not the command Vercel actually runs**
+(`vercel.json`'s `buildCommand` is `pnpm run build:edge`, which sets `DEPLOY_TARGET=edge` and runs
+`scripts/sync-deploy-base.mjs` first). Reproducing the *exact* command
+(`NODE_OPTIONS=--max-old-space-size=3072 pnpm run build:edge`) immediately surfaced rolldown's
+`[MISSING_EXPORT]` error. Fixed by adding `ensureInferencePool()`; verified via a second clean
+`build:edge` run before closing out. `vercel.json`'s `git.deploymentEnabled` was briefly set to
+`false` mid-investigation (PR #289) and reverted once root-caused — net diff of that PR is a
+`TODO.md` incident write-up, no functional change.
+
+## Final verification (this doc's own sprint, PR #291 — docs cleanup)
+
+```bash
+$ pnpm exec tsx scripts/audit-feature-parity.ts
+=== Summary ===
+Total flags: 22
+Critical errors: 0
+Warnings: 0
+✓ Audit passed — all flags consistent
+```
+
+- `docs/adr/0015-worker-generation-consolidation.md` — new ADR, supersedes 0014.
+- `docs/adr/0014-worker-generation-duplication.md` — status line changed to `Superseded by 0015`
+  (body left untouched, per this repo's own "supersede, don't edit history" convention).
+- `docs/adr/README.md` — index gained rows 0010–0015 (0010–0014 were pre-existing files missing
+  from the index before this sprint; unrelated drift, fixed opportunistically).
+- `CLAUDE.md`/`AGENTS.md` — directory map, WorkerBus v2 section, DuckDB section, Known Technical
+  Debt all updated; fixed 2 pre-existing doc-truth bugs found while reading the WorkerBus v2 source
+  (`WorkerHandlerContext.emitProgress` is a flat function, not `context.progress.emit(...)`; no
+  `background` priority tier exists, only `critical > high > normal > low`).
+- `TODO.md` — F-14 entry marked done with the PR chain; a genuinely stale "Tag v1.24.2" entry
+  (already tagged/released, unrelated to this sprint) also caught and fixed while in the file.
+- `AUDIT.md` — F-14 and F-11 (same stale-tag issue) findings updated to resolved.
+- `CHANGELOG.md` — `[Unreleased]` section added (Changed/Fixed/Removed) covering the full sprint.
+
+## Known, deliberately unresolved
+
+- **`WorkerBus.runTask()` doesn't enforce `timeoutMs`** — confirmed via inspection (no timer on
+  either the bus or worker-side bootstrap rejects a hung task). Pre-existing, not introduced by
+  this sprint; scoped out to keep this migration bounded to what ADR-0014 named. Tracked in
+  ADR-0015 and `TODO.md`.
+- **Why local `tsgo` typecheck didn't catch the missing-export bug** — genuinely unresolved; worth
+  a follow-up look at whether a project-reference or cache-behavior gap exists, since it's the kind
+  of thing that could mask a real error again.