samagotchi 0.79.0 → 0.81.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fc74f7069433e0f6be4252973309183e17c3ecc7ad06800684bf9be6fe40015f
-  data.tar.gz: 12a8d7e7c8002a8762d7752f6cae9bd20fae6565cb2d81636cc1ca9a6ff2469d
+  metadata.gz: e0e5c6acd4a2774291e421b71b7b5729b0e3031c9afaa46715f40a1d976ebed2
+  data.tar.gz: 6390322560ddd65a847ea4d3a122b3751be778c40eb573d457c617880daa0e06
 SHA512:
-  metadata.gz: 004ef50c618ba8bb488adf9e5623da491691bf37850946870bb94511451d8e56876288232d0bae0212dcfc7d9a1c79544d4297ef0ab8692f5678ff3617fc144c
-  data.tar.gz: cb551afd6bdae21bfd61a4ff64ead0306816b41b88f4b5083fbf5e7d2afbb9ef9b9353d5d5750ccbfd1764fe10db8c60f8eb534a2cd4d728b04e3145f84dad4a
+  metadata.gz: c1d209965a45e687b89280cbcecfe0b51798dcff1a418837b3604f4b3b1e69e8d0f210d8b4972c84912e274c7f738c322a2270af36833fe17049e999081a2705
+  data.tar.gz: 9c5d2a4e2205da68d70d99db385ab3f79ebec1f83f8762baaf36d3ae466fc98204c68bcd93ab1868127e703f5d50eaed0dd363ac910541849298c3bbc72bb931

data/CHANGELOG.md

@@ -8,6 +8,62 @@ and commands may change between minor versions. How releases are made:
 
 ## [Unreleased]
 
+## [0.81.0] - 2026-10-18
+
+### Added
+
+- Stats: side requests (the idle recap, `/btw` and plugins' `ctx.ask_model`) are counted on their own
+  `side requests:` line in `/stats` and the web's ctx tooltip, with their tokens and cost; the session's totals stay
+  its turns'.
+
+### Fixed
+
+- Guardrails: a `command:` rule no longer matches the text of a heredoc its command only reads as data
+  (`git commit -F -`, `gh pr create --body-file -`, `cat` to stdout, a `"$(cat <<'EOF' …)"` commit message); a
+  heredoc fed to a shell or an interpreter, or piped on (also from a `( … )` or `{ … }` group), is still
+  matched. The bundle's `chi-answer-piped` (guardrails bundle 0.9.1) no longer asks about stdin from
+  `/dev/null`.
+- Guardrails: the `rm` and `touches` checks now see a heredoc that bash runs after all — piped on from a `( … )` or
+  `{ … }` group, fed through `<( … )` / `>( … )`, or written with `&>` / `>& file` and then run — which they used to
+  read as plain data.
+- Plugins: a `chi.service` that starts lazily from a tool or hook handler runs its start block outside the handler,
+  so Stop no longer cancels the service's startup `ctx.http` calls (as docs/plugins.md says).
+- Bundles: the test kit's sandbox also points `XDG_DATA_HOME` and `XDG_CACHE_HOME` at its temp folder, so a bundle
+  test no longer writes to your own data or cache home when you set them.
+- `chi bootstrap`: re-running it against a server the config already has says so, without the misleading "saved as …"
+  line before it.
+
+Update with `chi update` (the system bundle 0.81.0, `guardrails` 0.9.1, `slow-commands` 0.2.3), then restart
+`chi web`.
+
+## [0.80.0] - 2026-10-17
+
+### Added
+
+- Web: the message box has an image button next to Start / Send that opens a file picker (on a phone, the camera or
+  the photo library); the picked images are added like pasted ones. A message now takes at most 20 images of up to
+  20 MB each as you add them, pasted, dropped or picked, and a toast names the files left out, instead of the send
+  failing.
+- Bundles: `samagotchi/testing` (experimental), a test kit for bundles: load a bundle in a sandbox, fire its hooks, run its commands and tools, record steers, notices and cards (RSpec `:bundle` groups or Minitest `Testing::Case`; docs/plugins.md "Testing a bundle"). The shipped bundles' specs now live in each bundle's own `spec/` and use it; a boundary spec keeps bundles on the stable surface.
+- Plugins: `ctx.http`, an HTTP client for calling services (`get`, `post_json`, `request`): short default timeouts, one error type (`Samagotchi::Plugin::HttpError`), a 4xx/5xx returned as a Response, one INFO `http` log line per call without query, headers or body (`purpose=plugin`, `bundle=`), and a call made for the turn stops when the turn is stopped (docs/plugins.md "Calling services"; experimental until 1.0). The test kit fakes it: `bundle.http.stub(…)`, `requests`, `unmatched`, and a request no stub answered fails the test.
+- `chi bootstrap` sets up Anthropic Messages hosts: a server that refuses the OpenAI model list but lists Anthropic's
+  way (api.anthropic.com, a Messages-only gateway) is written as `api: anthropic` (the url without `/v1`, `auth: bearer`
+  when only Bearer worked), with `dialect: fireworks` for Fireworks' host or model ids. `--api openai|anthropic` and
+  `--dialect standard|fireworks` override the detection; direct Fireworks stays `api: openai` with a hint, and a test
+  turn's 404 on `/chat/completions` hints `--api anthropic`. A hand-written urlless `api: anthropic` host counts as
+  api.anthropic.com, so bootstrapping it again writes nothing.
+- Plugins: `ctx.ask_model(model: "host:id")` asks a configured model (a host:id ref, an alias, or a model one of the hosts lists) instead of the session's; an unknown ref raises `ArgumentError`.
+
+### Changed
+
+- Web: the start page says "+ new session" (and "new session in …") instead of "+ new chat", matching the rest of the UI.
+- Web: the latest-sessions strip hides and shows with the same edge grip as the composer's (a drag up hides it, a drag
+  down or a click shows it, Enter/Space on the focused grip toggles, and the choice is remembered): the tile's `hide ▴`
+  and the top bar's `▴ hide` are gone, and while the strip is hidden its pill — now only its status — opens All
+  sessions in one click instead of showing the strip first.
+
+Update with `chi update` (the system bundle 0.80.0), then restart `chi web`.
+
 ## [0.79.0] - 2026-10-17
 
 ### Fixed
@@ -3282,7 +3338,9 @@ and long-lived sessions.
 - A macOS desktop helper (`chi desktop install`): a "Send to chi" Service and a
   hotkey panel that send selected text or the clipboard to your sessions.
 
-[Unreleased]: https://github.com/dm1try/samagotchi/compare/v0.79.0...HEAD
+[Unreleased]: https://github.com/dm1try/samagotchi/compare/v0.81.0...HEAD
+[0.81.0]: https://github.com/dm1try/samagotchi/compare/v0.80.0...v0.81.0
+[0.80.0]: https://github.com/dm1try/samagotchi/compare/v0.79.0...v0.80.0
 [0.79.0]: https://github.com/dm1try/samagotchi/compare/v0.78.0...v0.79.0
 [0.78.0]: https://github.com/dm1try/samagotchi/compare/v0.77.0...v0.78.0
 [0.77.0]: https://github.com/dm1try/samagotchi/compare/v0.76.0...v0.77.0

data/README.md

@@ -69,10 +69,12 @@ Point chi at your model server; it works out the rest and writes
 chi bootstrap 192.168.1.29:8081          # llama.cpp on another machine
 chi bootstrap localhost:11434            # any OpenAI-compatible server
 chi bootstrap https://openrouter.ai/api/v1 --key-env OPENROUTER_API_KEY
+chi bootstrap https://api.anthropic.com --key-env ANTHROPIC_API_KEY
 chi bootstrap                            # look on this machine's usual ports
 ```
 
-It finds out whether the server is llama.cpp or OpenAI-compatible, picks the
+It finds out whether the server is llama.cpp, OpenAI-compatible or Anthropic's
+Messages API, picks the
 model (or asks, when there are several), sends one test request and writes
 the config. With a config already there, it adds a `hosts:` entry and keeps
 the rest of the file. Then it installs the `core` bundles (loop-guard,
@@ -127,7 +129,7 @@ pbpaste | chi send -m "same bug?" <id>    # a message to a session, the clipboar
 chi send --new --wait -m "review feat/x"  # a new session you can watch in the web; prints the answer
 ```
 
-`@shot.png` in a prompt (or a pasted/dropped image in the web UI) shows the model an image, when it can see them; see [Images](docs/cli.md#images).
+`@shot.png` in a prompt (or a pasted, dropped or picked image in the web UI) shows the model an image, when it can see them; see [Images](docs/cli.md#images).
 
 `/model` switches models, Ctrl-C cancels a turn, and Ctrl-D or `/detach` detaches (the session keeps running; `chi --attach ID` comes back). `/exit` detaches and stops the session's worker too, unless something still needs it (a running turn, another UI); `chi --resume ID` picks the conversation up again. `/exit --delete` also deletes the session once the worker has gone; `chi sessions delete ID` deletes one from the shell. `/archive` (or `chi sessions archive ID`) hides a session from every list and keeps it for good; `chi sessions list --archived` finds it again.
 
@@ -220,9 +222,9 @@ once, for the session, for the repo, or for the whole rule in the repo.
 ## Development
 
 ```sh
-bundle exec rspec    # Ruby specs
-npm test             # web frontend specs
-npm run e2e          # web UI happy paths in Chromium, fake model (once: npx playwright install chromium)
+bundle exec rspec spec lib/samagotchi/bundles/*/spec   # Ruby specs (chi's and the shipped bundles' own)
+npm test                                               # web frontend specs
+npm run e2e                                            # web UI happy paths in Chromium, fake model (once: npx playwright install chromium)
 ```
 
 Integration specs against a live model server, and what the suite isolates: [docs/testing.md](docs/testing.md).

data/docs/architecture.md

@@ -338,6 +338,14 @@ carries the generation's `speed` (`{decode_tps, source}`, null without one), its
 counts (`prompt_tokens`, `cached_tokens`, `cache_write_tokens`: null when the server reported no writes) and
 those running `tokens` and `model_segments`: the Engine closes the generation in `SessionMetrics#finish_generation` before relaying
 it, so the web's info bar updates per generation without parsing chunk payloads.
+Side requests (the idle recap, a plugin's `ctx.ask_model` such as `/btw`) are counted apart, in a `side` block
+(only when there were any; `SessionMetrics::SideTotals`: requests, token sums, `cost_sum` null until reported,
+`cost_estimate_sum` from the target host's price, `by_kind`): `IdleClient` hands each reply's usage to its
+`on_usage:` callback, `Engine#note_side_usage`, which folds it (`SessionMetrics#add_side`) and announces
+`:side_usage` (`kind`, the whole `side` block) under the event lock, so the blocks arrive in fold order, then saves
+`analytics.json` between turns (a running turn's end saves it). `tokens`, `model_segments` and the turn records
+stay the turns' only. `SessionMetrics#persist` is serialized (its own mutex, taken before the metrics one), so two
+threads' saves land in snapshot order.
 
 The page's frequent reads of `GET /api/sessions/:id` stay light too:
 - `?tail=1&recent=1` (each turn's end, a cancel, an answer display): `{tail, session: {id, status,
@@ -523,7 +531,7 @@ A map of the parts the overview above doesn't name (paths under `lib/samagotchi/
 | Attached context | `context_sources.rb` (`ContextSources`), `context_poller.rb`, `context_absorber.rb`, `peer_sources.rb` (`PeerSources`: the sources peer bundles declare) | External sources a session keeps fresh, and the peer loop's wakes ([context.md](context.md)). |
 | LLM context strategies | `llm_context_strategy.rb`, `llm_context_view.rb`, `llm_context_stale.rb`, `llm_context_forget.rb` | What a request sends of the history (none, stale, forget) ([internals/llm-context-forget.md](internals/llm-context-forget.md)). |
 | Session chains | `session_continue.rb` (`SessionContinue`), `session_chain.rb` (`SessionChain`) | A session that continues an earlier one. `SessionChain.opener_for` gives the text web `continue →` prefills in the new link: the previous link's own first typed message when that link continues one itself, else nil (the 201's `opener`; not saved) ([sessions.md](sessions.md)). |
-| Analytics | `analytics_file.rb` (`AnalyticsFile`), `session_metrics/totals.rb` (`SessionMetrics::Totals`), `session_metrics/model_segment.rb` (`SessionMetrics::ModelSegment`) | A session's `analytics.json` (`SessionMetrics#persist`); the sums over its turn records (`Totals`: tokens, cost, speeds, kept as running counters) and their split per model after a `/model` switch (`ModelSegment`: a run of turns on one model, the `model_segments` rows). |
+| Analytics | `analytics_file.rb` (`AnalyticsFile`), `session_metrics/totals.rb` (`SessionMetrics::Totals`), `session_metrics/model_segment.rb` (`SessionMetrics::ModelSegment`) | A session's `analytics.json` (`SessionMetrics#persist`); the sums over its turn records (`Totals`: tokens, cost, speeds, kept as running counters) and their split per model after a `/model` switch (`ModelSegment`: a run of turns on one model, the `model_segments` rows). `session_metrics/side_totals.rb` (`SessionMetrics::SideTotals`) and `side_usage.rb` (`SideUsage`): the side requests' sums, apart from the turns'. |
 | Images / vision | `image_store.rb` (`ImageStore`), `vision_support.rb`, `vision_context.rb` | Stored prompt images and whether a model takes them. |
 | Toolkits | `toolkit.rb` (`Toolkit`), `toolkit_binding.rb` (`ToolkitBinding`, the Engine's seam), `toolkit_command.rb` (`/toolkit`), `tools/registry.rb` (`Registry#toolkit`, `#left_out_names`), `web/public/toolkit_chip.js` | Which registered tools a session's prompts declare: saved in the session, resolved at a turn's start (`Engine#apply_toolkit!`), named in the prompt's not-loaded line, a kit's prompt text after the appended files; `chi.toolkit` and `ctx.use_toolkit` for plugins ([configuration.md](configuration.md#toolkits)). |
 | Tool index | `tools/tool_index.rb` (`Tools::ToolIndex`) | `find_tools` and `call_tool`: the tools a session knows but doesn't declare one by one (an mcp bundle's servers through `chi.tool_source`, the built-ins its toolkit leaves out), searched and called by name ([plugins.md](plugins.md)). |

data/docs/cli.md

@@ -2,7 +2,7 @@
 
 ## Commands
 
-- `chi bootstrap [HOST[:PORT]|URL]` — first setup: find the model server (llama.cpp or OpenAI-compatible), pick the model, send a test request and write config.yml, or add a `hosts:` entry to an existing one (see [First setup](#first-setup))
+- `chi bootstrap [HOST[:PORT]|URL]` — first setup: find the model server (llama.cpp, OpenAI-compatible or Anthropic Messages), pick the model, send a test request and write config.yml, or add a `hosts:` entry to an existing one (see [First setup](#first-setup))
 - `chi` — start a session in a background worker and attach the terminal to it, so the Web UI (or another terminal) can share it (see [Sharing a session](#sharing-a-session))
 - `chi -p "your prompt"` — run a prompt, then stay attached
 - `chi -p "your prompt" --non-interactive` — run a prompt, print the answer, exit
@@ -33,12 +33,23 @@
 ```sh
 chi bootstrap 192.168.1.29:8081          # host:port (an IP or localhost: port 8080 when none; a domain: https 443, then http 80)
 chi bootstrap https://openrouter.ai/api/v1 --key-env OPENROUTER_API_KEY
+chi bootstrap https://api.anthropic.com --key-env ANTHROPIC_API_KEY
 chi bootstrap                            # try localhost 8080, 11434, 1234, 8000
 ```
 
 - **What it is.** llama.cpp's `/props` answering means the native API (no
   `api:`); otherwise `GET /v1/models` answering means an OpenAI-compatible
-  server (`api: openai`). A URL with a path is the API base as given
+  server (`api: openai`). Only when that list is refused with 400, 401 or 403
+  does chi ask Anthropic's way (`anthropic-version`, the key in `x-api-key`,
+  once more as Bearer after a 401/403): a list there means Anthropic's
+  Messages API (`api: anthropic`, the url without `/v1`; `auth: bearer` when
+  only Bearer worked). A server that serves both, such as Splash, stays
+  `api: openai`. Fireworks (its host, or model ids under `accounts/fireworks/`)
+  on the Messages API gets `dialect: fireworks`; direct Fireworks is found as
+  OpenAI-compatible first and stays `api: openai`, with a line saying
+  `--api anthropic` takes its Messages API instead. `--api openai|anthropic`
+  and `--dialect standard|fireworks` (which implies `--api anthropic`) skip the
+  detection. A URL with a path is the API base as given
   (`…/api/v1`); a domain without a scheme is tried over https, then http.
   Each request is tried once, with 5 s timeouts, so a refused port answers
   at once.
@@ -51,8 +62,11 @@ chi bootstrap                            # try localhost 8080, 11434, 1234, 8000
   (a terminal gets a numbered list, a script the ids and exit 2). A llama.cpp
   server also shows its context size and the prompt profile its chat template
   matches.
-- **The test.** One short chat request ("test: answered in 1.1 s"); `--no-test`
-  skips it. A failed test still writes the config, says so and exits 1.
+- **The test.** One short chat request ("test: answered in 1.1 s"; `POST /v1/messages`
+  on `api: anthropic`); `--no-test` skips it. A failed test still writes the config,
+  says so and exits 1. A server found as OpenAI-compatible whose `/chat/completions`
+  answers 404 gets the hint `try --api anthropic` (a gateway's Messages url that also
+  lists the OpenAI way).
 - **The file.** With no config.yml it writes a small commented one:
   `default.model` as `<host>:<model>` and one `hosts:` entry named `local`
   (localhost), `lan` (an IP) or after the domain (`openrouter`); `--name`
@@ -472,6 +486,14 @@ Generations under 8 tokens or 100 ms get no speed of their own, nor does a
 reply without server token counts or a non-streamed one. A delegated child
 keeps its own numbers: a parent's tokens and cost leave them out.
 
+Side requests have their own line, right after `cost:` (in its place without one), only when the session made any:
+`side requests:    3 (recap 2, btw 1) · 14.2k in / 380 out · $0.0012 + ~$0.0009 (not in the totals above)`. It
+counts the idle recap (`recap`), `/btw` and every other plugin's `ctx.ask_model` (under the asking bundle's name),
+with their tokens and cost: a reported cost as is, else estimated from the price of the model they asked, on its
+host (as a turn's, `~`). They are never in the tokens, `models:` or `cost:` lines above it, which stay the turns'.
+A recap thrown away (stale, overdue) still counts: it was billed. `chi sessions stats` shows the line too (saved
+between turns), and the web's ctx tooltip has the same words.
+
 After a `/model` switch (or a hook's) the tokens line becomes a `models:` block, a row per run of turns on one
 model, in order (A → B → A is three rows): the model (`host:model` as asked), when (`10:43–now` while it runs; with
 the day when the rows span several), turns, tokens in/out, its average speed and cost. Under the row of the model
@@ -662,9 +684,12 @@ A model that can see images gets them these ways:
 - **A path in plain words**: "check /home/me/shot.png and describe it". The
   model calls `read` on it and sees the picture; the tool line ends in
   `→ image 1280×800`.
-- **The Web UI**: paste or drop images into the composer. Each shows as a chip
-  (× removes it) and is sent with the message; an image alone is sent as
-  `[image: name]`. Messages show thumbnails; a click opens one full size.
+- **The Web UI**: paste or drop images into the composer, or pick them with
+  its image button (left of Start / Send; on a phone it offers the camera and
+  the photo library, and is hidden while a turn runs). Each shows as a chip (× removes it) and is sent with the
+  message; an image alone is sent as `[image: name]`. A message takes up to 20
+  images of up to 20 MB each; a toast names the files left out (over a cap, or
+  not an image). Messages show thumbnails; a click opens one full size.
 - **`chi send --image PATH`** (repeatable, up to 20) with a message, from a
   script or another terminal: `chi send --image shot.png -m "why is this red?"
   3fa2`. The attached terminal and the web show it like an image typed there.

data/docs/configuration.md

@@ -10,8 +10,8 @@ Chi reads its settings from three places; the first that sets a value wins:
 
 then the built-in default. [All settings](#all-settings) lists them.
 
-`chi bootstrap HOST[:PORT]` writes a first config for a model server, or adds
-it to this file as a `hosts:` entry (see [First setup](cli.md#first-setup)).
+`chi bootstrap HOST[:PORT]` writes a first config for a model server (llama.cpp, OpenAI-compatible or Anthropic
+Messages), or adds it to this file as a `hosts:` entry (see [First setup](cli.md#first-setup)).
 
 Default path:
 
@@ -343,6 +343,9 @@ hosts:
 
 `auth:` works on any host (`bearer` is the default everywhere but `api: anthropic`).
 
+`chi bootstrap https://api.anthropic.com --key-env ANTHROPIC_API_KEY` writes such an entry (a gateway: its url;
+`--api anthropic` / `--dialect fireworks` when the detection can't tell, see [First setup](cli.md#first-setup)).
+
 **Claude 5.x preserved thinking:** Claude 5.x models (Opus, Sonnet and Haiku 5.5, Fable 5.1) bind each thinking
 block to everything before it: the system prompt, the tools and the earlier messages. chi keeps the history
 append-only, but the system prompt or the tools can change under a session: a resume or a worker respawn after
@@ -570,6 +573,9 @@ hosts:
 - The estimate is saved apart from the reported cost (`cost_estimate` per turn, `cost_estimate_sum` in the
   session's totals in `analytics.json`) and shows with a `~`.
 - A server that sends no cached counts has its whole prompt priced at `input`: an overestimate.
+- Side requests (the idle recap, `/btw`, a plugin's `ctx.ask_model`) are priced by the same rule from the price of
+  the model they asked on its host: the recap's host and model (`recap.*`, else the session's), `ask_model(model:)`'s
+  host. They count on `/stats`' own `side requests:` line, never in the session's `cost:`.
 
 ## Thinking
 
@@ -1467,8 +1473,8 @@ its own). The first target is a long session such as a day-long coordinator, whe
   (the same flags on `chi send --new`), in the session with `/llm-context strategy … apply … budget …`
   (docs/cli.md, "Session commands"), or from the web's `llm ctx` chip in the info bar.
 - **A new web chat:** the start page's `llm ctx` chip, beside the model picker, shows the picked model's values
-  and follows a model pick. Its form (titled "new chat") sets a choice for that one chat: the chip reads
-  `llm ctx stale · new chat` in the accent colour, and the create sends it as `POST /api/sessions`'s
+  and follows a model pick. Its form (titled "new session") sets a choice for that one chat: the chip reads
+  `llm ctx stale · new session` in the accent colour, and the create sends it as `POST /api/sessions`'s
   `llm_context` (`{"strategy": "stale,forget", "apply": "turn_end", "budget": "64k"}`, each a word as
   `/llm-context` takes it, `default` for unset; anything else answers `400 invalid_llm_context` and starts
   nothing), so the session file holds it before the first turn runs. It is not remembered: it resets after a

data/docs/guardrails.md

@@ -230,7 +230,7 @@ guardrails:
   rules:
     - id: git-push
       tool: shell            # execute + task_create; or a tool name, a glob, or a list
-      command: '\bgit\s+push\b'   # Ruby regex on the command
+      command: '\bgit\s+push\b'   # Ruby regex on the command (data heredoc bodies left out)
       verdict: ask           # ask | deny
       reason: git push publishes commits
       scopes: [once, session, repo]   # optional; default all four
@@ -248,6 +248,23 @@ guardrails:
 
 A rule gives at least one of `tool`, `command`, `path`, `git`, `touches`, `rm` and `memory`.
 
+`command:` reads the command without the body of a heredoc its command
+only reads as data: `cat` or `tee` to stdout, `git commit`/`git tag` with
+`-F -`/`--file -`, `gh pr|issue`/`gh release` with `--body-file -`/
+`--notes-file -`, and a `"$(cat <<'EOF' … EOF)"` given to `-m`, `--body`
+or another message option. Each counts only when its command ends at a
+newline, `;`, `&&` or `||` and sits outside any `( … )` or `{ … }` group;
+the `<<TAG` word and the terminator line stay in the text, so a rule on
+`<<` or on what follows the terminator still matches. A heredoc fed to
+anything else (`bash`, an interpreter, `ssh`, a wrapper), an unquoted one
+whose body holds `$(…)` or backticks, a piped one, a file-writing
+`cat`/`tee` (a `>&2` or `>&-` writes no file; `>& file` does), a
+here-string and an unterminated heredoc all stay in it. An fd opened
+earlier and written to by number (`exec 3>r.sh; cat <<E >&3`) isn't
+followed, so that body counts as data: out of scope here, which is
+chi-nah's job for a model that goes looking. Approvals, the approval
+question and hooks see the whole command.
+
 `memory: remove` matches a `memory_write` with `remove: true` (it moves a
 memory into the bundle trash). Nothing else asks about it: a memory's file is
 never outside the repo (below), so without such a rule any session, a delegate
@@ -493,7 +510,7 @@ only by the user: these change a model's system prompt for later sessions (see
 [Model notes](memory.md#model-notes); a shell command reaches them only under
 `shell-touches-chi`'s text heuristic); and answering chi's
 questions around `chi answer`: `chi --attach` or `chi -p` with stdin from a
-pipe, a here-string or a file (`chi-answer-piped`), and `curl`/`wget` to a
+pipe, a here-string or a file, not `/dev/null` (`chi-answer-piped`), and `curl`/`wget` to a
 session's `/answer` route (`chi-answer-http`), both once or for the session.
 `chi answer` itself isn't asked about. It denies writes into `.git/hooks`.
 
@@ -591,7 +608,13 @@ else goes to chi's own rules. It needs nah installed; see its README for the set
 
 Text matching on shell commands stops accidents, not a model set on getting
 around it: `sh -c`, base64, a script written earlier, `git -C` variants and
-aliases can get past a regex. `outside_repo` covers the file tools and git
+aliases can get past a regex, and these rules are built for trusted models (a
+model set on getting around them is chi-nah's job). A heredoc counts as data
+only for the consumers listed under [Rules in config.yml](#rules-in-configyml)
+(`cat`/`tee` to stdout, `git commit`/`git tag` `-F -`, `gh`'s body and notes
+files, a `"$(cat <<'EOF' … EOF)"` message): anything else keeps its body in
+the text a rule sees, and a function or alias shadowing a reader in the same
+command isn't seen at all. `outside_repo` covers the file tools and git
 only: `sed -i`, `cp` or `cat > file` into another folder from the shell aren't
 asked about, and neither is git run through `sh -c`, a script, an alias, `make`
 or a folder in a variable. `!cmd` lines typed by you are not checked. The only

data/docs/internals/anthropic.md

@@ -180,7 +180,9 @@ Why not send drop_block on every request: it needs adaptive or enabled thinking
 thinking field, `off` sends disabled), it would put a beta header on every request to every host, and it would drop
 the same blocks again on every request until something pruned them. The reactive form does the same work in one
 place, for one extra 400 round trip per break. The `anthropic-thinking-prefix-mismatch` diagnosis header (on the
-400, undocumented) is kept on the provider error and logged as `diagnosis` on `thinking_recovered`.
+400, undocumented) is named by the adapter to its `LLM::HTTP` (`diagnosis_header:`, from
+`AnthropicBindingRecovery::DIAGNOSIS_HEADER`), which keeps it on the provider error; it is logged as `diagnosis` on
+`thinking_recovered`. The shared transport reads no provider header of its own.
 
 ## Cache breakpoints
 

data/docs/internals/bundles.md

@@ -44,6 +44,10 @@ user-facing side (what a bundle owns, profiles, needs) is in [memory.md](../memo
 Readers of the installed state: `Hooks::BundleLoader` (Engine), `GuardrailWiring#bundle_rules`, `Plugin::Loader`,
 `ContextProviders` (scripts), `BundleNeeds` (index markers). Each goes through `Provenance.each_installed` / `#record`
 and checks the recorded sha256 (and `requires_chi`) before loading.
+The checks live in `Hooks::BundleLoader.load` and `Plugin::Loader.load_bundle`; the loading itself is
+`BundleLoader.load_hook_file` (one hook file, into a given `namespace:`) and `Plugin::Loader.register_file` (one
+plugin file: build, `register`, `commit!`), which raise instead of logging: the bundle test kit
+(`Samagotchi::Testing::Bundle`) loads a bundle's source through them, unchecked.
 
 ## Installer#run, in order
 

data/docs/internals/engine.md

@@ -350,14 +350,22 @@ read: the idle scheduler, the Bridge's request threads, plugin threads, the UIs.
 TurnState
   ├── running?
   ├── controller        (the running turn's CancellationController)
+  ├── thread, ended     (the turn's own thread; its end event is out: post-turn work)
   ├── sink              (the turn's on_event)
   ├── steers            (plugin steers for the running turn's next boundary)
   ├── carried_steers    (for the next turn that begins)
   └── activity clock    (last_activity_at, activity_seq)
 ```
 
-- `begin!(controller:, sink:)`: running, with controller and sink, in one step; carried steers become steers.
-- `finish!`: not running, controller and sink cleared; returns the steers never taken (logged as dropped).
+- `begin!(controller:, sink:)`: running, with controller and sink (and the calling thread, the turn's own), in one
+  step; carried steers become steers.
+- `ended!`: the turn's end is decided (`end_turn`, next to `turn.ended`): its after_turn / session_end hooks run
+  after it and before `finish!`.
+- `own_controller(handler:)`: the controller for work done for the turn itself, which a plugin's `ctx.http` call
+  without `cancel:` stops with (`Plugin::Host#cancel_controller`, `Engine#plugin_cancel_controller`): the turn's, on
+  its thread or inside a plugin handler, until `ended!`; nil elsewhere (an anytime command, a service, a plugin's
+  own thread) and outside a turn. An init task's own controller wins inside one.
+- `finish!`: not running, controller, thread and sink cleared; returns the steers never taken (logged as dropped).
 - `steer(text, source:)`: queues a steer for the running turn (false with no turn).
 - `steer_next_turn(text, source:)`: queues a steer for the next turn that begins.
 
@@ -515,7 +523,8 @@ Engine initialization (in this order, among other things):
   @tools = Tools::Builtins.registry; @command_registry (SessionCommands' built-ins); @plugin_tasks
   @toolkit_binding (ToolkitBinding: the kits, the plugins' among them, and the turn-start apply)
   @thinking_notices (ThinkingNotices); @tool_index = Tools::ToolIndex.new; @peer_sources = PeerSources.new
-  the bundles' plugins load (load_plugins → ExtensionLoad#load_plugins),
+  the bundles' plugins load (load_plugins → ExtensionLoad#load_plugins; each plugin's ctx is a
+    Plugin::Context over plugin_host, whose ctx.sessions it builds itself: the test kit passes its own, sessions:),
     then (plugins or not) @tool_index.declare(@tools): find_tools + call_tool (source "index", not core),
     declared per toolkit by Registry#declared? (a source registered at load, or a reachable built-in) and
     sets call_tool's unwrap (Tools::ToolIndex: the chi group from Registry#reachable_names, the sources'
@@ -728,6 +737,7 @@ Paths are under `lib/samagotchi/`.
 | `toolkit_binding.rb` | `ToolkitBinding`: the Engine's toolkit seam (the kits, `#explained`, `ctx.use_toolkit`, the turn-start `#apply!` behind `Engine#apply_toolkit!`) |
 | `hooks/registry.rb` | Hook registry, fire order, `Hooks::Runtime` |
 | `hook_routes.rb` | `HookRoutes`: the Engine's routes for a hook's or plugin's notice (`:hook_notice`, `fallback_for:`), question, stop and steer, and the guardrails' after-load line |
+| `question_desk.rb`, `pending_question.rb`, `question_answer.rb` | `QuestionDesk`: the one open question (ask, post, answer, cancel, relay mark); `PendingQuestion` and `QuestionAnswer`, its values (Hashes only in events, Bridge JSON, the session file and the hook/plugin `ask_user` result) |
 | `event_routes.rb` | `EventRoutes`: where a card (`Engine#show_card`), a notice (`HookRoutes#notify`) and a guardrails line (`#guardrail_notify`, turn or between turns only) go: held while the plugins load, an anytime command's, an init task's, a running turn's event, else announced or held for `holding_announcements` |
 | `engine_peers.rb`, `peer_sources.rb` | `Engine::PeerView` (what the kernel's peer tools see of the Engine) and `Engine::RelayPeer` (a delegate's approval relay); `PeerSources`: the attached context sources a peer bundle declares as its peer's answers (`chi.peer_source`) |
 | `extension_load.rb` | What an Engine loads at start: config.yml and bundle hooks, plugins, `bundles:` settings; events held while plugins load |

data/docs/plugins.md

@@ -744,6 +744,7 @@ full label, `plugin.rb (bundle my-bundle)`.
 | `ctx.stop_turn(reason)` | stop the running turn after a warn notice with the reason; true when it stopped one now. In a `:before_tool_call` block it also denies that call |
 | `ctx.stop_generation(reason)` | cut the generation that is streaming: the turn goes on and the model is asked again ([hooks.md](hooks.md#watching-the-stream)). Shows nothing: post your own notice. True when it cut one now |
 | `ctx.ask_model(messages:, prompt:, …)` | a side answer from the session's model: see [Side answers](#side-answers-ctxask_model) |
+| `ctx.http` | an HTTP client for calling services (`get`, `post_json`, `request`): see [Calling services](#calling-services-ctxhttp) |
 | `ctx.sessions` | fork, send to, read, list and stop other sessions: see [Other sessions](#other-sessions-ctxsessions) |
 | `ctx.toolkit` | the name of the session's toolkit (`full` for a session from before toolkits); nil with no session |
 | `ctx.declared_tools` | the tool names the session's next turn declares (its toolkit resolved, with its own adds and removes): ask this, not the name, whether a tool is there |
@@ -842,6 +843,10 @@ next turn never see it, and no hook fires. It returns the answer text.
 - `max_tokens:` defaults to 1024. An answer cut off by it ends with `…`.
 - `cancel:` takes a `Samagotchi::CancellationController`; cancelling it
   aborts the request.
+- `model:` names a configured model instead of the session's: `"host:id"` for a host in config.yml `hosts:`, an
+  alias from `models:`, or a bare id one of the hosts lists or declares. The host's own key and settings are used;
+  a plugin never names a URL or a key here (that is [`ctx.http`](#calling-services-ctxhttp)). A ref that names
+  nothing configured raises `ArgumentError`, asking nothing: a typo never goes to another model.
 - It blocks until the answer comes, so call it from an anytime command or a
   thread of your own. A local server that runs one request at a time
   (llama.cpp with one slot) answers it after a running turn's current
@@ -853,6 +858,83 @@ next turn never see it, and no hook fires. It returns the answer text.
 It goes through the host's OpenAI API (`/v1/chat/completions`), which
 llama.cpp serves on a native host too.
 
+Each call counts in the session's side requests, under the bundle's name: `/stats`' `side requests:` line and the
+web's ctx tooltip (`2 (btw 1, recap 1) · …`), with its tokens and its cost (reported, else estimated from the target
+model's price), never in the session's own totals.
+
+## Calling services: `ctx.http`
+
+```ruby
+# The http-echo bundle (spec fixture, docs/plugins.md "Calling services"):
+# one tool that asks a local HTTP service and returns its answer.
+class Plugin
+  def initialize(settings)
+    @url = settings.fetch("url", "http://127.0.0.1:9000/ask")
+  end
+
+  def register(chi)
+    chi.tool "ask_service", "Ask the local question service and return its answer",
+             params: { question: { type: "string", description: "What to ask", required: true } },
+             label: "asking" do |args, ctx|
+      res = ctx.http.post_json(@url, { question: args["question"] }, timeout: 5)
+      if res.ok?
+        res.json["answer"].to_s
+      else
+        ctx.log.warn(:ask_failed, status: res.status)
+        "the service answered #{res.status}"
+      end
+    rescue Samagotchi::Plugin::HttpError => e
+      "the service is not reachable: #{e.message}"
+    end
+  end
+end
+```
+
+That is `spec/fixtures/http_echo_bundle` (a spec keeps the two the same; `chi bundle install` it to try it): the
+shape to copy for a plugin that calls a service, tested on `bundle.http` as in
+`spec/samagotchi/plugin/http_echo_bundle_spec.rb`.
+
+One way to call an HTTP service, with timeouts, errors, logging and Stop handled the same for every bundle.
+`Net::HTTP` stays available for what this doesn't do (streaming, multipart, redirects, connection reuse).
+
+| | |
+|---|---|
+| `ctx.http.get(url, headers: {}, timeout: 10)` | GET |
+| `ctx.http.post_json(url, body, headers: {}, timeout: 10)` | POST `body` encoded as JSON, with `Content-Type` and `Accept: application/json` (unless `headers` names them) |
+| `ctx.http.request(method, url, body: nil, headers: {}, timeout: 10)` | GET, POST, PUT, PATCH, DELETE or HEAD; `body` is a String sent as is (set your own `Content-Type`) |
+
+Every call also takes `cancel:`, a `Samagotchi::CancellationController`, which replaces the default (below).
+
+- `url` is a String or URI, `http` or `https`. A bad URL, another scheme, an unknown method, a bad header, a
+  `timeout` that isn't a positive number, or a body `post_json` can't encode as JSON raises **ArgumentError**
+  before any request.
+- `timeout` (seconds) is the connect, the write and the **per-read** timeout, not a total deadline: a server that dribbles
+  bytes can take longer.
+- It returns a `Samagotchi::Plugin::Http::Response`: `status` (Integer), `headers` (frozen, lower-case names,
+  repeated values joined with `", "`), `body` (a String, `""` for HEAD or no body), `ok?` (2xx) and `json`. A
+  **4xx or 5xx is returned, not raised**: check `ok?`. A redirect is not followed: the 3xx comes back with its
+  `location` header.
+- `body` is tagged UTF-8 when its bytes are valid UTF-8, else left binary: `body.scrub` it before handing unknown
+  text to the model. There is no size limit: don't read an endpoint you don't trust to be small.
+- `json` parses the body on each call and raises `HttpError` ("not JSON: …") when it isn't JSON.
+- **One error type.** `Samagotchi::Plugin::HttpError` means the request didn't complete: refused, timed out, DNS,
+  TLS, reset, a malformed response, a bad compressed body, or `json` on a body that isn't JSON. No raw `Errno`,
+  `Net::` or `Zlib` error escapes (the original is the error's `cause`). The message says what and where
+  (`"POST 127.0.0.1:9000: connection refused"`), never headers or a body. `Samagotchi::Plugin::HttpCancelled`
+  (a subclass) means the call was cancelled.
+- `http_proxy`, `https_proxy` and `no_proxy` are honoured as for chi's model calls (loopback is never proxied).
+  chi's own `User-Agent` is always sent: yours is replaced.
+- **Stop.** A call made for the turn (a tool, a hook's handler) stops when the turn is stopped, and a call inside an
+  init task when chi shuts down; a call from your own thread, a `chi.service` or an anytime command has only its
+  timeout unless you pass `cancel:`. After the turn has ended (an `:after_turn` or `:session_end` hook of a
+  stopped turn) a call is not cancelled by that stop. A service's start block counts as the service's even when its
+  first `value` comes from a handler.
+- **The log.** Each call writes one `http` line to the debug log: INFO (ERROR when it fails) with `bundle=`,
+  `purpose=plugin`, the method, the URL **without its query**, the status and the time. Never headers or bodies.
+  A plugin that polls a dead service therefore logs an ERROR per poll.
+
+`ctx.http` is experimental until 1.0, like the test kit.
+
 ## Other sessions: `ctx.sessions`
 
 ```ruby
@@ -1003,7 +1085,9 @@ CHANGELOG line and bumps the shipped bundles that use it. Anything else under
    `Samagotchi::Plugin::ToolResult`, `Samagotchi::Plugin::ModelError` (and its
    subclass `Samagotchi::Plugin::ModelCancelled`),
    `Samagotchi::Plugin::Service::Stopped`, `Samagotchi::Plugin::Sessions::Error`
-   and `Samagotchi::Plugin::AttachedContext::Error`.
+   and `Samagotchi::Plugin::AttachedContext::Error`. `ctx.http` and its
+   `Samagotchi::Plugin::HttpError` (with the subclass `HttpCancelled`) and
+   `Samagotchi::Plugin::Http::Response` are **experimental until 1.0**, like the test kit.
 2. `Samagotchi::Plugin::Peer` as a base class. A subclass defines `post`,
    `check_hint!`, `paired_lines`, `transport_line`, `peer_dir` and
    `setup_paragraph` (optionally `skill_substitutions`), and sets `NAME`,
@@ -1020,6 +1104,12 @@ CHANGELOG line and bumps the shipped bundles that use it. Anything else under
    `Samagotchi::Log.debug`, `Samagotchi::Config.get` and
    `Samagotchi::VERSION`.
 
+`Samagotchi::Testing::Boundary::ALLOWED` is the checked copy of this list,
+and `Boundary::EXCEPTIONS` the per-bundle list of what each shipped bundle
+(and its specs) reaches beyond it, each with why: the APIs to design before
+that bundle could leave chi's repo. `spec/samagotchi/testing/boundary_spec.rb`
+fails on a reference in neither (docs/testing.md).
+
 **Used by shipped bundles today, but internal** (may change without notice; a
 bundle that needs one should ask for an API instead):
 
@@ -1032,6 +1122,62 @@ bundle that needs one should ask for an API instead):
   `Samagotchi::Guardrails::GitInfo`.
 - `Samagotchi::Tools::Execute.const_get` reflection.
 
+## Testing a bundle (experimental)
+
+`samagotchi/testing` loads a bundle the way chi does and records what it does at chi's edges, so a test
+needs no fake `chi` or `ctx`. It is **experimental**: it may change in any release before 1.0.0 and is not
+part of "Stable for bundles".
+
+```ruby
+require "samagotchi/testing"
+
+bundle = Samagotchi::Testing::Bundle.load("path/to/my-bundle", settings: { "every" => 3 },
+                                          host: { session_id: "s1", cwd: Dir.pwd })
+bundle.fire(:after_turn, status: "completed")            # → the event, after the hooks
+bundle.command("/mine stop")                             # → what the command returned
+bundle.tool("my_tool", path: "a.txt")                    # → the text the model reads
+verdict = bundle.tool_call({ name: "execute", content: "rm -rf /" })
+verdict.deny?                                            # a real Guardrails::Verdict (votes: verdict.votes)
+bundle.notices.map(&:text)                               # also cards, steers, stops, generation_stops, questions
+bundle.answer({ selected: "yes" })                       # the next ask_user's answer
+bundle.model_answers << "a summary"                      # the next ask_model's answer
+bundle.sessions.on(:children) { |all:| [] }              # ctx.sessions, scripted and recorded
+bundle.http.stub(:post, "http://127.0.0.1:9000/classify", json: { label: "safe" })   # ctx.http, never the network
+bundle.set(running: false)                               # the session's values: cwd:, messages:, cancelled: …
+bundle.shutdown
+```
+
+- **Real seams.** The plugin loads through `Plugin::Loader.register_file` (the real `chi` API and a real `ctx`),
+  the hook files through `Hooks::BundleLoader.load_hook_file`, into registries that already hold chi's own
+  commands and tools: a name chi has fails the load as it would in chi. `tool_call` runs a real
+  `Guardrails::Gate` (context and targets computed for the call; `verdict:` starts from one with a vote in it).
+  Only the edges are recorded: the session (`Testing::Host`), the hook helpers (`Testing::Runtime`),
+  `ctx.sessions`, `chi.init` tasks (`bundle.run_inits`) and `chi.replace_tools` sets
+  (`bundle.apply_staged_tools!`). No sha256 or `requires_chi` check: it loads the source as it is.
+- **More:** `bundle.plugin` (the instance `register` ran on, for its own methods), `bundle.declarations` (the
+  `chi.*` calls `register` made, in order, as made), `bundle.namespace`, `bundle.hook_names(event)`,
+  `bundle.run_inits`, `sandbox.write_memory(name, text, scope:)` / `memory_dir`, `sandbox.fake_executable(name,
+  body)` (first on `PATH`), `wait_until { }`.
+- **`ctx.http` is faked.** `bundle.http.stub(method, url_or_regexp, status: 200, headers: {}, body: nil, json: nil,
+  error: nil) { |request| … }` answers it: a String URL matches exactly (query included), a Regexp the full URL, later
+  stubs win, and a stub answers every matching call (a block that counts makes a sequence). `error: :refused` or
+  `:timeout` raises the `HttpError` the real client would; `bundle.http.requests` lists what the plugin sent
+  (`method`, `url`, `headers`, `body`, `json`) and `bundle.http.unmatched` what no stub answered. A request no stub
+  answered raises `Samagotchi::Testing::UnstubbedRequest` (not an `HttpError`, but a plugin may rescue it anyway) and
+  **fails the test at teardown** (RSpec and Minitest adapters: after the cleanup, and only a test that passed), so a
+  spec can't reach the network. With plain `Bundle.load` there is no teardown: check `bundle.http.unmatched`.
+  `bundle.set(cancelled: true)` makes a call without `cancel:` raise `HttpCancelled`.
+- **A hook that raises fails the call** (`Testing::HookFailed`, with the hook's error) where chi would log it and
+  go on; `bundle.lenient { … }` collects them in `bundle.errors` instead.
+- **Sandbox.** A test runs with temp config, state, data and cache homes (config.yml, memories, `ctx.data_dir`, the
+  debug log), `HOME`, `CLAUDE_CONFIG_DIR` and `CODEX_HOME`, no git config of yours, no Keychain and none of your
+  `SAMAGOTCHI_*` settings; `sandbox.config(hash)` writes its config.yml.
+- **RSpec:** `require "samagotchi/testing/rspec"`; example groups tagged `:bundle` (a spec under a bundle's own
+  `spec/` is tagged by itself) get `load_bundle(dir)`, `shipped_bundle(name)` and `sandbox`, each example in its
+  own sandbox, its bundles shut down after it (chi's shipped bundles keep theirs in `<bundle>/spec/`,
+docs/testing.md). **Minitest:** `require "samagotchi/testing/minitest"` and subclass
+  `Samagotchi::Testing::Case` (the same helpers).
+
 ## The btw bundle
 
 `chi bundle install btw` (or the `dev` profile) installs the bundle shipped with chi. It is written
@@ -1097,7 +1243,7 @@ bundles:
   and values: only the digest is stored) and `cwd`. A session with a saved
   list can search its tools at once and **doesn't start the server**: the
   first call of one of its tools does (the call's row shows the wait). So a
-  session that never uses MCP spawns nothing, and a new chat opens without
+  session that never uses MCP spawns nothing, and a new session opens without
   waiting for `npx`. If the live list differs from the saved one, the saved
   one is replaced, and so is what a search finds. The model's tools never
   change, so the prompt cache keeps. The saved file also keeps the first
@@ -1127,7 +1273,7 @@ bundles:
   you want at once.
 - **`npx -y …@latest` checks the npm registry on every start** (~3.4 s for
   `chrome-devtools-mcp`, against ~0.9 s for the installed binary). The cache
-  hides it from new chats, but not from the first call. For a faster first
+  hides it from new sessions, but not from the first call. For a faster first
   call, install the server once and run it directly:
 
   ```yaml