@homeflare/alchemy 0.32.0 → 0.34.0

package/dist/proxmox/zfs-pool-form.d.ts

@@ -0,0 +1,124 @@
+/**
+ * The create lane for `Proxmox.ZfsPool`: the form PVE wants, and the wait for the worker it forks.
+ * Split out of zfs-pool.ts (2026-09-24, the distilled migration) — same seam as before, now naming
+ * the write side the way storage.ts/storage-form.ts does.
+ *
+ * ⚠️ `createPool` TAKES THE READ AS A PARAMETER, GENERIC IN ITS ERROR AND REQUIREMENT CHANNELS,
+ *   rather than importing the read module and coupling to its exact effect shape here. This file
+ *   answers "how does a declaration become a pool on disks"; zfs-pool-wire.ts answers "what is a
+ *   zpool, and when has it changed" — the caller (zfs-pool.ts) is what ties the two together, so
+ *   this file cannot accidentally read the cluster differently from `diff`.
+ */
+import * as Effect from 'effect/Effect';
+import * as nodes from '@distilled.cloud/proxmox/nodes';
+import type { ZfsPoolAttributes, ZfsPoolProps } from './zfs-pool.ts';
+import type { NodesNodeDisksZfsPostParams } from './generated/pve.ts';
+export declare const ZFS_POOL_CREATE = "pve:POST /nodes/{node}/disks/zfs";
+/**
+ * PVE's layouts, generated (2026-09-23) from `NodesNodeDisksZfsPostParams['raidlevel']`
+ * (`generated/pve.ts`, manifest `pve-apidoc` pve-manager 9.2.11 sha256 9def8f13…) rather than
+ * hand-typed, per decision 9. ⚠️ Each has a minimum disk count PVE enforces, and `raid10` needs an
+ * even one. ⛔ THERE IS NO `stripe` IN THIS ENUM. n1's `speed` pool is one (decision 14 accepts it
+ * as-is): `ZfsPoolProps` (zfs-pool.ts) is why a stripe pool is declarable at all — as an
+ * ADOPT-ONLY declaration with no `raidlevel`, never as a full one.
+ */
+export type ZfsRaidLevel = NonNullable<NodesNodeDisksZfsPostParams['raidlevel']>;
+/** Generated the same way, from `NodesNodeDisksZfsPostParams['compression']`. */
+export type ZfsCompression = NonNullable<NodesNodeDisksZfsPostParams['compression']>;
+/**
+ * ★ CHECKED AGAINST THE VENDOR TABLE ONLY FOR A FULL DECLARATION — decision 9's adopt-only mode.
+ *   `guardCreate` (distilled-guard.ts's `guardWrite`) runs on the FIRST plan of ANY declaration and
+ *   checks the create form's REQUIRED fields whenever this resolves to the real endpoint key — and
+ *   PVE marks both `devices` and `raidlevel` required (codegen/constraints's `pve-nodes-disks`
+ *   row). An adopt-only declaration deliberately omits both, so checking it would refuse a MATCHING
+ *   adoption at plan time, before `read` ever ran. Returning `undefined` (no key) makes the guard a
+ *   no-op for an adopt-only declaration, while a FULL one (`devices` and `raidlevel` both present)
+ *   is checked exactly as before — zfs-pool.ts's `diff` passes this as the `guardWrite` endpoint.
+ * ⚠️ THE RUNTIME BACKSTOP IS `createPool` BELOW, NOT THIS FUNCTION. Skipping the plan-time guard
+ *   for an adopt-only declaration does not skip the check that the pool is actually there —
+ *   `createPool` refuses before any POST when the read comes back absent and either field is
+ *   undefined, which is what a genuinely absent adopt-only declaration hits at apply time.
+ */
+export declare const zfsPoolCreateEndpoint: (props: ZfsPoolProps) => "pve:POST /nodes/{node}/disks/zfs" | undefined;
+/**
+ * The wire form, PVE's own field names — what `guardWrite` (zfs-pool.ts) checks.
+ *
+ * ⚠️ `devices` IS JOINED IN DECLARED ORDER AND NOT PUT THROUGH `csv()` FROM values.ts. `csv` sorts,
+ *   and PVE walks this list two at a time to pair `raid10` mirrors — MEASURED in the node's own
+ *   `PVE::API2::Disks::ZFS` — so sorting it builds a different pool from the one declared. The list
+ *   is never compared against anything, so it needs no normalisation, only faithful order.
+ * ⚠️ AN OMITTED OPTIONAL IS NOT SENT. PVE's own defaults (ashift 12, compression on) are then
+ *   applied by the node. Sending a guessed default would be indistinguishable here — the values
+ *   are unreadable afterwards either way — but it would put a number in the request that no
+ *   declaration asked for, and this is the one call that writes to physical disks.
+ * ⚠️ `node` IS NOT IN THE FORM: it is the `nodes/{node}` path label, and a second copy could only
+ *   disagree with it.
+ * ⚠️ EVERY KEY IS OMITTED WHEN ABSENT, `devices` AND `raidlevel` INCLUDED — not just the optional
+ *   ones. An adopt-only declaration (both undefined, decision 9) must produce a form `createPool`'s
+ *   own guard can inspect for their absence, and one this function itself does not throw building.
+ */
+export declare const createForm: (props: ZfsPoolProps) => Record<string, string>;
+/**
+ * Create the pool if it is absent, and otherwise leave it completely alone.
+ *
+ * ⛔ THE POST ONLY FORKS A WORKER. MEASURED in `/usr/share/perl5/PVE/API2/Disks/ZFS.pm` on node-b:
+ *   the create handler ends in `$rpcenv->fork_worker('zfscreate', ...)` and its HTTP answer is a
+ *   UPID returned the instant the worker is forked — before `zpool create` has run, let alone
+ *   finished. A read-back taken immediately would report a successful create as the failure "the
+ *   write returned no error but the object is still absent". THAT is why this function polls.
+ *
+ * ⚠️ THERE IS NO UPDATE BRANCH BECAUSE PVE HAS NO PUT HERE. An existing pool is returned exactly as
+ *   read, unwritten: the only write this resource ever makes is the create of a pool that is not
+ *   there. Do not add a "repair" write; there is no field it could set.
+ *
+ * ⛔ AND IF THE READ IS WRONG, THE POST IS STILL SAFE — measured, not hoped for. `readPool` folds a
+ *   403 or an unreachable node into "absent", so a too-narrow lease would send this down the create
+ *   path over a live pool. PVE's handler calls `get_pool_data()` before it forks anything and dies
+ *   with "pool '<name>' already exists on node '<node>'", and `assert_disk_unused` refuses every
+ *   device that pool is holding. A create aimed at a pool that is really there fails loudly rather
+ *   than wiping it.
+ *
+ * ⚠️ SHORT POLLS WITH A HARD CAP, NOT ONE LONG WAIT, NOT `@distilled.cloud/proxmox`'s `awaitTask`.
+ *   `readPool` cannot tell "not yet" from "forbidden" — both fold to `undefined` — so the loop
+ *   gives up with the UPID rather than retrying forever, and the UPID is the only thing that leads
+ *   to the worker's real error. Distilled's own task-status poller exists (`Task.ts`) and would
+ *   remove this ambiguity, but swapping to it changes this resource's OBSERVABLE behaviour (what a
+ *   caller sees on a slow create) beyond a transport swap — left as a follow-up, not folded into a
+ *   migration PR silently.
+ *
+ * ⛔ THE SAME AMBIGUITY MAKES A RE-RUN AFTER THE GIVE-UP DIE GENUINELY UNSAFE, NOT MERELY SLOW TO
+ *   CONFIRM — FOUND BY ADVERSARIAL REVIEW, 2026-09-24, of THIS migration, though the shape is
+ *   unchanged from before it (`git blame` shows the same settle-poll pre-dates this PR). "If the
+ *   read is wrong, the POST is still safe" above is true for the FIRST call into this function —
+ *   PVE's own `get_pool_data()` refuses a create over a pool it can already see. It is NOT true
+ *   for a SECOND deploy attempt started while the FIRST worker is still mid-`zpool create`: that
+ *   worker has not yet made the pool visible to a read, so `existing = yield* read(props)` at the
+ *   top of THIS call can also fold to `undefined` — not because the pool is gone, but because the
+ *   first attempt has not finished — and this function would POST a SECOND `zpool create` at the
+ *   SAME devices while the first is still writing them. There is no lock or marker anywhere in
+ *   this package that would stop it. The give-up message below says so explicitly and names the
+ *   task log to check FIRST; that message, and an operator reading it, are the only safeguard.
+ *
+ * ⛔ THE ADOPT-ONLY GUARD, RIGHT AFTER THE READ AND BEFORE ANYTHING ELSE. Decision 9 (2026-09-23):
+ *   omitting `devices` and `raidlevel` declares a pool this resource may only ADOPT, for a pool
+ *   PVE's own schema cannot fully describe — n1's `speed` is a stripe, and `raidlevel`'s enum has
+ *   no stripe (zfs-pool.ts). `zfsPoolCreateEndpoint` above already keeps the vendor constraint
+ *   guard from refusing such a declaration at PLAN time; this is the matching refusal at APPLY
+ *   time, for the one case that guard cannot see — the pool genuinely is not there.
+ */
+export declare const createPool: <E, R>(props: ZfsPoolProps, read: (props: ZfsPoolProps) => Effect.Effect<ZfsPoolAttributes | undefined, E, R>) => Effect.Effect<ZfsPoolAttributes, E | Error | import("effect/unstable/http/HttpClientError").HttpClientError | import("./credential-errors.ts").PveCredentialDenied, R | import("effect/unstable/http/HttpClient").HttpClient>;
+/**
+ * ⛔ `DELETE /nodes/{node}/disks/zfs/{name}` RUNS `zpool destroy` AND THE DATASETS GO WITH IT. Per
+ *   S14 (alchemy-provider-standard), it is implemented rather than stubbed — a `delete` that
+ *   silently does nothing lies to whoever reads the plan — and what keeps an ordinary removed
+ *   declaration from reaching it is the resource's `defaultRemovalPolicy: 'retain'` (zfs-pool.ts):
+ *   an orphaned pool is forgotten, not destroyed, unless a caller opts in with
+ *   `.pipe(RemovalPolicy.destroy())`. See the corrected header in zfs-pool.ts.
+ *
+ * ⚠️ `cleanup-config`/`cleanup-disks` ARE NOT SENT. The first would additionally remove the PVE
+ *   storage entry pointing at this pool, which is a different object with its own resource
+ *   (`Proxmox.Storage`); one resource reaching over to delete another's is how a stack ends up with
+ *   state describing something that is gone. Neither is offered as a prop, for the same reason.
+ */
+export declare const destroyPool: (props: ZfsPoolProps) => Effect.Effect<string, Error | import("./distilled-pve.ts").PveClusterExhausted | import("./credential-errors.ts").PveCredentialDenied | import("effect/Cause").TimeoutError | nodes.ProxmoxOpError, import("effect/unstable/http/HttpClient").HttpClient>;
+//# sourceMappingURL=zfs-pool-form.d.ts.map

package/dist/proxmox/zfs-pool-form.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"zfs-pool-form.d.ts","sourceRoot":"","sources":["../../src/proxmox/zfs-pool-form.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AACH,OAAO,KAAK,MAAM,MAAM,eAAe,CAAC;AACxC,OAAO,KAAK,KAAK,MAAM,gCAAgC,CAAC;AAKxD,OAAO,KAAK,EAAE,iBAAiB,EAAE,YAAY,EAAE,MAAM,eAAe,CAAC;AACrE,OAAO,KAAK,EAAE,2BAA2B,EAAE,MAAM,oBAAoB,CAAC;AAEtE,eAAO,MAAM,eAAe,qCAAqC,CAAC;AAElE;;;;;;;GAOG;AACH,MAAM,MAAM,YAAY,GAAG,WAAW,CAAC,2BAA2B,CAAC,WAAW,CAAC,CAAC,CAAC;AAEjF,iFAAiF;AACjF,MAAM,MAAM,cAAc,GAAG,WAAW,CAAC,2BAA2B,CAAC,aAAa,CAAC,CAAC,CAAC;AAErF;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,qBAAqB,UAAW,YAAY,mDACmC,CAAC;AAE7F;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,UAAU,UAAW,YAAY,KAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAOpE,CAAC;AA0BH;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+CG;AACH,eAAO,MAAM,UAAU,GAAI,CAAC,EAAE,CAAC,SACtB,YAAY,QACb,CAAC,KAAK,EAAE,YAAY,KAAK,MAAM,CAAC,MAAM,CAAC,iBAAiB,GAAG,SAAS,EAAE,CAAC,EAAE,CAAC,CAAC,kOA8D/E,CAAC;AAEL;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,WAAW,UAAW,YAAY,8PAM5C,CAAC"}

package/dist/proxmox/zfs-pool-wire.d.ts

@@ -0,0 +1,78 @@
+import * as Effect from 'effect/Effect';
+import type { ZfsPoolProps } from './zfs-pool.ts';
+import { UNREADABLE, type Unreadable } from './unreadable-read.ts';
+/**
+ * ⚠️ EVERYTHING HERE IS REPORTED, NOTHING HERE IS COMPARED — see the ⛔ on `matches` below. These
+ *   exist so a plan and the state store can say what the pool actually is, on a family where the
+ *   declaration and the live object share no comparable field at all.
+ */
+export interface ZfsPoolAttributes {
+    /** ★ The value a `Proxmox.Storage` should read to order itself after this pool. */
+    name: string;
+    node: string;
+    /** `ONLINE` | `DEGRADED` | `FAULTED` | … Health, not configuration. */
+    state: string;
+    /** ZFS's own error summary, e.g. `No known data errors`. */
+    errors: string;
+    /**
+     * The leaf devices ZFS reports, in vdev order, comma-joined.
+     *
+     * ⚠️ THIS IS WHAT ZFS RESOLVED, NOT WHAT WAS DECLARED, and the two normally differ: PVE rewrites
+     *   a `/dev/sdb` into a by-id link before creating, and ZFS reports partition paths (`…-part3`)
+     *   for a pool built on partitions — MEASURED, that is exactly what node-b's `rpool` reports.
+     *   Never compare it with `props.devices`.
+     */
+    devices: string;
+}
+/**
+ * The device paths at the bottom of PVE's vdev tree, in the order ZFS reports them.
+ *
+ * ⚠️ "NO CHILDREN" IS THE LEAF TEST, AND IT IS NOT A GUESS — MEASURED in the node's `preparetree`,
+ *   which sets `leaf` to 0 when there are children and 1 otherwise. Reading the flag would work
+ *   equally well; recursing on `children` needs no second field to be present and is what makes
+ *   nested sections (mirrors inside a raid10, `spares`, `cache`) flatten correctly.
+ */
+export declare const leafDevices: (children: unknown) => string[];
+/**
+ * ★ Default `read` role — `Sys.Audit` on `/` is all this GET checks (zfs-pool.ts's header).
+ * ⛔ `{ node: props.node, name: props.name }`, NEVER THE WHOLE `props` — storage.ts's/user.ts's own
+ *   ⛔, the kit 0.31.1 regression: `GetNodeDiskZfsRequest`'s schema declares only `node` and `name`
+ *   (both path labels); any OTHER key on the object passed to `nodes.getNodeDiskZfs` is treated by
+ *   distilled's `buildRequest` as an "unknown key" and JSON-encoded onto this bodyless GET, which a
+ *   stricter fetch client refuses outright.
+ * ⛔ A MISSING POOL IS A 500, NOT A 404 — MEASURED against the live cluster (TB4 n2, 2026-09-24,
+ *   read-role, read-only probe): `GET /nodes/n2/disks/zfs/hf-measure-nonexistent-pool` answers
+ *   `{"message":"command '/sbin/zpool status -P hf-measure-nonexistent-pool' failed: exit code
+ *   1\n","data":null}` at HTTP 500 — PVE shells out to `zpool status` and reports its exit code
+ *   as a generic command failure, not a typed "not found". The same shape as user.ts's/group.ts's/
+ *   storage.ts's own measured 500s. `readPool` below (used by `createPool`'s settle-poll and by
+ *   `reconcile`/`read`) still folds it, exactly as `readUser`/`readGroup`/`readStorage` do — the
+ *   whole reason `createPool` can tell "not built yet" from "forbidden" only by giving up after
+ *   `SETTLE_ATTEMPTS` (zfs-pool-form.ts's own ⚠️ on that); `readPoolOrFail` (used by `diff`) does
+ *   not fold it, so a genuine transient failure there propagates and fails the plan loudly instead.
+ */
+export declare const readPoolOrFail: (props: ZfsPoolProps) => Effect.Effect<typeof UNREADABLE | ZfsPoolAttributes | undefined, import("@distilled.cloud/caddy").BadGateway | import("@distilled.cloud/caddy").BadRequest | import("@distilled.cloud/caddy").ConfigError | Error | import("@distilled.cloud/caddy").GatewayTimeout | import("effect/unstable/http/HttpClientError").HttpClientError | import("@distilled.cloud/caddy").InternalServerError | import("@distilled.cloud/proxmox/Errors").ParameterVerificationFailed | import("@distilled.cloud/proxmox/Errors").ProxmoxParseError | import("./distilled-pve.ts").PveClusterExhausted | import("@distilled.cloud/caddy").ServiceUnavailable | import("effect/Cause").TimeoutError | import("@distilled.cloud/caddy").TooManyRequests | import("@distilled.cloud/caddy").Unauthorized | import("@distilled.cloud/proxmox/Errors").UnknownProxmoxError, import("effect/unstable/http/HttpClient").HttpClient>;
+/**
+ * ⛔ FOLDS A GENUINE READ FAILURE TO `undefined` TOO, AND ONLY `createPool`'s settle-poll AND
+ *   `read`/`reconcile` MAY USE IT — user.ts's `readUser` has the full reasoning. Safe here because
+ *   a wrongful fold during create costs at most a redundant `createNodeDiskZfs` POST, which PVE
+ *   refuses loudly ("pool already exists") rather than silently corrupting anything — zfs-pool.ts's
+ *   own header, measured.
+ * ⛔ `zfs-pool.ts`'s `diff` does **NOT** use this — the same bug class as the credential denial fix:
+ *   folding a TRANSIENT failure into "absent" at PLAN TIME would force a false `update` with
+ *   nothing compared. `diff` calls `readPoolOrFail` directly, so a genuine failure there propagates
+ *   and fails the whole plan loudly instead.
+ */
+export declare const readPool: (props: ZfsPoolProps) => Effect.Effect<typeof UNREADABLE | ZfsPoolAttributes | undefined, never, import("effect/unstable/http/HttpClient").HttpClient>;
+/** `read`/`reconcile`/`createPool` return `Attributes | undefined`; only `diff` sees `UNREADABLE`. */
+export declare const dropUnreadable: (live: ZfsPoolAttributes | Unreadable | undefined) => ZfsPoolAttributes | undefined;
+/**
+ * ⛔ THERE IS NO `matches` FUNCTION HERE — UNLIKE EVERY OTHER MIGRATED FAMILY, AND DELIBERATELY.
+ *   Every create parameter on this family is write-only (this file's own `attributesOf`), so
+ *   there is nothing a declaration and a live pool can ever be compared on — a `matches` that
+ *   invented one would plan a replace (`zpool destroy`, since this family has no PUT) over a
+ *   difference it could never verify. `zfs-pool.ts`'s `diff` returns `noop` unconditionally once a
+ *   pool is found, rather than calling a function that would only ever return `true` — found by
+ *   adversarial review that an earlier draft exported one here anyway, unused by anything.
+ */
+//# sourceMappingURL=zfs-pool-wire.d.ts.map

package/dist/proxmox/zfs-pool-wire.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"zfs-pool-wire.d.ts","sourceRoot":"","sources":["../../src/proxmox/zfs-pool-wire.ts"],"names":[],"mappings":"AAMA,OAAO,KAAK,MAAM,MAAM,eAAe,CAAC;AAExC,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,eAAe,CAAC;AAClD,OAAO,EAAE,UAAU,EAAE,KAAK,UAAU,EAAoB,MAAM,sBAAsB,CAAC;AAGrF;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAChC,mFAAmF;IACnF,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,uEAAuE;IACvE,KAAK,EAAE,MAAM,CAAC;IACd,4DAA4D;IAC5D,MAAM,EAAE,MAAM,CAAC;IACf;;;;;;;OAOG;IACH,OAAO,EAAE,MAAM,CAAC;CACjB;AAED;;;;;;;GAOG;AACH,eAAO,MAAM,WAAW,aAAc,OAAO,KAAG,MAAM,EAO9C,CAAC;AAmBT;;;;;;;;;;;;;;;;;GAiBG;AACH,eAAO,MAAM,cAAc,UAAW,YAAY,+2BAe/C,CAAC;AAEJ;;;;;;;;;;GAUG;AACH,eAAO,MAAM,QAAQ,UAAW,YAAY,kIACuB,CAAC;AAEpE,sGAAsG;AACtG,eAAO,MAAM,cAAc,SAAU,iBAAiB,GAAG,UAAU,GAAG,SAAS,kCACvC,CAAC;AAEzC;;;;;;;;GAQG"}

package/dist/proxmox/zfs-pool.d.ts

@@ -26,14 +26,14 @@
  * ⛔ THERE IS NO PUT ON THIS FAMILY AT ALL. MEASURED from the cluster's own published schema
  *   (`/usr/share/pve-docs/api-viewer/apidoc.js`, read on node-b 2026-09-13): `/nodes/{node}/disks/zfs`
  *   has GET and POST, `/nodes/{node}/disks/zfs/{name}` has GET and DELETE, and that is the whole
- *   surface. So `updateForm` is omitted — which, per `resource.ts`, makes any `matches` = false a
- *   REPLACE. A replace is a delete followed by a create, and on this family the delete is the
- *   thing above. Read the ⛔ on `matches` before adding anything to it.
+ *   surface — CONFIRMED again in `@distilled.cloud/proxmox`'s generated `nodes.ts`, which declares
+ *   no `putNodeDiskZfs` at all. So `matches` (zfs-pool-wire.ts) always answers `true`: there is
+ *   nothing to plan a replace over, and the family's one write is the create below.
  *
  * ⛔ NOT ONE CREATE PARAMETER COMES BACK ON READ, SO `matches` COMPARES NOTHING. MEASURED against
- *   the live cluster: `GET /nodes/node-b/disks/zfs/rpool` answers exactly
- *   `{action, children, errors, leaf, name, scan, state, status}` — no `ashift`, no `compression`,
- *   no `raidlevel`, no `devices`, no `add_storage`. Every create parameter is write-only. There is
+ *   the live cluster: `GET /nodes/n2/disks/zfs/rpool` answers exactly
+ *   `{action?, children, errors, name, scan?, state, status?}` — no `ashift`, no `compression`, no
+ *   `raidlevel`, no `devices`, no `add_storage`. Every create parameter is write-only. There is
  *   therefore no field a declaration and a live pool can both be asked about, and a `matches` that
  *   invented one would plan a replace — i.e. a `zpool destroy` — over a difference it could never
  *   verify in the first place.
@@ -46,11 +46,20 @@
  *   is compared, and the three churning strings are kept out of the state store entirely rather
  *   than rewriting this resource's row every time somebody writes a file.
  *
- * ⚠️ TWO HANDLERS ARE OVERRIDDEN AND THE OTHER THREE COME FROM THE FACTORY — see the ★ above
- *   `handlers`. `delete` is the ⛔ above. `reconcile` is because the create is a FORKED WORKER, so
- *   the factory's immediate read-back would report a successful create as a failure; the measured
- *   detail, and the adopt-only refusal decision 9 adds, are both in `createPool` in
- *   zfs-pool-write.ts.
+ * ⛔ A MISSING POOL IS A 500, NOT A 404 — MEASURED against the live cluster (TB4 n2, 2026-09-24,
+ *   read-role, read-only probe): `GET /nodes/n2/disks/zfs/hf-measure-nonexistent-pool` answers a
+ *   generic shelled-out command failure at HTTP 500, the same shape as every other family this
+ *   package has migrated. `zfs-pool-wire.ts` carries the same dual-path read PR 239/243
+ *   established: `readPoolOrFail` (non-folding, used by `diff`) and `readPool` (folding, used by
+ *   `createPool`'s settle-poll and by `read`/`reconcile`).
+ *
+ * ★ MIGRATED OFF `client.ts`'s generic `pve()`/`pveOperations` ONTO `@distilled.cloud/proxmox`'s
+ *   typed `nodes.getNodeDiskZfs`/`createNodeDiskZfs`/`deleteNodeDiskZfs` (2026-09-24, decision
+ *   43's proxmox walk-down, nodes/storage sub-area). `distilled-pve.ts`'s `runPve` replaces
+ *   `pve()`; the cries-wolf fix is wired the same way as every other migrated family. `reconcile`
+ *   and `delete` are still hand-written (never the factory) for the SAME two reasons as before the
+ *   migration — the forked-worker settle-poll, and a DELETE that destroys data — now calling
+ *   `zfs-pool-form.ts`'s `createPool`/`destroyPool` directly instead of through `pveHandlers`.
  *
  * ⚠️ PRIVILEGES, FROM THE SCHEMA. Read and diff need `Sys.Audit` on `/` — both GETs check it.
  *   Reconcile needs `Sys.Modify` on `/` for the POST. `Datastore.Allocate` on `/storage` is NOT
@@ -60,26 +69,15 @@
  *   family checks it, not only the POST. MEASURED the same day as the rest of this paragraph:
  *   `ceph-osd.ts`'s own privilege comparison names `disks/zfs` as one of the sibling families
  *   whose write verbs DO carry a `Sys.Modify` check, unlike `ceph/osd`'s create and delete, which
- *   carry no permissions block at all and 403 for any identity but `root@pam`. This line
- *   previously said delete "needs nothing at all, since it calls nothing", which repeated the same
- *   mistake the header above corrects: `delete` calls the DELETE endpoint, so it needs whatever
- *   that endpoint checks.
+ *   carry no permissions block at all and 403 for any identity but `root@pam`.
  */
 import { Resource } from 'alchemy';
 import * as Provider from 'alchemy/Provider';
-import type { NodesNodeDisksZfsPostParams } from './generated/pve.ts';
-import { type PveRequirements, type WithTarget } from './resource.ts';
-/**
- * PVE's layouts, generated (2026-09-23) from `NodesNodeDisksZfsPostParams['raidlevel']`
- * (`generated/pve.ts`, manifest `pve-apidoc` pve-manager 9.2.11 sha256 9def8f13…) rather than
- * hand-typed, per decision 9. ⚠️ Each has a minimum disk count PVE enforces, and `raid10` needs an
- * even one. ⛔ THERE IS NO `stripe` IN THIS ENUM. n1's `speed` pool is one (decision 14 accepts it
- * as-is): `ZfsPoolProps` below is why a stripe pool is declarable at all — as an ADOPT-ONLY
- * declaration with no `raidlevel`, never as a full one.
- */
-export type ZfsRaidLevel = NonNullable<NodesNodeDisksZfsPostParams['raidlevel']>;
-/** Generated the same way, from `NodesNodeDisksZfsPostParams['compression']`. */
-export type ZfsCompression = NonNullable<NodesNodeDisksZfsPostParams['compression']>;
+import type { PveRequirements, WithTarget } from './resource-spec.ts';
+import type { ZfsPoolAttributes } from './zfs-pool-wire.ts';
+import type { ZfsCompression, ZfsRaidLevel } from './zfs-pool-form.ts';
+export type { ZfsPoolAttributes } from './zfs-pool-wire.ts';
+export type { ZfsCompression, ZfsRaidLevel } from './zfs-pool-form.ts';
 /**
  * ⛔ THERE IS NO `add_storage`, `cleanup-config` OR `cleanup-disks` PROP, AND THAT IS NOT AN
  *   OVERSIGHT. The last two belong to the DELETE this resource refuses to make. `add_storage=1`
@@ -116,7 +114,7 @@ export interface ZfsPoolProps extends WithTarget {
      *   both this and `raidlevel` undeclared declares an ADOPT-ONLY pool — one this resource may
      *   read and report but never build. That is the only shape available for a pool PVE's own POST
      *   schema cannot fully describe, such as n1's `speed`, whose layout is a stripe and whose
-     *   `raidlevel` enum (above) has no stripe to declare. `createForm` (zfs-pool-write.ts) omits
+     *   `raidlevel` enum (above) has no stripe to declare. `createForm` (zfs-pool-form.ts) omits
      *   both keys when they are absent, and `createPool` refuses before any POST if the pool it
      *   would need to build is not already there — an adopt-only declaration never creates. Declare
      *   both fields together for a pool this resource should build from scratch; declaring only one
@@ -145,29 +143,6 @@ export interface ZfsPoolProps extends WithTarget {
      */
     'draid-config'?: string;
 }
-/**
- * ⚠️ EVERYTHING HERE IS REPORTED, NOTHING HERE IS COMPARED — see the ⛔ on `matches`. These exist
- *   so a plan and the state store can say what the pool actually is, on a family where the
- *   declaration and the live object share no comparable field at all.
- */
-export interface ZfsPoolAttributes {
-    /** ★ The value a `Proxmox.Storage` should read to order itself after this pool. */
-    name: string;
-    node: string;
-    /** `ONLINE` | `DEGRADED` | `FAULTED` | … Health, not configuration. */
-    state: string;
-    /** ZFS's own error summary, e.g. `No known data errors`. */
-    errors: string;
-    /**
-     * The leaf devices ZFS reports, in vdev order, comma-joined.
-     *
-     * ⚠️ THIS IS WHAT ZFS RESOLVED, NOT WHAT WAS DECLARED, and the two normally differ: PVE rewrites
-     *   a `/dev/sdb` into a by-id link before creating, and ZFS reports partition paths (`…-part3`)
-     *   for a pool built on partitions — MEASURED, that is exactly what node-b's `rpool` reports. Never
-     *   compare it with `props.devices`.
-     */
-    devices: string;
-}
 export interface ProxmoxZfsPool extends Resource<'Proxmox.ZfsPool', ZfsPoolProps, ZfsPoolAttributes, never, PveRequirements> {
 }
 /** ★ `retain` by default — a pool holding datasets cannot be rebuilt. See the ★ in resource.ts. */

package/dist/proxmox/zfs-pool.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"zfs-pool.d.ts","sourceRoot":"","sources":["../../src/proxmox/zfs-pool.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkEG;AACH,OAAO,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AACnC,OAAO,KAAK,QAAQ,MAAM,kBAAkB,CAAC;AAE7C,OAAO,KAAK,EAAE,2BAA2B,EAAE,MAAM,oBAAoB,CAAC;AACtE,OAAO,EAAE,KAAK,eAAe,EAAE,KAAK,UAAU,EAA8B,MAAM,eAAe,CAAC;AAIlG;;;;;;;GAOG;AACH,MAAM,MAAM,YAAY,GAAG,WAAW,CAAC,2BAA2B,CAAC,WAAW,CAAC,CAAC,CAAC;AAEjF,iFAAiF;AACjF,MAAM,MAAM,cAAc,GAAG,WAAW,CAAC,2BAA2B,CAAC,aAAa,CAAC,CAAC,CAAC;AAErF;;;;;;;;GAQG;AACH,MAAM,WAAW,YAAa,SAAQ,UAAU;IAC9C;;;;;OAKG;IACH,IAAI,EAAE,MAAM,CAAC;IACb,+FAA+F;IAC/F,IAAI,EAAE,MAAM,CAAC;IACb;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACH,OAAO,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAC5B,SAAS,CAAC,EAAE,YAAY,CAAC;IACzB;;;;;;;OAOG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB;;;OAGG;IACH,WAAW,CAAC,EAAE,cAAc,CAAC;IAC7B;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB;AAED;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAChC,mFAAmF;IACnF,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,uEAAuE;IACvE,KAAK,EAAE,MAAM,CAAC;IACd,4DAA4D;IAC5D,MAAM,EAAE,MAAM,CAAC;IACf;;;;;;;OAOG;IACH,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,cAAe,SAAQ,QAAQ,CAC9C,iBAAiB,EACjB,YAAY,EACZ,iBAAiB,EACjB,KAAK,EACL,eAAe,CAChB;CAAG;AAEJ,mGAAmG;AACnG,eAAO,MAAM,cAAc,iDAEzB,CAAC;AAqBH,eAAO,MAAM,sBAAsB,oIACoD,CAAC"}
+{"version":3,"file":"zfs-pool.d.ts","sourceRoot":"","sources":["../../src/proxmox/zfs-pool.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwEG;AACH,OAAO,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AAEnC,OAAO,KAAK,QAAQ,MAAM,kBAAkB,CAAC;AAI7C,OAAO,KAAK,EAAE,eAAe,EAAE,UAAU,EAAE,MAAM,oBAAoB,CAAC;AAGtE,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,oBAAoB,CAAC;AAE5D,OAAO,KAAK,EAAE,cAAc,EAAE,YAAY,EAAE,MAAM,oBAAoB,CAAC;AAEvE,YAAY,EAAE,iBAAiB,EAAE,MAAM,oBAAoB,CAAC;AAC5D,YAAY,EAAE,cAAc,EAAE,YAAY,EAAE,MAAM,oBAAoB,CAAC;AAEvE;;;;;;;;GAQG;AACH,MAAM,WAAW,YAAa,SAAQ,UAAU;IAC9C;;;;;OAKG;IACH,IAAI,EAAE,MAAM,CAAC;IACb,+FAA+F;IAC/F,IAAI,EAAE,MAAM,CAAC;IACb;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACH,OAAO,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAC5B,SAAS,CAAC,EAAE,YAAY,CAAC;IACzB;;;;;;;OAOG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB;;;OAGG;IACH,WAAW,CAAC,EAAE,cAAc,CAAC;IAC7B;;;;OAIG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB;AAED,MAAM,WAAW,cAAe,SAAQ,QAAQ,CAC9C,iBAAiB,EACjB,YAAY,EACZ,iBAAiB,EACjB,KAAK,EACL,eAAe,CAChB;CAAG;AAEJ,mGAAmG;AACnG,eAAO,MAAM,cAAc,iDAEzB,CAAC;AAEH,eAAO,MAAM,sBAAsB,oIAyEhC,CAAC"}

package/docs/grafana-alerting.md

@@ -0,0 +1,145 @@
+# Grafana alerting provisioning — `@homeflare/alchemy/grafana`
+
+Declares Grafana's alerting-provisioning objects (decision 40: every internal alert lands in one
+place). Ships in three stacked PRs, in the order this file's own history records:
+
+1. **This PR:** `Grafana.ContactPoint`, `Grafana.MuteTiming`, `Grafana.MessageTemplate`.
+2. Next: `Grafana.AlertRuleGroup`.
+3. Then: `Grafana.NotificationPolicy` — the singleton policy tree, last on purpose (it references
+   contact points, mute timings and templates by name).
+
+All three ship on the same `@distilled.cloud/grafana@0.2.0` operations
+[grafana.md](./grafana.md#the-sdk-gap--history-and-what-shipped-on-top-of-the-fix) already
+unblocked (`skipDeprecated` patched false for the 32 alerting-provisioning-write operations). No
+live call was made writing this PR — see "Measured vs inferred" below.
+
+## Foreign-provenance refusal — shared, `alerting-provenance.ts`
+
+Every resource in this family reads a `provenance` string off what Grafana returns and refuses to
+write when it names an owner other than this API. **Measured against Grafana's own source**
+(`pkg/services/ngalert/models`, not re-fetched live): `ProvenanceNone = ""` (unclaimed),
+`ProvenanceAPI = "api"` (this API's own writes), `ProvenanceFile = "file"`,
+`ProvenanceConvertedPrometheus = "converted_prometheus"`. `alerting-provenance.ts`'s
+`WRITABLE_PROVENANCES` is an **allowlist** of `{"", "api"}`, not a denylist of the two named
+foreign values — an unnamed future provenance source refuses by default, the safer failure
+direction for a control-plane write. Corroborated by Grafana's docs
+(grafana.com/docs/grafana/v13.1/alerting/set-up/provision-alerting-resources/http-api-provisioning/),
+whose example payloads show exactly `"api"` and `"file"`.
+
+This is **defense in depth, not the only guard**: Grafana's alerting provisioning API also enforces
+this server-side (grafana/grafana#103597, "Unable to delete file provisioned alert rules," reports
+the block firing) — unlike the classic folder/dashboard write API `provisioned.ts` guards, which
+has no such server-side check at all. `create` is never at risk for any resource below: it only
+runs when `fetchLive` already found nothing.
+
+⛔ **A missing `provenance` field is treated as foreign, never as `ProvenanceNone` — fixed after an
+adversarial review of this PR found the guard failing OPEN.** The first version mapped
+`live.provenance ?? ''`, collapsing "the field is absent" into "the field is explicitly empty" —
+both writable. `isForeignProvenance`/`refuseIfForeignProvenance` now keep `undefined` as its own
+value: only a field Grafana explicitly reports as `""` or `"api"` is writable. Every resource below
+has a test pinning all three cases (missing refuses, explicit `""` is writable, `"file"` refuses).
+
+`X-Disable-Provenance` is **never set** by any resource in this family. Every create/update
+therefore leaves the object at `provenance: "api"` — Grafana's own default for an API write, which
+blocks UI edits afterward. Deliberate: an object this family declares should stay owned by the
+declaration, the "one owner per resource" posture `provisioned.ts` already established for
+folders/dashboards.
+
+## `Grafana.ContactPoint`
+
+```ts
+import { GrafanaContactPoint, grafanaProviders } from '@homeflare/alchemy/grafana';
+
+export class OncallSlack extends GrafanaContactPoint('oncall-slack', {
+  uid: 'slack-oncall',
+  name: 'On-call Slack',
+  type: 'slack',
+  settings: { recipient: '#oncall' },
+  secureSettingsRefs: { url: 'GRAFANA_SLACK_WEBHOOK_URL_ENV' },
+}) {}
+```
+
+- **No by-uid GET route exists** — measured: `services/grafana.ts` has only `routeGetContactpoints`
+  (list, optional `name` filter) and its export sibling. Narrowing that GET to the declared `name`
+  is not safe either: `name` is a renameable grouping label (Grafana's own doc: "used as grouping
+  key in the UI"), so `fetchLive` lists every contact point unfiltered and matches `uid`
+  client-side — the same ambiguity `resource.ts`'s header and netbox's `soleMatch` name.
+- **Secrets never appear as a literal prop (S25).** A secure `settings` key (a webhook URL, an API
+  key, …) is named in `secureSettingsRefs` (field -> env var NAME), resolved fresh inside
+  `create`/`update`'s own effect and merged into `settings` only there. Grafana's plain GET has no
+  `decrypt` option (only the export route does, org-admin only) — a secure key always comes back
+  redacted, so `matches` excludes every `secureSettingsRefs` key from comparison entirely, even if
+  `settings` also names it with a stale placeholder value (`contact-point.test.ts`'s own test for
+  this). Non-secret `settings` compares via `subset-match.ts`'s `declaredContentMatches`, tolerating
+  a default Grafana injects that the declaration never mentioned.
+
+## `Grafana.MuteTiming`
+
+```ts
+import { GrafanaMuteTiming, grafanaProviders } from '@homeflare/alchemy/grafana';
+
+export class Weekends extends GrafanaMuteTiming('weekends-mute', {
+  name: 'weekends',
+  timeIntervals: [{ weekdays: ['saturday', 'sunday'] }],
+}) {}
+```
+
+- ⚠️ **A genuine, surprising SDK finding, worth restating here.** The generated `MuteTimeInterval`
+  type declares only `name`/`time_intervals` — no `provenance`, no `version`, unlike every other
+  type this family reads. A first pass assumed the data was gone; empirically it is not:
+  `@distilled.cloud/core`'s response decoding is `JSON.parse` + a key-rename pass, never a strict
+  schema decode — any key a type doesn't model passes through **verbatim** (`protocol-http.ts`'s
+  `mapKeys`, confirmed by calling the real operation with a `provenance`/`version`-bearing response
+  through this family's own fake-Grafana harness). `mute-timing.ts` reads both through a small
+  local `& { provenance?: string; version?: string }` intersection rather than the SDK's own type.
+  The same passthrough applies outbound: `timeIntervals` is typed as an opaque
+  `Record<string, unknown>[]`, not the SDK's own too-narrow `TimeInterval` (which is missing the
+  real Alertmanager fields — `weekdays`/`times`/`months`/`days_of_month`/`years`/`location` — for
+  the same reason), and a real weekday/time entry reaches the wire unchanged. Tracked as a real SDK
+  type-generation gap in `docs/upstream-conformance.md` (the S22 fix route) — not a data-loss gap.
+- **`version` rides on `destroy`, not `update`** — measured: `RouteDeleteMuteTimingRequest.version`
+  exists for optimistic concurrency; `RoutePutMuteTimingRequest` has no `version` field at all, a
+  real Grafana API asymmetry between the two write routes.
+
+## `Grafana.MessageTemplate`
+
+```ts
+import { GrafanaMessageTemplate, grafanaProviders } from '@homeflare/alchemy/grafana';
+
+export class SlackBody extends GrafanaMessageTemplate('slack-body-template', {
+  name: 'slack-body',
+  template: '{{ define "slack-body" }}...{{ end }}',
+}) {}
+```
+
+- **Create and update are the same wire call** — measured: no `routePostTemplate` exists, only
+  `routePutTemplate` (`PUT /v1/provisioning/templates/{name}`, upsert by name). Kept as two spec
+  functions anyway so the shared engine's `diff` reports a content change as `update`, not the
+  `replace` it shows for any resource whose `spec.update` is `undefined` (`resource.ts`).
+  `version` rides on `update` when Grafana reports one, for optimistic concurrency.
+
+## Tests
+
+Each resource's `*.test.ts` uses the family's `fake-grafana.ts` harness (the real distilled
+protocol, only wire responses faked) and proves: a GET never carries a body; a foreign-provenance
+object — an explicit `"file"` OR a MISSING `provenance` field — refuses update/destroy with no write
+sent, while an explicit `""` is writable; a transient failure (401/403) propagates rather than
+folding to absent; an unchanged declaration is a noop despite Grafana injecting an extra field the
+declaration never mentioned; and — `Grafana.ContactPoint` only — a secret value never appears in the
+attributes a real `reconcile` returns (driven end to end through create and the read-back
+`resource.ts` always does, not just asserted absent from a declaration that never held it).
+`Grafana.ContactPoint`'s tests are split three ways (`contact-point.test.ts`/`-secrets.test.ts`/
+`-provenance.test.ts`, sharing fixtures from `contact-point-fixtures.ts`) to stay under the house's
+250-line file cap.
+
+## Measured vs inferred (no live call in this PR)
+
+**Measured**, against the SDK's generated types and/or Grafana's own docs: the provenance enum and
+its values; the absence of a by-uid contact-point GET; the create/update PUT-only shape for
+templates and the `version`-on-destroy-only shape for mute timings; the response-decode
+verbatim-passthrough behavior (traced into `@distilled.cloud/core`'s own source and confirmed
+against the real operation through this family's fake-Grafana harness — as close to "measured" as
+this PR gets without a live Grafana instance). **Inferred, not measured live:** whether Grafana's
+real server-side provenance enforcement covers every write route this family calls the same way (only
+the alert-rule-deletion case is corroborated by a filed issue); whether a genuine mute-timing
+`version` conflict on delete surfaces as a typed `Conflict` in practice.