kyle/boxmaker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

M5c-2 plan: task 11, the admin socket's requests move out of serve.rs

Browse Source 
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
kyle
2026-09-28 21:07:18 -07:00
co-authored by Claude Opus 5.5
parent 531a723e39
commit 5b39b7ffc3
4 changed files with 535 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans/M5c2/README.md
+4 -2
View File
@@ -83,9 +83,10 @@ Honcho sources and chats outside its state lock, and answers `ask_memory`.
| 08 | `memoryd`: `recall`'s Honcho part (`honcho/search.rs`): every source of `recall_sources` at once, each on its own thread with a limit of 5 s from the start; a read agent's workspace is a search and two conclusion queries; `<source>: unavailable`; a query holding a secret asks nothing; the answer from the local items and Honcho's, with the stricter label | memoryd |
| 09 | `memoryd`: `recall` with `[honcho]` runs the local part under the state lock and the Honcho part outside it; the readers taken at start; without `[honcho]`, `recall` as before | memoryd |
| 10 | `memoryd`: `ask_memory`: workspace names checked against `[honcho]`, both chats at once, each answer tagged and capped, labels, `<workspace>: unavailable`; a question holding a secret sends nothing | memoryd |
| 11 | `memoryd` serves `ask_memory` beside `recall` and `memory`, outside the lock; `bxctl`'s usage and the runbook where a new message needs a pointer | memoryd, bxctl |
| 11 | `memoryd`, making room: `reindex` and `admin` move unchanged from `serve.rs` to `serve/admin.rs`, with tests for four of their behaviours no test pinned | memoryd |
| 12 | `memoryd` serves `ask_memory` beside `recall` and `memory`, outside the lock; `bxctl`'s usage and the runbook where a new message needs a pointer | memoryd, bxctl |
After task 11, the design model runs the M5c-2 device check (spec 13) on straylight, rift and the
After task 12, the design model runs the M5c-2 device check (spec 13) on straylight, rift and the
owner's Mattermost: a second `memoryd` under its own name writes a fleet note that `recall` finds,
tagged `memory-tainted`, turning the session untrusted; `ask_memory` answers from the agent's own
trusted workspace within its limit; with rift down, `recall` answers from the local index with
@@ -109,6 +110,7 @@ The gate count is the passed total of `cargo test --workspace` plus one, for the
| 08 | 1430 | 19, 19 |
| 09 | 1434 | 8, 8 |
| 10 | 1444 | 18, 18 |
| 11 | 1448 | 8, 8 |
**A flaky test, fixed before the run:** `bxctl`'s `chat_approvals` test
`json_prints_only_json_and_never_asks_brokerd` failed once in 5 loaded runs of the whole workspace