Publish curated ITWorx-ModelForge source from 990401737f96c8d46a9f7b0d84994516cadcb6a0

docs/operations/RUNBOOK_NODE_LOSS.md

@@ -31,9 +31,17 @@ matches and the node reconnects on its own.
 identity file, so it re-enrols onto the same node id with its accelerators, storage roots and
 history intact. Enrolment revokes the previous credential automatically.
 
+If the node's identity volume is still present and an administrator can install a replacement
+credential directly, open the node detail and use **Rotate node credential**. Rotation revokes the
+old key immediately. Replace `/data/state/node-credential` with the one-time value and recreate the
+agent before expecting heartbeats or inventory to resume. The Console cannot install the value on
+the node. If the identity volume is missing, use fresh enrolment instead.
+
 **The credential is believed stolen.** Revoke it first
 (`DELETE /api/v1/admin/hardware/nodes/{node_id}/credential`), then re-enrol. Revocation is
-permanent: the old credential stays refused after re-enrolment.
+permanent: the old credential stays refused after re-enrolment. If a replacement can be installed
+immediately, the node detail's rotation action combines revocation and replacement; the old key is
+still permanently refused.
 
 **The identity file is also lost.** The agent enrols as a new node, because ModelForge genuinely
 cannot tell it apart from different hardware. If the old identity is permanently superseded, use