joakimp/pi-devbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CHANGELOG: pi -p skips the palace feed in print/JSON mode (mempalace-toolkit f590a3a)
Lint / skill-floor (push) Successful in 12s
Details
Lint / hadolint (push) Successful in 16s
Details
Lint / actionlint (push) Successful in 20s
Details
Lint / doc-drift (push) Successful in 18s
Details

Browse Source 
Measured on tor-ms22: pi -p 2.9 s, --mode json 3.8 s (45 s with only the
timer fix 2f0edf5, 315 s before it). MEMPALACE_FEED_PRINT=1 restores the
feed. check-doc-drift.sh: DRIFT before this entry, rc=0 after.
This commit is contained in:
Joakim Persson
2026-10-13 14:52:13 +02:00
parent 28e324d68f
commit 1d53e008d4
1 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+13 -7
View File
@@ -18,7 +18,7 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
| Component | Baked in v1.11.0 | Next build | Why | | Component | Baked in v1.11.0 | Next build | Why |
|---|---|---|---| |---|---|---|---|
| pi-extensions | `a88fa99` | **`750b2a8`** (or later: CI resolves `main` at build time) | `mcp-loader.ts` retired; `install.sh` prunes stale links (below) | | pi-extensions | `a88fa99` | **`750b2a8`** (or later: CI resolves `main` at build time) | `mcp-loader.ts` retired; `install.sh` prunes stale links (below) |
| mempalace-toolkit | `975ab92` | **`2f0edf5`** (or later) | `pi -p` exits when the feed's mine returns, not 5 min later (below). Also `a30af61`: the bridge's `RemoteMcpClient` is now the only copy, and `scripts/check-mcp-client-sync.sh` is removed (comment/README only) | | mempalace-toolkit | `975ab92` | **`f590a3a`** (or later) | `pi -p` returns in seconds: `2f0edf5` clears the feed's leftover 5-min timer, and `f590a3a` skips the feed in print/JSON mode (below). Also `a30af61`: the bridge's `RemoteMcpClient` is now the only copy, and `scripts/check-mcp-client-sync.sh` is removed (comment/README only) |
### Fixed ### Fixed
@@ -31,12 +31,18 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
(pi 1.1.0): before the fix, `PONG` came at 4 s and exit at 315 s, and that (pi 1.1.0): before the fix, `PONG` came at 4 s and exit at 315 s, and that
timer was the only live resource for the last 265 s. After `2f0edf5`, exit timer was the only live resource for the last 265 s. After `2f0edf5`, exit
is at 45 s, the moment the session's catch-up feed finishes (prepare 11 s, is at 45 s, the moment the session's catch-up feed finishes (prepare 11 s,
mine 31 s). That wait is by design. `MEMPALACE_FEED=0` skips it: 3.8 s. mine 31 s). `f590a3a` then makes print and JSON mode skip that feed by
pi 1.0.0 behaved the same, so it predates v1.11.0. `pi-task` and `fork` default: `pi -p` takes 2.9 s and `--mode json` 3.8 s. Nothing is lost. A
children run `--no-extensions` and were never affected. one-shot run's own transcript rarely passes the exporter's quality gate, and
`scripts/test-feed-exit.sh` in mempalace-toolkit pins it; the pre-fix source the next interactive session files the device's other sessions the same
fails it. Until the next build, scripts that call `pi -p` on a devbox should way. The mine skips an unchanged transcript and purges a grown one before
keep their `timeout` or set `MEMPALACE_FEED=0`. refiling, so nothing is filed twice. `MEMPALACE_FEED_PRINT=1` restores the
feed for a device that only runs `pi -p`. pi 1.0.0 behaved the same, so it
predates v1.11.0. `pi-task` and `fork` children run `--no-extensions` and
were never affected. `scripts/test-feed-exit.sh` in mempalace-toolkit pins
both changes, and each change's pre-fix source fails it. Until the next
build, scripts that call `pi -p` on a devbox should keep their `timeout` or
set `MEMPALACE_FEED=0`.
### Changed ### Changed