release(v1.12.1): ssh-lan.conf Include fix, pi-studio v0.10.2, gitea-mcp v1.10.0

Patch release. The fix itself is c693aa3: setup-lan-access.sh now writes the
ssh-lan.conf Include whether or not the file exists at container start.

Upstream survey on 2026-10-19 (check-doc-drift check 9, npm, PyPI, tags, and
the GitHub/Gitea release APIs for every base tool pinned to `latest`):
- moved: pi-studio v0.10.1 -> v0.10.2 (4b4abd1), pi-toolkit 3760d90 -> 7c05901,
  gitea-mcp v1.9.0 -> v1.10.0
- unchanged: pi 1.3.0, mempalace 3.11.0, pi-atelier v0.16.0, pi-obsmem 022da5e,
  pi-extensions, pi-fork, mempalace-toolkit, skillset snapshot, and every
  other base tool
Audits, all on tor-ms22:
- pi-studio 0.10.2: lockfile packages identical to 0.10.1's. Loaded into
  pi 1.3.0, it registers the same 4 studio_* tools, rc 0.
- pi-toolkit: the new model IDs are in pi 1.3.0's bedrock registry, and they
  reach fresh volumes only (the settings merge fills only missing keys).
- gitea-mcp 1.10.0: stdio tools/list gives 58 -> 61 tools, none removed, and
  stdout carries JSON only.

CHANGELOG: Unreleased -> v1.12.1 with the components table and the audits.
README: "Since v1.12.1". Dockerfile.base: BASE_REBUILD_DATE marker refreshed;
the base rebuilds anyway because rootfs changed.
check-doc-drift rc 0, lint-shell, the link-pi contract tests, skill-floor and
the Dockerfile directives check: all clean.

CHANGELOG.md

@@ -11,6 +11,87 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
 
 ---
 
+## v1.12.1 — 2026-10-19
+
+Patch release. Headline: **`ssh-lan.conf` is Included even if it is created
+after the container started** (*Fixed*, below). Also **pi-studio `v0.10.2`**,
+pi-toolkit `7c05901` (new Bedrock defaults for fresh volumes) and gitea-mcp
+`v1.10.0`. Surveyed 2026-10-19; no other upstream moved. Unchanged since v1.12.0:
+pi `1.3.0` (npm `latest`), mempalace `3.11.0` (PyPI `latest`), pi-atelier `v0.16.0`
+(`3b42825`, newest tag), pi-observational-memory `022da5e` (= `master`),
+pi-extensions `4c1d28d`, pi-fork `e69725c`, mempalace-toolkit `d5a03f4`. The
+skillset snapshot needs no refresh (`vendor-mempalace-skill.sh --check`: OK,
+still `96b840e`). The base image is rebuilt because `rootfs/` changed, so apt
+and the base tools pinned to `latest` re-resolve. Of those, only gitea-mcp moved
+upstream: `v1.9.0` → `v1.10.0`. uv `0.13.1`, Node `v24.22.0`, nvim `0.12.6`,
+fzf `0.74.5`, gitleaks `8.30.1`, bat `0.26.1`, eza `0.23.5`, zoxide `0.10.0`,
+git-lfs `3.8.0`, gosu `1.19`, micro `2.0.15`, tealdeer `1.9.0`, typst `0.15.1`,
+yq `4.54.1`, agent-browser `0.39.1` and playwright `1.64.1` match their newest
+releases. Each was compared against the v1.12.0 image on tor-ms22.
+
+### Components that move with this release
+
+| Component | Baked in v1.12.0 | v1.12.1 | Why |
+|---|---|---|---|
+| **pi-studio** (`-studio` tags) | `v0.10.1` (`76db01f`) | **`v0.10.2`** (`4b4abd1`) | newest tag, see *Changed* below |
+| pi-toolkit | `3760d90` | **`7c05901`** (or later: CI resolves `main` at build time) | `settings.example.json` defaults move to Claude 5.5 on Bedrock, see *Changed* below |
+| gitea-mcp (base) | `v1.9.0` | **`v1.10.0`** (or later: `latest` at build time) | additive, see *Changed* below |
+
+### Changed
+
+- **pi-studio `v0.10.1` → `v0.10.2`** (`-studio` tags only). Windows fixes. The
+  REPL waits for the runtime's prompt before saying it started. Stopping a
+  session ends its processes. Code goes only to the exactly named session. The
+  selected session follows what you choose. One behaviour change for agents: a
+  `studio_repl_send` that names no session now fails when Studio shows none
+  selected ("No REPL session is selected in Studio …"). Before, it picked a
+  session. Audited 2026-10-19 on tor-ms22. Dependencies are unchanged:
+  `package-lock.json` packages are identical to 0.10.1's, `ws` is the only
+  runtime dependency, and pi peers are `*`. Loaded into this image's pi `1.3.0`
+  with `pi --no-extensions -e <clone>/index.ts -p`, it registers the same four
+  tools as 0.10.1 (`studio_repl_status`, `studio_repl_send`, `studio_export_pdf`,
+  `studio_export_html`), with no extension error and rc 0. Control: the same
+  run against the baked 0.10.1.
+- **pi-toolkit `3760d90` → `7c05901`:** `settings.example.json` now defaults to
+  `eu.anthropic.claude-opus-5-5`. `enabledModels` becomes opus/sonnet/haiku `-5-5`,
+  and the observational-memory and pi-fork `fast`/`balanced`/`deep` models move
+  to the same family. Also a `*.bak-*` gitignore. **Only a fresh
+  `devbox-pi-config` volume gets these defaults.** On an existing volume, the
+  entrypoint's settings merge fills in only *missing* keys and keeps arrays
+  verbatim, so a model you already set stays. All three IDs are in pi
+  `1.3.0`'s built-in `amazon-bedrock` registry, and `eu.anthropic.claude-opus-5-5`
+  is this session's default model on tor-ms22.
+- **gitea-mcp `v1.9.0` → `v1.10.0`** (base, `latest` at build time). Additive: three
+  new tools (`compare_commits`, `get_commit_status`, `create_commit_status`) and
+  new methods on existing ones. The fix that matters for stdio clients: logs go
+  to stderr, and `-d` no longer writes to stdout, where it corrupted the protocol.
+  Measured 2026-10-19 with a stdio `initialize` + `tools/list` against
+  gitea.jordbo.se: 1.9.0 lists 58 tools, 1.10.0 lists 61. None were removed,
+  and stdout carried JSON only. The image only bakes the binary; nothing in it
+  configures it.
+
+### Fixed
+
+- **`~/.config/devbox-shell/ssh-lan.conf` is Included even if it is created
+  after the container started.** `setup-lan-access.sh` wrote the
+  `Include ~/.config/devbox-shell/ssh-lan.conf` line only if the file was
+  readable at container start. A file created afterwards was visible in the
+  container and silently ignored, so ssh fell through to `~/.ssh/config`. Hit on
+  EMB-3HXGNXJ0 on 2026-10-18: its `tor-ms22` override (container key, no
+  passphrase) was skipped. ssh then used the Mac's passphrase-protected key, and
+  `BatchMode` failed with `Permission denied (publickey,…)`. Rerunning the script
+  inside the container fixed it. The line is now written whether or not the file
+  exists. With this image's OpenSSH 10.0p2, an `Include` whose file (or parent
+  directory) is missing is skipped. A file created later is read on the next
+  connection, and a directory at that path is ignored. A file that **exists but
+  is unreadable** makes ssh abort every connection (`Can't open user config
+  file`), so that one case is still left out, now with a warning on stderr.
+  Output is byte-identical to v1.12.0 when the file exists at start.
+  `scripts/smoke-test.sh` gains two checks: Included when created after start,
+  and left out when unreadable. Against the v1.12.0 script the first fails and
+  the second passes. README *Naming LAN peers* no longer says that creating the
+  file needs a restart.
+
 ## v1.12.0 — 2026-10-18
 
 Minor release. Headlines: **pi 1.3.0**, **mempalace 3.11.0**, **pi-atelier

Dockerfile.base

@@ -14,7 +14,7 @@
 # content-addressed over this file, so any byte change invalidates the
 # cache. Recommended cadence: once per release for security updates.
 #
-# BASE_REBUILD_DATE: 2026-10-18 (v1.12.0 — mempalace 3.11.0, link-pi-extensions.sh, studio-expose and skill doc fixes; apt and base tools re-resolve (upstream on 2026-10-18: uv 0.13.1, gitea-mcp 1.9.0, Node v24.22.0; nvim 0.12.6, fzf 0.74.5 unchanged); previous marker 2026-10-14 / v1.11.1)
+# BASE_REBUILD_DATE: 2026-10-19 (v1.12.1 — setup-lan-access.sh always Includes ssh-lan.conf; apt and base tools re-resolve (upstream on 2026-10-19: gitea-mcp 1.10.0; uv 0.13.1, Node v24.22.0, nvim 0.12.6, fzf 0.74.5 unchanged); previous marker 2026-10-18 / v1.12.0)
 #
 # ── Lineage note ─────────────────────────────────────────────────────
 # Adapted from opencode-devbox/Dockerfile.base (commit before v1.16.2).

README.md

@@ -1174,12 +1174,20 @@ published image (they are a fact about your LAN, not the image). Alternatively,
 set `DEVBOX_LAN_AUTOJUMP_PRIVATE=1` to ProxyJump *any* RFC1918 address through
 the host without naming peers (see `.env.example`).
 
-Once the file exists it is re-read on every connection, so *edits* take effect
+ssh reads the file on every connection, so creating it and editing it both take
-immediately — no container or session restart. **Creating it for the first time
+effect immediately — no container or session restart. Since v1.12.1,
-does need one restart**, because `setup-lan-access.sh` only emits the
+`setup-lan-access.sh` writes the `Include ~/.config/devbox-shell/ssh-lan.conf`
-`Include ~/.config/devbox-shell/ssh-lan.conf` line when the file is already
+line whether or not the file exists yet (ssh skips an `Include` whose file is
-readable at container start (`if [ -r "$SSH_LAN_CONF" ]`). Until then ssh never
+missing). Images up to and including v1.12.0 wrote that line only if the file
-looks at it — which reads exactly like "my override is being ignored".
+was readable at container start. There, a file created afterwards is ignored
+until a restart, or until you run `bash /usr/local/lib/pi-devbox/setup-lan-access.sh`
+in the container.
+That looks exactly like "my override is being ignored". One case still needs
+action: a file that exists but the container cannot read is left out, because
+ssh would otherwise refuse every connection. The script then prints a warning at
+start. Two other permission traps apply to this file as to any ssh config.
+ssh rejects it if it is world-writable (`Bad owner or permissions`). And on native
+Linux, the host user's uid must match the container's `developer` (1000).
 
 #### Giving the container its own key for a peer
 

rootfs/usr/local/lib/pi-devbox/setup-lan-access.sh

@@ -51,8 +51,8 @@
 # HOST-OWNED PEER POLICY (portable; keeps this image generic)
 #   Named LAN peers are facts about a *specific* host's network, not about the
 #   image — a roaming laptop sees different LANs. So we never bake peer names
-#   here. Instead, if the host bind-mounts ~/.config/devbox-shell/ssh-lan.conf
+#   here. Instead we Include ~/.config/devbox-shell/ssh-lan.conf (the host
-#   (the same devbox-shell bridge dir used for shared aliases), we Include it
+#   bind-mounts the devbox-shell bridge dir, also used for shared aliases)
 #   *before* ~/.ssh/config. That file holds the host's own jump overrides, e.g.
 #       Host pve pve-2 pbs-vm
 #           ProxyJump host
@@ -151,8 +151,22 @@ EOF
 
   # Optional host-owned named-peer jump overrides (portable: lives on the host,
   # not in the image). Included BEFORE ~/.ssh/config so its ProxyJump wins.
+  #
+  # Included even when the file does not exist yet. ssh skips an Include whose
+  # file is missing, and reads it on the next connection once it appears.
+  # Through v1.12.0 the Include was written only if the file was readable at
+  # container start. A file created later was then visible in the container but
+  # ignored, until a restart (EMB-3HXGNXJ0, 2026-10-18: its tor-ms22 override
+  # was skipped, so ssh fell back to a passphrase key and BatchMode failed).
+  # Only a file that EXISTS but cannot be read is left out. ssh aborts every
+  # connection on one ("Can't open user config file"), which would break all
+  # ssh, git included. A directory at that path is harmless (ssh ignores it).
+  # Measured with this image's OpenSSH 10.0p2; scripts/smoke-test.sh checks
+  # both cases.
   SSH_LAN_CONF="${HOME}/.config/devbox-shell/ssh-lan.conf"
-  if [ -r "$SSH_LAN_CONF" ]; then
+  if [ -e "$SSH_LAN_CONF" ] && [ ! -r "$SSH_LAN_CONF" ]; then
+    echo "setup-lan-access: $SSH_LAN_CONF exists but is not readable, so it is not Included (ssh would refuse every connection). Fix its permissions, then rerun this script or restart the container." >&2
+  else
     LAN_CONF_BLOCK=$(cat <<'EOF'
 
 # Host-owned named-peer jump overrides (bind-mounted; edit on the host).

scripts/smoke-test.sh

@@ -696,6 +696,29 @@ exec_test "git core.sshCommand matches sidecar presence" '
   else
     [ -z "$cmd" ] || exit 1; echo "no sidecar, correctly unset"
   fi'
+# ssh-lan.conf is Included whether or not it exists at container start. Until
+# v1.12.0 the Include was written only if the file was readable at start, so a
+# file created later was silently ignored (EMB-3HXGNXJ0, 2026-10-18). ssh skips
+# an Include whose file is missing, and picks the file up once it appears, with no
+# restart. The exception is a file that exists but cannot be read: ssh then
+# aborts every connection, so that case is still left out. 644 is set
+# explicitly because ssh rejects a world-writable config file.
+exec_test "ssh-lan.conf Included even if created after start" '
+  T=$(mktemp -d) && mkdir -p $T/.config/devbox-shell &&
+  HOME=$T DEVBOX_LAN_ACCESS=jump bash /usr/local/lib/pi-devbox/setup-lan-access.sh >/dev/null 2>&1 &&
+  grep -qx "Include ~/.config/devbox-shell/ssh-lan.conf" $T/.ssh-local/config &&
+  HOME=$T ssh -F $T/.ssh-local/config -G lanpeer 2>/dev/null | grep -qx "hostname lanpeer" &&
+  printf "Host lanpeer\n    HostName 10.9.9.9\n" > $T/.config/devbox-shell/ssh-lan.conf &&
+  chmod 644 $T/.config/devbox-shell/ssh-lan.conf &&
+  HOME=$T ssh -F $T/.ssh-local/config -G lanpeer 2>/dev/null | grep -qx "hostname 10.9.9.9"
+  r=$?; rm -rf $T; exit $r'
+exec_test "unreadable ssh-lan.conf left out (ssh would abort)" '
+  T=$(mktemp -d) && mkdir -p $T/.config/devbox-shell && : > $T/.config/devbox-shell/ssh-lan.conf &&
+  chmod 000 $T/.config/devbox-shell/ssh-lan.conf &&
+  HOME=$T DEVBOX_LAN_ACCESS=jump bash /usr/local/lib/pi-devbox/setup-lan-access.sh >/dev/null 2>&1 &&
+  ! grep -q "ssh-lan.conf$" $T/.ssh-local/config &&
+  HOME=$T ssh -F $T/.ssh-local/config -G lanpeer >/dev/null 2>&1
+  r=$?; rm -rf $T; exit $r'
 # The vendored mempalace snapshot is refreshed MANUALLY per release (see
 # rootfs/usr/local/share/pi-devbox/skills/VENDORED.md). Through v1.8.4 it also
 # silently SHADOWED the live skillset copy, so staleness was invisible — and the