hive-c0re: seed an agent's proposed config from the forge when it exists
The swarm writes agent-configs/<agent> when it creates an agent, before any hive is told to deploy it. setup_proposed authored a second copy of those same bytes locally, so an agent's initial config had two sources of truth, each unaware of the other and free to disagree. It now clones that repo and falls back to the template only when there is nothing there to take. Preferred-source rather than a new-path-only variant because provision_container is the Provision node for the swarm deploy and the approval flow both, and cannot tell them apart. The approval flow creates agent-configs/<agent> only after the first spawn (forge_after_first_spawn), so it finds nothing and lands on the template: the fallback becomes unreachable when hive-level create is removed, rather than becoming something someone has to find and delete. clone, not the neighbouring init+fetch. A failed fetch leaves an empty .git behind, and that .git is exactly the byte setup_proposed reads to decide whether seeding is still needed, so the fallback would have seen a seeded repo. git removes a directory it created when a clone fails. --branch main also makes an empty repo fail cleanly instead of cloning to an unborn HEAD that would look seeded.
This commit is contained in:
parent
bfae9aa51a
commit
ccf9951e5d
5 changed files with 118 additions and 27 deletions
|
|
@ -380,12 +380,17 @@ impl Client {
|
|||
/// Seed `repo` with the two files every agent config repo needs:
|
||||
/// `agent.nix` (the agent's own module) and `flake.nix` (the
|
||||
/// boilerplate that lets the meta flake import this repo as a flake
|
||||
/// input) — same content `hive-c0re::lifecycle::setup::setup_proposed`
|
||||
/// writes at the per-hive level, committed here in one atomic
|
||||
/// `repo_change_files` call instead of a local `git commit` (this
|
||||
/// process has no working tree to commit from — it only ever talks to
|
||||
/// the forge over HTTP). The whole job of the `InitAgentConfigRepo`
|
||||
/// node.
|
||||
/// input) — committed here in one atomic `repo_change_files` call
|
||||
/// instead of a local `git commit` (this process has no working tree to
|
||||
/// commit from — it only ever talks to the forge over HTTP). The whole
|
||||
/// job of the `InitAgentConfigRepo` node.
|
||||
///
|
||||
/// **This is the agent's config, not a copy of it.** A hive told to
|
||||
/// deploy the agent clones this repo
|
||||
/// (`hive-c0re::forge::clone_config_into_proposed`) rather than writing
|
||||
/// the same files again locally; the byte-identical template in
|
||||
/// `hive-c0re::lifecycle::setup::seed_template` is only reached when no
|
||||
/// repo exists here to clone.
|
||||
///
|
||||
/// Idempotent by construction rather than by catching a conflict: an
|
||||
/// unconditional `repo_change_files` against an already-seeded repo
|
||||
|
|
|
|||
Loading…
Reference in a new issue