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/codegen/kigi-sandbox/tests/integration_test.rs

@@ -0,0 +1,105 @@
+//! Integration tests for kigi-sandbox.
+//!
+//! Note: `Sandbox::apply()` is irreversible and process-wide, so we cannot
+//! test actual kernel enforcement in standard `#[test]` functions (they share
+//! a process). Use the `sandbox_smoke_test` example for enforcement testing.
+//! These tests verify the API contracts, config loading, and support detection.
+
+// `support_info` is only available with the `enforce` feature (it returns a
+// nono type), so gate this test the same way.
+#[test]
+#[cfg(all(feature = "enforce", unix))]
+fn test_support_info() {
+    // Verify that nono can report platform support status without applying
+    let support = kigi_sandbox::SandboxManager::support_info();
+    // On macOS and Linux 5.13+, this should be supported
+    // On other platforms, it gracefully reports unsupported
+    println!(
+        "Sandbox support: supported={}, details={}",
+        support.is_supported, support.details
+    );
+    // We don't assert is_supported because CI may run on any platform
+}
+
+// `to_capability_set` is only available with the `enforce` feature.
+#[test]
+#[cfg(all(feature = "enforce", unix))]
+fn test_profile_capability_set_construction() {
+    use kigi_sandbox::ProfileName;
+
+    // Use CWD as workspace — guaranteed to exist
+    let workspace = std::env::current_dir().expect("cwd");
+
+    // All profiles should produce valid CapabilitySets without panicking
+    for profile in [
+        ProfileName::Workspace,
+        ProfileName::ReadOnly,
+        ProfileName::Strict,
+        ProfileName::Off,
+    ] {
+        let result = profile.to_capability_set(&workspace);
+        assert!(
+            result.is_ok(),
+            "Profile {:?} failed to build CapabilitySet: {:?}",
+            profile,
+            result.err()
+        );
+    }
+}
+
+#[test]
+fn test_sandbox_manager_lifecycle() {
+    use kigi_sandbox::{ProfileName, SandboxManager};
+
+    let workspace = std::env::current_dir().expect("cwd");
+
+    // Off profile: apply should succeed without actually sandboxing
+    let mut manager = SandboxManager::new(ProfileName::Off, &workspace);
+    assert!(!manager.is_applied());
+    assert!(!manager.restrict_child_network());
+
+    let result = manager.apply(&workspace);
+    assert!(result.is_ok());
+    // Off profile doesn't actually apply
+    assert!(!manager.is_applied());
+}
+
+#[test]
+fn test_sandbox_logger() {
+    use kigi_sandbox::{SandboxEvent, SandboxLogger};
+
+    let logger = SandboxLogger::new();
+
+    // Log some events (use violation events — profile_applied requires a resolved profile)
+    logger.log(SandboxEvent::fs_violation("workspace", "/tmp/test", "read"));
+    logger.log(SandboxEvent::fs_violation(
+        "workspace",
+        "/etc/shadow",
+        "write",
+    ));
+    logger.log(SandboxEvent::net_violation("strict", "evil.com:443"));
+
+    // Check metrics
+    assert_eq!(logger.metrics().fs_violation_count(), 2);
+    assert_eq!(logger.metrics().net_violation_count(), 1);
+
+    // Take events drains the buffer
+    let events = logger.take_events();
+    assert_eq!(events.len(), 3);
+
+    // Buffer is now empty
+    let events2 = logger.take_events();
+    assert!(events2.is_empty());
+}
+
+#[test]
+fn test_should_restrict_child_network_default() {
+    // Before any sandbox is applied, child network should not be restricted
+    // Note: this test may interfere with other tests if they set the global.
+    // In practice, the global is set once at process startup and never unset.
+    // For testing, we just verify the default state.
+    //
+    // We can't meaningfully test the "set" path without applying a sandbox
+    // (which is irreversible), so we verify the default is false.
+    assert!(!kigi_sandbox::should_restrict_child_network());
+}