@homeflare/alchemy 0.10.1 → 0.12.0

package/src/proxmox/node-network-form.ts

@@ -14,14 +14,14 @@
  *
  * * ⛔ THE LAST SEVEN ARE REPORTED AND NEVER COMPARED, AND EACH ONE IS A MEASURED FOREVER-DIFF.
  *   `priority` is assigned by PVE FROM FILE ORDER — `my $priority = 2; ... $d->{priority} =
- *   $priority++` — and it is not a POST or PUT parameter at all. MEASURED ACROSS TB4: vmbr1.11 is
- *   priority 16 on n2 and n3 and 15 on n4, because n4 has no `wlp91s0` above it. One declaration
+ *   $priority++` — and it is not a POST or PUT parameter at all. MEASURED ACROSS C1: vmbr1.42 is
+ *   priority 16 on node-b and node-c and 15 on node-d, because node-d has no `wlan0` above it. One declaration
  *   reused across three nodes would diff on exactly one of them, forever, over nothing.
  *   `method` is RECOMPUTED on every write from whether the form carried an address, `families` is
  *   recomputed the same way and never written to the file, `active` and `exists` describe the
  *   kernel rather than the config, and `bond_miimon`, `bridge_stp` and `bridge_fd` are emitted by
  *   PVE's writer with defaults (100, `off`, 0) while appearing in NEITHER write schema —
- *   `additionalProperties => 0` means sending one is a 400. Live proof of all three: n2's bond0
+ *   `additionalProperties => 0` means sending one is a 400. Live proof of all three: node-b's bond0
  *   returns `bond_miimon "100"` and vmbr1 returns `bridge_stp "off"`, `bridge_fd "0"`, none of
  *   which any declaration can set.
  */
@@ -74,7 +74,7 @@ export const ifaceList = (value: unknown) =>
  *   `ceph transport` comes back as `ceph transport\n` and the two never compare equal.
  * ⚠️ AND THE READER FOLDS `comments6` INTO `comments` (`$d->{comments} .= $comments6`), so on an
  *   interface that carries an IPv6 comment a declared `comments` CANNOT match what comes back.
- *   TB4 has none; on an interface that does, leave `comments` undeclared rather than fighting it.
+ *   C1 has none; on an interface that does, leave `comments` undeclared rather than fighting it.
  */
 export const comment = (value: unknown) => text(value).replace(/\s+$/, '');
 
@@ -111,7 +111,7 @@ const field = (name: string, value: string | undefined): Record<string, string>
  *
  * ⚠️ `netmask` IS A WRITABLE PARAMETER AND IS DELIBERATELY NOT OFFERED. PVE raises
  *   "netmask conflicts with cidr" when both are sent, and the reader rewrites whatever was written
- *   into prefix form — MEASURED: n2's vmbr1.11 reports `"netmask":"24"`, never `255.255.255.0`.
+ *   into prefix form — MEASURED: node-b's vmbr1.42 reports `"netmask":"24"`, never `255.255.255.0`.
  *   A resource accepting both spellings would let a declaration diff against its own value.
  */
 export const body = (props: NodeNetworkProps): Record<string, string> => ({
@@ -144,7 +144,7 @@ export const body = (props: NodeNetworkProps): Record<string, string> => ({
  *   `ifreload -a` I did NOT measure. Clearing cidr explicitly at least produces a clean, honest
  *   manual interface — and `matches` compares `cidr` UNCONDITIONALLY, so the plan says so first.
  *
- * ⛔ ON vmbr1.11 THAT IS THE CEPH TRANSPORT. A declaration of that interface without its `cidr` is
+ * ⛔ ON vmbr1.42 THAT IS THE CEPH TRANSPORT. A declaration of that interface without its `cidr` is
  *   a declaration that it should have no address, applied across three nodes. The plan will read
  *   `1 to update` rather than `noop`; do not wave it through.
  *
@@ -177,7 +177,7 @@ export const readAttributes = (
    *   same call metric-server.ts makes, for a worse reason. `type` is required on the PUT and
    *   the PUT MERGES, so a declaration naming `bridge` for what is really a vlan would write
    *   `type bridge` into the stanza and PVE's writer would then emit bridge-ports and
-   *   bridge-stp lines for vmbr1.11. Reporting absent instead makes reconcile POST a create,
+   *   bridge-stp lines for vmbr1.42. Reporting absent instead makes reconcile POST a create,
    *   which PVE refuses with "interface already exists": loud, and it changes nothing.
    */
   const liveType = text(live['type']);

package/src/proxmox/node-network.ts

@@ -11,23 +11,23 @@
  *   that apply — this one never calls it, exactly as `Proxmox.SdnZone` never calls
  *   `Proxmox.SdnApply`.
  *
- * ⛔ CEPH ON TB4 RIDES TWO NETWORKS AND THIS API ONLY SEES ONE OF THEM. Measured from
+ * ⛔ CEPH ON C1 RIDES TWO NETWORKS AND THIS API ONLY SEES ONE OF THEM. Measured from
  *   `/etc/pve/ceph.conf` on 2026-09-13:
  *
- *     public_network  = 10.20.11.0/24     -> vmbr1.11, which this resource DOES see
- *     cluster_network = 10.100.0.0/24     -> every OSD's cluster_addr: .102 / .103 / .104
+ *     public_network  = 198.51.100.0/24     -> vmbr1.42, which this resource DOES see
+ *     cluster_network = 203.0.113.0/24     -> every OSD's cluster_addr: .102 / .103 / .104
  *
  *   The cluster network — OSD REPLICATION, the traffic that rebuilds a lost replica — lives on
- *   `10.100.0.10X/32` addresses carried by `en05`, `en06` and `dummy_tb4`: the Thunderbolt mesh.
+ *   `203.0.113.10X/32` addresses carried by `tb0`, `tb1` and `dummy_c1`: the Thunderbolt mesh.
  *
  * ⛔ AND THOSE ADDRESSES ARE INVISIBLE HERE, WHICH IS THE TRAP. They are declared in
  *   `/etc/network/interfaces.d/sdn`, and PVE's network API does not parse that directory.
- *   MEASURED: `GET /nodes/n2/network/en05` answers `{"method":"manual","type":"eth",…}` with NO
- *   address, while `ip -br -4 addr` shows `en05  UP  10.100.0.102/32`. So this resource reports
- *   en05 and en06 as address-less manual ports and will plan `noop` over them — implicitly
+ *   MEASURED: `GET /nodes/node-b/network/tb0` answers `{"method":"manual","type":"eth",…}` with NO
+ *   address, while `ip -br -4 addr` shows `tb0  UP  203.0.113.102/32`. So this resource reports
+ *   tb0 and tb1 as address-less manual ports and will plan `noop` over them — implicitly
  *   asserting they carry no address, which is FALSE.
  *
- *   The consequence, stated plainly: declaring en05/en06 from what this API reports and then
+ *   The consequence, stated plainly: declaring tb0/tb1 from what this API reports and then
  *   DESTROYING or applying over them takes out OSD replication on a cluster whose pools are
  *   size 3 / min_size 2. They read as the most boring interfaces on the node and are the two most
  *   dangerous. Leave them undeclared; if they must be managed, manage the file that actually
@@ -55,7 +55,7 @@
  *   interface a node already has would otherwise leave it holding a pending network change.
  *
  * ⚠️ WHAT IS STILL TRUE: when `matches` is false the PUT rewrites the whole stanza, and that can
- *   ADD lines the file did not have — a `vlan-raw-device vmbr1` under `vmbr1.11`, where PVE had
+ *   ADD lines the file did not have — a `vlan-raw-device vmbr1` under `vmbr1.42`, where PVE had
  *   been deriving it from the name. Harmless in content, and it costs nothing until somebody
  *   applies; one more reason the apply is a separate resource.
  *
@@ -79,10 +79,10 @@ import {
 import { type PveRequirements, type WithTarget, pveHandlers } from './resource.ts';
 
 /**
- * PVE's interface types. `unknown` is what a NIC it does not manage reports — n2 and n3 both
- * report `wlp91s0` that way, and n4 has no such interface at all.
+ * PVE's interface types. `unknown` is what a NIC it does not manage reports — node-b and node-c both
+ * report `wlan0` that way, and node-d has no such interface at all.
  *
- * ⚠️ THAT ASYMMETRY IS A TRAP FOR A DECLARATION SHARED ACROSS NODES. On n4 the read answers 404,
+ * ⚠️ THAT ASYMMETRY IS A TRAP FOR A DECLARATION SHARED ACROSS NODES. On node-d the read answers 404,
  *   which this provider cannot tell from "deleted", so reconcile POSTs — writing a stanza for a
  *   card that is not in the machine. Declare per node what each node actually has; a physical
  *   interface is discovered, not decided.
@@ -104,24 +104,24 @@ export type NodeNetworkType =
 export interface NodeNetworkProps extends WithTarget {
   /** Which node's file this stanza lives in. Interfaces are per node, never cluster-wide. */
   node: string;
-  /** `vmbr0`, `bond0`, `vmbr1.11`. 2-20 characters, PVE's `pve-iface` format. */
+  /** `vmbr0`, `bond0`, `vmbr1.42`. 2-20 characters, PVE's `pve-iface` format. */
   iface: string;
   /** ⛔ REQUIRED ON EVERY WRITE, update included, never used to retype — see `readAttributes`. */
   type: NodeNetworkType;
   /**
-   * `10.20.11.12/24`. ⛔ THE ONE FIELD WITH NO UNMANAGED MODE: leaving it out is an instruction
+   * `198.51.100.12/24`. ⛔ THE ONE FIELD WITH NO UNMANAGED MODE: leaving it out is an instruction
    * to make the interface `manual`, not an instruction to leave its address alone. The ⛔ on
    * `updateBody` in node-network-form.ts has the measurement and the consequence.
    */
   cidr?: string;
   /** ⚠️ PVE allows exactly ONE default gateway per node and refuses a second with "Default
-   *  gateway already exists on interface '<other>'". On TB4 it is vmbr0.10's. */
+   *  gateway already exists on interface '<other>'". On C1 it is vmbr0.41's. */
   gateway?: string;
   /**
    * `auto <iface>` in the file. Absent on read means off, which is why `bool`'s fallback is used.
    * ⚠️ UNDECLARED IS UNMANAGED ON AN UPDATE AND OFF ON A CREATE — the same asymmetry storage.ts
    *   has, and it bites harder here: an interface created without `autostart` is one the node
-   *   will not bring up at boot. Every TB4 bridge, bond and vlan carries it.
+   *   will not bring up at boot. Every C1 bridge, bond and vlan carries it.
    */
   autostart?: boolean;
   /** 1280-65520. Unset leaves the file without an `mtu` line and the kernel default in force. */
@@ -145,7 +145,7 @@ export interface NodeNetworkProps extends WithTarget {
   bond_xmit_hash_policy?: string;
   /** active-backup only. Kept hyphenated because that is the wire name. */
   'bond-primary'?: string;
-  /** ⚠️ DERIVED FROM A DOTTED NAME. `vmbr1.11` reports `vlan-id` 11 with no such line in the file;
+  /** ⚠️ DERIVED FROM A DOTTED NAME. `vmbr1.42` reports `vlan-id` 42 with no such line in the file;
    *  declaring it there is harmless but adds a line the file did not have. */
   'vlan-id'?: number;
   'vlan-raw-device'?: string;
@@ -209,7 +209,7 @@ const handlers = pveHandlers<NodeNetworkProps, NodeNetworkAttributes>({
    *   omission is an edit. Comparing it unconditionally is what makes that edit visible in `plan`
    *   instead of at `ifreload` time.
    *
-   * ⚠️ NOTHING IN THE REPORTED-ONLY BLOCK IS HERE, and that is what makes the TB4 declaration
+   * ⚠️ NOTHING IN THE REPORTED-ONLY BLOCK IS HERE, and that is what makes the C1 declaration
    *   plan as `noop` on all three nodes at once — the ⛔ above `NodeNetworkAttributes` lists them
    *   and the measurement behind each.
    */

package/src/proxmox/notification-target.ts

@@ -39,8 +39,9 @@
  *     reconcile  POST + PUT                   Mapping.Modify on /mapping/notifications AND one of
  *                                             Sys.Audit / Sys.Modify / Sys.AccessNetwork on /
  *     delete     DELETE                       Mapping.Modify on /mapping/notifications
- *   `LXCProvisioner` already carries Sys.Audit on `/` (see lxc.ts), so the delta is the two Mapping
- *   privileges — notably NOT the `Sys.Modify` a backup job costs.
+ *   The provision role already carried Sys.Audit on `/` (see lxc.ts), so the delta was the two
+ *   Mapping privileges — notably NOT the `Sys.Modify` a backup job costs. `PROVISION_PRIVILEGES`
+ *   carries both on `/`: the baseline took the trade below knowingly.
  *   ⚠️ PREFER A SECOND ROLE GRANTED AT `/mapping/notifications` OVER WIDENING THE PROVISIONING ROLE
  *     ON `/`. `/mapping` also holds the PCI and USB passthrough maps, so Mapping.Modify at the root
  *     lets a credential scoped to make containers rewire somebody's hardware.

package/src/proxmox/pbs-datastore-guard.ts

@@ -54,7 +54,7 @@ export const guardPath = (live: PbsDatastoreAttributes, props: PbsDatastoreProps
  *
  * ⚠️ AN UNDECLARED `backend` IS NOT A DIVERGENCE. Undeclared is unmanaged everywhere in this
  *   family, and this guard keeps that rule: it fires only when the declaration says something and
- *   PBS says something else. Adopting `r2-offsite` without mentioning `backend` still plans noop.
+ *   PBS says something else. Adopting `offsite` without mentioning `backend` still plans noop.
  *
  * ⚠️ COMPARED AS A CANONICAL PROPERTY STRING, so `bucket=x,type=s3` and `type=s3,bucket=x` are the
  *   same backend and key order cannot deadlock a plan — the reason `samePath` trims a slash.

package/src/proxmox/pbs-datastore.ts

@@ -10,7 +10,7 @@
  *   `{"data":{"pong":true}}` against a Let's Encrypt certificate for CN=pbs.example.com;
  *   `/version` and `/config/datastore` answer 401 "authentication failed";
  *   `pbs.mgmt.example.com:8007` answers 401 and its certificate verifies too; and
- *   `/access/domains` lists the realms `pbs`, `pam` and an openid realm `Schenanigans`. So the
+ *   `/access/domains` lists the realms `pbs`, `pam` and an openid realm. So the
  *   prefix, the `{"data": …}` envelope and the strict-TLS story are PVE's exactly — and only the
  *   credential differs. There is no `pve` realm here; a PVE token cannot authenticate at all.
  *   The header differs too, which is why `pve()` exists rather than `pve()` being reused — see the
@@ -18,18 +18,18 @@
  *
  * ⛔ THERE IS NO OPENBAO MOUNT FOR PBS TODAY, SO NOTHING HERE CAN DEPLOY YET. `PbsTarget.mount` is
  *   a parameter for the reason `PveTarget.mount` is — the provider must be able to leave this
- *   estate — but the estate has nothing to put in it. MEASURED: under the `claude-code` approle,
- *   `bao token capabilities` answers `deny` for `proxmox-tb4/creds/{read,provision}`,
- *   `proxmox-ops/creds/read` and every `…pbs…` path tried, and `sys/mounts` is 403 — so I could
+ *   estate — but the estate has nothing to put in it. MEASURED: under the agent's approle,
+ *   `bao token capabilities` answers `deny` for `proxmox-c1/creds/{read,provision}`,
+ *   `proxmox-c2/creds/read` and every `…pbs…` path tried, and `sys/mounts` is 403 — so I could
  *   not enumerate the mounts to PROVE a PBS one is absent. That it is absent is the brief's
  *   statement, not my measurement.
  *   ★ WHAT THE MOUNT MUST VEND, so `mint()` is reused unchanged: `bao read -format=json
  *     <mount>/creds/<role>` answering `{"data":{"token_id":…,"secret":…}}`, where `token_id` is a
  *     PBS token id `user@realm!tokenname` — `hf-read@pbs!…` and `hf-provision@pbs!…`. Same short,
- *     non-renewable lease contract as `proxmox-tb4`.
+ *     non-renewable lease contract as `proxmox-c1`.
  *   ⚠️ PBS HAS NO DYNAMIC-SECRETS PLUGIN OF ITS OWN — OpenBao's Proxmox support is a PVE thing — so
  *     the mount is a small custom vendor against `POST /access/users/{id}/token/{name}`. Say which
- *     mount and role you needed rather than reaching for the read-only `monitoring@pbs` token on
+ *     mount and role you needed rather than reaching for the read-only `metrics@pbs` token on
  *     the kv shelf: widening that would delete the outer lock for every reader of the shelf.
  *
  * ⛔ A DATASTORE HOLDS THE BACKUPS, SO `retain` IS THE DEFAULT AND `delete` IS FULLY IMPLEMENTED —
@@ -47,7 +47,7 @@
  * ⛔ NO SECRET IS A PROP OR AN ATTRIBUTE, AND THIS FAMILY IS CLEAN BY CONSTRUCTION: a datastore
  *   section holds no password, token or key — encryption keys belong to the backup CLIENT. Every
  *   field below is a name, a path, a schedule, a count or a policy string, all of which are safe in
- *   a state store Alchemy writes UNENCRYPTED and this estate dumps to CT100 nightly.
+ *   a state store Alchemy writes UNENCRYPTED and this estate copies to a backup guest nightly.
  */
 import { Resource } from 'alchemy';
 import { isResolved } from 'alchemy/Diff';
@@ -131,11 +131,11 @@ export interface PbsDatastoreProps {
    *   `datastore create --help` offers `--backend`, `datastore update --help` does NOT, and
    *   `backend` is absent from update's `--delete` enum. PBS will not move a datastore between
    *   local disk and object storage, ever.
-   * ★ IT IS A PROP AT ALL BECAUSE THE ESTATE HAS ONE. `r2-offsite` holds
-   *   `type=s3,client=cloudflare-r2,bucket=homeflare-pbs`. Leaving it undeclared would still plan
+   * ★ IT IS A PROP AT ALL BECAUSE THE ESTATE HAS ONE. `offsite` holds
+   *   `type=s3,client=cloudflare-r2,bucket=example-pbs`. Leaving it undeclared would still plan
    *   noop — undeclared is unmanaged here — but the declaration would then describe a LOCAL
    *   datastore, and anyone recreating from it would get exactly that: an empty directory on the
-   *   mini's disk where the offsite copy used to be, behind a green plan the whole way.
+   *   host's disk where the offsite copy used to be, behind a green plan the whole way.
    * ⚠️ A property string. Compared canonically, so key order is never a diff.
    */
   backend?: string;

package/src/proxmox/pbs-prune-job.ts

@@ -37,10 +37,10 @@
  *   answers 401 "authentication failure", which reads as a bad credential rather than as a
  *   malformed header — the same trap credentials.ts already records for PVE's colon form.
  *   ⛔ AND THERE IS NO MOUNT TO MINT FROM. `mint()` runs `bao read <mount>/creds/<role>`; no
- *     OpenBao mount vends PBS tokens — `proxmox-tb4` and `proxmox-ops` vend PVE ones. The
+ *     OpenBao mount vends PBS tokens — `proxmox-c1` and `proxmox-c2` vend PVE ones. The
  *     `kv/infra/proxmox` shelf holds a READ-ONLY `Audit` token for PBS, and a read-only token
  *     cannot create a prune job. I could not confirm that shelf's contents: this machine's
- *     claude-code approle answers 403 on `sys/mounts` AND on `kv/metadata/infra/proxmox`
+ *     agent approle answers 403 on `sys/mounts` AND on `kv/metadata/infra/proxmox`
  *     (MEASURED). What is needed is a dynamic PBS mount vending a `provision` role with
  *     `Datastore.Modify` — say that, rather than reaching for the stored auditor token.
  *

package/src/proxmox/pbs-sync-job.ts

@@ -12,14 +12,14 @@
  *
  * ⛔ THE CREDENTIAL IS A PBS TOKEN AND IT DOES NOT EXIST YET; NO MOUNT NAME IS INVENTED IN THIS
  *   FILE. PBS wants `user@realm!tokenname` plus a UUID secret, issued by PBS — a PVE token is not
- *   one, whatever it is spelled like. MEASURED from this machine on 2026-09-13: the `claude-code`
+ *   one, whatever it is spelled like. MEASURED from this machine on 2026-09-13: the agent's
  *   approle cannot enumerate mounts (`bao secrets list` -> 403) and
  *   `bao token capabilities kv/infra/proxmox/pbs` -> `deny`, so I could not confirm from here what
  *   does or does not exist. What credentials.ts records is that every PBS token on the kv shelf is
- *   READ-ONLY (`Audit`, as `monitoring@pve`) and STATIC — too narrow to create a sync job, and
+ *   READ-ONLY (`Audit`, as `metrics@pve`) and STATIC — too narrow to create a sync job, and
  *   exactly the kind of credential this provider exists to avoid writing with.
  *   ★ SO THE MOUNT IS A `PbsTarget.mount` THE STACK SUPPLIES, and somebody has to build it first:
- *     a dynamic PBS mount with `read` and `provision` roles mirroring `proxmox-tb4`. Until it
+ *     a dynamic PBS mount with `read` and `provision` roles mirroring `proxmox-c1`. Until it
  *     exists this family can be declared and cannot be deployed. `permission denied` means the
  *     grant is missing — say which mount and role you needed; do not fall back to the shelf token.
  *
@@ -83,7 +83,7 @@ export interface SyncJobProps extends WithPbsTarget {
    *   `Pbs.Remote` family is OUT OF SCOPE for this package rather than merely unwritten:
    *   `POST /config/remote` requires `password`, and Alchemy persists props and attributes to its
    *   state store UNENCRYPTED (StateEncoding.ts tags Redacted values rather than encrypting them),
-   *   which here is the `alchemy` Postgres that pg-backup.sh dumps nightly to CT100. A remote's
+   *   which here is the `alchemy` Postgres that a nightly job dumps to a backup guest. A remote's
    *   password in a prop is that password in four places, for months. The only Remote resource that
    *   could exist would refuse `password` the way storage.ts refuses it — as a `never` — and could
    *   therefore never CREATE a remote, which is a resource that cannot do what its name promises.

package/src/proxmox/pbs-verify-job.ts

@@ -11,7 +11,7 @@
  *
  * ⛔ THIS FILE CANNOT AUTHENTICATE UNTIL TWO THINGS OUTSIDE IT CHANGE, AND IT IS SHIPPED SAYING SO
  *   RATHER THAN SHIPPED LOOKING FINISHED. Both are recorded on `PbsTarget` below:
- *     1. `credentials.ts` has no PBS mint. MEASURED 2026-09-13 from this Mac: the `claude-code`
+ *     1. `credentials.ts` has no PBS mint. MEASURED 2026-09-13 from this Mac: the agent's
  *        approle is refused `sys/mounts`, `kv/infra/proxmox` and `proxmox-pbs/creds/read` alike —
  *        403 permission denied on all three — so there is no mount to name and none is invented.
  *     2. `client.ts`'s `authorization()` builds a PVE header, and PBS will not accept it. See the

package/src/proxmox/pool.test.ts

@@ -17,14 +17,14 @@ const target: PoolProps['target'] = {
 
 const props = (over: Partial<PoolProps> = {}): PoolProps => ({
   target,
-  poolid: 'house',
+  poolid: 'lab',
   ...over,
 });
 
 describe('pool forms match generated POST/PUT parameters', () => {
   it('createForm sends exactly poolid and comment', () => {
     const form: PoolsPostParams = poolCreateForm(props({ comment: 'estate' }));
-    assert.deepEqual(form, { poolid: 'house', comment: 'estate' });
+    assert.deepEqual(form, { poolid: 'lab', comment: 'estate' });
     assert.deepEqual(Object.keys(form).sort(), ['comment', 'poolid']);
   });
 

package/src/proxmox/pool.ts

@@ -8,11 +8,11 @@
  *   its own state would have reported noop straight past a hand-edit in the UI.
  *
  * ⚠️ IT 403'd UNTIL THE ROLE WAS WIDENED, AND THE HISTORY IS WORTH KEEPING. `hf-provision@pve`
- *   held `LXCProvisioner` on `/` with no `Pool.Allocate`, so reconcile answered
- *   "Permission check failed (/pool/house, Pool.Allocate)". The credential could not widen itself
+ *   held the provision role on `/` with no `Pool.Allocate`, so reconcile answered
+ *   "Permission check failed (/pool/lab, Pool.Allocate)". The credential could not widen itself
  *   — `PUT /access/roles` is 403 for it too — so the role was extended over SSH with
- *   `pveum role modify LXCProvisioner --privs "<existing>,Pool.Allocate,Pool.Audit"`, preserving
- *   every existing privilege. Each new resource in this package should state the privileges its
+ *   `pveum role modify <role> --privs "<existing>,Pool.Allocate,Pool.Audit"`, preserving every
+ *   existing privilege. `PROVISION_PRIVILEGES` (provision-baseline.ts) carries both now. Each new resource in this package should state the privileges its
  *   reconcile needs, so widening stays a deliberate act rather than a reaction to a 403.
  */
 import { Resource } from 'alchemy';

package/src/proxmox/provision-baseline.test.ts

@@ -0,0 +1,87 @@
+/**
+ * The baseline itself: the one privilege list, the generic defaults, and the names both halves
+ * refuse before either can paste them into a root shell or a declaration.
+ */
+import { describe, expect, test } from 'bun:test';
+import {
+  PROVISION_DEFAULTS,
+  PROVISION_PRIVILEGES,
+  provisionBaseline,
+} from './provision-baseline.ts';
+
+describe('PROVISION_PRIVILEGES', () => {
+  test('is 27 privileges, sorted, unique and frozen', () => {
+    expect(PROVISION_PRIVILEGES).toHaveLength(27);
+    expect([...PROVISION_PRIVILEGES].sort()).toEqual([...PROVISION_PRIVILEGES]);
+    expect(new Set(PROVISION_PRIVILEGES).size).toBe(27);
+    expect(Object.isFrozen(PROVISION_PRIVILEGES)).toBe(true);
+  });
+
+  test('holds what the lane needs to repair its own baseline (role.ts: no lock-out)', () => {
+    for (const needed of [
+      'Sys.Modify', // the role
+      'Realm.AllocateUser', // the users
+      'User.Modify',
+      'Group.Allocate', // the mint group
+      'Permissions.Modify', // the grants, and reading them at all (acl.ts)
+    ]) {
+      expect(PROVISION_PRIVILEGES).toContain(needed);
+    }
+  });
+});
+
+describe('provisionBaseline', () => {
+  test('defaults: one role, one mint group, two lanes bound on /', () => {
+    const baseline = provisionBaseline();
+    expect(baseline.role).toEqual({ privs: PROVISION_PRIVILEGES, roleid: 'HfProvisioner' });
+    expect(baseline.group).toEqual({ comment: PROVISION_DEFAULTS.comment, groupid: 'hf-mint' });
+    expect(baseline.users.map((u) => [u.lane, u.userid, u.groups])).toEqual([
+      ['provision', 'hf-provision@pve', ['hf-mint']],
+      ['read', 'hf-read@pve', ['hf-mint']],
+    ]);
+    expect(baseline.grants).toEqual([
+      { lane: 'provision', roleid: 'HfProvisioner', userid: 'hf-provision@pve' },
+      { lane: 'read', roleid: 'PVEAuditor', userid: 'hf-read@pve' },
+    ]);
+  });
+
+  test('a site passes its own names; an explicit undefined is the default', () => {
+    const baseline = provisionBaseline({
+      mintGroup: 'mint',
+      provisionUser: 'provisioner@pve',
+      readRole: 'Auditor',
+      readUser: 'auditor@pve',
+      role: undefined,
+    });
+    expect(baseline.role.roleid).toBe('HfProvisioner');
+    expect(baseline.grants.map((g) => `${g.userid} ${g.roleid}`)).toEqual([
+      'provisioner@pve HfProvisioner',
+      'auditor@pve Auditor',
+    ]);
+    expect(baseline.users.every((u) => u.groups.join() === 'mint')).toBe(true);
+  });
+
+  test('readUser null is a baseline with no read lane', () => {
+    const baseline = provisionBaseline({ readUser: null });
+    expect(baseline.users.map((u) => u.lane)).toEqual(['provision']);
+    expect(baseline.grants.map((g) => g.lane)).toEqual(['provision']);
+  });
+
+  test('refuses, all at once, every name that would need quoting or is not PVE-shaped', () => {
+    const attempt = () =>
+      provisionBaseline({
+        comment: "it's",
+        mintGroup: 'a b',
+        provisionUser: 'no-realm',
+        readRole: 'x;rm',
+        readUser: 'q{}@pve',
+        role: '$(id)',
+      });
+    expect(attempt).toThrow(/role `\$\(id\)`.*mintGroup `a b`.*readRole `x;rm`/);
+    expect(attempt).toThrow(/provisionUser `no-realm`.*readUser `q\{\}@pve`.*comment/);
+  });
+
+  test('refuses one user for both lanes', () => {
+    expect(() => provisionBaseline({ readUser: 'hf-provision@pve' })).toThrow(/one user/);
+  });
+});

package/src/proxmox/provision-baseline.ts

@@ -0,0 +1,162 @@
+/**
+ * The provisioning baseline: the access every PVE cluster and node needs before a stack built on
+ * this package can manage it — one role, the users OpenBao mints tokens for, the group that fences
+ * the mint, and the grants that bind them. ONE description, read by both halves:
+ *   · provision-declare.ts turns it into `Proxmox.Role`/`Group`/`User`/`Acl` resources, so a stack
+ *     adopts the baseline and keeps it (drift is a plan, not a 403 weeks later);
+ *   · provision-bootstrap.ts turns it into the one-time root commands for a NEW cluster or node.
+ * The two cannot drift apart because neither holds a name or a privilege of its own.
+ *
+ * ⛔ THE PROVISION LANE CANNOT CREATE ITSELF. Every write here runs as a token OpenBao mints for the
+ *   provision user, and minting needs that user to exist, in the mint group, bound to this role.
+ *   So a new cluster is bootstrapped ONCE by root@pam with the generated commands, and the stack
+ *   then adopts what they made (docs/provision-baseline.md).
+ *
+ * ★ ONE PRIVILEGE LIST FOR EVERY FAMILY, NOT A ROLE PER RESOURCE. The list is what the families'
+ *   reconciles need, unioned — the set a hand-kept provision role reached one 403 at a time, each
+ *   step recorded where it was hit (pool.ts, sdn-vnet.ts, ha-rule.ts). It includes what the lane needs
+ *   to manage THIS baseline (`Sys.Modify` for the role, `Realm.AllocateUser`/`User.Modify` for the
+ *   users, `Group.Allocate`, `Permissions.Modify` for the grants), so declaring it can never narrow
+ *   the lane out of its own repair (role.ts: "A ROLE CAN LOCK ITS OWN PROVIDER OUT").
+ * ⚠️ NOT EVERY FAMILY: root@pam-only writes (device passthrough, bind mounts — lxc-judge.ts) and
+ *   privileges a family names as still missing (`VM.Replicate`, replication-job.ts) are outside it.
+ */
+
+/** The provision role's privileges, sorted — the exact set, never an addition to a live one. */
+export const PROVISION_PRIVILEGES: readonly string[] = Object.freeze([
+  'Datastore.Allocate',
+  'Datastore.AllocateSpace',
+  'Datastore.Audit',
+  'Group.Allocate',
+  'Mapping.Audit',
+  'Mapping.Modify',
+  'Permissions.Modify',
+  'Pool.Allocate',
+  'Pool.Audit',
+  'Realm.AllocateUser',
+  'SDN.Allocate',
+  'SDN.Audit',
+  'SDN.Use',
+  'Sys.Audit',
+  'Sys.Console',
+  'Sys.Modify',
+  'User.Modify',
+  'VM.Allocate',
+  'VM.Audit',
+  'VM.Backup',
+  'VM.Config.CPU',
+  'VM.Config.Disk',
+  'VM.Config.HWType',
+  'VM.Config.Memory',
+  'VM.Config.Network',
+  'VM.Config.Options',
+  'VM.PowerMgmt',
+]);
+
+/** The names a baseline uses. Every field has a generic default (`PROVISION_DEFAULTS`). */
+export interface ProvisionNames {
+  /** The role holding `PROVISION_PRIVILEGES` on `/`. */
+  readonly role?: string | undefined;
+  /** The user OpenBao's `provision` role mints tokens for, realm-qualified. */
+  readonly provisionUser?: string | undefined;
+  /** The group whose members OpenBao may mint for — the fence around the mint. */
+  readonly mintGroup?: string | undefined;
+  /** The user OpenBao's `read` role mints for, or `null` for a baseline with no read lane. */
+  readonly readUser?: string | null | undefined;
+  /** The role the read user holds on `/`. ⛔ It must already exist: a built-in, or one you declare. */
+  readonly readRole?: string | undefined;
+  /** The comment on the group and both users — how a person on the node learns what they are. */
+  readonly comment?: string | undefined;
+}
+
+/** Every name, resolved: what `PROVISION_DEFAULTS` holds and what a baseline is built from. */
+export type ResolvedProvisionNames = {
+  readonly [K in keyof ProvisionNames]-?: Exclude<ProvisionNames[K], undefined>;
+};
+
+/** ★ Generic, kit-prefixed names: nothing here is any one estate's. */
+export const PROVISION_DEFAULTS: ResolvedProvisionNames = Object.freeze({
+  comment:
+    'provision baseline from @homeflare/alchemy - OpenBao mints short-lived tokens for members',
+  mintGroup: 'hf-mint',
+  provisionUser: 'hf-provision@pve',
+  readRole: 'PVEAuditor',
+  readUser: 'hf-read@pve',
+  role: 'HfProvisioner',
+});
+
+/** Which credential lane a user or a grant belongs to — the OpenBao role that mints for it. */
+export type ProvisionLane = 'provision' | 'read';
+
+/** A baseline, resolved: exactly what the declaration holds and the bootstrap makes. */
+export interface ProvisionBaseline {
+  readonly role: { readonly roleid: string; readonly privs: readonly string[] };
+  readonly group: { readonly groupid: string; readonly comment: string };
+  readonly users: readonly {
+    readonly lane: ProvisionLane;
+    readonly userid: string;
+    readonly comment: string;
+    readonly groups: readonly string[];
+  }[];
+  /** Each binds one user to one role on `/`, with propagate — the only shape the lanes need. */
+  readonly grants: readonly {
+    readonly lane: ProvisionLane;
+    readonly userid: string;
+    readonly roleid: string;
+  }[];
+}
+
+/**
+ * ⛔ NAMES ARE CHECKED HERE, ONCE, FOR BOTH HALVES — and conservatively. The bootstrap pastes them
+ *   into a root shell, so a name that would need quoting is refused rather than quoted: PVE's own
+ *   ids (`pve-roleid`, `pve-groupid`, `pve-userid`) are narrower than what a shell tolerates.
+ */
+const ID = /^[A-Za-z0-9][A-Za-z0-9._-]*$/;
+const USERID = /^[A-Za-z0-9][A-Za-z0-9._-]*@[A-Za-z][A-Za-z0-9._-]*$/;
+const COMMENT = /^[A-Za-z0-9 ._,()@/+-]*$/;
+
+const problems = (names: ResolvedProvisionNames): string[] => {
+  const found: string[] = [];
+  if (!ID.test(names.role)) found.push(`role \`${names.role}\` is not a PVE role id`);
+  if (!ID.test(names.mintGroup)) found.push(`mintGroup \`${names.mintGroup}\` is not a group id`);
+  if (!ID.test(names.readRole)) found.push(`readRole \`${names.readRole}\` is not a PVE role id`);
+  for (const [field, userid] of [
+    ['provisionUser', names.provisionUser],
+    ['readUser', names.readUser],
+  ] as const) {
+    if (userid !== null && !USERID.test(userid)) {
+      found.push(`${field} \`${userid}\` is not a realm-qualified user id (name@realm)`);
+    }
+  }
+  if (names.readUser === names.provisionUser) found.push('readUser and provisionUser are one user');
+  if (!COMMENT.test(names.comment))
+    found.push('comment holds a character the bootstrap will not quote');
+  return found;
+};
+
+/** Resolve `names` over the defaults and check them. Throws with every problem at once. */
+export const provisionBaseline = (names: ProvisionNames = {}): ProvisionBaseline => {
+  // ⚠️ An explicit `undefined` means "the default", not "blank": spread alone would keep it.
+  const given = Object.entries(names).filter(([, value]) => value !== undefined);
+  const resolved: ResolvedProvisionNames = {
+    ...PROVISION_DEFAULTS,
+    ...Object.fromEntries(given),
+  };
+  const found = problems(resolved);
+  if (found.length > 0) throw new Error(`provision baseline: ${found.join('; ')}`);
+  const lanes: [ProvisionLane, string, string][] = [
+    ['provision', resolved.provisionUser, resolved.role],
+  ];
+  if (resolved.readUser !== null) lanes.push(['read', resolved.readUser, resolved.readRole]);
+  return {
+    grants: lanes.map(([lane, userid, roleid]) => ({ lane, roleid, userid })),
+    group: { comment: resolved.comment, groupid: resolved.mintGroup },
+    role: { privs: PROVISION_PRIVILEGES, roleid: resolved.role },
+    users: lanes.map(([lane, userid]) => ({
+      comment: resolved.comment,
+      groups: [resolved.mintGroup],
+      lane,
+      userid,
+    })),
+  };
+};