M0: compilable skeleton — Kigi 0.1.0 fork surgery

Hard fork of xai-org/grok-build (Apache-2.0) re-targeted as Kigi, an
unofficial Kimi Code CLI community build.

Rename & identity
- 72 xai-*/xai-grok-* crates -> kigi-* (explicit: xai-grok-pager-bin ->
  kigi-bin [binary `kigi`], xai-grok-pager -> kigi-tui; rest mechanical);
  ptyctl, ptyctl-cli, third_party/ unchanged; proto package
  xai.grok.tools.v1 -> kigi.tools.v1
- Config home ~/.kigi (KIGI_SHARE_DIR override), env prefix GROK_* ->
  KIGI_*, `kigi --version` carries the unofficial-community-build notice
- clap identity, help text, startup banner, prompt templates rebranded
  (templates re-encrypted)

Deletions (PRD removal list #5/#6/#7/#9/#10)
- voice input (xai-grok-voice) and all TUI wiring
- telemetry: Mixpanel client, external OTel stream, Sentry, OTLP layers,
  trace/GCS/S3 upload queues (kigi-file-utils halved), workspace upload
  module & dc_log, heap-profile uploader, auth-diagnostics uploader,
  session-analytics halves of feedback; local zero-egress observability
  preserved in new kigi-log crate (unified log, --debug firehose,
  subsystem file logs, opt-in instrumentation)
- announcements (crate, remote-settings fields, TUI surfaces)
- plugin marketplace (crate, sources/browse/CTA/extensions-modal tab);
  direct plugin install/uninstall/update via kigi-agent git_install kept
- relay/gateway/assets endpoints and features (agent relay, headless
  relay transport, gateway bridge, LeaderEnvUrls); leader IPC socket now
  ~/.kigi/leader.sock + KIGI_LEADER_SOCKET, no ws-url derivation
- functional types rehomed instead of deleted: PermissionMode ->
  kigi-config-types, McpInitStrategy -> kigi-mcp, PrCreationSource ->
  session signals, TerminalDiagnostics -> kigi-pager-render, agent_id ->
  shell util

Endpoints
- kigi-env rewritten: single production KigiEndpoints {coding_api_base_url
  https://api.kimi.com/coding/v1 (KIGI_CODE_BASE_URL), oauth_host
  https://auth.kimi.com (KIGI_OAUTH_HOST), update_base_url (GitHub
  Releases API), upgrade_page_url}; GrokBuildEnvironment enum deleted

Toolchain & workspace hygiene
- Rust 1.97.0 pinned; edition 2024; full cargo update; git2 hoisted to
  workspace at 0.21 (Option->Result API migration), quick-xml 0.41
- Root Cargo.toml hand-maintained (PRD §8.1): version 0.1.0 inherited by
  all members, members sorted, unused deps pruned
- cargo-deny advisories gate (deny.toml with documented transitive
  exceptions); CI workflow (check/clippy/fmt/deny/test, macOS+Linux)
- cross-crate test seams re-gated behind `test-support` cargo feature;
  insta snapshot baselines renamed to the kigi_tui prefix
- clippy --workspace --all-targets: zero warnings; fmt clean

Fixes surfaced by the port
- updater probe/installer divergence (bin/kigi vs bin/grok symlink set)
- idle model-metadata refresh dead under KIGI_CODE_BASE_URL override
  (new is_effective_coding_endpoint_url, loopback+override aware)
- macOS symlinked-TMPDIR fixture canonicalization (foreign_sessions,
  fast-worktree); RSS measurement tests serialized via serial_test

Docs & legal (Apache §4)
- NOTICE added (upstream attribution + change statement); THIRD-PARTY
  notices sustained; kigi-tools ported-code notices extended; README,
  CONTRIBUTING, SECURITY, AGENTS.md rewritten

Out of scope for M0 (tracked): Kimi auth/inference (M1), search/fetch,
command parity, config import (M2), Computer Hub excision & final
brand-token sweep (M2), distribution & self-update rewrite (M3).

crates/common/kigi-tool-runtime/src/dispatch.rs

@@ -0,0 +1,68 @@
+//! Object-safe `ToolDispatch` trait — the runtime contract for handling tool calls.
+//!
+//! `Tool` itself is not object-safe (it carries associated `Args` /
+//! `Output` types), so implementations expose a JSON-typed surface and rely on
+//! per-tool adapters to encode/decode at the boundary. The default
+//! `call_terminal` impl drains the stream so the common "I just want the
+//! result" path doesn't have to depend on `futures` internals.
+//!
+//! This crate is upstream of every concrete impl. Doc-comments here describe
+//! trait semantics in terms of "the runtime" or "the implementation" —
+//! concrete dispatch routers live downstream and are intentionally not named
+//! here.
+
+use async_trait::async_trait;
+use futures::StreamExt;
+use serde_json::Value;
+
+use kigi_tool_protocol::ToolId;
+
+use crate::context::ToolCallContext;
+use crate::error::ToolError;
+use crate::tool::{ToolStream, ToolStreamItem, TypedToolOutput};
+
+/// Object-safe tool dispatch interface.
+///
+/// Implementations route the `tool_id` to the correct tool, decode `args`
+/// against the tool's typed `Args`, and return the streaming result as
+/// [`TypedToolOutput`] — preserving model-facing content blocks and
+/// optional chat-completion metadata end-to-end. Raw `Value` only appears
+/// at JSON-RPC wire encode/decode boundaries.
+#[async_trait]
+pub trait ToolDispatch: Send + Sync {
+    /// Streaming dispatch. The returned stream MUST end with exactly one
+    /// `Terminal` item per the [`ToolStream`] invariant.
+    async fn call(
+        &self,
+        tool_id: ToolId,
+        args: Value,
+        ctx: ToolCallContext,
+    ) -> ToolStream<TypedToolOutput>;
+
+    /// Drain the stream and return only the terminal result. Useful for
+    /// callers that don't care about progress chunks.
+    ///
+    /// Default impl pulls items off the stream and discards `Progress`
+    /// items; the first `Terminal` short-circuits. A stream that ends
+    /// without a `Terminal` is a protocol violation by the implementation;
+    /// the default surfaces this as `ToolError::Custom { code:
+    /// "stream_no_terminal", ... }`.
+    async fn call_terminal(
+        &self,
+        tool_id: ToolId,
+        args: Value,
+        ctx: ToolCallContext,
+    ) -> Result<TypedToolOutput, ToolError> {
+        let mut stream = self.call(tool_id, args, ctx).await;
+        while let Some(item) = stream.next().await {
+            match item {
+                ToolStreamItem::Progress(_) => continue,
+                ToolStreamItem::Terminal(result) => return result,
+            }
+        }
+        Err(ToolError::custom(
+            "stream_no_terminal",
+            "dispatch stream ended without a terminal item",
+        ))
+    }
+}