chore: drop obsolete scripts and a stale dev dependency, make knip report clean

- Nine one-off scripts from January and February that nothing references:
  three Ralph wizard drivers that click the start-screen button removed in
  1.50 (against the production port, with a personal case name), a respawn
  monitor with a hardcoded session id, link-detection experiments for
  patterns that no longer exist, and two screenshot and data helpers.
- @types/uuid: uuid 14 ships its own types and TypeScript already
  resolves them from the package.
- config/knip.json now describes the workspace layout it runs in (its
  top-level entry and project keys were being ignored), names the manual
  scripts as entries, lists the system binaries tests shell out to, and
  honours @knipignore. `npm run knip` reports nothing; CLAUDE.md says so.
- Two more unused tap helpers in the mobile test toolkit.
- Docs that pointed at files which no longer exist: the browser testing
  guide (four deleted test files), the orchestrator panel's file name, two
  spawn modules in the Ralph guide, the respawn mock utilities.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>

docs/browser-testing-guide.md

@@ -8,8 +8,8 @@ This guide documents the browser testing infrastructure, framework comparison re
 # Run standalone benchmark (recommended - avoids vitest hook issues)
 npx tsx scripts/browser-comparison.mjs
 
-# Run existing browser E2E tests
-npm test -- test/browser-e2e.test.ts
+# Run the browser suite (Playwright; the files are listed in config/test-suites.ts)
+npm run test:browser
 ```
 
 ## Framework Comparison Results
@@ -67,7 +67,7 @@ We tested three browser automation frameworks against the Codeman web UI:
    });
    ```
 
-3. **Use the existing browser-e2e.test.ts pattern** which uses agent-browser CLI commands via `execSync` (avoids async hook issues)
+3. **Drive agent-browser through its CLI** with `execSync`, as `scripts/browser-comparison.mjs` does (avoids async hook issues)
 
 ## Test File Structure
 
@@ -93,10 +93,8 @@ fixed ports 3180-3182.
 
 | File | Framework | Status |
 |------|-----------|--------|
-| `test/browser-e2e.test.ts` | agent-browser | ✅ Working |
-| `test/browser-playwright.test.ts` | Playwright | ⚠️ Vitest hook issues |
-| `test/browser-puppeteer.test.ts` | Puppeteer | ⚠️ Vitest hook issues |
-| `test/browser-agent.test.ts` | agent-browser | ⚠️ Vitest hook issues |
+| `test/*.browser.test.ts` and the other files in `BROWSER_TEST_GLOBS` (`config/test-suites.ts`) | Playwright | ✅ `npm run test:browser` |
+| `test/mobile/**` | Playwright | ✅ `npm run test:mobile` |
 | `scripts/browser-comparison.mjs` | All three | ✅ Working (standalone) |
 
 ## Framework-Specific Patterns

docs/orchestrator-loop-architecture.md

@@ -363,5 +363,5 @@ The Orchestrator can optionally USE the Ralph Loop internally for phase executio
 | `src/types/orchestrator.ts` | Type definitions |
 | `src/prompts/orchestrator.ts` | Prompt templates |
 | `src/web/routes/orchestrator-routes.ts` | API endpoints |
-| `src/web/public/orchestrator-ui.js` | Frontend panel |
+| `src/web/public/orchestrator-panel.js` | Frontend panel |
 | `src/web/ports/orchestrator-port.ts` | Port interface |

docs/ralph-wiggum-guide.md

@@ -837,8 +837,6 @@ POST /api/sessions/:id/auto-clear
 - `src/ralph-tracker.ts` - Core detection engine
 - `src/ralph-loop.ts` - Task orchestration
 - `src/respawn-controller.ts` - Session cycling
-- `src/spawn-orchestrator.ts` - Autonomous agent lifecycle (uses RalphTracker for completion)
-- `src/spawn-detector.ts` - Detects `<spawn1337>` tags in terminal output
 - `src/types.ts` - Type definitions
 
 ---

docs/respawn-state-machine.md

@@ -79,5 +79,5 @@ Uses temp file for prompt to avoid E2BIG errors with large terminal buffers.
 
 - `test/respawn-scenarios.md` - Comprehensive test scenarios for edge cases
 - `test/respawn-test-plan.md` - Test environment architecture and strategies
-- `test/respawn-test-utils.ts` - Mock utilities (MockSession, MockAiIdleChecker, MockAiPlanChecker)
+- `test/mocks/mock-session.ts` - `MockSession`, the session double the respawn tests drive
 - `test/respawn-analysis.md` - Code coverage analysis and identified issues