Two details needed before the first client flip.
1. MEMPALACE_REMOTE_URL is the full endpoint including /mcp with no trailing
slash. The feeder POSTs to it verbatim (bin/mempalace-pi-session:718), and the
server matches `path != "/mcp"` exactly, so a base URL or a trailing slash
both 404 -- and a 404 here looks like a routing/proxy fault, not a config
typo, which is a bad hour to spend. Matches the existing pi-devbox examples.
For this fleet: https://mempalace.jordbo.se/mcp
2. The 3.7 trap has TWO symptoms, not one, and I had only documented the loud
one. Direct runs / session-end / cron exit 1 with a clear error (:298-300).
But pi-devbox's entrypoint-user.sh:134 checks the same condition and skips
*quietly* -- and the skip happens before the subshell that writes
~/.pi/agent/mempalace-catchup.log, so there is not even an empty log to find.
A container flipped with REMOTE_URL but no SSH_TARGET therefore contributes
nothing to the palace and leaves no artifact explaining why. The skip is
correct in itself (there is genuinely no inbox to ship to) but it is
indistinguishable from a healthy run with nothing to do. Documented with two
commands that tell those apart after a flip.
Joakim Persson
2e73a9eae8