diff --git a/hive-sh4re/src/assets.rs b/hive-sh4re/src/assets.rs
index aa353f46..2db24e1d 100644
--- a/hive-sh4re/src/assets.rs
+++ b/hive-sh4re/src/assets.rs
@@ -24,18 +24,11 @@
 //!     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
 //! typed helpers (`branding_svg()`, `prompt_template()`, …) so the
 //! lookup contract is centralised. Missing files panic at first
 //! call with a clear "set `HIVE_ASSETS_DIR` + put the file at …"
-//! message — same failure shape as the old `include_*!` macros
-//! (which would have failed at compile time, not runtime, but the
-//! diagnostic value is identical).
+//! message.
 
 use std::path::PathBuf;
 
diff --git a/hive-sh4re/src/paths.rs b/hive-sh4re/src/paths.rs
index 1da656d1..9a3609e7 100644
--- a/hive-sh4re/src/paths.rs
+++ b/hive-sh4re/src/paths.rs
@@ -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") {