diff --git a/hive-c0re/src/forge/repos.rs b/hive-c0re/src/forge/repos.rs index 008a1841..7405a82f 100644 --- a/hive-c0re/src/forge/repos.rs +++ b/hive-c0re/src/forge/repos.rs @@ -466,10 +466,12 @@ pub async fn clone_config_into_proposed(dir: &Path, name: &str) -> bool { true } Ok(o) => { - // `info`, not `warn`: on the hive-level create flow every first - // spawn lands here and nothing is wrong. Logged at all because - // "where did this agent's config come from" is worth answering - // from the journal, and proposed is seeded exactly once. + // `info`, not `warn`: the normal case right after + // `swarm-controller` creates the agent, before it has pushed + // anything into the repo it just made, and nothing is wrong. + // Logged at all because "where did this agent's config come + // from" is worth answering from the journal, and proposed is + // seeded exactly once. tracing::info!( %name, stderr = %String::from_utf8_lossy(&o.stderr).trim(), diff --git a/hive-c0re/src/lifecycle/setup.rs b/hive-c0re/src/lifecycle/setup.rs index 992a5eba..033af761 100644 --- a/hive-c0re/src/lifecycle/setup.rs +++ b/hive-c0re/src/lifecycle/setup.rs @@ -23,9 +23,11 @@ use super::git::{ /// avoided: whichever wrote second would win, and neither knows about /// the other. /// -/// The template ([`seed_template`]) is what the hive-level create flow -/// still lands on, since that flow creates the forge repo *after* the -/// first spawn. +/// The template ([`seed_template`]) is what this still falls back to when +/// there's genuinely nothing to clone yet — `swarm-controller` creates +/// `agent-configs/` before telling a hive to deploy, but hasn't +/// necessarily pushed `main` to it yet, or the forge is unreachable, or +/// the core token isn't minted. /// /// **Seeding is the whole of hive-c0re's write.** Changes to the repo /// arrive as PRs from a clone, via the forge, like any other code