mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

leave the old applied dirs alone: no startup deletion. Refs #5913

Browse source
This commit is contained in:
damocles 2026-11-01 17:49:06 +01:00
commit c39a836bc5
1 changed files with 8 additions and 68 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/agent-lifecycle/config-changes.md
View file

@ -195,8 +195,8 @@ hive-c0re keeps no copy of an agent's config: the forge's `agent-configs/<name>`
record what the agent's last successful build pinned, and nothing else.
Older hives also kept an *applied* repo at `applied/<name>` and a *proposed*
clone at `agents/<name>/config`. The startup migration removes the applied
repos. Nothing reads the proposed clone any more, and you can delete it.
clone at `agents/<name>/config`. Nothing reads either any more, and you can
delete them.
The container's `--flake` ref is `internal/meta` (see "Meta flake" above).
The agent's `agent-configs/<n>/flake.nix`
@ -271,9 +271,6 @@ host set up before the current deploy scheme (described above)
converges to it automatically. Each phase is a no-op
once already applied:
- **Applied repos**: deletes the per-agent `applied/<n>` repos an earlier hive
kept. The deploy markers beside them stay. Non-destructive for everything
else — it doesn't touch live containers, state dirs, or claude creds.
- **Agent files**: refreshes the files that follow the agent set
(`agent_set::refresh`) from the current agent list. Set
`HIVE_SKIP_META_MIGRATION=1` on the service to defer this phase.