treefmt: apply prettier
Pure `nix fmt` output from the commit before this one — no hand edits. 203 files: 52 md, 42 tsx, 32 js, 32 css, 21 ts, 13 html, 8 json, 3 mjs. Reproduce with `nix develop -c nix fmt` on the parent commit; the result should be byte-identical to this tree. None of the 13 `.prettierignore` entries appears here — verified by intersecting the changed-file list against the ignore file, with a control proving the intersection finds a match when one exists.
This commit is contained in:
parent
5d24bedd60
commit
39b95c2ede
203 changed files with 10090 additions and 6085 deletions
|
|
@ -1,8 +1,8 @@
|
|||
# hive-agent-sock
|
||||
|
||||
Wire types for the **in-agent socket** — the one the `hive-agent` harness serves
|
||||
*inside* the container to its local producers. The matrix / bash MCP daemons
|
||||
and `forge_notify` are the *built-in* producers that ship today, but any
|
||||
_inside_ the container to its local producers. The matrix / bash MCP daemons
|
||||
and `forge_notify` are the _built-in_ producers that ship today, but any
|
||||
user-configured MCP server declared in an agent's `agent.nix` can dial this
|
||||
socket and push its own todos with an arbitrary `subsystem` marker — the
|
||||
wire format doesn't restrict the set. Unlike the host-served sockets, this
|
||||
|
|
@ -25,5 +25,5 @@ these stores travel with the agent for hive portability.
|
|||
|
||||
## Not to be confused with `hive-core-agent-sock`
|
||||
|
||||
That crate is the *host*-served core↔agent protocol on `/run/hive/mcp.sock`
|
||||
That crate is the _host_-served core↔agent protocol on `/run/hive/mcp.sock`
|
||||
(the harness talking out to `hive-c0re`). This socket is purely intra-container.
|
||||
|
|
|
|||
Loading…
Reference in a new issue