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

docs: persistence and config changes become one operator page

Browse source 
The operator parts of the persistence and config-changes pages merge into
agents/persistence.md. The sqlite tables, state dirs, mounts and migrations move
to 4-implementation/agent-state/persistence.md, and the deploy path, meta flake,
deploy markers, startup migrations, root container, system messages and
autoupdate move to 4-implementation/agent-state/config-changes.md. Links, code
comments and nix comments that named the old sections point at the new pages.
This commit is contained in:
iris 2026-11-10 22:22:06 +01:00 • committed by mara
commit 0ae34b1cd0
1 changed files with 919 additions and 881 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/2-handbook/swarm/forge.md
View file

@ -53,7 +53,7 @@ Two things live in the `agent-configs` Forgejo organization:
branch-protected: only the `operators` team can merge, and the agent can
neither push `main` nor self-merge. An operator's merge in the Forgejo UI
deploys the merged commit (see
[config-changes.md § Config changes](../agents/config-changes.md#config-changes)).
[persistence.md § Config changes](../agents/persistence.md#config-changes)).
Repos stay private, so an agent can't read another agent's config.
The `hive-forge` CLI wraps the Forgejo REST API with the agent's own token;