job_queue: move the jobs wire types to hive-host-sock
The DagView / NodeView / Source / State / PermPayload types only ever travel on the host admin socket and the dashboard channels hive-c0re serves off the same snapshot; their whole consumer set is hive-c0re, hivectl and the socket protocol crate itself. Living in hive-sh4re made the five other crates that depend on it carry job-queue types they never name. Pure move: git mv of the module plus the import sweep, no type changes. hive-sh4re keeps its own chrono (wire_time still needs it).
This commit is contained in:
parent
8a7a450240
commit
a8728ac532
8 changed files with 39 additions and 27 deletions
|
|
@ -2,16 +2,22 @@
|
|||
//!
|
||||
//! The host-control protocol spoken between `hivectl` and the `hive-c0re`
|
||||
//! daemon. Re-homed out of `hive-sh4re` so a standalone `hivectl` can depend
|
||||
//! on just this protocol crate instead of the whole daemon crate. The shared
|
||||
//! payload types it references (`Approval`, `AgentStatusRow`, `jobs::DagView`)
|
||||
//! stay in `hive-sh4re`.
|
||||
//! on just this protocol crate instead of the whole daemon crate. The
|
||||
//! job-queue wire types ([`jobs`]) travel on this socket and the dashboard
|
||||
//! channels `hive-c0re` serves off the same snapshot, and on nothing else —
|
||||
//! their whole consumer set is `hive-c0re` + `hivectl` + this crate — so they
|
||||
//! live here rather than in the shared crate. The payload types genuinely
|
||||
//! shared with the *agent* sockets (`Approval`, `AgentStatusRow`) stay in
|
||||
//! `hive-sh4re`.
|
||||
|
||||
use std::path::PathBuf;
|
||||
|
||||
use hive_sh4re::{AgentStatusRow, Approval, jobs};
|
||||
use hive_sh4re::{AgentStatusRow, Approval};
|
||||
use hive_types::Ident;
|
||||
use serde::{Deserialize, Serialize};
|
||||
|
||||
pub mod jobs;
|
||||
|
||||
// ── Shared hive layout facts ──────────────────────────────────────────────
|
||||
// Paths + names both the `hive-c0re` daemon and the host-side `hivectl` CLI
|
||||
// must agree on. Homed here (the protocol crate both sides already depend on)
|
||||
|
|
|
|||
Loading…
Reference in a new issue