@forgezero/agent 0.1.30 → 0.1.32

package/README.md

@@ -145,6 +145,34 @@ file before executing any command, prepares only the selected profile, and gives
 step only the vault values it explicitly names. `await` returns the complete
 pipeline result; no polling service or persistent queue is required.
 
+Create and validate that file with the same public package that executes it:
+
+```bash
+fz deploy catalog --channel production
+fz deploy init --profile app --software bun@1.3.14
+# Replace the explicit safe blockers with this project's release and health commands.
+fz deploy check
+fz deploy sync
+```
+
+`init` refuses to invent a generic release or health check: both generated steps
+exit non-zero until the project replaces them. `check` validates the published
+v2 schema and active software coordinates, then prints a formatting-independent
+semantic SHA-256 digest. The schema ships at
+`@forgezero/agent/schema/deploy-v2.json` and is served from
+`https://www.forgezero.net/schemas/deploy-v2.json`.
+
+Git is the only local-to-live synchronization mechanism. `sync` validates and
+prints that rule; it does not create a second mutable command copy in the API.
+The verified webhook identifies one exact commit, and a successful Agent result
+persists the definition digest so the Applications screen can prove which local
+contract became live.
+
+Catalog status is an admission boundary, not a suggestion. `testing` coordinates
+are visible in the development catalog for ForgeZero qualification but cannot be
+selected by any deploy file. A repository cannot promote software by calling
+itself development; only a reviewed catalog change to `active` unlocks it.
+
 The daemon owns source checkout and command execution. Bootstrap explicitly
 awaits release one because the API does not exist yet, then the Agent consumes a
 one-use platform enrolment capability. There is no branch watcher. Every normal

package/dist/agent-heartbeat.d.ts

@@ -1,6 +1,6 @@
 import type { NodeKeyPair } from '@forgezero/runtime/identity';
 import { type AgentRelease } from './agent-update';
-import { type AgentUpdateResponse } from './agent-update-helper';
+import { type AgentUpdateReceipt, type AgentUpdateResponse } from './agent-update-helper';
 export interface AgentObservation {
     version: string;
     os: {
@@ -9,12 +9,18 @@ export interface AgentObservation {
     };
     architecture: string;
     mode: 'attested' | 'enrolled';
+    update?: AgentUpdateReceipt;
 }
 export interface AgentHeartbeatResponse {
     ok: true;
     nodeKey: string;
     intervalSeconds: number;
     desiredAgentRelease?: AgentRelease;
+    desiredAgentUpdate?: {
+        attemptId: string;
+        leaseExpiresAtTs: number;
+        release: AgentRelease;
+    };
 }
 export interface AgentHeartbeatOptions {
     apiUrl: string;
@@ -26,11 +32,13 @@ export interface AgentHeartbeatOptions {
     fetch?: (input: URL, init: RequestInit) => Promise<Response>;
     requestTimeoutMs?: number;
     observation?: () => AgentObservation;
+    receiptPath?: string;
+    now?: () => number;
     /** Stop new lifecycle/deploy claims and await current jobs before replacement. */
     prepareUpdate?: (release: AgentRelease) => Promise<void>;
     /** Restart the drained current process if staging is refused before activation. */
     recoverUpdate?: (cause: unknown) => Promise<void> | void;
-    applyUpdate?: (release: AgentRelease, currentVersion: string) => Promise<AgentUpdateResponse>;
+    applyUpdate?: (release: AgentRelease, currentVersion: string, attemptId: string) => Promise<AgentUpdateResponse>;
     setTimer?: (callback: () => void, ms: number) => unknown;
     clearTimer?: (handle: unknown) => void;
     onEvent?: (event: string, detail?: unknown) => void;