A taken tunnel's found configuration is retired once the take is proven (hq ADR 0119)

Kept on disk it was the take's fallback; once the mesh's interface is up in its place and a peer
has handshaken with it, it is an unmaintained way back onto the network, held for ever. It is now
removed from where its unit reads it, its kept original verified first and left as it is, and the
hold ends. Until proven — no handshake, or wg not answering — it is kept and the report says why.
The retirement is recorded apart from holds, so later applies, an undeclare, and a reassignment
find it retired rather than missing, and nothing writes it back.

internal/declaration/declaration.go

@@ -706,9 +706,10 @@ type Service struct {
 
 	// TakesOver names the found tunnel this service replaces (novox/hq ADR 0105): before this unit
 	// is started, the named unit is stopped and disabled — never flushed — and its configuration
-	// file is kept like any held file. Only on an adopted node, and only said by the controller,
-	// which knows the found tunnel's key is this node's own: without that, starting this unit on
-	// the found one's port would drop every peer's packets.
+	// file is kept like any held file — until the take is proven by a peer's handshake, and then
+	// retired, its original staying kept (novox/hq ADR 0119). Only on an adopted node, and only
+	// said by the controller, which knows the found tunnel's key is this node's own: without that,
+	// starting this unit on the found one's port would drop every peer's packets.
 	TakesOver *TakeOver `json:"takes-over,omitempty"`
 }