refactor(#2077): drop impl-history from hive-sh4re asset/path comments
This commit is contained in:
parent
b1502392e5
commit
7ba5193167
2 changed files with 5 additions and 15 deletions
|
|
@ -2,10 +2,9 @@
|
|||
//!
|
||||
//! Every process that runs inside an agent container - the harness plus
|
||||
//! the out-of-process MCP daemons (bash, matrix, ...) - must resolve the
|
||||
//! harness directory layout identically. These helpers previously had to
|
||||
//! be hand-mirrored across crates (each copy carrying a "keep in sync"
|
||||
//! comment) because there was no shared home for them; they live here so
|
||||
//! the resolution exists exactly once.
|
||||
//! harness directory layout identically. These helpers live here so the
|
||||
//! resolution exists in exactly one place rather than being mirrored
|
||||
//! across crates.
|
||||
|
||||
use std::path::PathBuf;
|
||||
|
||||
|
|
@ -14,9 +13,7 @@ use std::path::PathBuf;
|
|||
/// split). For pre-split / dev deployments where it isn't set, falls back to
|
||||
/// a `harness/` sibling of `HYPERHIVE_STATE_DIR`, and finally to
|
||||
/// `/agents/{HIVE_LABEL}/harness` when neither dir env var is present — the
|
||||
/// shape the harness derives from its label alone. The label tier subsumes
|
||||
/// the resolver `hive-ag3nt` previously kept as its own copy, so the
|
||||
/// resolution now genuinely lives here exactly once.
|
||||
/// shape the harness derives from its label alone.
|
||||
#[must_use]
|
||||
pub fn harness_dir() -> PathBuf {
|
||||
if let Some(p) = std::env::var_os("HYPERHIVE_HARNESS_DIR") {
|
||||
|
|
|
|||
Loading…
Reference in a new issue