threadwire 0.1.19 → 0.1.21

package/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 ## Unreleased
 
+- Make the checked-in development container portable and secure for direct
+  native Kimi: runtime paths (`DEV_CONTAINER_HOME`, `KIMI_CODE_HOME`) are
+  explicit, portable, and absolute instead of hard-coded `/home/dev`; the
+  immutable agent context mounts from the named external Docker volume
+  `AGENT_CONTEXT_VOLUME` rather than a host path; agent-context links for Kimi
+  go to the configured `KIMI_CODE_HOME`, which may differ from the dev home;
+  direct Kimi auth mounts from the named external volume `KIMI_AUTH_VOLUME`
+  only as narrow subpaths under the configurable `KIMI_AUTH_VOLUME_SUBPATH`
+  (default `.kimi-code`; `credentials` writable, `config.toml` and `device_id`
+  read-only) in the normal `app` service; a dedicated profiled `kimi-auth`
+  service bypasses the normal dev entrypoint, mounts the full auth volume root
+  writable, bootstraps the configured subpath, and runs `kimi login` for
+  interactive authentication/refresh. The Kimi Code CLI in the dev image is
+  pinned to `0.34.0` with the same integrity verification used in production.
+  Production runtime files remain unchanged.
 - Resolve native Kimi through the normal `PATH` (`kimi`) instead of requiring
   `/usr/local/bin/kimi`; `THREADWIRE_KIMI_BIN` remains the explicit override.
 - Resolve native Codex through `THREADWIRE_CODEX_BIN` or normal `PATH` lookup,

package/docs/development-container.md

@@ -6,14 +6,22 @@ installs Codex CLI, Claude Code CLI, the official Kimi Code CLI, OpenCode,
 `oc-codex-multi-auth`, `@ai-sdk/openai-compatible`, and `@ai-sdk/xai` during the
 Docker build. Runtime setup never downloads a plugin through `npx`.
 
-## Source paths
+## Source paths and volumes
 
 All source paths in `.env` are required and have no checked-in host defaults:
 
-- `DEV_HOME_PATH` is the complete dedicated development home. It remains the
-  owner of OpenCode database, session, log, and cache state.
+- `DEV_HOME_PATH` is the complete dedicated development home on the host. It
+  remains the owner of OpenCode database, session, log, and cache state.
+- `DEV_CONTAINER_HOME` is the absolute container path where `DEV_HOME_PATH` is
+  bind-mounted writable. The Threadwire checkout is expected at
+  `${DEV_CONTAINER_HOME}/threadwire`.
+- `KIMI_CODE_HOME` is the absolute container path for the direct Kimi Code CLI
+  home. It must be a strict descendant of `DEV_CONTAINER_HOME` (for example
+  `${DEV_CONTAINER_HOME}/.kimi-code`) so the dev home bind remains the only
+  writable home mount. The Kimi auth volume's `credentials`, `config.toml`, and
+  `device_id` are mounted beneath this path.
 - `GH_CONFIG_SOURCE_PATH` is the GitHub CLI config directory and mounts
-  read-only.
+  read-only at `${DEV_CONTAINER_HOME}/.config/gh`.
 - `CODEX_AUTH_SOURCE_PATH` is native Codex's `auth.json` and mounts read-write
   so OAuth refreshes persist to its canonical owner.
 - `OPENCODE_AUTH_SOURCE_PATH` is OpenCode's native `auth.json`. DeepSeek, xAI,
@@ -23,14 +31,52 @@ All source paths in `.env` are required and have no checked-in host defaults:
   containing the OpenAI OAuth file and global account pool. It mounts
   read-write as a directory because pool updates use atomic sibling-file
   replacement.
-- `AGENT_CONTEXT_PATH` is the immutable agent-context snapshot and mounts
-  read-only.
+- `AGENT_CONTEXT_VOLUME` is the name of the external Docker volume that holds
+  the immutable agent-context snapshot. It mounts read-only at
+  `/opt/agent-context`.
+- `KIMI_AUTH_VOLUME` is the name of the external Docker volume that holds the
+  direct Kimi Code auth store.
+- `KIMI_AUTH_VOLUME_SUBPATH` is the directory inside `KIMI_AUTH_VOLUME` that
+  contains the Kimi Code CLI home (default `.kimi-code`). The volume root may
+  hold other state, so the app mounts `credentials`, `config.toml`, and
+  `device_id` from this subpath.
 
 Hermes owns the canonical credential files. Do not copy them into the checkout,
 the image, or project-keyed task-home files. The app sets
 `CODEX_AUTH_PER_PROJECT_ACCOUNTS=0`, so `oc-codex-multi-auth` uses its one
 global mounted account pool rather than creating per-project credential copies.
 
+## Kimi auth
+
+The normal `app` service mounts only narrow subpaths of the Kimi auth volume,
+all under `${KIMI_AUTH_VOLUME_SUBPATH:-.kimi-code}`:
+
+- `${KIMI_AUTH_VOLUME_SUBPATH:-.kimi-code}/credentials` → `${KIMI_CODE_HOME}/credentials` read-write
+- `${KIMI_AUTH_VOLUME_SUBPATH:-.kimi-code}/config.toml` → `${KIMI_CODE_HOME}/config.toml` read-only
+- `${KIMI_AUTH_VOLUME_SUBPATH:-.kimi-code}/device_id` → `${KIMI_CODE_HOME}/device_id` read-only
+
+The normal app never receives a full writable Kimi auth home. Because the
+read-only `config.toml` and `device_id` file subpaths must already exist in the
+volume, a fresh `KIMI_AUTH_VOLUME` must be initialized before `app` starts.
+
+Interactive Kimi login and refresh use the dedicated `kimi-auth` service, which
+bypasses the normal dev entrypoint:
+
+```sh
+docker compose -f compose.dev.yaml up --build home-init
+docker compose -f compose.dev.yaml --profile kimi-auth run --rm kimi-auth
+docker compose -f compose.dev.yaml --profile app up --detach
+```
+
+This mounts the full `KIMI_AUTH_VOLUME` root writable at `/var/lib/kimi-auth`.
+The service starts as `root` only to create
+`${KIMI_AUTH_VOLUME_SUBPATH:-.kimi-code}` and its `credentials` directory in a
+fresh root-owned external volume, `chown`s them to UID/GID `1000`, drops to
+`1000:1000`, sets
+`KIMI_CODE_HOME=/var/lib/kimi-auth/${KIMI_AUTH_VOLUME_SUBPATH:-.kimi-code}`,
+and runs `kimi login`. It does not mount project source, GitHub auth, agent
+context, Codex, or OpenCode credentials.
+
 ## OpenCode catalog
 
 The image-owned `/usr/local/share/threadwire-dev/opencode.json` is root-owned,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "threadwire",
-  "version": "0.1.19",
+  "version": "0.1.21",
   "description": "Stream Codex, Claude, Kimi Code, and OpenCode worker progress to an explicit Telegram destination",
   "keywords": [
     "ai-agent",