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
|
|
@ -24,18 +24,11 @@
|
||||||
//! claude-settings.json
|
//! claude-settings.json
|
||||||
//! ```
|
//! ```
|
||||||
//!
|
//!
|
||||||
//! A convenience `cargo xtask seed-dev-assets` could materialise this
|
|
||||||
//! by copying `branding/` + `hive-ag3nt/prompts/` + rendering
|
|
||||||
//! `agent-configs.png` via rsvg-convert, but it's intentionally not
|
|
||||||
//! shipped yet — dev setups vary too much for one helper to fit.
|
|
||||||
//!
|
|
||||||
//! Each crate that wants a specific asset goes through one of the
|
//! Each crate that wants a specific asset goes through one of the
|
||||||
//! typed helpers (`branding_svg()`, `prompt_template()`, …) so the
|
//! typed helpers (`branding_svg()`, `prompt_template()`, …) so the
|
||||||
//! lookup contract is centralised. Missing files panic at first
|
//! lookup contract is centralised. Missing files panic at first
|
||||||
//! call with a clear "set `HIVE_ASSETS_DIR` + put the file at …"
|
//! call with a clear "set `HIVE_ASSETS_DIR` + put the file at …"
|
||||||
//! message — same failure shape as the old `include_*!` macros
|
//! message.
|
||||||
//! (which would have failed at compile time, not runtime, but the
|
|
||||||
//! diagnostic value is identical).
|
|
||||||
|
|
||||||
use std::path::PathBuf;
|
use std::path::PathBuf;
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -2,10 +2,9 @@
|
||||||
//!
|
//!
|
||||||
//! Every process that runs inside an agent container - the harness plus
|
//! Every process that runs inside an agent container - the harness plus
|
||||||
//! the out-of-process MCP daemons (bash, matrix, ...) - must resolve the
|
//! the out-of-process MCP daemons (bash, matrix, ...) - must resolve the
|
||||||
//! harness directory layout identically. These helpers previously had to
|
//! harness directory layout identically. These helpers live here so the
|
||||||
//! be hand-mirrored across crates (each copy carrying a "keep in sync"
|
//! resolution exists in exactly one place rather than being mirrored
|
||||||
//! comment) because there was no shared home for them; they live here so
|
//! across crates.
|
||||||
//! the resolution exists exactly once.
|
|
||||||
|
|
||||||
use std::path::PathBuf;
|
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
|
/// split). For pre-split / dev deployments where it isn't set, falls back to
|
||||||
/// a `harness/` sibling of `HYPERHIVE_STATE_DIR`, and finally to
|
/// a `harness/` sibling of `HYPERHIVE_STATE_DIR`, and finally to
|
||||||
/// `/agents/{HIVE_LABEL}/harness` when neither dir env var is present — the
|
/// `/agents/{HIVE_LABEL}/harness` when neither dir env var is present — the
|
||||||
/// shape the harness derives from its label alone. The label tier subsumes
|
/// shape the harness derives from its label alone.
|
||||||
/// the resolver `hive-ag3nt` previously kept as its own copy, so the
|
|
||||||
/// resolution now genuinely lives here exactly once.
|
|
||||||
#[must_use]
|
#[must_use]
|
||||||
pub fn harness_dir() -> PathBuf {
|
pub fn harness_dir() -> PathBuf {
|
||||||
if let Some(p) = std::env::var_os("HYPERHIVE_HARNESS_DIR") {
|
if let Some(p) = std::env::var_os("HYPERHIVE_HARNESS_DIR") {
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue