9 Commits

Include renames

Author	SHA1	Message	Date
ZacharyZhang-NY	7bdf50a716	Bump version to 0.1.1 ... Fix round on top of v0.1.0: installers persist PATH themselves, install.ps1 strict-mode crash fixed, /feedback opens GitHub issues, moon-phase waiting spinner, Changelog feature excised.	2026-07-18 12:33:48 -04:00
ZacharyZhang-NY	48e7f0e338	Bump windows crate 0.61 -> 0.62 (fixes the Windows release build) ... The third Windows release failure was a genuine cross-version type mismatch: process-wrap 9.1.0 wraps windows 0.62's PROCESS_CREATION_FLAGS in its CreationFlags wrapper, while the workspace pinned windows 0.61 — the CREATE_NEW_PROCESS_GROUP | CREATE_NO_WINDOW constants we pass came from a different nominal type. Aligning the workspace on 0.62 leaves a single windows crate in the graph. Windows code cannot be compiled on this host (a full cross-typecheck dies in ring's C build), so the change is verified by auditing every windows-crate item our cfg(windows) code imports (25 items across 9 files) plus all seven Win32_* feature names against the actual windows-0.62.2 registry sources — all present — and by confirming process-wrap's CreationFlags field is the same 0.62 type our call site now names.	2026-07-18 05:52:48 -04:00
ZacharyZhang-NY	86e3724310	F8: distribution and GitHub-Releases self-update ... - .github/workflows/release.yml: on tag v* build all 5 targets (macOS arm64/x86_64, Linux arm64/x86_64 incl. free arm runners, Windows x86_64) with the release-dist profile, archive kigi-<version>-<triple> with LICENSE/NOTICE/THIRD-PARTY-NOTICES, generate SHA256SUMS, publish the release (prerelease for tags containing '-'), with a tag↔workspace version guard. - install.sh / install.ps1 (repo root): platform detection, latest or --version download from GitHub Releases, SHA-256 verification against SHA256SUMS, install into the kigi home's downloads/ + bin/kigi symlink (the same layout the self-updater manages), smoke test, PATH guidance. - kigi-update rewritten onto the GitHub Releases API (documented wire shape; stable=/latest, alpha=semver-max across the list, pinned=/tags): SHA-256 gate before any binary swap, tar.gz/zip extraction per platform, atomic bin/kigi symlink swap, channel/rollback semantics and the KIGI_AUTO_UPDATE gate preserved verbatim; every x.ai/GCS/npm endpoint deleted, npm/gh-release installers removed, legacy grok/agent links retired on install. kigi-env owns the update base URL with a KIGI_UPDATE_BASE_URL override (this is what the test artifact server injects). - .cargo/config.toml: removed the non-portable neoverse-v2 CPU pin on Linux arm64 (fleet-specific); RELRO/NX hardening link-args now apply to the gnu targets too, matching the release-dist profile's contract. - THIRD-PARTY-NOTICES regenerated via cargo-about (about.toml + template); the M0 hand-built file is dropped and README points at the generated one. docs/RELEASE.md carries the release checklist. - Deleted xAI-era leftovers: kigi-tui/scripts/install*.{sh,ps1} (x.ai CDN) and the @xai-official/grok npm skeleton (PRD F8: no npm). Gates: fmt clean; workspace check/clippy 0/0 (--locked, -D warnings); kigi-update 58 lib + 86 integration tests green; deny ok; release-dist build of kigi-bin succeeds and reports 'kigi 0.1.0'.	2026-07-18 00:54:53 -04:00
ZacharyZhang-NY	5e4e24db99	M2 audit: excise managed connectors and xAI media-gen tools ... Managed connectors (grok.com MCP admin) removed root-and-branch: - The managed-MCP fetch/injection pipeline is gone, including the whole kigi-shell-session-support crate (managed-config fetch client, gateway tool catalog + dispatch, header injection, refresh task), reactive managed re-auth, mcp_doctor's grok.com-source discovery, and the [managed_mcps] config surface. - TUI: the 'Managed by grok.com' section, connectors URL/deep-link, Action::OpenManagedConnectors, and session_team_id are gone. Local MCP management (list/toggle/add/remove/auth/tools) is fully intact. - Kept as LOCAL policy: managed-settings.json MCP allow/deny enforcement, the multi-source local MCP merge, folder-trust gating. PluginOrigin Project/User labels kept (they tag locally discovered plugin dirs). imagine/media-gen tools (xAI image/video generation) removed: - image_gen, image_edit, video_gen, image_to_video, reference_to_video implementations, registrations, ToolKind/ToolInput/Output variants (serde-safe), config plumbing end to end, ZDR video machinery, /imagine + /imagine-video commands and guidance text, the bundled imagine skill (added to legacy cleanup so user installs delete it), and the media-gen render path. - Kept: image INPUT (paste/attach, [Image #N] meta, pdf/image fetch, clipboard wrap), generic media-ref rendering, and the generic tool 401-retry machinery (tests renamed, assertions unweakened). - deploy_app stays: it is a permanently-disabled local stub deploying nowhere. 121 files changed, 8 deleted. Gates: workspace check/clippy 0/0, fmt, deny ok; suites green (tools 2554, shell 4862, tui 6608, workspace 1042). Remaining grok.com strings live only in the auth-method ids and changelog archives (§9/M3 sweep).	2026-07-17 23:45:05 -04:00
ZacharyZhang-NY	fa75eb139a	M2 audit: excise the Computer Hub stack — Kigi's last remote-cloud surface ... Removed root-and-branch for the zero-egress guarantee (the hub was xAI's remote-workspace/cloud-sandbox service): - Crates deleted: kigi-computer-hub-core, kigi-computer-hub-sdk, kigi-computer-hub-mcp-adapter, kigi-workspace-client (hub-proxied workspace RPC client), and kigi-tracing (its sole network path was the OTLP gRPC exporter; zero consumers remained). kigi-tracing-macros (purely local) stays. - kigi-workspace: every hub surface deleted — hub server/channel/auth, HITL-over-hub permissions, donation/metrics pumps, file upload RPCs, hub tool-snapshot merge (resolve pipeline is MCP-only now), WorkspaceOps::Proxy. Local worktrees, sessions, leader IPC, MCP, and the ACP permission prompt path are untouched; LocalRegistry re-homed into kigi-tool-runtime on the existing ToolDyn types so in-process tool dispatch is unchanged. - kigi-shell: leader workspace-exposure control surface (incl. the wss://computer-hub... URL), [hub] config, ObservabilityBridge, hub WebSocket proxy, dead OTLP config knobs. ClientMode::Headless (never constructed) removed. - kigi-tui/bin: hidden `kigi workspace` command removed (`kigi worktree` stays). - Renames: --xai-api-base-url → --api-base-url / KIGI_API_BASE_URL / [endpoints] api_base_url (serde alias keeps old configs working; the flag feeds BYOK/custom-endpoint routing, not main inference); grok_version → kigi_version in inspect/models-cache/trace metadata (old caches self-heal via version-mismatch refetch). - Dependency tree: dropped fastrace*, opentelemetry-otlp/http/proto, tokio-tungstenite from the workspace; fixed the 4 real useless_format violations the fastrace lint allowance was masking and removed the allowance. - marketplaceAllowlist kept: it gates the LOCAL plugin-marketplace feature, not an xAI service. Known §9 leftover (deliberate, for the M3 sweep): the BYOK default base URL string. Gates: workspace check/clippy 0/0, fmt, deny ok; suites green (workspace 1042, shell 4918, tui 6634, tools 2608, tool-runtime 47, mcp 154).	2026-07-17 22:34:10 -04:00
ZacharyZhang-NY	9e70a8fa18	Silence the macOS __eh_frame linker note; wire kigi-bin into workspace lints ... macOS ld cannot encode >16MB of __eh_frame in its compact unwind table and says so on every debug link of the large binary. All profiles build with panic=abort, so Rust never unwinds and the note's exception-handling caveat does not apply. Allow rust.linker_messages at the workspace level with that rationale, and give kigi-bin the missing [lints] workspace = true (it was not inheriting workspace lints at all). Also drop the stale xAI authors field and Grok wording from the kigi-bin manifest.	2026-07-17 18:22:00 -04:00
ZacharyZhang-NY	ea0ce9d15f	F3: Kimi inference pipeline + full grok cloud-surface excision ... Sampler / inference (PRD F3): - kimi_compat.rs: single adaptation point for the Kimi chat/completions dialect (thinking-field mapping, model_id stripping, empty-content tool-call message fix, stream_options.include_usage), with kimi-cli source citations - Rate-limit handling reworked for Kimi/Moonshot semantics; UA kigi/{version} - /models replaces the xAI models-v2 endpoint everywhere; idle model refresh carries X-Msh-* device headers only (X-XAI-Token-Auth and x-grok-client-mode/CLIENT_MODE_HEADER machinery deleted) Cloud-surface excision (PRD §5, zero-egress): - remote/ conversations lane, cli-chat-proxy-types crate, prod/ dir, share command, credit bar: deleted (single local session lane; paginate() replaces merge_and_paginate) - Subscription/tier gate stack deleted end-to-end: AppView gate/tier/team/ZDR fields, app/subscription.rs watch loop, dispatch/billing.rs paywall + SuperGrok upsell, free-usage-exhausted chain, tier-restricted commands, GateInfo, RemoteSettings gate fields, SettingsUpdateNotification gate fields - /privacy + coding-data-sharing setting deleted (backed by a dead xAI RPC; Kigi is zero-egress — nothing to share or retain remotely) Auth UX correctness (user-reported): - Device-flow fixtures now mirror the live Kimi payload shape (https://www.kimi.com/code/authorize_device?user_code=..., verified against auth.kimi.com); the fabricated auth.kimi.com/device?code=... URLs are gone - open_browser_detached is a no-op under cfg(test): unit tests drove wiremock fixture URLs into the real browser (root cause of the "garbage mock link" ABCD-1234 tabs) - Welcome/pager-minimal rebrand: Grok Build -> Kigi, grok.com -> kimi.com, "Sign in to Grok" -> "Sign in to Kimi"	2026-07-17 16:05:51 -04:00
ZacharyZhang-NY	021b82443d	M1/F1: Kimi Code OAuth device-code flow ... Replace the xAI OAuth stack with the Kimi device authorization grant: - kimi_oauth.rs wire layer (device_authorization + token poll + refresh against kigi_env::oauth_host(); client_id per PRD; retryable statuses 429/5xx with backoff; expired_token restarts authorization) - X-Msh-Device-{Name,Model,Id} headers; device_id minted uuid4-hex at ~/.kigi/device_id (0600) - Storage: system keyring service `kigi`, entry `oauth/kimi-code` (macOS/Windows native backends), atomic-file fallback under ~/.kigi; official client's keyring/~/.kimi never touched - Refresh manager: 60s tick, threshold max(300, expires_in*0.5), 401-tombstone keyed by rejected refresh token with 300s cooldown and rotation auto-clear, cross-process lock with sibling-adoption triple-check, sleep/wake forced refresh - Deleted xAI machinery: enterprise OIDC (PKCE/JWKS/teams), devbox login, external auth provider, JWT tier gating + subscription paywall stack, X-XAI-Token-Auth marker headers, ZDR gates, /user enrichment - kigi login / TUI /login both drive the device flow; login-host display now derives from kigi_env::oauth_host() - 264 auth unit/wiremock tests; live contract probe of auth.kimi.com/api/oauth/device_authorization matches the wire shapes Gates: check/clippy --all-targets clean, fmt, deny ok, kigi-shell lib 5131 tests green.	2026-07-17 07:37:29 -04:00
ZacharyZhang-NY	d6c20fc13f	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).	2026-07-17 05:31:01 -04:00