samagotchi 0.18.1 → 0.19.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 34f4c3e1960aa23902e27160bd1f325ba035731c283a93b2cd819676481c90a2
-  data.tar.gz: 708e58e5bfc26d10fe9f20bd1b696f6355e2a25749a36ca6503e82ca9077fa64
+  metadata.gz: 5b6bb51634467b04d3519fc2c42a778be2db25558565e8e872bc2fbdc17f5c76
+  data.tar.gz: 9f1e4b1bd71272126a3dea346b2b0f5125a608770a97832b17c42ec4a237156b
 SHA512:
-  metadata.gz: 56c634e50c34f3fd027ca9ed7208d7edaab21a639050fe321c1d9fa5e8a0e818a31ae6c6351f8c21c0417984f3235a1a44b14aaa3d415b392a85d3bff2916aa1
-  data.tar.gz: 41862c98747027f791e4aa59b4c6d2eda092d818e3492212fbc79a24970c74734c3196c480511876aa97b95a8e1245c8bfd6fceccb73d47ade67d3f96ced89fa
+  metadata.gz: b1b2eb7e4142061cce070830722bc88625cfc8b8301b97e836751ac9690d0e78984741afd747a6cc9ac42be6a0b59122bc49075273522629eda56f22327999d9
+  data.tar.gz: 6277d5a520c55f5b620f79936321c2536739409ef98a5a7b530e41505a2ffb17bd0bf04987fc0bf027c09a24dbedbea29f61affca2bf7f3a74218bbcf8651df8

data/CHANGELOG.md

@@ -8,6 +8,89 @@ and commands may change between minor versions. How releases are made:
 
 ## [Unreleased]
 
+## [0.19.0] - 2026-10-03
+
+### Changed
+
+- A new or woken session worker runs the newest chi installed, whoever starts it: a `chi web`, `chi send` or
+  terminal left on an older chi no longer starts workers on its own version. A worker already running keeps its
+  version until it is restarted.
+
+### Added
+
+- `chi web` notices a newer chi installed (`chi update`, `gem update`, a `git pull` in a checkout) and says to
+  restart it, in its terminal and once in each open page.
+- The web's info bar marks a session whose worker runs an older chi than the newest installed, with a Restart button
+  (or, for a worker from before restarts, the `chi sessions stop ID` to run); the page and the draft in the
+  composer stay as they are and follow the new worker.
+- An attached terminal says in one line when the session's worker or the terminal itself runs an older chi than
+  the newest installed, and how to move each (`chi sessions restart ID`; `/detach`, then `chi --attach ID`). When
+  the worker restarts, the terminal stays attached and says so.
+- `chi sessions restart ID...` moves a running session to a new worker on the newest chi installed, keeping its
+  attached terminal and web tabs on it; it is refused, with the reason, while a turn, a question, reminders or
+  background tasks would be lost.
+- A bundle can ship per-model memory overlays (`tips.<model-key>.md` beside `tips.md`): they load only for that
+  model, as a `memory_write current_model_only` overlay does, and `chi bundle build tips.md` brings them along.
+
+### Fixed
+
+- `chi update` no longer says running sessions move to the new chi "at idle exit (30 min)": a worker keeps its chi
+  until restarted, and idles out only with nothing attached, after `session.idle_exit_minutes` (never with 0). The
+  workers row names `chi sessions restart ID` (or `stop` for a worker from before restarts).
+- `chi web` no longer leaves exited session workers behind as zombie processes.
+- The web's model picker lists a host added to (or changed in) `hosts:` while `chi web` runs, instead of the hosts
+  it started with.
+- A bundle's model overlay no longer gets an `index.md` line of its own after `chi bundle install`, which showed it
+  to every model as a memory to read; `chi bundle status` reads it `ok (model overlay)`, uninstall no longer re-adds
+  its line, and an overlay whose base is nowhere, or only among your installed memories, installs with a warning. A
+  line an earlier install wrote goes with the bundle's next upgrade.
+- source-links (0.3.2): a `case_insensitive: true` source no longer lists a ref in its `sources:` note when the ref
+  is a markdown link's label whose target names it in another case (`[jira-1](…/JIRA-1)`). Run `chi update` to get it.
+- An `@path` image in a prompt takes backslash escapes, as a Finder drag into the terminal types them:
+  `@my\ shot.png` and `@a\ \(1\).png` attach the file instead of stopping at the first space.
+- An `http` host named by a public name (`gpu.example.com`) counts as a remote provider (120-second first-token
+  limit, no llama.cpp `/props`), as a public IP address already did. Names without a dot and local suffixes
+  (`.local`, `.lan`, `.home.arpa`, `.internal`, `.ts.net`, `fritz.box`, …) stay local; `hosts.<name>.remote` decides
+  either way.
+- `chi web` no longer logs `ERROR HTTPRequest#fixup: WEBrick::HTTPStatus::LengthRequired occurred.` after a POST
+  without a body.
+- The web's delete confirm no longer promises a running worker from a stale list: it says the worker is stopped
+  first if it is still running.
+- The web's scope links (`all`, `← project`) keep the page's `?view=stage|turn`.
+- An approval card's verdict (`Allowed (scope)` / `Denied`) reads above the command it decided, so it no longer
+  looks like part of the tool call when the card's details are expanded.
+- Answering or dismissing a question no longer says "Session is not running" when the worker is live but failed the
+  request: the server answers 502 with the worker's detail and the card shows it. 503 stays for a session with no
+  live worker.
+- A turn that failed to send no longer leaves its prompt waiting to be restored into the composer later; and text
+  typed while a fast-failed turn's prompt was coming back is kept, with the restored prompt going under it.
+- A worker that dies between a turn's end and its after-turn display no longer leaves the turn's answer bubble
+  waiting: the page stops waiting when the worker goes away, or after 20 s.
+- A first web message the page answers itself (`/stats`, `/exit` …) or that is a typo of a command (`/modle`) no
+  longer leaves an empty session behind.
+- A question card reopened after a reload shows its result once, in the collapsed summary, not twice.
+- After a mid-turn reload, this tab's own prompt is still recognized as its own instead of being labelled `web`.
+- A `chi scratch` session no longer offers `send_note`, so it leaves no note behind in another session.
+- A `chi scratch` session's tool approvals offer only "Allow once" and "for the session", and keep a session
+  approval in memory: no "in this repo" or rule approval from it stays in the approvals store.
+- A message sent (web, `chi send`, a delegate) to a session whose worker is slow to start no longer starts a second
+  worker beside it.
+- The note a cancelled turn leaves for the model says "the reply above ends where it was cut off", not "the
+  answer", so narration cut off before a tool call isn't taken for an answer.
+- A session worker that wakes again shows the model the server last said it served (`/stats`, the status row,
+  the web's info bar) right away, instead of none until its first generation.
+- A tool call still running when its turn is cancelled (or fails) is saved in the session's analytics as
+  `canceled`, so the session's tool totals (`/stats`) count it as the turn did instead of dropping it.
+- A session's `analytics.json` `session_duration_ms` runs from the session's `started_at`, not from when its current
+  worker started.
+- A session started with `chi --model X` no longer hands X to the commands it runs as the default model: a `chi
+  self` (or other chi) run there reports and uses the configured default, with X as this session's model. A
+  `SAMAGOTCHI_DEFAULT_MODEL` you export yourself still passes.
+- A preloaded memory that can't be loaded is warned about once, not again each time the prompt is rebuilt (another
+  thinking level, a `/model` switch).
+
+Update with `chi update`: source-links moves to 0.3.2 (case-insensitive link targets). Restart `chi web` afterwards; from now on it tells you when a newer chi is installed.
+
 ## [0.18.1] - 2026-10-03
 
 ### Fixed
@@ -1035,7 +1118,8 @@ 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.18.1...HEAD
+[Unreleased]: https://github.com/dm1try/samagotchi/compare/v0.19.0...HEAD
+[0.19.0]: https://github.com/dm1try/samagotchi/compare/v0.18.1...v0.19.0
 [0.18.1]: https://github.com/dm1try/samagotchi/compare/v0.18.0...v0.18.1
 [0.18.0]: https://github.com/dm1try/samagotchi/compare/v0.17.0...v0.18.0
 [0.17.0]: https://github.com/dm1try/samagotchi/compare/v0.16.0...v0.17.0

data/README.md

@@ -54,9 +54,10 @@ chi update              # the gem, then the bundles and the desktop helper
 stay installed: running sessions still use them), then brings the rest up to
 the new version: the system bundle, the bundles chi ships that you installed,
 and the macOS helper (rebuilt only when its sources changed). Memory files you
-edited are kept, and the table says which. Running sessions move to the new
-chi when their worker idles out (30 min) or on `chi sessions stop ID`; a
-running `chi web` needs a restart. From a checkout, `git pull` instead. See
+edited are kept, and the table says which. Running sessions keep their chi
+until restarted (`chi sessions restart ID`, or the Restart badge on the web);
+new and woken ones start on the new chi. A running `chi web` needs a restart,
+and its page says so. From a checkout, `git pull` instead. See
 [CLI: Updating](docs/cli.md#updating).
 
 ## Set up

data/docs/architecture.md

@@ -213,6 +213,10 @@ process that already owns the `Engine`); every worker starts it, and it exposes:
   too-old reconnects, and cursors from another worker's epoch, receive a `reset` marker carrying
   `session_state_snapshot`. `?snapshot=1` joins with a snapshot frame instead of a replay;
   `?client_id=` names whose stream it is (`Bridge#open_streams_except`, used by `POST /exit`).
+  An attached terminal's stream (`EventStream` with `rediscover:`) looks for the session's live
+  worker whenever it drops: a new one (a restart) is followed from its snapshot, and the terminal
+  sends its requests there (`worker_changed`); it gives up after ~12 s, or at once when the session
+  was stopped.
 - `POST /session/:id/turn` — fire-and-forget turn creation; returns `202` with an `enqueued_id`
   (delivery is at-least-once via the worker's file-IPC input path — it never calls `run_turn`
   across the HTTP boundary). Only the bridge's own session: another id, in the path or the body's
@@ -302,7 +306,13 @@ the server, no daemon) that keeps an in-memory projection of the session list an
 changes to every open tab over `GET /api/events` (SSE: a `snapshot` frame on every connect,
 then `session` for an upsert and `session_gone` for a removal, `: ping` while idle, no replay).
 The snapshot names chi's version: a tab served by another one (its `<body data-version>`) offers a
-reload in a toast, since an open tab keeps its old JS across a `chi web` upgrade.
+reload in a toast, since an open tab keeps its old JS across a `chi web` upgrade. It also names
+`installed`, the newest chi on this machine (`InstalledVersions`: the highest `samagotchi-<v>.gemspec`
+in RubyGems' specification dirs, or a checkout's `version.rb` on disk; looked at again on each full
+probe, every 10 s), and a change is a `chi` frame `{version, installed}`. A newer one than the
+server runs is said in chi web's terminal and on the page: restart chi web (its workers already
+run the newest chi, [Sessions](sessions.md)). `GET /api/info` carries `installed` too, and the
+feature `newest_workers`.
 Files stay the source of truth and workers don't know the hub. Its watcher is a 1 s tick that
 stats the sessions dir (every session writer goes tmp + rename, which bumps the dir's mtime) and
 each `<id>/` folder (recap.json, bridge.json, the stopped and archived markers), re-parsing only the files whose mtime or size
@@ -310,7 +320,10 @@ moved through `Session.summary_from_file`. Liveness is probed, since a killed ow
 file trace: the owner lock every tick for the sessions the projection believes owned, and every
 session every 10 s, so a `kill -9` shows within a second. The summary (`Web::SessionSummary`,
 shared with `/api/sessions` and the session view) carries `owner`, `project_root` and
-`bridge_up` (the sidecar is there *and* the lock is held: the page attaches its stream on it).
+`bridge_up` (the sidecar is there *and* the lock is held: the page attaches its stream on it), and
+from that sidecar `worker_version` (the chi the worker runs) and `worker_features`
+(`Bridge::FEATURES`, what a client may ask of it beyond the routes). A worker's Bridge snapshot
+names its `chi_version` too.
 `POST/DELETE /api/sessions` and `/stop` rescan the session before answering (`SessionHub#touch`).
 `GET /api/sessions` is the hub's projection too (its sort, paging and total). `Server` always builds
 a hub; an `App.new` without one answers both routes `503 no_hub`.

data/docs/cli.md

@@ -15,7 +15,7 @@
 - `chi web --web-host lan` — the Web UI on your home network too, for your phone: a link with an access token and its QR code (see [chi web on your phone](#chi-web-on-your-phone)); `chi web --new-token` replaces the token
 - `chi web --web-markdown` — opt in to sanitized Markdown rendering for completed assistant messages
 - `chi web --web-view turn` — draw turns with the turn view (each turn as one block of steps, the running one at the bottom of the history) instead of the default stage view (the running turn pinned above the composer); `?view=stage|turn` on the page URL overrides it (see [Web views](#web-views))
-- `chi sessions list|stop|archive|unarchive|delete|prune|clean` — manage persisted sessions; `list` shows this git project's, `list --scope=all` every one, a delegated session with `↳ <parent>`, `list --archived` the archived ones too (see [Sessions](sessions.md)). A usage error (an unknown subcommand or flag, a flag missing its value, `stop` or `delete` with no ids, a bad `list --format` or `--scope`) exits 2; an unknown or refused session exits 1
+- `chi sessions list|stop|restart|archive|unarchive|delete|prune|clean` — manage persisted sessions; `list` shows this git project's, `list --scope=all` every one, a delegated session with `↳ <parent>`, `list --archived` the archived ones too (see [Sessions](sessions.md)). A usage error (an unknown subcommand or flag, a flag missing its value, `stop`, `restart` or `delete` with no ids, a bad `list --format` or `--scope`) exits 2; an unknown or refused session exits 1
 - `chi note [--source NAME] [-m TEXT] (ID|PREFIX)... | --all` — add a context note (TEXT or stdin) to sessions: background the model sees on its next turn; it starts no turn (see [Sessions: Context notes](sessions.md#context-notes))
 - `chi send [-m TEXT] [--image PATH]... (ID|PREFIX)...` — send a message to sessions as if typed there: a turn starts (or a running one picks it up); piped stdin goes above `-m` as quoted context, and `--image` attaches images (see [Sessions: Sending a message](sessions.md#sending-a-message)); `--new` starts a session with it instead, and `--wait` prints the answer (`--wait ID` with no message waits for the next reply without sending; `--format json` prints one JSON object instead; exit 3 a question waits, its options on stderr; exit 4 `--timeout` passed with the turn still running; see [Starting a session](sessions.md#starting-a-session))
 - `chi answer ID --question QID (--option N|LABEL)... [--text T] [--timeout S] [--format json]` (or `--dismiss`) — answer the question a session waits on (the one `chi send --wait` exited 3 with), then wait and print what comes next as `chi send --wait` does: the reply (0), the next question (3), still running after `--timeout` (4). `--option` is 1-based or the label, repeated on a multi-select question; `--text` is free text, or a Deny's reason; `--dismiss` leaves it unanswered and the model finishes its reply. A question no longer open (the web answered first) isn't answered again: it waits for that turn's reply. An option the question doesn't offer exits 2; a worker that is gone exits 1 (`send the task again: chi send --wait -m "…" ID`). An approval can be denied, not allowed, unless `guardrails.parent_approvals: once` (a convention, not a security boundary; see [Guardrails](guardrails.md#approvals-from-a-parent-agent))
@@ -104,17 +104,19 @@ known-names    0.1.0  0.1.1  updated
 core           0.1.0  0.2.0  updated (+ new-bundle)
 infra_tools    1.0.0         skipped (not from chi)
 Chi Helper     0.2.0         up to date (launch file refreshed)
-workers                      2 live on 0.2.0: they move to 0.3.0 at idle exit (30 min) or chi sessions stop 2ea8c1f0 91b0d2aa
+workers                      2 live on 0.2.0: they keep it until restarted (chi sessions restart 2ea8c1f0 91b0d2aa); or they idle out after 30 min with nothing attached
 Also shipped, not installed: dev (mcp, skills, source-links) (chi bundle install NAME)
 done
 ```
 
 - **The gem.** It asks rubygems.org for the newest samagotchi (5 s timeout)
   and, when that's newer, runs `gem install samagotchi` with the gem command
-  of the Ruby chi runs on (the real one, not a mise/rbenv/asdf shim). Then it
+  of the Ruby chi runs on (the real one, not a mise/rbenv/asdf shim; a chi
+  installed under another Ruby is a separate install it doesn't touch). Then it
   hands over to the new chi, which does the rest and prints the table. Old
-  versions stay installed: running workers and an old `chi web` still use
-  them (so don't `gem cleanup` while they run). Offline, the row says
+  versions stay installed: running workers and an old `chi web` still load
+  files from them, so a `gem cleanup` while they run breaks them (a
+  `LoadError`, missing web assets); restart them first. Offline, the row says
   "couldn't check" and the rest still runs; a failed install fails the row
   and the rest runs on the current version. Under Bundler (`bundle exec`)
   the row says `bundle update samagotchi` instead.
@@ -137,9 +139,15 @@ done
 - **The desktop helper** (macOS) is rebuilt and restarted only when its Swift
   sources changed (or the Ruby it runs moved); otherwise only its launch file
   is refreshed. See [Desktop helper](desktop.md).
-- **Running processes** are reported, never stopped: live workers on another
-  version, and a `chi web` on `web.port` running an older chi (sessions it
-  starts run that version too: restart it).
+- **Running processes** are reported, never stopped. A live worker keeps its
+  chi until it is restarted: `chi sessions restart ID` (one from before
+  restarts: `chi sessions stop ID`, and the next prompt starts it on the new
+  chi); it exits on its own only when nothing is attached (no web tab, no
+  terminal, no reminder) and `session.idle_exit_minutes` pass (never with 0).
+  A new or woken worker always starts on the newest chi installed. A `chi web`
+  on `web.port` running an older chi needs a restart (Ctrl-C, then `chi web`):
+  its page says so too. One from before workers started on the newest chi
+  also starts its new sessions on its own version until then (the row says so).
 
 `--dry-run` shows the table with "would update" and changes nothing. It is
 this version's view: bundles that only a newer gem ships newer show up once
@@ -251,8 +259,12 @@ and `--shared` are refused. Its first line says it is a scratch session.
   answers "scratch session: nothing is saved", and `write`/`edit` into the
   memories folder are denied (a guardrail, rule `scratch-session`). `execute`
   can still write files anywhere, memories included.
+- An approval offers only "Allow once" and "for the session", and a session
+  approval is kept in memory, not in the approvals store; approvals stored
+  before still apply.
 - No child sessions: the `delegate` tools are not offered, and a plugin's
   `ctx.sessions.fork` (btw's side session) refuses, since they would outlive it.
+  Nor is `send_note`, whose note would stay in the other session.
 
 ### Sharing a session
 
@@ -320,6 +332,20 @@ a `chi --resume ID` after it starts a fresh one. A worker still running an
 older chi (from before an upgrade) takes turns but not commands; the attached
 terminal and the Web UI say so, with that restart line.
 
+`chi sessions restart ID...` hands each session to a new worker on the newest
+chi installed, without stopping it: an attached terminal and the web's tabs
+move to the new worker. It is refused, with the reason, while something would
+be lost: a turn running or queued, a question or approval waiting, reminders,
+a `/btw` still running, an approval relayed from a delegate, or background
+tasks the session started. A session with no running worker needs none (its
+next prompt starts one on the newest chi), and a worker from before restarts
+needs `chi sessions stop ID`. The Web UI's `POST /api/sessions/:id/restart`
+does the same (409 with `reason` and `detail` when it can't). An attached
+terminal says at the join, in one `chi>` line, when the worker or the terminal
+runs an older chi than the newest installed (the worker moves with `chi
+sessions restart ID`, the terminal with `/detach` and `chi --attach ID`), and
+`chi> the session's worker restarted on chi X` when its worker was replaced.
+
 `chi sessions archive ID...` hides sessions from every list (the terminal's,
 the web's, `list_sessions`) and keeps them for good: the retention sweep never
 deletes an archived session, nor counts it. Its delegates go with it. A live

data/docs/configuration.md

@@ -94,8 +94,9 @@ Behavior:
 - An edit to the file needs no restart of `chi web`: a new session's worker
   reads the file when it starts, and a running chi takes a changed value the
   next time it reads that setting (a worker keeps `hosts:` and what it set up
-  at its start until it is stopped). A worker gets the CLI flags of the chi
-  that started it through its environment.
+  at its start until it is stopped; the web's model picker lists a `hosts:`
+  edit at once). A worker gets the CLI flags of the chi that started it
+  through its environment.
 - Workers inherit hosts via `SAMAGOTCHI_HOSTS_JSON` propagated through `SessionManager.spawn_options`.
 
 This lets you run `chi` without repeating common defaults such as model
@@ -235,8 +236,11 @@ hosts:
 **Remote or local.** chi treats a host as a remote provider by its address, not
 by its key: an `https` url, or an `http` IP address outside the loopback,
 private (`10.*`, `172.16–31.*`, `192.168.*`, IPv6 `fc00::/7`), link-local and
-CGNAT/Tailscale (`100.64.0.0/10`) nets. An `http` host given by a name
-(`localhost`, `box`, `mac.local`) is local: chi doesn't look names up. A remote
+CGNAT/Tailscale (`100.64.0.0/10`) nets, or an `http` name with a dot that
+doesn't end in a local suffix (`gpu.example.com`). A name without a dot (`box`)
+or ending in `localhost`, `.local`, `.lan`, `.home`, `.home.arpa`, `.internal`,
+`.intranet`, `.localdomain`, `.private`, `.corp`, `.test`, `.box` (`fritz.box`)
+or `.ts.net` (Tailscale) is local: chi doesn't look names up. A remote
 host keeps its model list for 10 minutes, gets a 120-second first-token limit,
 and isn't asked for llama.cpp's `/props` (its context window and served model
 come from its model list and each turn). `remote: true` or `remote: false` on a

data/docs/memory.md

@@ -27,6 +27,10 @@ Each memory entry may have a companion file named `<name>.<model-key>.md` in the
 - **In the system prompt**: the identity memory and the preloaded memories (`--memory`, config `memories:`) get their overlays too, as `memory_read` gives them; after `/model` the rebuilt prompt carries the new model's.
 - **Dormancy**: Overlays are only active under the matching model key; other models see the base entry only.
 - **Invariant**: The base entry is the contract. Overlays only add model-specific guidance and never contradict the base protocol.
+- **In a bundle**: ship `<name>.<key>.md` next to `<name>.md` (ship the base too; an overlay with no base anywhere installs with a warning and loads only once the base exists; one whose base is only among your installed memories is taken as an overlay of it, with a warning naming it). The overlay gets no `index.md` line, so other models don't see it, and `chi bundle status` reads it `ok (model overlay)`; `chi bundle build FILES...` brings a named memory's overlays along.
+  - The key is the `model key` row of `chi self` under that model. It follows the provider's model id: OpenRouter's `deepseek/deepseek-v4.1-flash` keys as `deepseek-deepseek-v4-1-flash`, while a local server names the same model differently, so one model may need one overlay per provider.
+  - Key an alias by its **target**, not the alias: the alias's own key is read only as a fallback, when the alias was typed and the target has no overlay.
+  - The overlay is read in the scope its base is found in: a project memory with the same name shadows a system-scope bundle's base and overlay.
 
 
 At startup, the agent reads both scope indexes with blank-name memory reads

data/docs/sessions.md

@@ -13,17 +13,19 @@ Sessions are plain files — no DB. Each session is `~/.local/state/samagotchi/s
 
 A session is deleted if **expired by age OR overflow by count** (unless `keep_status` or the live-owner guard: a session a worker or `chi` still has open is never pruned). A session's `status` is its turn state (`idle`/`running`), not whether a worker is alive. Orphan dirs without a `*.json` are never deleted, except skeleton-only ones (see *Empty sessions*). Deletion removes both `*.json` and sidecar dir atomically. Set both `DAYS=0` and `MAX=0` to retain forever.
 
-**Worker idle exit:** a background worker (plain `chi`, Web UI sessions) exits after `SAMAGOTCHI_SESSION_IDLE_EXIT_MINUTES` (`session.idle_exit_minutes`, default `30`, `0`=never) with no turn running or queued, no client on its stream (an open web tab or attached terminal keeps it), no reminder registered and no continue offer (the step-limit question) waiting for an answer. It removes `bridge.json` and frees `owner.lock`; the next prompt or `--attach` wakes a new worker (`WorkerIdleExit`, `SessionManager.run_session_loop`). A client can also ask the worker to exit right away (Bridge `POST /session/:id/exit`; `/exit` in an attached terminal does, `/detach` doesn't): the same rules apply without the timeout (even with `0`), and the asker's own stream doesn't count. The reply names what keeps it up. The session's status stays as it was, not `stopped`.
+**Worker idle exit:** a background worker (plain `chi`, Web UI sessions) exits after `SAMAGOTCHI_SESSION_IDLE_EXIT_MINUTES` (`session.idle_exit_minutes`, default `30`, `0`=never) with no turn running or queued, no client on its stream (an open web tab or attached terminal keeps it), no reminder registered and no continue offer (the step-limit question) waiting for an answer. It removes `bridge.json` and frees `owner.lock`; the next prompt or `--attach` wakes a new worker (`WorkerIdleExit`, `SessionManager.run_session_loop`). A client can also ask the worker to exit right away (Bridge `POST /session/:id/exit`; `/exit` in an attached terminal does, `/detach` doesn't): the same rules apply without the timeout (even with `0`), and the asker's own stream doesn't count. The reply names what keeps it up. The session's status stays as it was, not `stopped`. With `"restart": true` (a worker whose sidecar lists the `restart` feature) the worker hands the session to a new worker on the newest chi installed: it leaves, then starts its successor once its lock is free, keeping even an empty session and writing no recap. Clients' streams don't hold a restart (a web tab and an attached terminal reconnect to the new worker); what would be lost does: a turn running or queued, a continue offer, a question or approval waiting, reminders, a `/btw` (or another anytime command) still running, a delegate's approval relay open or settled in the last 10 minutes, and background tasks this conversation started that still run (`WorkerIdleExit#hold_for_restart`; 409 `held` with `reason`). What lives only in the worker's memory goes: the event history a late client replays, the kept `/btw` answers, a plugin's in-memory state.
 
 **Empty sessions:** a session nothing happened in is deleted when it is left, so `chi` → `/exit` leaves no trace. Empty means: no messages, no turn tried (a failed turn leaves a `last_prompt` and keeps it), no memory used, no pending question, nothing in `input/`, `notes/` or `images/`, nothing in its dir beyond the worker's skeleton, mode `assist`, and the default model. A session on another model (`/model`, `--model`) counts as prepared and stays (`SessionManager.discardable?`). The worker checks as it idle-exits or leaves on a client's request and deletes it once its lock is free, checking again first. The attached `/exit` then says `Detached; the session was empty, so it is discarded.` The REPL (`--no-shared`) does the same at `/exit` or Ctrl-D. The retention sweep catches those killed first: empty sessions over an hour old with no live owner, whatever `DAYS`/`MAX`, and skeleton-only dirs with no `*.json`. `session.keep_empty: true` (env `SAMAGOTCHI_SESSION_KEEP_EMPTY`) turns all of it off.
 
 **Attached by default:** plain `chi` and `chi --resume ID` run their session in a background worker and attach to it (`session.shared`, default `true`; env `SAMAGOTCHI_SESSION_SHARED`). The worker runs in the session's `working_directory`, so `!commands` and tools see the directory the session was started in. `session.shared: false` keeps the in-process REPL, `--no-shared` does for one run; a session the REPL has open can't be attached ("close it there first"). See [CLI: Sharing a session](cli.md#sharing-a-session).
 
+**Which chi a worker runs:** a new or woken worker runs the newest chi installed for this Ruby (`gem 'samagotchi', '>= 0.a'`, prereleases count), whoever starts it: a `chi web` or terminal still on an older chi starts it on the newest one, so a stale process doesn't spread old code. A worker already running keeps its version until it is restarted. Should the newest install fail to load, the worker runs the starter's own version and logs `boot_fallback` (its stdio is `/dev/null`). Under `bundle exec` the worker drops Bundler's env first, so it activates the newest gem too. Two consequences: a wrapper pin (`chi _0.17.0_ web`) pins only that process, not the workers it starts; and a source checkout (`bin/chi` in a worktree, `bundle exec`) starts its workers on its own `lib/`, but a session it made that is later woken by an installed chi (`chi web`, `chi send`) runs the installed code. The names an older starter hands a newer worker (the boot line, its env keys, `input/` files, the session JSON fields and the Bridge routes sessions use on each other) are pinned in `spec/worker_contract_spec.rb`.
+
 **Stopping a worker:** `chi sessions stop ID` marks the session stopped (an empty `<id>/stopped` file, not a session.json field, which a worker saving at that moment would write over; a resume removes it), sends its worker TERM and waits (up to 10 s) until the worker has let go of `owner.lock`, so a `chi --resume ID` right after spawns a fresh worker. That is also how to restart a worker still running an older chi, which the attached terminal reports when a command or a question dismiss gets a 404, and the web when an answer, a dismiss, a command or a cancel does (`501 not_supported`; `BridgeClient.stale_worker_message`). The web's `POST /api/sessions/:id/stop` waits the same way, for 2 s.
 
 **Deleting a session:** `chi sessions delete ID...`, `/exit --delete` in a terminal and the Web UI's delete all go through `SessionManager.delete_session`: it resolves a unique prefix, removes `<id>.json` and the whole `<id>/` dir, and returns what it removed. A session a plain REPL has open (`owner.lock` kind `tui`) is always refused. One a worker runs is refused unless the caller asks to stop it: then it stops the worker as `chi sessions stop` does and deletes once `owner.lock` is free (`--force` on the CLI, 10 s; the web always, 2 s; `/exit --delete` after the worker agreed to exit, 10 s). A worker that outlives the wait leaves the session in place. The web's route is `DELETE /api/sessions/:id` (200 `{status: "deleted", session_id, stopped}`; 409 `owned_by_tui` or `still_stopping`; 404).
 
-<a id="archiving-a-session"></a>**Archiving a session:** `chi sessions archive ID...`, `/archive` in a terminal and the Web UI's `archive` go through `SessionManager.archive_session`: it writes `<id>/archived` (`{"archived_at": …}`; not a session.json field, which every save rewrites) for the session and its delegated children. `Session.list` leaves archived sessions out unless `include_archived:`, and everything built on it follows: `chi sessions list` (`--archived` shows them, `[archived]`), the summaries (`--live`, json/tsv, the desktop panel, the agent's `list_sessions`) and the retention prune, which neither deletes nor counts them against `max_count`. `children_of` (max_children, `delegate_result`) still sees them, and `--resume`/`--attach ID`, `chi send`/`chi note ID` reach them as before. Refused: a turn running in the session or in one of its children (naming the child; 409 `busy` on the web), a plain REPL owning it (`owned_by_tui`), a `chi scratch` session (`scratch`). A live idle worker is stopped first, and the marker is written even if it is still shutting down. Input a human typed brings a session back (`{"unarchived_at": …}`): a prompt from the web, an attached or plain terminal or `chi send` (origin `web:*`, `tui:*`, `cli:send`, none), steering merged into a running turn, a `/continue` answer or a question answered (the step-limit question too); a delegate's follow-up, a plugin's turn, a reminder, the idle recap, a note and just opening it don't. A child's input brings only the child back. The retention sweep ages an unarchived session from when it was unarchived, so unarchiving an old session doesn't let the next sweep take it. `/archive` leaves the session first, as `/exit` does, then archives it: in an attached terminal the worker is asked to exit (one that stays up for another UI is stopped by the archive; a running turn refuses it), and an empty session is discarded instead; `chi scratch` refuses it. `chi sessions unarchive ID...` and the web's `unarchive` bring back the whole family. Web routes: `POST /api/sessions/:id/archive` (200 `{status, session_id, archived, stopped, discarded}`, ids) and `POST /api/sessions/:id/unarchive` (200 `{status, session_id, unarchived}`). The session hub and `GET /api/sessions` keep archived sessions, `archived: true` in their summaries: the page leaves them out of the strip, its count and the list at render, and "include archived" by the all-sessions search shows them, dimmed with an `archived` badge. The info bar reads `archive · stop · delete` (`unarchive` on an archived one); archiving the open session stays on it, with an Undo toast.
+<a id="archiving-a-session"></a>**Archiving a session:** `chi sessions archive ID...`, `/archive` in a terminal and the Web UI's `archive` go through `SessionManager.archive_session`: it writes `<id>/archived` (`{"archived_at": …}`; not a session.json field, which every save rewrites) for the session and its delegated children. `Session.list` leaves archived sessions out unless `include_archived:`, and everything built on it follows: `chi sessions list` (`--archived` shows them, `[archived]`), the summaries (`--live`, json/tsv, the desktop panel, the agent's `list_sessions`) and the retention prune, which neither deletes nor counts them against `max_count`. `children_of` (max_children, `delegate_result`) still sees them, and `--resume`/`--attach ID`, `chi send`/`chi note ID` reach them as before. Refused: a turn running in the session or in one of its children (naming the child; 409 `busy` on the web), a plain REPL owning it (`owned_by_tui`), a `chi scratch` session (`scratch`). A live idle worker is stopped first, and the marker is written even if it is still shutting down. Input a human typed brings a session back (`{"unarchived_at": …}`): a prompt from the web, an attached or plain terminal or `chi send` (origin `web:*`, `tui:*`, `cli:send`, none), steering merged into a running turn, a `/continue` answer or a question answered (the step-limit question too); a delegate's follow-up, a plugin's turn, a reminder, the idle recap, a note and just opening it don't. A child's input brings only the child back. The retention sweep ages an unarchived session from when it was unarchived, so unarchiving an old session doesn't let the next sweep take it. `/archive` leaves the session first, as `/exit` does, then archives it: in an attached terminal the worker is asked to exit (one that stays up for another UI is stopped by the archive; a running turn refuses it), and an empty session is discarded instead; `chi scratch` refuses it. `chi sessions unarchive ID...` and the web's `unarchive` bring back the whole family. Web routes: `POST /api/sessions/:id/archive` (200 `{status, session_id, archived, stopped, discarded}`, ids) and `POST /api/sessions/:id/unarchive` (200 `{status, session_id, unarchived}`). The session hub and `GET /api/sessions` keep archived sessions, `archived: true` in their summaries: the page leaves them out of the strip, its count and the list at render, and "include archived" by the all-sessions search shows them, dimmed with an `archived` badge. The info bar marks a session whose live worker runs an older chi than the newest installed (`worker_version` in its summary): `chi 0.18.1 · Restart`, which asks to confirm and calls `POST /api/sessions/:id/restart` (a refusal's reason shows in a toast); a worker from before restarts shows `chi sessions stop ID` instead. The info bar reads `archive · stop · delete` (`unarchive` on an archived one); archiving the open session stays on it, with an Undo toast.
 
 **Lazy sweep:** automatic prune runs only while `chi web` runs, at most once per `session.sweep_interval_hours` (default 24): the web's session hub gives it a chance on its periodic full scan, and `GET /api/sessions` does too. No cron, and a terminal-only chi never sweeps. Manual prune is always available.
 
@@ -118,8 +120,8 @@ system message marked `kind: turn_note` (the UIs don't show it; they showed the
   before any answer: network error after 2 attempts (host main: Errno::ECONNREFUSED). The message went back to
   the user, who may send it again.]` in the REPL and attached mode, where the prompt is given back;
   `… The user's last message was not answered.]` after `-p`, where the prompt stays in the session;
-- cancelled (Ctrl-C, the web's stop): `[SYSTEM: the previous turn was cancelled (ctrl-c) after 12s; the answer
-  above ends where it was cut off.]`, or `…; no answer had been shown.]` when only thinking had streamed;
+- cancelled (Ctrl-C, the web's stop): `[SYSTEM: the previous turn was cancelled (ctrl-c) after 12s; the reply
+  above ends where it was cut off.]` (an answer or only narration had streamed), or `…; no answer had been shown.]` when only thinking had streamed;
 - ended with nothing visible: `[SYSTEM: the previous turn ended with no visible answer (thinking only, or
   nothing). The user's last message is still unanswered.]`.
 

data/lib/samagotchi/bridge.rb

@@ -212,8 +212,10 @@ module Samagotchi
     # The pending question at the top level too: one asked between turns
     # (the step-limit question) belongs to no turn, so the accumulator
     # doesn't keep it.
+    # chi_version: the chi this worker runs (an attaching TUI compares it
+    # with its own).
     # @return [Hash] {messages:, current_turn:, queued:, recap:, saved_recap:, continue_offer:, pending_question:,
-    #   guardrail_warning:, plugin_warning:, init_tasks:, cards:, commands:, event_seq:, event_id:}
+    #   guardrail_warning:, plugin_warning:, init_tasks:, cards:, commands:, chi_version:, event_seq:, event_id:}
     def snapshot
       @engine.synchronize_events do
         seq = @engine.event_count
@@ -230,6 +232,7 @@ module Samagotchi
           init_tasks: @engine.init_tasks,
           cards: @cards.list,
           commands: command_registry.listing,
+          chi_version: Samagotchi::VERSION,
           event_seq: seq,
           event_id: event_id(seq)
         }
@@ -452,6 +455,12 @@ module Samagotchi
       !host.empty? && !LOOPBACK_NAMES.include?(host.downcase.sub(/:\d*\z/, ""))
     end
 
+    # What a client may ask of this worker beyond the routes, named in its
+    # sidecar (WorkerSidecar#features): a client checks a name here rather
+    # than a version.
+    # restart: POST /exit takes "restart": true (WorkerIdleExit#hold_for_restart).
+    FEATURES = ["restart"].freeze
+
     # The routes, by method and what follows /session/:id/: a handler takes
     # the session id and the request body and returns [headers, status, body].
     # GET stream is served apart (#serve_sse owns the connection).
@@ -683,11 +692,13 @@ module Samagotchi
       @engine.announce(type: :command_queued, **command, **anytime)
     end
 
-    # A client asks the worker to exit now (`/exit` in the attached TUI). The
-    # worker decides with the event log held, so no POST /turn lands between
-    # its check and its answer; it leaves from its loop after this reply.
-    # 200 {status: "exiting", discard?: the session is empty and goes}, or 409 {status: "held", reason:} naming what
-    # keeps it up. Returns [headers, status, body].
+    # A client asks the worker to exit now (`/exit` in the attached TUI), or
+    # with "restart": true to hand the session to a new worker on the newest
+    # chi installed (the "restart" feature). The worker decides with the
+    # event log held, so no POST /turn lands between its check and its
+    # answer; it leaves from its loop after this reply.
+    # 200 {status: "exiting", discard?: the session is empty and goes} ({status: "restarting"} for a restart), or 409
+    # {status: "held", reason:} naming what keeps it up. Returns [headers, status, body].
     def handle_exit_request(session_id, body)
       return [{}, 501, { error: "exit_unavailable" }] unless @on_exit_request
 
@@ -696,8 +707,12 @@ module Samagotchi
 
       client_id = fetched(parsed, "client_id")
       delete = fetched(parsed, "delete") == true
-      reason = @engine.synchronize_events { @on_exit_request.call(client_id, delete: delete) }
+      restart = fetched(parsed, "restart") == true
+      options = restart ? { delete: delete, restart: true } : { delete: delete }
+      reason = @engine.synchronize_events { @on_exit_request.call(client_id, **options) }
       if reason.nil?
+        return [{}, 200, { status: "restarting", session_id: @session_id }] if restart
+
         body = { status: "exiting", session_id: @session_id }
         body[:discard] = @exit_discards.call == true if @exit_discards
         return [{}, 200, body]
@@ -1029,9 +1044,10 @@ module Samagotchi
     end
 
     def write_sidecar
-      # version: the chi this worker runs (chi update reports older ones).
+      # version: the chi this worker runs (chi update and the web's badge
+      # report older ones); features: what a client may ask of it.
       WorkerSidecar.new(port: @port, bind: @bind, session_id: @session_id, started_at: Time.now.iso8601(3),
-                        version: Samagotchi::VERSION, input_format: @input_format).write(session_dir)
+                        version: Samagotchi::VERSION, input_format: @input_format, features: FEATURES).write(session_dir)
     rescue StandardError => e
       Log.warn(:bridge, "sidecar_write_failed", echo: "Bridge: failed to write #{WorkerSidecar::FILE}: #{e.class}: #{e.message}", error: e.class.name)
     end

data/lib/samagotchi/bridge_client/event_stream.rb

@@ -17,8 +17,17 @@ module Samagotchi
     # not serve the session (404), it yields one synthetic
     # `{"type" => "stream_closed", "reason" => ...}` and stops. #close stops
     # it without that event.
+    #
+    # With +rediscover+, a failed connection first looks for the session's
+    # live worker (its sidecar): a new one (a restart) is followed from its
+    # snapshot, announced by a synthetic `{"type" => "worker_changed",
+    # "port" => ...}` first, since its event ids start over. (A new worker
+    # on the old one's port is the plain reconnect: its Bridge can't replay
+    # the old ids and sends a reset.)
     class EventStream
       DEFAULT_RECONNECT_DELAYS = [0.1, 0.25, 0.5, 1.0, 2.0].freeze
+      # Long enough for a restarted worker to boot (its Engine, the plugins).
+      REDISCOVER_DELAYS = [0.1, 0.25, 0.5, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 2.0, 2.0, 2.0].freeze
       HEADER_TIMEOUT = 5.0
 
       # @return [String, nil] the id of the last frame yielded (the reconnect cursor)
@@ -30,9 +39,13 @@ module Samagotchi
       #   tell this client's stream from others' (Bridge#open_streams_except)
       # @param reconnect_delays [Array<Float>] sleeps between failed attempts;
       #   one more failure than there are delays gives up
+      # @param rediscover [#call, nil] → a BridgeClient for the session's live
+      #   worker now, nil when there is none yet, or :gone to give up now
       # @yieldparam event [Hash] string-keyed event
-      def initialize(client, snapshot: true, client_id: nil, reconnect_delays: DEFAULT_RECONNECT_DELAYS, &on_event)
+      def initialize(client, snapshot: true, client_id: nil, reconnect_delays: DEFAULT_RECONNECT_DELAYS, rediscover: nil,
+                     &on_event)
         @client = client
+        @rediscover = rediscover
         params = []
         params << ["snapshot", "1"] if snapshot
         params << ["client_id", client_id] if client_id
@@ -86,6 +99,13 @@ module Samagotchi
             next
           end
 
+          case rediscover_worker
+          when :moved
+            failures = 0
+            next
+          when :gone then return finish("unreachable")
+          end
+
           failures += 1
           return finish("unreachable") if failures > @reconnect_delays.size
 
@@ -148,6 +168,22 @@ module Samagotchi
         nil
       end
 
+      # @return [Symbol, nil] :moved to a new worker's Bridge, :gone, or nil
+      def rediscover_worker
+        return nil unless @rediscover
+
+        found = @rediscover.call
+        return :gone if found == :gone
+        return nil if found.nil? || found.port == @client.port
+
+        @client = found
+        @last_event_id = nil
+        @on_event.call({ "type" => "worker_changed", "port" => found.port }) unless closed?
+        :moved
+      rescue StandardError
+        nil
+      end
+
       def finish(reason)
         @on_event.call({ "type" => "stream_closed", "reason" => reason }) unless closed?
       end

data/lib/samagotchi/bridge_client.rb

@@ -156,14 +156,16 @@ module Samagotchi
       post("command", payload, read_body: true)
     end
 
-    # POST /session/:id/exit: ask the worker to exit now. 200 = it will
-    # (status "exiting"), 409 = something keeps it up (reason), 404 with
+    # POST /session/:id/exit: ask the worker to exit now (+restart+: hand
+    # the session to a new worker, a worker with the "restart" feature). 200
+    # = it will (status "exiting"/"restarting"), 409 = something keeps it up (reason), 404 with
     # error "not_found" = a worker older than the route.
     # @param client_id [String] the asking UI, whose own streams don't hold
     # @return [Response]
-    def request_exit(client_id:, delete: false)
+    def request_exit(client_id:, delete: false, restart: false)
       body = { client_id: client_id }
       body[:delete] = true if delete
+      body[:restart] = true if restart
       post("exit", body, read_body: true)
     end
 
@@ -290,11 +292,13 @@ module Samagotchi
     # Follow the session's events on a reader thread (see EventStream).
     # @param snapshot [Boolean] join with a snapshot frame
     # @param client_id [String, nil] names the stream (see EventStream)
+    # @param rediscover [#call, nil] follows a new worker (see EventStream)
     # @yieldparam event [Hash] string-keyed event
     # @return [EventStream] started
-    def follow(snapshot: true, client_id: nil, reconnect_delays: EventStream::DEFAULT_RECONNECT_DELAYS, &on_event)
+    def follow(snapshot: true, client_id: nil, reconnect_delays: EventStream::DEFAULT_RECONNECT_DELAYS, rediscover: nil,
+               &on_event)
       EventStream.new(self, snapshot: snapshot, client_id: client_id, reconnect_delays: reconnect_delays,
-                            &on_event).start
+                            rediscover: rediscover, &on_event).start
     end
 
     # Open GET /session/:id/stream and read past the response headers.

data/lib/samagotchi/bundle_command.rb

@@ -360,8 +360,9 @@ module Samagotchi
           mods << "conflict (kept your edits over v#{st[:provenance][:version]}: chi bundle diff #{name} #{k})" if info[:conflict]
           mods << "modified" if info[:modified]
           mods << "missing" if info[:missing]
-          mods << "no-index" unless info[:index_present]
+          mods << "no-index" unless info[:index_present] || info[:overlay]
           label = mods.empty? ? "ok" : mods.join(",")
+          label += " (model overlay)" if info[:overlay]
           @stdout.puts "  #{k}: #{label}"
         end
         # Hooks

data/lib/samagotchi/bundles/source-links/hooks/source_links.rb

@@ -321,7 +321,8 @@ class SourceLinks
     links.any? do |link|
       in_target = start >= link[:target][0] && finish <= link[:target][1]
       in_label = start >= link[:label][0] && finish <= link[:label][1]
-      in_target || (in_label && target_names_ref?(link[:target_text], text[start...finish]))
+      in_target || (in_label && target_names_ref?(link[:target_text], text[start...finish],
+                                                   case_insensitive: match.regexp.casefold?))
     end
   end
 
@@ -330,10 +331,12 @@ class SourceLinks
   # the ref. So `[JIRA-1](…/JIRA-12)` is NOT skipped (the target names
   # JIRA-12), while `[JIRA-123](…/JIRA-123)` is. Note this is stricter than
   # the bare-text scan's `\b`, which treats `-` as a boundary: `…/JIRA-1-foo`
-  # would match there but not here.
-  def target_names_ref?(target, ref)
+  # would match there but not here. A case_insensitive source compares
+  # without case too: `[jira-1](…/JIRA-1)` is skipped.
+  def target_names_ref?(target, ref, case_insensitive: false)
     escaped = Regexp.escape(ref)
-    target.match?(/(?<![A-Za-z0-9\-])#{escaped}(?![A-Za-z0-9\-])/)
+    flags = case_insensitive ? Regexp::IGNORECASE : 0
+    target.match?(Regexp.new("(?<![A-Za-z0-9\\-])#{escaped}(?![A-Za-z0-9\\-])", flags))
   end
 
   # A ref glued to URL punctuation is part of a link too, even when the span

data/lib/samagotchi/bundles/source-links/manifest.yml

@@ -1,6 +1,6 @@
 ---
 name: source-links
-version: 0.3.1
+version: 0.3.2
 scope: system
 description: Links source refs (JIRA tickets, GitHub issues, …) in the model's answer — inline links in the web, and a one-line note after the turn (note false turns it off); sources are configured patterns
 trust_level: reviewed
@@ -8,7 +8,7 @@ files:
   source_links.md: sha256:aebd37f1e25491780994ecc4afc20ed6e8db32b724dc038302bb050177efada8
 hooks:
   source_links.rb:
-    sha256: sha256:574ea0c2b36f80dde410c4251753d70cbeea081d129f3f3547f41370e3990993
+    sha256: sha256:5a996b718b1db729305b893ed583b9e600e813570861d47e0b65a24fec36a35d
     event: after_turn
     on_error: log
     priority: 90

data/lib/samagotchi/bundles/system/manifest.yml

@@ -1,11 +1,11 @@
 ---
 name: samagotchi-system
-version: 0.18.1
+version: 0.19.0
 scope: system
 description: Default system memories — identity, self map, config modification protocol, memory guide and the delegated-session rules
 files:
   identity.md: sha256:29c2f7df9f6c5acbc5ec17000a4490741e55e426af15ca0d81c8706edd9bd027
   self_map.md: sha256:69bc0ec091fdaeedf6e3aa7365275461fe3eba32b2dedc9cf45044176c356af5
   config_modification_protocol.md: sha256:8d8921854e616d840b393cdda6fd911b7d5e8172501bb8293c01f734121ccc21
-  memory_guide.md: sha256:e535e31fcf29b4b32c270042851ecdd5f412ef2e3c56b0076963e3e1f1a08ef8
+  memory_guide.md: sha256:8819678a243590203fa439ad736bf1959af4b4677bc6d2d507bad92c46fb1ccc
   delegated.md: sha256:0a71d5dfa7127df2d51cb5f0e7214240ed88777e36559430a8724c796d7ae561