Publish curated ITWorx-ModelForge source from 990401737f96c8d46a9f7b0d84994516cadcb6a0

docs/architecture/NODE_AGENT_PROTOCOL.md

@@ -45,6 +45,18 @@ Administrative token creation, revocation, node metadata changes and credential
 under `/api/v1/admin`. They require `X-ModelForge-Admin-Token`; the API fails closed when
 `MODELFORGE_OPERATOR_API_KEY` is unset.
 
+Temporary enable/disable uses an authenticated impact-preview and execute pair:
+`POST /api/v1/admin/hardware/nodes/{id}/lifecycle/preview` and
+`POST /api/v1/admin/hardware/nodes/{id}/lifecycle`. Preview is bound to the node generation and a
+digest of current dependencies. Disable is refused while the dependency scan finds deployments,
+jobs, probes, residencies, leases, requests, pending transitions, or other listed work. Execute
+rechecks under the same dependency-table lock set used by decommission and uses a generation CAS.
+The older metadata `PATCH` still handles display name, labels, role and eligibility, but rejects
+`enabled`; it cannot bypass preview and typed identity confirmation. A remote node can be enabled
+only with an active node credential. Re-enable clears the prior protocol, capability, agent-version
+and heartbeat evidence, sets liveness to offline, and requires a fresh authenticated compatible
+heartbeat before readiness can be inferred. Decommission remains a distinct terminal transition.
+
 `POST /api/v1/admin/hardware/nodes/{id}/credential/rotate` atomically revokes the previous
 credential and returns its replacement once. Install the replacement in the protected agent state
 file before restarting it. Rotation and revocation are separate audited operations.