samagotchi 0.78.0 → 0.80.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1b19c3433cc4f46956563a8e4e6532d8b60061084b8050b534b9230b3c608c54
-  data.tar.gz: 97b8e078c43e1c9901139f1f937d16e43b57b6147cd8298fbb9b77abb37c0b96
+  metadata.gz: 5e8f390119025dcb6df095574fb9e59e94952c709a69ae6bc6e02ffa037e1a0d
+  data.tar.gz: c67e91b18d0ef7ac8916b03045c214c12ebcf98b469f84b0ae355bb41491388e
 SHA512:
-  metadata.gz: '0022706491e62a2d7f603a5290fd4c5525b17c6712af6d31dc5ce163b36c4e4414074d7b4da609f890ec5e243ea89b33a5ba0621528d8face6c5226108d0a443'
-  data.tar.gz: da23fef030284a3401d5ec17017ef2a7d1165d30909f4a96e095823315bc38bbbe1eaf1bdfd76eefe604af19cd160c5f68fd19cb3c4ccb478b28bd9ea1de57eb
+  metadata.gz: 4c936b332ee7cafb74cb4e09b7f3b80acac7ba1247988e755078c61e72c201489b1a48f8970c6c3d70d88b7cedc31cf432d01c5b14018073a517b65f76e45de6
+  data.tar.gz: dc77457ac7bf6a0018966bef40ccaa67da732a43edbe21e0fbcef1193583a3e00934c70c4230d3fcf14f5dd23012730f9c41bb16be8d7a64754f361ff3c2ab4a

data/CHANGELOG.md

@@ -8,6 +8,47 @@ and commands may change between minor versions. How releases are made:
 
 ## [Unreleased]
 
+## [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
+
+- Web: a repeated toast cannot unstick a sticky error and make it time out.
+- Anthropic: `api: anthropic` hosts on the Claude API now read their model list, including 1M-token windows and image
+  input, so `chi models` and model validation work.
+- Anthropic: on Claude 5.x models, which turn thinking off by `between_tools` and refuse `disabled`, recaps, side
+  answers and `--thinking off` sessions now send `thinking: {type: "between_tools"}` after that 400 (a recap used to
+  fall back to adaptive thinking at low effort, a `--thinking off` session to the provider's default thinking). Each
+  side-answer client learns it once for itself.
+- A host whose model list fails is asked again at most once a minute (it was asked on every context-window lookup).
+
 ## [0.78.0] - 2026-10-17
 
 ### Added
@@ -3269,7 +3310,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.78.0...HEAD
+[Unreleased]: https://github.com/dm1try/samagotchi/compare/v0.80.0...HEAD
+[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
 [0.76.0]: https://github.com/dm1try/samagotchi/compare/v0.75.0...v0.76.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/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`
@@ -662,9 +676,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
@@ -644,8 +647,10 @@ What each backend gets:
 | Messages host, `dialect: fireworks` | `thinking: {type: "disabled"}` | `thinking: {type: "adaptive"}` and `output_config: {effort: <level>}` (no `display`) |
 
 On a Messages host `default` sends nothing: the provider's own default, which differs by model (some Claude models
-think adaptively but show no thinking text, their blocks still going back; others, and Splash, don't think at all). A model that refuses `disabled` (current
-Claude models) gets the request again without it, as on any chat host. A model that refuses adaptive thinking
+think adaptively but show no thinking text, their blocks still going back; others, and Splash, don't think at all). A model that refuses `disabled` and names `between_tools` in the 400 (Claude 5.x) gets `thinking: {type:
+"between_tools"}` wherever `off` asked for `disabled`, from then on: the adapter keeps that per model for as long as it
+lives, so a worker's turns keep it, and each side-answer client (recap, `ctx.ask_model`, a broadcast's triage) learns it
+once for itself. One that refuses `disabled` without naming it gets the request again without it, as on any chat host. A model that refuses adaptive thinking
 (older Claude: Haiku 4.5) is switched, once and for the worker's life, to the budget form: `thinking: {type:
 "enabled", budget_tokens: B}` with B 2048 / 8192 / 24576 for low / medium / high and no effort; `max_tokens` always
 stays above the budget (the budget is lowered to leave 1024 for the answer, or `max_tokens` raised to 2048). A
@@ -1465,8 +1470,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/internals/anthropic.md

@@ -17,7 +17,7 @@ ChatLoop::Run#generate
       → POST {base}/v1/messages             # LLM::HTTP: retries, cancel, first-token limit
       → AnthropicAssembly#add per SSE event # → ChatResponse (text, reasoning, tool_calls, usage,
                                             #   finish_reason, provider_content)
-      → a signature 400 (Claude 5.x preserved thinking): #binding_recovery, then the same
+      → a signature 400 (Claude 5.x preserved thinking): AnthropicBindingRecovery#advance, then the same
         request with drop_block or the blocks stripped; ChatResponse#thinking_drop names them
       → a 400 it can fix: #refusal_fix, then the same request again (once per kind)
   → ChatLoop#settle_dropped_thinking!       # the dropped blocks leave the stored model entries
@@ -31,6 +31,7 @@ Paths are under `lib/samagotchi/llm/`.
 |---|---|
 | `adapters.rb` | `Adapters::BY_API` (`openai`, `anthropic`), `.for(entry)`, `.build(api:, …)` for side requests (`IdleClient`) |
 | `anthropic_messages.rb` | `AnthropicMessages`: the request body, `#chat` (streamed or not), the 400 fixes, `#list_models`, `#thinking_fields`, `#replays_content?` |
+| `anthropic_binding_recovery.rb` | `AnthropicBindingRecovery`: the preserved-thinking recovery (`#advance` picks drop_block or strip for a signature 400, `#recovered_body`, `#with_thinking_drop`); one per adapter |
 | `anthropic_wire.rb` | `AnthropicWire`: ChatLoop's wire messages as Messages' `system` and `messages`, the two breakpoints, tool ids and names |
 | `anthropic_assembly.rb` | `AnthropicAssembly`: a response from a whole body (`.from_message`) or stream events (`#add`), its usage in the OpenAI shape |
 | `dialect.rb` | `Dialect` (`STANDARD`, `FIREWORKS`): what a provider's `/v1/messages` does differently |
@@ -54,7 +55,8 @@ with `tool_choice: {type: "auto"}` (when any), then the loop's options. The opti
 (`default.max_tokens`), else the model list's `max_tokens` capped at `DEFAULT_MAX_TOKENS` (64000), and never over an
 output cap a 400 named. `#with_budget_room` keeps `max_tokens` above a budget-form `budget_tokens` plus `MIN_BUDGET`.
 
-`#thinking_fields(level)` is the thinking level on this wire: `off` is `thinking: {type: "disabled"}`; `low`, `medium`
+`#thinking_fields(level)` is the thinking level on this wire: `off` is `thinking: {type: "disabled"}` (sent as `{type:
+"between_tools"}` to a model whose 400 for `disabled` names that form, Claude 5.x: see the 400 fallbacks); `low`, `medium`
 and `high` are `thinking: {type: "adaptive", display: <dialect's>}` with `output_config: {effort: <level>}`; `default`
 sends nothing. `#thinking_off_refused_fields` (low effort) is what `IdleClient` sends a side ask whose model refused
 thinking off.
@@ -137,7 +139,7 @@ A model switch never 400s: the API drops blocks another model can't read silentl
 
 **Recover on the 400, then settle.** Normal requests carry no beta header and no `block_binding`, so Fireworks,
 Splash and gateways see the same bytes as before. On a signature 400, before anything streamed,
-`AnthropicMessages#binding_recovery` picks the next step, once each per request:
+`AnthropicBindingRecovery#advance` (one per adapter, `anthropic_binding_recovery.rb`) picks the next step, once each per request:
 
 - **drop_block**: the same body with `thinking.block_binding: {prefix_mismatch_behavior: "drop_block"}` (the body's
   adaptive or enabled thinking, `display` as sent; adaptive when the level sends none) and the header
@@ -178,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
 
@@ -209,12 +213,15 @@ thinking, nil for none), `cache_breakpoints` and `session_header`.
 
 `AnthropicMessages#chat` handles the 400s it can fix itself, once each per request, and remembers the fix for the
 adapter's life, so ChatLoop's broader paths never see them (`#refusal_fix`, logged under `http`; kept in an
-`LLM::RefusalMemo`, locked, since the turn, side-ask and recap threads share the host's adapter):
+`LLM::RefusalMemo`, locked, since the turn thread and the model-list reads share the host's adapter; `IdleClient`,
+whose recap, side answers and triage each build their own adapter (`Adapters.build`), keeps what it learned for that
+client's life only):
 
 | 400 about | Fix | Remembered |
 |---|---|---|
 | `thinking.display` (`DISPLAY_RE`) | no `display` from now on (`#without_display`), the thinking kept | per host (`thinking_display_refused`) |
 | adaptive thinking or its effort (`ADAPTIVE_REFUSED_RE`) | the budget form: `thinking: {type: "enabled", budget_tokens: BUDGETS[level]}`, no effort (`#budget_form`) | per model (`thinking_form_switched`) |
+| `thinking: {type: "disabled"}` where the 400 names `between_tools` (`THINKING_OFF_FORM_RE`; Claude 5.x) | `thinking: {type: "between_tools"}` wherever `disabled` was asked (`#thinking_between_tools`), so a recap or side answer (`IdleClient` step 0) and a `--thinking off` session never fall back to adaptive low or to no thinking fields; a model that refuses `between_tools` too raises the 400 as before | per model (`thinking_off_form_switched`) |
 | `cache_control` | no breakpoints | per host (`cache_control_refused`) |
 | `max_tokens: N > M` (`OUTPUT_CAP_RE`) | `max_tokens` capped at M | per model (`output_cap`) |
 | `block_binding` or the binding beta, on a drop_block retry (`thinking_binding_unsupported?`) | the strip instead (Preserved thinking) | per host (`binding_controls_refused`) |

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

@@ -273,8 +273,8 @@ One iteration with tool calls:
           → an ask verdict: Gate#settle_ask (asks the user, records waited_ms)
           → KernelLoop#dispatch_tool_call, or the denial text
           → :tool_call_completed, then the :after_tool_call hook
-          → returns {output:, capped_output:, truncated:, activity:, images:, shown_params:,
-                     shown_label:, diff:}
+          → returns a ToolRun value object with output, capped_output, truncated, activity, images, shown_params,
+            shown_label, refs, diff and output_file; fields a call doesn't produce are nil
       → :tool_dispatch_completed {iteration, call_count}
     → native: ToolResponse.joined(runs, ids:), one entry with the capped outputs
       chat:   ToolResponse.single(run, tool_call_id:, ids:) as each call finishes (the block), with the
@@ -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,78 @@ 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.
 
+## 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.
+- **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 +1080,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 +1099,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 +1117,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 and state 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 +1238,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 +1268,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

data/docs/releasing.md

@@ -63,7 +63,7 @@ as the GitHub release body.
 | `rake 'bundles:check[ci]'` | The CI workflow's (every push and PR): the same, except the version check leaves out the system bundle, which is changed and unbumped between releases (`release:bump` moves its version with VERSION). A task argument, not `CI=1`: GitHub sets `CI` in the release workflow too. |
 | `rake release:draft_changelog` | A draft Unreleased section from the commit subjects since the last tag, grouped. Stdout only. |
 | `rake release:bump[X.Y.Z]` | VERSION, the system manifest, Gemfile.lock, CHANGELOG, and `requires_chi: ">= X.Y.Z"` for each bundle marked `requires_chi_next` (the marker dropped). No commit. |
-| `rake release:check` | Clean tracked tree, VERSION == system bundle, a CHANGELOG section, no `requires_chi_next` left, `bundles:check`, `rake lint` (RuboCop), rspec + npm test, `gem build`, then a clean install into a temp GEM_HOME that runs `chi --version`, `chi self` and `chi bundle list` with a temp HOME. Needs the network (gem dependencies). |
+| `rake release:check` | Clean tracked tree, VERSION == system bundle, a CHANGELOG section, no `requires_chi_next` left, `bundles:check`, `rake lint` (RuboCop), rspec (both roots: `spec` and the bundles' own `spec/`) + `rake bundles:specs` + npm test, `gem build`, then a clean install into a temp GEM_HOME that runs `chi --version`, `chi self` and `chi bundle list` with a temp HOME. Needs the network (gem dependencies). |
 | `rake release:notes[X.Y.Z]` | Prints the CHANGELOG section (default: the current VERSION). |
 
 ## Runbook
@@ -165,4 +165,4 @@ things differ there, and a new spec that trips on them fails only on CI:
 To run it locally, use Docker with the Ruby build CI uses
 (`ruby-X.Y.Z-ubuntu-24.04-x64.tar.gz` from ruby/ruby-builder's releases) on
 `ubuntu:24.04` with `LANG=C.UTF-8`, `zip` and `git`, and run
-`CI=1 BUNDLE_PATH=… bundle exec rspec`.
+`CI=1 BUNDLE_PATH=… bundle exec rspec spec lib/samagotchi/bundles/*/spec`.