@forgezero/agent 0.1.17 → 0.1.19

package/README.md

@@ -103,23 +103,19 @@ acknowledgement. The short-lived token is therefore not an unsigned Agent path.
 ## The socket interface
 
 ```
-identity   who this node is
-sign       sign a request with the node key
-attest     a hardware report, or a refusal — never a fake
 get        one secret
 sync       what changed since a cursor
 held       what this guest is holding, by name only
 ```
 
-The vault socket never accepts commands or deployment definitions. Deployment
-enters through the root-only control socket or the signed outbound claim path,
-then the deployment manager validates the checked-in definition and submits it
-to the common keyed queue. Keeping execution off the vault socket prevents a
-compromised application from turning secret-read access into a local shell.
-
-`attest` **refuses** when no source is configured rather than returning
-something attestation-shaped. An operator who believes they have an attestation
-when nothing produced one is worse off than one told plainly it is unavailable.
+The application Vault socket never accepts identity, signing, attestation,
+commands or deployment definitions. The Agent signs and attests only inside its
+own outbound clients. Otherwise a compromised application could ask for a valid
+node signature over a deployment or whole-project sync request and impersonate
+the Agent without ever extracting its key. Deployment enters through the
+root-only control socket or signed outbound claim path, then the deployment
+manager validates the checked-in definition and submits it to the common keyed
+queue.
 
 ## Deployment definitions
 

package/dist/cache.d.ts

@@ -60,7 +60,8 @@ export interface CacheOptions {
      * Every name in the assigned scope. Present means REPLICA mode.
      *
      * Absent means the old behaviour — fetch on demand, hold what was asked for.
-     * Present means the agent pulls the whole project+environment at startup and
+     * Present means the agent pulls the whole bound project across every
+     * environment at startup and
      * on every resync, so an application reads with no round trip and keeps
      * working while the platform is unreachable.
      *

package/dist/fz-agent.js

@@ -255,6 +255,13 @@ function startNodeVaultSync(cache, options = {}) {
 }
 
 // src/socket.ts
+var APPLICATION_VAULT_OPS = new Set(["get", "held", "sync"]);
+function handleApplicationRequest(options, request) {
+  if (!APPLICATION_VAULT_OPS.has(request?.op)) {
+    return Promise.resolve(refuse("APP_OPERATION_REFUSED", "The application Vault socket serves scoped replica reads only; node signing and attestation are internal."));
+  }
+  return handleRequest(options, request);
+}
 var MAX_LINE_BYTES = 64 * 1024;
 function handleRequest(options, request) {
   switch (request?.op) {
@@ -390,7 +397,7 @@ async function respond(options, socket, line) {
     return;
   let response;
   try {
-    response = await handleRequest(options, JSON.parse(line));
+    response = await handleApplicationRequest(options, JSON.parse(line));
   } catch (cause) {
     response = refuse("MALFORMED", cause instanceof Error ? cause.message : "Malformed request.");
   }
@@ -1516,7 +1523,7 @@ ExecStartPre=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStart=${bin} deploy-runner --root=${root} --home=${root}/runner-home
 ExecStartPost=+/usr/bin/chown ${agentUser}:${agentUser} ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStartPost=+/usr/bin/chmod 0600 ${DEPLOYMENT_RUNNER_SOCKET}
-ExecStartPost=+/usr/bin/chown root:root /run/forgezero-deploy
+ExecStartPost=+/usr/bin/chown root:${VAULT_GROUP} /run/forgezero-deploy
 ExecStopPost=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 Restart=always
 RestartSec=2
@@ -2711,7 +2718,7 @@ async function applyMetalIsolation(profile, exec = defaultExec) {
 }
 
 // src/version.ts
-var VERSION = "0.1.17";
+var VERSION = "0.1.19";
 
 // src/index.ts
 function loadOrCreateSeed(path) {
@@ -3215,6 +3222,7 @@ export {
   loadOrCreateSeed,
   loadGuestBinding,
   handleRequest,
+  handleApplicationRequest,
   guestNameFor,
   enrolGuestIdentity,
   createSystemdDeploymentSecrets,

package/dist/fz.js

@@ -217,7 +217,7 @@ ExecStartPre=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStart=${bin} deploy-runner --root=${root} --home=${root}/runner-home
 ExecStartPost=+/usr/bin/chown ${agentUser}:${agentUser} ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStartPost=+/usr/bin/chmod 0600 ${DEPLOYMENT_RUNNER_SOCKET}
-ExecStartPost=+/usr/bin/chown root:root /run/forgezero-deploy
+ExecStartPost=+/usr/bin/chown root:${VAULT_GROUP} /run/forgezero-deploy
 ExecStopPost=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 Restart=always
 RestartSec=2
@@ -774,7 +774,7 @@ async function resolveIdentity(selector, socketPath) {
 }
 
 // src/version.ts
-var VERSION = "0.1.17";
+var VERSION = "0.1.19";
 
 // src/cli/index.ts
 var DEFAULT_MODE = THRESHOLD_MODES[0].id;

package/dist/index.d.ts

@@ -3,7 +3,7 @@ import { type NodeKeyPair } from '@forgezero/runtime/identity';
 import { startAgent, type AgentOptions, type AttestationSource } from './socket';
 import type { SecretCache } from './cache';
 export { VERSION } from './version';
-export { startAgent, handleRequest } from './socket';
+export { startAgent, handleRequest, handleApplicationRequest } from './socket';
 export type { AgentOptions, AttestationSource, Request, Response } from './socket';
 export { createSecretCache, CacheError } from './cache';
 export type { SecretCache, CacheOptions } from './cache';

package/dist/metal-helper-socket.js

@@ -250,7 +250,7 @@ ExecStartPre=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStart=${bin} deploy-runner --root=${root} --home=${root}/runner-home
 ExecStartPost=+/usr/bin/chown ${agentUser}:${agentUser} ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStartPost=+/usr/bin/chmod 0600 ${DEPLOYMENT_RUNNER_SOCKET}
-ExecStartPost=+/usr/bin/chown root:root /run/forgezero-deploy
+ExecStartPost=+/usr/bin/chown root:${VAULT_GROUP} /run/forgezero-deploy
 ExecStopPost=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 Restart=always
 RestartSec=2

package/dist/metal-provision.js

@@ -250,7 +250,7 @@ ExecStartPre=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStart=${bin} deploy-runner --root=${root} --home=${root}/runner-home
 ExecStartPost=+/usr/bin/chown ${agentUser}:${agentUser} ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStartPost=+/usr/bin/chmod 0600 ${DEPLOYMENT_RUNNER_SOCKET}
-ExecStartPost=+/usr/bin/chown root:root /run/forgezero-deploy
+ExecStartPost=+/usr/bin/chown root:${VAULT_GROUP} /run/forgezero-deploy
 ExecStopPost=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 Restart=always
 RestartSec=2

package/dist/provision.js

@@ -110,7 +110,7 @@ ExecStartPre=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStart=${bin} deploy-runner --root=${root} --home=${root}/runner-home
 ExecStartPost=+/usr/bin/chown ${agentUser}:${agentUser} ${DEPLOYMENT_RUNNER_SOCKET}
 ExecStartPost=+/usr/bin/chmod 0600 ${DEPLOYMENT_RUNNER_SOCKET}
-ExecStartPost=+/usr/bin/chown root:root /run/forgezero-deploy
+ExecStartPost=+/usr/bin/chown root:${VAULT_GROUP} /run/forgezero-deploy
 ExecStopPost=+/usr/bin/rm -f ${DEPLOYMENT_RUNNER_SOCKET}
 Restart=always
 RestartSec=2

package/dist/socket.d.ts

@@ -2,7 +2,7 @@ import { type Server } from 'node:net';
 import { signRequest, type NodeKeyPair } from '@forgezero/runtime/identity';
 import type { SecretCache } from './cache';
 /**
- * The signing socket — why the application on managed compute holds nothing.
+ * The application Vault socket — why managed code holds no remote credential.
  *
  * `@forgezero/vault` discovers `/run/forgezero/vault.sock` and prefers it over
  * `FORGEZERO_API_KEY`, so moving an app onto managed compute is DELETING an
@@ -10,20 +10,14 @@ import type { SecretCache } from './cache';
  * for a long time nothing was: the client knew how to prefer the socket and the
  * agent was a version constant.
  *
- * ## The key never leaves
+ * ## The node identity never becomes an application signing oracle
  *
- * There is no `getKey` operation and there is deliberately no way to add one:
- * the socket signs, and signing is all it does. An application that could ask
- * for the key is an application that holds the key the moment it is compromised,
- * which is the entire difference between this and an API key in the environment.
- *
- * ## Why a signature and not a token
- *
- * A token would have to be handed to the caller, which puts it in a process we
- * do not control, in memory we do not own, for as long as the process lives. A
- * signature is bound to one method, one path and one body digest by
- * `canonicalString`, so a caller that captures one cannot reuse it for anything
- * else — and it expires with the clock-skew window rather than with the process.
+ * The Agent hybrid-signs its own outbound HTTPS requests internally. This
+ * socket never exposes `identity`, `sign` or `attest`: otherwise any tenant
+ * process admitted to the Vault group could ask the Agent to sign a deployment,
+ * heartbeat or whole-project replication request and act as the node without
+ * ever extracting its key. Applications receive only the environment they ask
+ * for from the already-bound, memory-only project replica.
  *
  * ## Peer credentials, not a shared secret
  *
@@ -99,6 +93,8 @@ export type Response = {
         message: string;
     };
 };
+/** The real Unix-socket boundary; privileged machine operations stay in-process. */
+export declare function handleApplicationRequest(options: AgentOptions, request: Request): Promise<Response>;
 /**
  * Produces a hardware attestation report for this guest.
  *

package/dist/version.d.ts

@@ -1,2 +1,2 @@
 /** One package version shared by both public binaries. Pinned to package.json by tests. */
-export declare const VERSION = "0.1.17";
+export declare const VERSION = "0.1.19";

package/package.json

@@ -1,7 +1,7 @@
 {
 	"//": "Publishing happens from an operator's machine, not CI \u2014 CLAUDE.md records that the absence of CI is deliberate. npm's `provenance` attests a tarball was built by a recognised CI provider from a named commit, so it cannot be produced here: it was set, and the first publish failed with `Automatic provenance generation not supported for provider: null`. A setting that can never be satisfied is worse than none, because it reads as a guarantee nobody is getting. Restore it the day this publishes from CI, and not before.",
 	"name": "@forgezero/agent",
-	"version": "0.1.17",
+	"version": "0.1.19",
 	"type": "module",
 	"scripts": {
 		"check": "tsc --noEmit",