From 49b6f0f0c328e8d2b9299ce77fbc410e6ecda3c8 Mon Sep 17 00:00:00 2001
From: atlas <atlas@hyperhive.local>
Date: Fri, 2 Oct 2026 01:58:25 +0200
Subject: [PATCH] docs(web-ui): say precisely what keeps old FORGES-tab
 accounts working

The old FORGES tab wrote forge-<label>-token/forge-<label>.json directly;
the swarm-fetch unit that replaced it never deletes a pair for a label it
doesn't list, so those files keep being read by hive-forge -f <label>
until the operator links an account under the same label in the swarm UI,
which overwrites both files (nix/agent-modules/forge-accounts.nix:11-13,159-176).
---
 docs/web-ui/dashboard.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/web-ui/dashboard.md b/docs/web-ui/dashboard.md
index 6132a85f..7b5a18c5 100644
--- a/docs/web-ui/dashboard.md
+++ b/docs/web-ui/dashboard.md
@@ -318,7 +318,7 @@ Provisioning posts `POST /api/github-account` (form-encoded `agent`,
 `application/problem+json` with the message in `detail`. The token is never
 echoed back in either direction.
 
-Link an external forge account from the swarm UI (`LinkForgeAccountForm` → swarm-controller); the agent fetches it into the files `hive-forge -f <label>` reads. Accounts already provisioned through the old FORGES tab keep working until the operator links them there.
+Link an external forge account from the swarm UI (`LinkForgeAccountForm` → swarm-controller); the agent fetches it into the files `hive-forge -f <label>` reads. A `forge-<label>-token`/`forge-<label>.json` pair left by the old FORGES tab is never deleted, so `hive-forge -f <label>` keeps reading it until the operator links an account under that label in the swarm UI, which overwrites both files with the fetched value (`nix/agent-modules/forge-accounts.nix:11-13,159-176`).
 
 ## P3RM1SS10NS tab