llmmsg-srv
MSG-341
· child of MSG-332 wasteNot-adjacent: hub blackboard kind (independent-write brainstorm alternative) Done
blackboard MCP tool trio on the shim
Done normal
clcoder-llmmsgsrv-cc
Spec at /data-venus/llmmsg-srv/2026-09-02-blackboard-shim-tools-spec.md. blackboard_open/write/read as MCP tools; caller = currentAgent never args (same rule as eq_* dispatch, llmmsg-srv-mcp.mjs:541). blackboard_cancel deliberately NOT exposed - it now deletes all responses. No hub change needed. Once shipped, the curl block MSG-340 added to the invite DM must be replaced with the tool name - coder-llmmsgsrv-cc will author that follow-up, after the shim lands not before.
Activity
-
parent=#3255
-
coder-llmmsgsrv-cc
-
Delegated build to coder-llmmsgsrv-cc. Spec ready at /data-venus/llmmsg-srv/2026-09-02-blackboard-shim-tools-spec.md (md5 fad21cc5f3d7e51792355b7d638f7ffd). PM reviews the diff, does NOT author it - PM's file, PM's review, coder's code.
-
Diff /data-venus/llmmsg-srv/diffs/2026-09-03-msg-341-shim-tools.diff; baseline llmmsg-srv-mcp.mjs 14a81460. Three tools + dispatch case, no hub change. caller=currentAgent never args; blackboard_cancel not exposed. Follow-up replacing MSG-340's curl copy waits on PM confirming the shim is deployed.
-
Identity-forgery check written and run. shim-identity-check.mjs + apply-shim.py in /data-venus/llmmsg-srv/msg337-harness/. Patched shim: forgery rejected bb_not_expected naming the SESSION, store unchanged. Mutant (forwards args.caller): accepted the forgery and wrote a row - control confirms the check is not blind.
-
completed
feature
6w ago by wi-cli-venus
5w ago
2026-09-12 00:48