feat(v2): OneCLI 0.3.1 — approvals, credential collection, threaded routing

Three features built on top of @onecli-sh/sdk 0.3.1, landed together because
they share wiring surfaces (session DB schema, delivery dispatcher, Chat SDK
bridge, channel adapter contract).

## OneCLI manual-approval handler

* `src/onecli-approvals.ts` — long-polls OneCLI via the SDK's
  `configureManualApproval`; on each request, delivers an `ask_question` card
  to the admin agent group's first messaging group, persists a
  `pending_approvals` row, and waits on an in-memory Promise resolved by the
  admin's button click or an expiry timer. Expired cards are edited to
  "Expired (...)" and a startup sweep flushes any rows left over from a
  previous process.
* Short 11-byte approval id (`oa-<8 base36>`) instead of the SDK's UUID so the
  Telegram 64-byte `callback_data` limit is respected; the OneCLI UUID stays
  in the persisted payload for audit.
* Migration 003 consolidated: `pending_approvals` now has the OneCLI-aware
  columns from the start (`agent_group_id`, `channel_type`, `platform_id`,
  `platform_message_id`, `expires_at`, `status`), `session_id` relaxed to
  nullable so cross-session approvals fit.
* `handleQuestionResponse` in `src/index.ts` now routes OneCLI approvals
  through `resolveOneCLIApproval` before falling back to the
  session-bound approval path.

## Credential collection from chat

New `trigger_credential_collection` MCP tool — the agent researches a
third-party API, calls the tool with `{name, hostPattern, headerName,
valueFormat, description}`, and blocks until the host reports saved, rejected,
or failed. The credential value never enters the agent's context: the user
submits it into a Chat SDK Modal on the host side, the host writes it to
OneCLI via a thin facade (`src/onecli-secrets.ts` — shells out to
`onecli secrets create`, shape mirrors the SDK we expect upstream), and only
the status string flows back to the container via a system message.

* `src/credentials.ts` — host-side handler: delivers the card to the
  conversation's own channel (not the admin channel — credential collection
  is a user-facing flow, distinct from admin approval), persists a
  `pending_credentials` row, drives the submit → `createSecret` → notify
  pipeline. Falls back gracefully when the channel doesn't support modals.
* `src/db/credentials.ts` + migration 005: `pending_credentials` table.
* `src/channels/chat-sdk-bridge.ts`: renders a `credential_request` card,
  handles the `nccr:` action prefix by opening a Modal with a TextInput,
  registers an `onModalSubmit` handler for the `nccm:` callback prefix.
* `container/agent-runner/src/mcp-tools/credentials.ts`: the blocking MCP
  tool, mirroring the `ask_user_question` polling pattern.
* `container/agent-runner/src/db/messages-in.ts`: `findCredentialResponse`
  helper to pick up the system message the host writes back.

## Threaded adapter routing

The destination layer previously didn't carry thread context, so agent replies
to Discord always landed in the root channel regardless of which thread the
inbound came from.

* `ChannelAdapter.supportsThreads: boolean` — declared by every channel skill
  at `createChatSdkBridge`. Threaded: Discord, Slack, Teams, Google Chat,
  Linear, GitHub, Webex. Non-threaded: Telegram, WhatsApp Cloud, Matrix,
  Resend, iMessage.
* `src/router.ts`: non-threaded adapters strip `threadId` at ingest (threads
  collapse to channel-level sessions). Threaded adapters override the
  wiring's `session_mode` to `'per-thread'` so each thread = a session
  (except `agent-shared`, which is preserved as a cross-channel intent the
  adapter can't know about).
* `session_routing` table in `inbound.db` — single-row default reply routing
  written by the host on every container wake from
  `session.messaging_group_id` + `session.thread_id`. Forward-compat
  `CREATE TABLE IF NOT EXISTS` handles older session DBs lazily.
* `container/agent-runner/src/db/session-routing.ts` — container-side reader.
* `send_message` / `send_file` / `ask_user_question` / `send_card` /
  scheduling tools all default their routing (channel, platform, **and**
  thread) from the session when no explicit `to` is given. Explicit `to`
  uses the destination's channel with `thread_id = null` (cross-destination
  sends start a new conversation elsewhere).
* `poll-loop.ts::sendToDestination` (the final-text single-destination
  shortcut) now inherits `thread_id` from `RoutingContext` too — this was
  the root cause of Discord replies landing in the root channel even after
  `send_message` was wired correctly.

## Related cleanups

* `src/container-runner.ts`: OneCLI agent identifier switched from the lossy
  folder-derived string to `agent_group.id`, making `getAgentGroup(externalId)`
  a trivial reverse lookup for per-agent scoping.
* `wakeContainer` race fix via an in-flight promise map — concurrent wakes
  during the async buildContainerArgs / OneCLI `applyContainerConfig` window
  no longer double-spawn containers against the same session directory.
* `src/db/db-v2.test.ts`: dropped the brittle `expect(row.v).toBe(N)` schema
  version assertion — it had to be bumped on every migration addition.

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

src/db/migrations/003-pending-approvals.ts

@@ -1,18 +1,39 @@
 import type { Migration } from './index.js';
 
+/**
+ * `pending_approvals` table — host-side records for any approval-requiring
+ * request. Used by:
+ *   - install_packages / request_rebuild / add_mcp_server  (session-bound,
+ *     `session_id` set, status stays at default 'pending' until handled)
+ *   - OneCLI credential approvals from the SDK `configureManualApproval`
+ *     callback (session_id may be null, action='onecli_credential').
+ *
+ * The OneCLI-specific columns (`agent_group_id`, `channel_type`, `platform_id`,
+ * `platform_message_id`, `expires_at`, `status`) let the host edit the admin
+ * card when a request expires and sweep stale rows on startup.
+ */
 export const migration003: Migration = {
   version: 3,
   name: 'pending-approvals',
   up(db) {
     db.exec(`
       CREATE TABLE pending_approvals (
-        approval_id  TEXT PRIMARY KEY,
-        session_id   TEXT NOT NULL REFERENCES sessions(id),
-        request_id   TEXT NOT NULL,
-        action       TEXT NOT NULL,
-        payload      TEXT NOT NULL,
-        created_at   TEXT NOT NULL
+        approval_id         TEXT PRIMARY KEY,
+        session_id          TEXT REFERENCES sessions(id),
+        request_id          TEXT NOT NULL,
+        action              TEXT NOT NULL,
+        payload             TEXT NOT NULL,
+        created_at          TEXT NOT NULL,
+        agent_group_id      TEXT REFERENCES agent_groups(id),
+        channel_type        TEXT,
+        platform_id         TEXT,
+        platform_message_id TEXT,
+        expires_at          TEXT,
+        status              TEXT NOT NULL DEFAULT 'pending'
       );
+
+      CREATE INDEX idx_pending_approvals_action_status
+        ON pending_approvals(action, status);
     `);
   },
 };

src/db/migrations/005-pending-credentials.ts

@@ -0,0 +1,34 @@
+import type { Migration } from './index.js';
+
+/**
+ * `pending_credentials` — backs the trigger_credential_collection flow.
+ * One row per in-flight credential request; status transitions
+ * pending → submitted → saved | rejected | failed.
+ */
+export const migration005: Migration = {
+  version: 5,
+  name: 'pending-credentials',
+  up(db) {
+    db.exec(`
+      CREATE TABLE pending_credentials (
+        id                   TEXT PRIMARY KEY,
+        agent_group_id       TEXT NOT NULL REFERENCES agent_groups(id),
+        session_id           TEXT REFERENCES sessions(id),
+        name                 TEXT NOT NULL,
+        type                 TEXT NOT NULL,
+        host_pattern         TEXT NOT NULL,
+        path_pattern         TEXT,
+        header_name          TEXT,
+        value_format         TEXT,
+        description          TEXT,
+        channel_type         TEXT NOT NULL,
+        platform_id          TEXT NOT NULL,
+        platform_message_id  TEXT,
+        status               TEXT NOT NULL DEFAULT 'pending',
+        created_at           TEXT NOT NULL
+      );
+
+      CREATE INDEX idx_pending_credentials_status ON pending_credentials(status);
+    `);
+  },
+};

src/db/migrations/index.ts

@@ -5,6 +5,7 @@ import { migration001 } from './001-initial.js';
 import { migration002 } from './002-chat-sdk-state.js';
 import { migration003 } from './003-pending-approvals.js';
 import { migration004 } from './004-agent-destinations.js';
+import { migration005 } from './005-pending-credentials.js';
 
 export interface Migration {
   version: number;
@@ -12,7 +13,7 @@ export interface Migration {
   up: (db: Database.Database) => void;
 }
 
-const migrations: Migration[] = [migration001, migration002, migration003, migration004];
+const migrations: Migration[] = [migration001, migration002, migration003, migration004, migration005];
 
 export function runMigrations(db: Database.Database): void {
   db.exec(`