From 4e18f7a183ee636fbb3927a7fdd06f4f0d39c560 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Sat, 5 Sep 2026 08:01:06 -0700 Subject: [PATCH] memory: laptop backup ruled out deliberately; MCP adoption is gated on ssh_config Records the operator's ruling that esh-macbook-air is regenerable surface and is not to be backed up, so a future session finds a settled decision rather than re-discovering an unbacked-up machine and re-raising it. Also records the real blocker on the MCP server, found by trying to use it: it addresses hosts only by exact ssh_config alias, and 15 of the 28 hosts in servers/ have no alias at all. The allowlist is not what limits coverage, so widening it would not have helped. --- persistent-memory.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/persistent-memory.md b/persistent-memory.md index 395237e..24eb450 100644 --- a/persistent-memory.md +++ b/persistent-memory.md @@ -324,6 +324,27 @@ below is a live commitment or a known-open risk._ zsh login shell; wrong — the server invokes `bash --noprofile --norc` explicitly, so the login shell is irrelevant.) +- **`esh-macbook-air` (10.0.10.83) is DELIBERATELY NOT BACKED UP — operator ruling + 2026-09-05, settled, do not re-raise.** Surveyed it and found no Time Machine + destination and no restic/borg/rclone/kopia installed, protecting 132 GiB. + Operator's answer: it is his laptop and the surface is **regenerable** — mostly + applications, with real data living in OneDrive, iCloud and ssh sessions — and he + does not want PBS filled with it. Correct call; the finding was real and the + conclusion is that it does not matter. FileVault On and SIP enabled already cover + the loss-and-theft axis. The same reasoning presumably extends to + `esh-mac-studio` and `vuongs-mac-mini`. **Still open and much smaller:** Remote + Apple Events (port 3031/eppc) is listening and nothing uses it — one toggle. + +- ⚠ **`remote-ssh` MCP could not be used for its FIRST real task, and the blocker + is `~/.ssh/config`, not the tool.** The server accepts only exact `Host` aliases, + so a host addressed by raw IP is structurally unreachable no matter what the + allowlist says. **13 of the 28 hosts in `servers/` have an alias; 15 do not** — + including `ana-docker`, `ana-ml2`, `nh3-docker`, `pfi-gx10`, `esh-docker-vm` and + every hypervisor, i.e. most of where the work happens. Widening + `~/.config/remote-ssh-mcp/config.json` does NOT fix this; the aliases have to + exist first. Any real adoption push starts with ssh_config coverage, not with the + allowlist. + ## Recent decisions - `[2026-09-05]` **A peer's "2.7x serving-stack effect" was a coin flip — the operator rejected it on instinct and the arithmetic backed him.** Each floor was `|b0-b1|` from n=2; the ratio is half-Cauchy, P=0.452. ⚠ The disconfirming evidence sat in brokkr's own sentence, and he named *why*: the claim was his and flattering. → `persistent-memory.d/2026-09-05-floor-claim-n2-retraction.md`