@forgezero/agent 0.1.22 → 0.1.24

package/README.md

@@ -135,6 +135,25 @@ platform or tenant release is a durable API row bound to one exact compute:
 code, and only an awaited successful pipeline writes `deployed`. An expired
 claim can be recovered; its stale token cannot renew or finish.
 
+Compute replacement uses the same outbound pattern through
+`@forgezero/agent/migration-pull`: claim one action for this exact compute,
+renew its fencing lease while the awaited function runs, and acknowledge the
+result before accepting more work. The public function accepts the executor as
+an async callback so an embedding Agent can keep privilege and OS policy outside
+the transport. Node evidence is deliberately local-only; it cannot claim
+Agency quorum, replication completion, seed residency, edge exclusion or
+Cloudflare route existence on behalf of the controller.
+
+The managed daemon uses `@forgezero/agent/lifecycle-helper` as that executor.
+It is a separate root service behind a group-scoped Unix socket and accepts only
+fixed lifecycle operations. Unit names and loopback health endpoints come from
+a root-owned profile; a signed claim cannot supply a command or path. For a
+cross-network database member, the common installer enrolls the headless WARP
+client from systemd credentials materialized only in `/run`. Readiness requires
+WARP to be connected and the controller-selected private peer IP and database
+port to be reachable. Database traffic is never exposed through a public IP,
+public hostname, or inbound firewall rule.
+
 The same package also runs the identity-only Metal Agent. It initiates outbound
 hybrid-signed HTTPS and requires request-bound PQ-sealed responses while pulling
 only claims assigned to its enrolled hostname, then passes
@@ -144,6 +163,11 @@ read Vault data, accept arbitrary commands, or retain tenant credentials. Root
 SSH is an operator-only platform-genesis/recovery path, not the normal tenant
 dispatch mechanism.
 
+New guests also call this same public `fz agent install --apply --enrol` path
+from cloud-init. Metal provisioning does not carry a second handwritten Agent
+unit or deployment runner, so platform and tenant guests cannot drift at that
+foundation boundary.
+
 Shutdown has one process-wide deadline. New deployment claims and background
 sync stop first, claimed work drains under its lease fence, and only then do the
 queues and application socket close. Vault/attestation calls or a stale local

package/dist/cli/agent-install.d.ts

@@ -50,6 +50,16 @@ export interface InstallOptions {
     deploymentEnvironment?: Record<string, string>;
     deploymentCredentials?: Record<string, string>;
     pullDeployments?: boolean;
+    pullMigrations?: boolean;
+    lifecycleProfilePath?: string;
+    lifecycleHelperSocketPath?: string;
+    warpOrganization?: string;
+    warpClientIdCredentialPath?: string;
+    warpClientSecretCredentialPath?: string;
+    cloudflareAccountId?: string;
+    cloudflareTunnelId?: string;
+    cloudflareVirtualNetworkId?: string;
+    cloudflareWarpPolicyId?: string;
     binPath?: string;
     sourceBinPath?: string;
     user?: string;