grokbox 0.1.0-alpha.9 → 0.1.1

package/README.md

@@ -10,9 +10,9 @@ This project is not affiliated with or endorsed by Anysphere, Cursor, xAI, or
 Grok Bot. Grok Bot, Cursor, and related names identify compatible products and
 remain the property of their respective owners.
 
-> **Alpha:** current source is `0.1.0-alpha.9`. npm `next` currently points to
-> `0.1.0-alpha.8`; `0.0.1` remains `latest`. Prereleases publish only after
-> release checks and explicitly scoped external acceptance.
+> **Release:** current source is `0.1.1`. Stable versions publish to npm
+> `latest`; prereleases use `next`. Upstream-private compatibility adapters
+> remain experimental and subject to the documented acceptance limits.
 
 ## What it does
 
@@ -47,7 +47,7 @@ never gain host filesystem or process authority.
 ## Prerequisites and platform support
 
 - Node.js 20+ for the published-style CLI runtime.
-- Bun 1.3.14 for source development and the pre-release source shim.
+- Bun 1.3.14 for source development and the source-backed shim.
 - An existing Grok Bot cloud computer that you own or are authorized to use.
 - Tailscale plus BatchMode SSH for remote bootstrap/recovery; bootstrap also
   needs npm or Bun locally to repack the installed runtime for transfer.
@@ -82,7 +82,7 @@ configured Profile is available, commands fail closed.
 ## Install
 
 ```bash
-npm install --global grokbox@next
+npm install --global grokbox@latest
 grokbox --version
 gbox --help
 ```
@@ -147,7 +147,7 @@ grokbox jobs list --table
 grokbox desktop status --table
 ```
 
-Routine reads expose bounded metadata only: prompt bodies, webhook credentials, native paths, and unknown provider fields stay private. Box-local Bots support create/update/enable/disable/delete; create always writes a disabled definition and later mutations require explicit confirmation plus the exact revision from a fresh `agents routines list/show`. Temporal Bots are Server-authoritative: list/show, webhook credential, enable/disable, and delete use the bounded Temporal Routine bridge; current upstream contracts do not expose Temporal definition create/update, so those commands refuse instead of writing the legacy Box store. `agents routines webhook credential <agent> <routine-id> --confirm` returns the URL while hiding the key; add `--reveal-key` only when secret output is explicitly required. Without the Host bridge, Temporal Routine reads fail closed rather than reporting a false empty list. Upstream Routine writes have no native compare-and-swap or idempotency contract, so an uncertain acknowledgement is never replayed automatically.
+Routine reads expose bounded metadata only, never prompts, keys, native paths, or unknown provider fields. Version 0.1.1 automatically uses proven current-box native Host authentication for `agents routines list/show` and `agents routines webhook credential <agent> <routine-id> --confirm`, without manual cloud token setup. This supports only the observed packaged production Linux Host layout described in the [native identity boundary](docs/upstream-integration.md#server-of-record-routine-surface); custom backends and lab/dev Hosts fail as unsupported. Explicit Profile credentials remain authoritative, including on rejection; remote Profiles never borrow local identity. Missing native proof retains Gateway/Host behavior, not false empty Temporal lists; authentication failures never fall back. Confirmation gates credential side effects, and the key cache remains stable across token renewal. `--reveal-key` reveals only the key; `--verify` never invokes the real Routine. Mutations retain the Host contract; capabilities remain conditional, not proof of authorization. Source-first real-box validation passed with the default Profile and no token injection: both CLI names read Routine list/show with the public Bot UUID and current cloud webhook URL; unknown Routine lookup returned exit 17. No real Routine was invoked and no webhook key was minted. See the [Routine contract](docs/product-contract.md#711-native-routines).
 
 Mutating commands require explicit capability and, where destructive, explicit
 confirmation. `desktop prune run` defaults to dry-run; `--yes` invokes the

package/README.zh-CN.md

@@ -6,7 +6,7 @@
 
 本项目与 Anysphere、Cursor、xAI 或 Grok Bot 没有隶属或背书关系。Grok Bot、Cursor 及相关名称仅用于标识兼容产品，其权利归各自所有者。
 
-> **Alpha：** 当前源码版本是 `0.1.0-alpha.9`。npm 的 `next` dist-tag 目前指向 `0.1.0-alpha.8`；`0.0.1` 仍是 `latest`。只有通过发布检查及明确范围的外部验收后，才会发布新的预发布版本。
+> **发布：** 当前源码版本是 `0.1.1`。正式版发布到 npm `latest`，预发布版使用 `next`。上游私有接口的兼容适配器仍为实验性，遵守文档中的验收范围与限制。
 
 ## 它能做什么
 
@@ -40,7 +40,7 @@ Daemon 不提供通用 raw RPC 或任意 shell。仅有 Gateway 权限的 Profil
 ## 前置条件与平台支持
 
 - 发布版 CLI 运行时需要 Node.js 20+。
-- 源码开发与发布前源码 shim 需要 Bun 1.3.14。
+- 源码开发与源码 shim 需要 Bun 1.3.14。
 - 需要一个你拥有或获准使用的 Grok Bot 云电脑。
 - 远程 bootstrap/recovery 需要 Tailscale 与 BatchMode SSH；bootstrap 还需要本机 npm 或 Bun，以便重新打包已安装运行时并传输。
 
@@ -70,7 +70,7 @@ bun run grokbox -- doctor
 ## 安装
 
 ```bash
-npm install --global grokbox@next
+npm install --global grokbox@latest
 grokbox --version
 gbox --help
 ```
@@ -128,7 +128,7 @@ grokbox jobs list --table
 grokbox desktop status --table
 ```
 
-Routine 读取只输出有界元数据，不暴露 prompt 正文、Webhook credential、原生路径或未知 provider 字段。Box-local Bot 支持 create/update/enable/disable/delete；create 始终只创建 disabled definition，后续 mutation 需要显式确认，并携带刚从 `agents routines list/show` 读到的精确 revision。Temporal Bot 的 Routine 以 Server 为权威：list/show、Webhook credential、enable/disable/delete 通过受限的 Temporal Routine bridge；当前官方合同没有暴露 Temporal definition create/update，因此 CLI 会明确拒绝，而不会误写旧 Box store。`agents routines webhook credential <agent> <routine-id> --confirm` 默认返回 URL 并隐藏 key；只有显式增加 `--reveal-key` 才把 key 输出到 stdout。Host bridge 不可用时，Temporal Routine 查询 fail-closed，不再冒充为空列表。上游 Routine 写接口没有 native compare-and-swap 或 idempotency 合同，因此回执不确定时不会自动重放。
+Routine 读取只输出有界元数据，不暴露 prompt、key、原生路径或未知 provider 字段。0.1.1 通过已证明归属的当前 box 原生 Host 身份，自动使用同一组 `agents routines list/show` 与 `agents routines webhook credential <agent> <routine-id> --confirm` 命令，无需手工配置 cloud token。仅支持[精确原生身份边界](docs/upstream-integration.md#server-of-record-routine-surface)中的已观察 packaged production Linux Host 布局；自定义 backend、lab/dev Host 以 unsupported 拒绝。显式 Profile 凭据优先，被拒绝后不 fallback；Remote Profile 不能借用本机身份。原生证明不可用时保留 Gateway/Host 行为，缺失 Temporal bridge 必须拒绝而非返回虚假空列表。确认后才发生 credential 副作用，key 缓存身份不随 token 续期变化；`--reveal-key` 只揭示 key，`--verify` 不调用真实 Routine。Mutation 保留 Host 合同；capabilities 仍为条件依赖，不宣称已授权。源码优先实机验收已通过：默认 Profile、无 token 注入下，两个 CLI 名称均可读取公开 Bot UUID 对应的 Routine list/show 与当前云端 webhook URL；未知 Routine 返回 exit 17。未调用真实 Routine，也未创建 webhook key。详见 [Routine 合同](docs/product-contract.md#711-native-routines)。
 
 变更命令需要显式 capability；破坏性操作还需要显式确认。`desktop prune run` 默认 dry-run；传入 `--yes` 后会调用上游 stop-window 路径，并删除该 fork 的 Chrome profile。