@heyamiko/amiko-cli 0.10.0-beta.0 → 0.10.0

package/README.md

@@ -1,4 +1,4 @@
-# @heyamiko/amiko-cli (v0.9.9)
+# @heyamiko/amiko-cli (v0.10.0)
 
 Manage wallets, credits, swaps, MPP marketplace services, and your Amiko twin (identity, documents, voice, avatar, friends, feed, Composio apps) from the terminal. Works for both human users and AI agents running on OpenClaw.
 
@@ -244,7 +244,9 @@ openclaw plugins install @heyamiko/amiko-cli
 
 This registers the CLI's skill file so the agent discovers all commands through the normal skill system. Updates to the CLI (`npm update -g @heyamiko/amiko-cli`) also update the skill docs.
 
-> **The skill is documentation, not a tool.** Agents must run `amiko <command>` through their shell/bash execution tool. Weaker models sometimes slugify the skill name (`amiko-cli` → `amiko_cli`) and try to call it as a tool, which fails with `Tool amiko_cli not found`. If you see that error, switch to a model with stronger tool discipline (e.g. Claude Sonnet 4.6) — see `skills/SKILL.md`.
+> **The skill is documentation, not a tool.** Agents must run `amiko <command>` through their shell/bash execution tool. Weaker models (especially `gemini-3.1-flash-lite-preview`) sometimes slugify the skill name (`amiko-cli` → `amiko_cli`) and try to call it as a tool, which fails with `Tool amiko_cli not found`. Worse, some models will then *retry the bad tool name 40+ times* before giving up, burning credits on every retry — see [the 2026-05-13 incident](https://platform.heyamiko.com).
+>
+> The SKILL.md in `v0.10.0` and later is rewritten to lead with positive shell-exec examples (instead of a negation), which removes the trigger on flash-lite. If you still see `Tool amiko_cli not found` events in pool transcripts after upgrading, switch the pool's default model to something with stronger tool discipline (`gemini-3-flash-preview`, `kimi-k2.6`, or Claude Sonnet 4.6).
 
 ### Authentication
 
@@ -391,6 +393,14 @@ npm publish
 
 ## Changelog
 
+### 0.10.0
+
+- **`SKILL.md` rewritten to lead with positive shell-exec examples.** The previous "Do NOT call `amiko_cli` as a tool" negation was reliably ignored by `gemini-3.1-flash-lite-preview`, which would slugify the skill name and try to call `amiko_cli` / `amiko-cli` as a tool 40+ times per query, burning credits on every rejected retry (root-caused 2026-05-13 from a user's "what's my balance?" question that triggered 51 OR generations in 110 s). The new SKILL.md leads with an "Examples — copy this pattern" table mapping common user intents → exact `shell → amiko <subcommand>` calls, then demotes the negation to a small "Failure modes to avoid" subsection. Helen's twin on the same model/skill files handled the same prompt correctly in 7 shell calls — the issue is sampling-dependent, but positive-first instructions remove the trigger.
+- **Platform-agnostic auth** (carried over from 0.10.0-beta.0, #61): `resolveAuth()` reads env vars (`AMIKO_TWIN_TOKEN`, `AMIKO_TWIN_ID`, `AMIKO_USER_ID`, `AMIKO_PLATFORM_URL`, `AMIKO_API_BASE`) when no `.amiko.json` is found. The CLI no longer walks up to `/` looking for the file — it checks `cwd/.amiko.json`, then the fixed `/data/.openclaw/workspace/.amiko.json` only under openclaw. Error messages no longer assume openclaw paths.
+- **`amiko update` openclaw sync is now properly gated** (0.10.0-beta.0): the `/data/.amiko-cli` copy + symlink rebuild + skill refresh only runs under `isOpenclawEnvironment()` (true iff `/data/.openclaw` exists AND CWD is under `/data/.openclaw/workspace`). Non-openclaw hosts short-circuit the whole refresh block. Renamed related constants with `OPENCLAW_` prefix for clarity.
+- **Atomic openclaw install swap** (0.10.0-beta.0, code-review followup): stage the new copy at `/data/.amiko-cli.tmp` first; only `rm` + `rename` after `cp` succeeds. A mid-copy failure no longer wipes the live install. `twinSpinner.stop()` moved into a `finally` so the spinner always cleans up even when the sync throws.
+- New `amikoApiBase` JSON alias (existing `apiBase` still accepted).
+
 ### 0.9.9
 
 - **Tempo support removed (breaking).** `wallets bridge` default destination is now Base instead of Tempo (see "Default route: Solana → Base" above and the existing `--from`/`--to` flags). The `tempo` entry is gone from `across.ts` and `lib/tempo.ts` is deleted, so `--to tempo` will now error with an unknown-chain message — there is no escape hatch. **Update any scripts or agents that relied on the old default**: pass `--to base` (or another supported chain) explicitly. `search` no longer falls back to the Tempo explorer either.