@rizzmyrobot/mochi-cli 0.0.4 → 0.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -193,8 +193,8 @@ as a default.
193
193
  ## Player Install
194
194
 
195
195
  Mochi is pre-alpha, and the fallback CLI package is registry-proven at
196
- `@rizzmyrobot/mochi-cli@0.0.3` by trusted publishing plus
197
- `npm view @rizzmyrobot/mochi-cli@0.0.3` proof. The public player install path is npm/npx,
196
+ `@rizzmyrobot/mochi-cli@0.0.4` by trusted publishing plus
197
+ `npm view @rizzmyrobot/mochi-cli@0.0.4` proof. The public player install path is npm/npx,
198
198
  not cloning the repository and running Bun.
199
199
 
200
200
  Because `@mochi/*` npm ownership is not proven, the fallback package scope is
@@ -240,18 +240,21 @@ npx @mochi/cli gateway status --dry-run
240
240
  mochi onboard
241
241
  ```
242
242
 
243
- Current public install `gateway start/status/doctor` commands remain dry-run
244
- planning proofs. Interactive `mochi onboard` may write local workspace seed
245
- files, runtime config refs, and local secrets; MiniMax OAuth may open a browser,
246
- start a loopback callback server, and call the provider token endpoint; Telegram
247
- setup may call only the Bot API `getMe` validation endpoint. It does not call
248
- model providers, poll Telegram, send Telegram messages, connect Discord,
249
- connect games, submit production intents, or change game canon. The separate
250
- credentialed `talk` command can call a selected model provider for a local
251
- Mochi reply; contributor/runtime docs describe the local owner proof for
252
- credentialed provider and Telegram conversation, and the mock-game proof
253
- exercises a fixture provider response
254
- plus a trusted local adapter receipt.
243
+ Current public install `gateway start --profile local --foreground` can start
244
+ the proven local loopback Gateway; `gateway status` and `gateway doctor` can
245
+ probe that local service. Dry-run planning remains available for setup review,
246
+ and `gateway install-service --confirm` can write/remove reviewed local launchd
247
+ or gated VPS systemd files without loading or starting them. Interactive
248
+ `mochi onboard` may write local workspace seed files, runtime config refs, and
249
+ local secrets; MiniMax OAuth may open a browser, start a loopback callback
250
+ server, and call the provider token endpoint; Telegram setup may call only the
251
+ Bot API `getMe` validation endpoint. It does not call model providers, poll
252
+ Telegram, send Telegram messages, connect Discord, connect production games,
253
+ submit production intents, or change game canon. The separate credentialed
254
+ `talk` command can call a selected model provider for a local Mochi reply;
255
+ contributor/runtime docs describe the local owner proof for credentialed
256
+ provider and Telegram conversation, and the mock-game proof exercises a fixture
257
+ provider response plus a trusted local adapter receipt.
255
258
 
256
259
  The local laptop Gateway install flow lives in
257
260
  [`docs/gateway/local-install.md`](docs/gateway/local-install.md).