feat: in-app Orchestrator (Phase 2) — multi-agent conductor

Brings the deterministic Han-flow conductor into BooCode: launch any read-only
flow from BooChat or BooCoder, watch each agent stream live in a Paseo-style
run pane, get an evidence-disciplined report — on local Qwen, persisted and
resumable. Read-only enforced hard via qwen --approval-mode plan (orchestrator
tasks fail closed if qwen is unavailable; never fall to write-capable native).

Backend (apps/coder): re-homed conductor defs, flow_runs/flow_steps schema,
flow-runner + dispatcher onTaskTerminal hook, restart-resume, runs routes
(launch/list/get/cancel), user-channel WS. Contracts: two flow_run_* frames.
Web: orchestrator pane kind + OrchestratorPane, Workflow button + slash flows
(BooChat/BooCoder parity), FlowLauncherDialog, "New Orchestrator" in the + and
split menus, runs history + export. Plan: openspec/changes/orchestrator.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

conductor/package.json

@@ -0,0 +1,11 @@
+{
+  "name": "@boocode/conductor",
+  "version": "0.1.0",
+  "private": true,
+  "type": "module",
+  "description": "Deterministic code conductor for multi-agent flows, modelled on Han. Code owns the sequence; Han agents run as bounded single-task workers on a local model via opencode.",
+  "scripts": {
+    "research": "tsx src/run.ts",
+    "typecheck": "tsc --noEmit"
+  }
+}