From 7b62f2c22ab76a4fd390f23428f3d98f7f2095cd Mon Sep 17 00:00:00 2001 From: damocles Date: Mon, 16 Nov 2026 01:08:03 +0100 Subject: [PATCH] docs: the config repo grant is read in the persistence and forge handbook pages --- docs/2-handbook/agents/persistence.md | 9 +++++---- docs/2-handbook/swarm/forge.md | 7 +++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/2-handbook/agents/persistence.md b/docs/2-handbook/agents/persistence.md index cb705427b..39c399f68 100644 --- a/docs/2-handbook/agents/persistence.md +++ b/docs/2-handbook/agents/persistence.md @@ -46,10 +46,11 @@ The tables, state directories, mounts and migrations behind this are in A config change is a pull request on the agent's config repo, `agent-configs/`. No tool exists for it: opening the PR is the request. -1. The agent clones its config repo, edits it (`agent.nix` is the entry point), - pushes a branch and opens the PR with `hive-forge`. Branch protection lets it - push branches but not `main`, so it **can't merge its own config PR**. An agent - can propose a change to another agent's config the same way. +1. The agent clones its config repo, edits it (`agent.nix` is the entry point) + and opens the PR with `hive-forge pr create --agit`. It has read access to + the repo and no push access, so it **can't push a branch or merge its own + config PR**. An agent can propose a change to another agent's config the same + way. 2. You review the PR on the forge, with its diff, comments and CI status, and merge it there. Merging needs membership of the `operators` team in `agent-configs`. The team starts empty: add each operator by hand in the forge diff --git a/docs/2-handbook/swarm/forge.md b/docs/2-handbook/swarm/forge.md index 5ebdb78f4..e3ff66e51 100644 --- a/docs/2-handbook/swarm/forge.md +++ b/docs/2-handbook/swarm/forge.md @@ -48,10 +48,9 @@ forge is re-minted within five minutes. Two things live in the `agent-configs` Forgejo organization: -- A config repo per agent, `agent-configs/`. The agent can push - config-change branches and open config PRs there, but `main` is - 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 +- A config repo per agent, `agent-configs/`. The agent is a read + collaborator there: it opens config PRs through the AGit flow, has no push + access, and only the `operators` team can merge, so it can't self-merge. An operator's merge in the Forgejo UI deploys the merged commit (see [persistence.md ยง Config changes](../agents/persistence.md#config-changes)). Repos stay private, so an agent can't read another agent's config.