58ef299c3c
Nothing submits an approval since scheduled prompts left hive-c0re, so the
queue only acted on rows written before that.
- hive-c0re: the approvals store and its migrations, approve/deny/
resolve actions, the ResolveApproval tail node (and meta_update's
approval_id), POST /api/approve and /api/deny, the approval views on
/api/state, the approval_resolved dashboard event, the orphan GC,
destroy/purge failing pending rows, and the approval rows in
get_loose_ends. DestroyBookkeeping loses the purge flag, which only
worded the approval-failure note.
- The CancelLooseEnd request goes: its only hive-c0re arm was the
approval one. cancel_loose_end handles reminder and todo in the harness.
- Wire types: hive_sh4re::approvals (ReminderStats moves to inbox),
LooseEnd::Approval, CancelLooseEndKind, HelperEvent::ApprovalResolved,
ToolGroup::Approvals, HostRequest::{Pending,Approve,Deny} and
HostResponse.approvals. HOST_SOCK_VERSION goes to 2 for the removed
field.
- hivectl loses the approvals verbs; docs/tools/hivectl-cli.md is
regenerated.
- The system prompt drops approval_resolved.
- The approvals table stays in broker.sqlite, unread, the same way the
operator_questions table was left when its store was removed.
- An `approvals` entry still in tool-groups.json is skipped with a warning
by ToolGroup::parse_list, like any unknown group.
- docs/agent-lifecycle/approvals.md is renamed to config-changes.md so the
code's doc pointers resolve; its content follows in the docs commit.
21 lines
968 B
Markdown
21 lines
968 B
Markdown
# hive-core-agent-sock
|
|
|
|
Wire types for the **per-agent + manager socket** (`/run/hive/mcp.sock`) — the
|
|
unified `Request` / `Response` protocol spoken between an agent's in-container
|
|
harness (and the manager) and the `hive-c0re` daemon.
|
|
|
|
## Why it's its own crate
|
|
|
|
Re-homed out of `hive-sh4re` so this one socket owns its protocol crate,
|
|
mirroring the `hive-host-sock` / `hive-priv-sock` splits. The shared payload
|
|
types it references (`Message`, `LooseEnd`, …) stay in `hive-sh4re`,
|
|
which this crate depends on — this crate is just the request/response envelope
|
|
for this socket.
|
|
|
|
## Not to be confused with `hive-agent-sock`
|
|
|
|
This is the **host-served** protocol: the harness talks _out_ to `hive-c0re`
|
|
over `/run/hive/mcp.sock` (broker sends, lifecycle).
|
|
`hive-agent-sock` is the separate _in-container_ socket the harness serves to
|
|
its own local producers — that one never leaves the container. See
|
|
`docs/trust-boundary/boundary.md` for the socket topology.
|