fix(fs-search): address the second-round #1119 review

- inline the collect() identity wrapper now that both streams use the
  seam's diagnostic-tail shape
- resolve the packaged rg path lazily at the first call (memoized):
  @vscode/ripgrep resolves its platform package at module evaluation, so a
  static import turned a missing/corrupt platform package into a Loader
  composition failure instead of the documented per-call SEARCH_FAILED
- classify synchronous spawn-creation throws (a NUL in argv, an abort
  racing the pre-check, a rejected resolution) into SEARCH_FAILED /
  SEARCH_ABORTED instead of leaking raw errors
- correct the stderrMaxBytes contract: the stderr excerpt is embedded in
  SEARCH_* error messages, not hidden from the model
- export virtualManifest and pin its three acceptance paths (prefix hit,
  pnpm-11 truncated-name content-scan fallback, both miss) with fixture
  unit tests

Tests: rg-path.spec.ts (resolution failure + memoized rejection),
tools.spec.ts spawn-creation classification, notices spec virtualManifest.

packages/fs/tool-fs-search/tests/rg-path.spec.ts

@@ -0,0 +1,37 @@
+/**
+ * Failure-path tests for the lazy packaged-ripgrep resolution. The success
+ * path (the real `@vscode/ripgrep` module) is exercised throughout
+ * tools.spec.ts; here the module is mocked to throw at evaluation, proving a
+ * missing or corrupt platform package (`--omit=optional`, partial install)
+ * surfaces as a per-call `SEARCH_FAILED` — not a composition-load failure.
+ */
+
+import { describe, expect, it, vi } from 'vitest'
+import { Context } from 'cordis'
+import { CallId } from '@deepseek-ai/dsh-llm'
+import type { ToolExecution } from '@deepseek-ai/dsh-tools'
+import { resolveRgPath, runRipgrep } from '@deepseek-ai/dsh-tool-fs-search'
+
+// Any access to the mocked module's surface throws — the shape a missing
+// platform package produces at module evaluation.
+vi.mock('@vscode/ripgrep', () => new Proxy({}, {
+  get() {
+    throw new Error('platform package @vscode/ripgrep-win32-x64 is not installed')
+  },
+}))
+
+describe('lazy packaged-ripgrep resolution', () => {
+  it('fails the first search call with SEARCH_FAILED instead of failing module load', async () => {
+    // The resolution rejects before any spawn, so no subprocess service is needed.
+    const controller = new AbortController()
+    const exec = { signal: controller.signal, name: 'glob', callId: CallId('missing-platform-package') } as unknown as ToolExecution
+
+    await expect(runRipgrep(new Context(), exec, 'glob', ['--files'], 1_000_000, 3_000, 64 * 1024))
+      .rejects.toMatchObject({ name: 'SearchError', code: 'SEARCH_FAILED' })
+  })
+
+  it('keeps failing every subsequent call (the resolution is memoized)', async () => {
+    await expect(resolveRgPath()).rejects.toThrow(/platform package/)
+    await expect(resolveRgPath()).rejects.toThrow(/platform package/)
+  })
+})

packages/fs/tool-fs-search/tests/tools.spec.ts

@@ -32,6 +32,7 @@ import {
   presentGrepCall,
   presentGrepResult,
   previewLine,
+  resolveRgPath,
   runRipgrep,
   sampleAcrossTopLevel,
   toWorkdirRelative,
@@ -468,6 +469,48 @@ describe('workdir derivation and signal forwarding', () => {
     expect(text(result)).toContain('could not start')
   })
 
+  it('classifies a synchronous spawn-creation throw as SEARCH_FAILED', async () => {
+    // Node's spawn() throws synchronously for a NUL in argv, and the local
+    // impl can throw synchronously for other invalid specs. Creation-time
+    // failures must join the error vocabulary instead of escaping raw.
+    const { ctx, subprocess } = await setup()
+    subprocess.handler = () => { throw new Error('spawn ERR_INVALID_ARG_VALUE') }
+
+    const result = await call(ctx, 'grep', { pattern: 'x' })
+
+    expect(result.isError).toBe(true)
+    expect(result.error).toMatchObject({ info: { name: 'SearchError', code: 'SEARCH_FAILED' } })
+    expect(text(result)).toContain('could not start')
+  })
+
+  it('classifies a synchronous spawn-creation throw after an abort as SEARCH_ABORTED', async () => {
+    // The local impl can throw synchronously when the signal aborts between
+    // the pre-spawn check and the spawn call; no process was launched, so the
+    // abort is the reportable cause.
+    const { ctx, subprocess } = await setup()
+    const controller = new AbortController()
+    subprocess.handler = () => {
+      controller.abort('timeout')
+      throw new Error('aborted during spawn')
+    }
+
+    const result = await call(ctx, 'glob', { pattern: '*' }, { signal: controller.signal })
+
+    expect(result.isError).toBe(true)
+    expect(result.error).toMatchObject({ info: { name: 'SearchError', code: 'SEARCH_ABORTED' } })
+    expect(text(result)).toContain('aborted before completion')
+  })
+
+  it('resolves the packaged ripgrep path lazily, once per process', async () => {
+    // The module must not touch @vscode/ripgrep at load (a missing platform
+    // package would otherwise fail the whole composition), and repeated
+    // resolution reuses the first result. The resolution-failure path is
+    // pinned separately in rg-path.spec.ts.
+    await setup()
+    expect(await resolveRgPath()).toBe(rgPath)
+    expect(resolveRgPath()).toBe(resolveRgPath())
+  })
+
   it('rejects when the subprocess implementation drops a requested collect stream', async () => {
     const { ctx, subprocess } = await setup()
     subprocess.dropReaders = true