Orbit v0.6.7

Orbit v0.6.7 is a Session resume hotfix on top of v0.6.6 Session-scoped Runs. It preserves per-DSH-Session durable state under .cx/sessions//state.json, independent Run IDs and persistent Commander/Executor sessions, while explicitly carrying owner_session_id through NEEDS_USER resume paths. Multiple Orbit Sessions can coexist in one project; mutation-capable Executor turns and MoA promotion remain serialized per physical workspace. Validated with 299 unit tests, 38 client tests, real two-Session E2E, full smoke, Browser, and MoA 0.2.23. Browser remains v0.1.0.

Orbit v0.6.6

Orbit v0.6.6 makes Orbit runs session-scoped. Multiple DSH chat Sessions can now own independent Orbit runs in the same project instead of being blocked by a single project-level .cx/state.json. New runs persist under .cx/sessions//state.json; legacy states remain readable and owner-scoped states migrate automatically. Writable Executor turns and MoA promotion are serialized per physical workspace to preserve mutation safety, while status/resume/stop target the current Session. Includes real two-Session DSH E2E coverage, legacy-state migration tests, mutation-lease cancellation tests, and validation with dsh-moa 0.2.23. Browser remains v0.1.0.

Orbit v0.6.1

Orbit v0.6.1 restores the compact first-level Orbit settings menu and moves detailed MoA configuration into a dedicated second-level menu. Candidate count and max-MoA-step controls now use explicit selectors instead of cycling values. MoA compatibility now accepts @goodandready/dsh-moa >=0.2.19 without an upper version gate; 0.2.19 and 0.2.20 were validated with real DSH E2E and smoke tests. Browser remains v0.1.0.

Orbit v0.6.0

Orbit v0.6.0 adds optional MoA execution for high-uncertainty steps. Orbit can fan out 2-4 isolated candidates, use a Judge for relative selection, promote the winner under Supervisor control, verify it with the normal Executor, and keep Commander as the final acceptance authority. Includes frozen MoA routes, bounded peer critique, durable recovery, promotion receipts, Token/cost reporting, UI controls, and DSH 0.1.5-rc.2 compatibility validation. Browser remains v0.1.0.

Orbit v0.5.10

DSH-Orbit v0.5.10

• 自动 Run 的循环预算按已接受计划自适应：max(5, 步数 + 2)，上限 7，减少较大计划或需要纠正时的预算耗尽
• 显式 approved_loop_count / max_loops 永不被自动放大
• Orbit 控件固定为输入区右侧列表的最后一项，原生模型选择器紧随其右
• 刷新 Orbit / Browser 插件描述与项目总览

Orbit v0.5.9

DSH-Orbit v0.5.9

• 硬激活 Run 达到 SUCCESS 后，Final Commander 的最终结果直接显示在发起会话中
• 展示内容带 Commander 冻结的 provider/model 来源
• 父模型与父工具保持 0 调用；最终输出仅用于呈现，不写入 Orbit durable state

Orbit v0.5.8

DSH-Orbit v0.5.8

• 修复跨 Session NEEDS_USER 误恢复旧 Run
• Executor 严格跟随当前 DSH Session 模型 Route
• Commander / Watchdog 模型完全由用户选择
• 移除 Orbit 内置模型与 reasoning 默认值
• Step Capability 实现 filesystem / shell / web / browser 权限隔离
• 增加 durable per-step evidence 与 FINAL_EVALUATE 完整证据
• 加强 workspace 单 mutation driver 隔离
• 改进旧 state、Route freeze、中文角色提示与发布隐私边界

Orbit v0.5.7

Orbit v0.5.7

Fixed

• The Executor route now follows the Session's durable modelSelection projection (pending → lastUsed), so a hard-activated run uses the model the native seat actually shows — a non-deepseek Session model no longer silently falls back to the configured executor route. The public request header stays as a low-priority compatibility fallback, then config.routes.executor.
• Commander, Executor and Watchdog runtime prompts are Simplified Chinese; only machine identifiers (decision enums, phases, capability ids, code, commands, paths, provider/model ids) stay English.

Distribution

• Orbit package: 0.5.7.
• Browser package: 0.1.0.
• Primary channel: the npm Registry (@kasenri/dsh-orbit, @kasenri/dsh-browser). The dedicated Git mirrors (github:KasenRi/dsh-orbit, github:KasenRi/dsh-browser) and the versioned release tarballs below remain available.

Orbit v0.5.6

Orbit v0.5.6

Fixed

• A NEEDS_USER run now continues from the user's actual reply: an ordinary message with completely different text (for example a port number) resumes the same run — the original goal, run_id and frozen state.routes are kept, and the reply is stored durably as pending_user_reply and read by the Commander and Executor.
• An explicit /agent-orbit <goal> statement now hard-activates Orbit on the host: the turn is consumed and OrbitService runs directly, so the parent chat model is never asked to call orbit_controller and never mutates the task.

Changed

• slashCommand only gates the /agent-orbit command registration; the per-chat toggle command and the host activation boundary (enabled-Session ordinary messages, explicit /agent-orbit messages) no longer depend on it.
• Hard-activation outcomes the user must see (a NEEDS_USER question, a refused start, an unfinished run, a startup failure) are surfaced as durable DSH notice messages in the conversation; the host stays the only mutation driver.

Distribution

• Orbit package: 0.5.6.
• Browser package: 0.1.0.
• Primary channel: the npm Registry (@kasenri/dsh-orbit, @kasenri/dsh-browser). The dedicated Git mirrors (github:KasenRi/dsh-orbit, github:KasenRi/dsh-browser) and the versioned release tarballs below remain available.

Orbit v0.5.5

Orbit v0.5.5

Fixed

• An enabled chat's ordinary message now hard-activates Orbit: the host pre-step boundary consumes the turn and calls the existing OrbitService directly, so the parent chat model no longer decides whether Orbit runs and cannot execute the task itself. The synthetic "Orbit is enabled… start or resume through orbit_controller" prompt is gone.
• Hard activation grants a budget that can finish a 2-5 step plan (minimum 5 loops, raised by the goal complexity estimate), so a normal create/verify/delete task is no longer cut off by the default single-loop estimate.
• The claimed user message is committed to the conversation exactly once, and explicit /agent-orbit keeps its own directive route without double-starting a run.

Changed

• Requirement: the Commander runs PLAN / STEP_EVALUATE / FINAL_EVALUATE and the Executor runs the steps, with configured role routes frozen into state.routes at run start.

Distribution

• Orbit package: 0.5.5.
• Browser package: 0.1.0.
• Primary channel: the npm Registry (@kasenri/dsh-orbit, @kasenri/dsh-browser). The dedicated Git mirrors (github:KasenRi/dsh-orbit, github:KasenRi/dsh-browser) and the versioned release tarballs below remain available.