@minniexcode/codex-switch 0.1.4 → 0.2.0

package/docs/cli-usage.md

@@ -1,6 +1,6 @@
 # codex-switch CLI Usage
 
-This document describes the current `0.1.4` repository development-line CLI contract for `@minniexcode/codex-switch`, including the bridge stability and observability boundary.
+This document describes the current `0.1.5` repository development-line CLI contract for `@minniexcode/codex-switch`, including the Copilot Bridge process-visibility boundary.
 
 Executable command name:
 
@@ -10,9 +10,9 @@ codexs
 
 ## 1. Version Context
 
-The current package version in this repository is `0.1.4`.
+The current package version in this repository is `0.1.5`.
 
-This release line targets Codex `0.134.0+`. The public contract assumes runtime routing is selected by top-level `model` plus `model_provider`, while legacy `profile` and `[profiles.*]` remain inspect-and-adopt inputs instead of the recommended runtime path. The current `0.1.4` development line tightens bridge reliability and release-hygiene verification without expanding the provider command surface.
+This release line targets Codex `0.134.0+`. The public contract assumes runtime routing is selected by top-level `model` plus `model_provider`, while legacy `profile` and `[profiles.*]` remain inspect-and-adopt inputs instead of the recommended runtime path. The current `0.1.5` development line adds Copilot Bridge process visibility, defensive SDK-event normalization, and unknown-event redaction hardening without expanding the provider command surface.
 
 ## 2. Primary Workflows
 
@@ -20,7 +20,7 @@ This release line targets Codex `0.134.0+`. The public contract assumes runtime
 
 ```bash
 codexs init
-codexs add <provider> --model <model> --api-key <key> [--base-url <url>]
+codexs add <provider> --profile <model-provider-id> --model <model> --api-key <key> [--base-url <url>]
 codexs switch <provider>
 codexs status
 codexs doctor
@@ -30,6 +30,7 @@ Intent:
 
 - `init` prepares the `codex-switch` tool home.
 - `add` creates a managed provider record with a target model and provider route identity.
+- Non-interactive runs should pass `--profile` explicitly; TTY mode can prompt for missing required fields.
 - `switch` projects the selected provider into the target Codex runtime.
 - `status` summarizes tool-home, runtime, provider, and health state.
 - `doctor` gives deeper repair-oriented diagnostics.
@@ -39,7 +40,7 @@ Intent:
 ```bash
 codexs init
 codexs login copilot
-codexs add <provider> --copilot --model <model>
+codexs add <provider> --copilot --profile <model-provider-id> --model <model>
 codexs switch <provider>
 codexs status
 codexs doctor
@@ -51,6 +52,7 @@ Important notes:
 - The current implementation prefers the bundled Copilot CLI from the managed runtime and falls back to `PATH` when needed.
 - `login copilot` succeeds only after auth readiness is rechecked.
 - `add --copilot` does not install or log in to Copilot for you.
+- Non-interactive Copilot adds should also pass `--profile` explicitly; TTY mode can still collect missing required fields.
 - Copilot runtime paths require Node.js `>=20`; direct providers remain supported on Node.js `>=18`.
 - The Copilot bridge is experimental and targets simple text-oriented turns through the local OpenAI-compatible bridge.
 
@@ -82,6 +84,7 @@ Copilot bridge projection also writes:
 Compatibility notes:
 
 - `--profile` is accepted as an alias for the managed `model_provider` id.
+- automation should still pass `--profile` explicitly instead of relying on prompts
 - legacy top-level `profile` and `[profiles.*]` may still appear in existing runtime state
 - `migrate`, `config show`, `config list-profiles`, and `doctor` can still inspect those legacy structures
 - new managed runtime projection should be described as route-first, not profile-first
@@ -262,6 +265,7 @@ codexs rollback [backup-id]
 
 - Create or update managed provider records rather than editing runtime files directly.
 - Treat `--profile` only as an alias for the managed `model_provider` id.
+- Require explicit `--profile` in non-interactive usage; allow TTY prompts to fill it when omitted.
 - Clean old `env_key` and `env_key_instructions` fields from managed projection during subsequent switching.
 
 ### `migrate`
@@ -288,7 +292,7 @@ codexs rollback [backup-id]
 - [PRD 0.1.1](./PRD/codex-switch-prd-v0.1.1.md)
 - [PRD 0.1.2](./PRD/codex-switch-prd-v0.1.2.md)
 - [PRD 0.1.3](./PRD/codex-switch-prd-v0.1.3.md)
-- [PRD 0.1.4](./PRD/codex-switch-prd-v0.1.4.md)
+- [PRD 0.1.5](./PRD/codex-switch-prd-v0.1.5.md)
 - [Design 0.1.2](./Design/codex-switch-v0.1.2-design.md)
 - [Design 0.1.3](./Design/codex-switch-v0.1.3-design.md)
-- [Design 0.1.4](./Design/codex-switch-v0.1.4-design.md)
+- [Design 0.1.5](./Design/codex-switch-v0.1.5-design.md)

package/docs/codex-switch-product-overview.md

@@ -4,21 +4,21 @@
 
 这份文档介绍当前活跃产品事实源下的 `codex-switch` 产品定位。
 
-当前仓库开发线 fact source 以这些文档为准：
-
-- [`cli-usage.md`](./cli-usage.md)
-- [`PRD/codex-switch-prd-v0.1.0.md`](./PRD/codex-switch-prd-v0.1.0.md)
-- [`PRD/codex-switch-prd-v0.1.1.md`](./PRD/codex-switch-prd-v0.1.1.md)
-- [`PRD/codex-switch-prd-v0.1.2.md`](./PRD/codex-switch-prd-v0.1.2.md)
-- [`PRD/codex-switch-prd-v0.1.3.md`](./PRD/codex-switch-prd-v0.1.3.md)
-- [`PRD/codex-switch-prd-v0.1.4.md`](./PRD/codex-switch-prd-v0.1.4.md)
-- [`Design/codex-switch-v0.1.2-design.md`](./Design/codex-switch-v0.1.2-design.md)
-- [`Design/codex-switch-v0.1.3-design.md`](./Design/codex-switch-v0.1.3-design.md)
-- [`Design/codex-switch-v0.1.4-design.md`](./Design/codex-switch-v0.1.4-design.md)
+当前仓库开发线 fact source 以这些文档为准：
+
+- [`cli-usage.md`](./cli-usage.md)
+- [`PRD/codex-switch-prd-v0.1.0.md`](./PRD/codex-switch-prd-v0.1.0.md)
+- [`PRD/codex-switch-prd-v0.1.1.md`](./PRD/codex-switch-prd-v0.1.1.md)
+- [`PRD/codex-switch-prd-v0.1.2.md`](./PRD/codex-switch-prd-v0.1.2.md)
+- [`PRD/codex-switch-prd-v0.1.3.md`](./PRD/codex-switch-prd-v0.1.3.md)
+- [`PRD/codex-switch-prd-v0.1.5.md`](./PRD/codex-switch-prd-v0.1.5.md)
+- [`Design/codex-switch-v0.1.2-design.md`](./Design/codex-switch-v0.1.2-design.md)
+- [`Design/codex-switch-v0.1.3-design.md`](./Design/codex-switch-v0.1.3-design.md)
+- [`Design/codex-switch-v0.1.5-design.md`](./Design/codex-switch-v0.1.5-design.md)
 
 ## 产品概述
 
-`codex-switch` 是一个本地 provider 管理 CLI，用于管理和切换目标 Codex runtime 的 provider/model-provider 路由配置，同时把工具自己的管理态保存在独立 tool home 下。
+`codex-switch` 是一个本地 provider 管理 CLI，用于管理和切换目标 Codex runtime 的 provider/model-provider 路由配置，同时把工具自己的管理态保存在独立 tool home 下。
 
 它不是旧 `setup` 小工具，也不是围绕单目录 `~/.codex` 组织全部状态的脚本集合。
 
@@ -54,11 +54,11 @@ target Codex runtime：
 
 ## 核心使用流程
 
-Direct 主路径：
+Direct 主路径：
 
 ```bash
 codexs init
-codexs add <provider> --model <model> --api-key <key> [--base-url <url>]
+codexs add <provider> --profile <model-provider-id> --model <model> --api-key <key> [--base-url <url>]
 codexs switch <provider>
 codexs status
 codexs doctor
@@ -69,7 +69,7 @@ Copilot 主路径：
 ```bash
 codexs init
 codexs login copilot
-codexs add <provider> --copilot --model <model>
+codexs add <provider> --copilot --profile <model-provider-id> --model <model>
 codexs switch <provider>
 codexs status
 codexs doctor
@@ -84,12 +84,13 @@ codexs migrate
 
 ## 当前产品判断
 
-`0.1.1` 的重点不是再加新命令，而是让用户在 README、help 和输出第一屏就能理解：
+`0.1.1` 的重点不是再加新命令，而是让用户在 README、help 和输出第一屏就能理解：
 
-- fresh install 应先走什么
-- Copilot 路径和 direct 路径有什么区别
-- `migrate` 何时才该使用
-- `status` / `doctor` 如何帮助定位下一步
-- 当前运行态是用顶层 `model` 与 `model_provider` 选择活动路由
-
-`0.1.4` 是当前仓库开发线，重点不是扩展 provider 面，而是把已有 Copilot bridge 实验路径变得更稳、更可诊断，并把 release hygiene 拉进真实门禁。当前实现边界仍然是：Copilot 路径要求 Node.js `>=20`，受管安装默认固定到 `@github/copilot-sdk@1.0.2`，本地 bridge 仍然只是面向 simple text-oriented turns 的 experimental bridge；Direct provider 路径继续支持 Node.js `>=18`。
+- fresh install 应先走什么
+- Copilot 路径和 direct 路径有什么区别
+- 非交互命令为什么应显式传 `--profile`，以及 TTY 模式下哪些缺失项可以补问
+- `migrate` 何时才该使用
+- `status` / `doctor` 如何帮助定位下一步
+- 当前运行态是用顶层 `model` 与 `model_provider` 选择活动路由
+
+`0.1.5` 是当前仓库开发线，重点不是扩展 provider 面，而是让已有 Copilot bridge 实验路径具备过程可见性：SDK 事件被归一化为稳定运行态事件，Responses 流可以显示 commentary/reasoning 信号，未知事件摘要会被脱敏和截断。当前实现边界仍然是：Copilot 路径要求 Node.js `>=20`，受管安装默认固定到 `@github/copilot-sdk@1.0.2`，本地 bridge 仍然只是面向 simple text-oriented turns 的 experimental bridge；Direct provider 路径继续支持 Node.js `>=18`。

package/docs/codex-switch-technical-architecture.md

@@ -7,12 +7,12 @@
 - [`PRD/codex-switch-prd-v0.1.1.md`](./PRD/codex-switch-prd-v0.1.1.md)
 - [`PRD/codex-switch-prd-v0.1.2.md`](./PRD/codex-switch-prd-v0.1.2.md)
 - [`PRD/codex-switch-prd-v0.1.3.md`](./PRD/codex-switch-prd-v0.1.3.md)
-- [`PRD/codex-switch-prd-v0.1.4.md`](./PRD/codex-switch-prd-v0.1.4.md)
+- [`PRD/codex-switch-prd-v0.1.5.md`](./PRD/codex-switch-prd-v0.1.5.md)
 - [`Design/codex-switch-v0.1.0-design.md`](./Design/codex-switch-v0.1.0-design.md)
 - [`Design/codex-switch-v0.1.1-design.md`](./Design/codex-switch-v0.1.1-design.md)
 - [`Design/codex-switch-v0.1.2-design.md`](./Design/codex-switch-v0.1.2-design.md)
 - [`Design/codex-switch-v0.1.3-design.md`](./Design/codex-switch-v0.1.3-design.md)
-- [`Design/codex-switch-v0.1.4-design.md`](./Design/codex-switch-v0.1.4-design.md)
+- [`Design/codex-switch-v0.1.5-design.md`](./Design/codex-switch-v0.1.5-design.md)
 
 ## Layers
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@minniexcode/codex-switch",
-  "version": "0.1.4",
-  "description": "Local-first CLI for managing and switching Codex provider/model-provider routing.",
+  "version": "0.2.0",
+  "description": "Local-first CLI for managing and switching Codex provider/model-provider routing.",
   "license": "MIT",
   "type": "commonjs",
   "bin": {