f0844f6da3
mara on #5170: "dont split caps and perms. its all perms. / dont include the now empty tool groups / nothing set -> default / also add perms to agent creation screen". - hive-sh4re: one `Permission` enum (messaging, meta, inbox, execution, web_tools, manage_root_agent) replaces `ToolGroup` and `Capability`; `lifecycle`/`forge` are gone. `Permission::default_for` is the default for an agent the swarm sets nothing for. - The record is `{ "permissions": [...] }`. Missing key, unset field or no successful read yet = default; `[]` = none; a failed read after a good one keeps the last value. - hive-agent reads its own key every 10s and builds each turn's --tools, --allowedTools and MCP config (rewritten before every turn) from it; the subagent daemon reads it on each start/continue. Agents get a read-only grant on their own key. - hive-c0re restarts an agent only when its manage_root_agent changes. The import now merges meta/capabilities.json and meta/tool-groups.json into one list per agent and deletes both; the "import pending, don't read" decision is `ImportOutcome::read_allowed`, table-tested. - swarm-controller: `GET /api/permissions` (names + default) and an optional `permissions` on `POST /api/agents`, stored before the job is queued. swarm-ui's create-agent form gets a permissions field. - Deleted: HIVE_TOOL_GROUPS and its forward to the subagent daemon, tool_groups.rs, ruth's tool-group seed, the permissions rebuild job (PermPayload/WritePermFile/perm_change), the dashboard permissions tab and its stale-entries panel. Part of #5170.
23 lines
1.1 KiB
Rust
23 lines
1.1 KiB
Rust
//! Vocabulary hive-c0re's job queue shares with its clients: the
|
|
//! scheduler's lifecycle [`State`].
|
|
//!
|
|
//! A `Source` enum lived here too — where a job came from, rendered as the
|
|
//! "why" chip. It was a field on the DAG container, and it went with it: a
|
|
//! job is its nodes now, and a node says what it does rather than who asked
|
|
//! for it.
|
|
//!
|
|
//! **The typed `DagView`/`NodeView` projection that used to live here is
|
|
//! gone.** One graph is served one way now — `hive_jobq_wire`'s generic
|
|
//! `GraphNode`, over the `QueueNodes` socket request and
|
|
//! `GET /api/jobq/graph` — so there is no second shape to keep in
|
|
//! agreement with the first. Queue internals (node kinds, edges,
|
|
//! scheduling) live in `hive-c0re::job_queue`.
|
|
//! Semantics: `docs/scheduler/coordinator.md::Job queue`.
|
|
|
|
pub use hive_jobq::State;
|
|
|
|
/// Node id. Carries the scheduler crate's globally-monotonic node id
|
|
/// (`hive_jobq::NodeId`) verbatim on the wire — unique across all DAGs, not
|
|
/// just within one. Consumers treat it opaquely (grouping + dep matching),
|
|
/// so the widening from the old dag-local `u32` is transparent.
|
|
pub type NodeId = u64;
|