@homeflare/alchemy 0.32.0 → 0.33.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-folder-dashboard.md

@@ -0,0 +1,145 @@
+# `Grafana.Folder` and `Grafana.Dashboard` — `@homeflare/alchemy/grafana`
+
+Built 2026-09-24 on the same `@distilled.cloud/grafana` (aliased onto
+`@homeflare/distilled-grafana@0.2.0`) operations that fixed the SDK gap
+[grafana.md](./grafana.md#the-sdk-gap--history-and-what-shipped-on-top-of-the-fix) recorded:
+`createFolder`/`getFolderByUID`/`updateFolder`/`deleteFolder`/`getFolders` and
+`postDashboard`/`getDashboard`/`deleteDashboard`, plus a typed `PreconditionFailed` (412) for
+dashboard version conflicts. No live call was made writing this PR — see "Measured vs inferred"
+below for exactly which claims that limits.
+
+## Both follow `Grafana.Datasource`'s doctrine
+
+Same file shape (`resource.ts`'s shared `GrafanaSpec`/`grafanaOperations`/`grafanaHandlers`), same
+credentials layer (`grafanaProviders(target)`), same **uid required, never generated** reasoning —
+`getFolderByUID`/`updateFolder`/`deleteFolder` and `getDashboard`/`postDashboard`/`deleteDashboard`
+are all UID-keyed, and neither `getFolders` nor a dashboard list endpoint takes a per-uid filter,
+so locating an object this resource didn't create would mean listing everything and matching by
+name — the ambiguity requiring `uid` up front sidesteps.
+
+## `Grafana.Folder`
+
+```ts
+import { GrafanaFolder, grafanaProviders } from '@homeflare/alchemy/grafana';
+
+export class Infra extends GrafanaFolder('infra-folder', {
+  uid: 'infra',
+  title: 'Infrastructure',
+}) {}
+```
+
+- **`description` is write-only** — MEASURED against the SDK's generated types: `Folder` (the GET
+  response) has no `description` field at all, though `CreateFolderRequest`/`UpdateFolderRequest`
+  both accept one. Sent on every create/update that declares it; never compared, the same
+  treatment `Grafana.Datasource` gives `secureJsonDataRefs` for the same reason (nothing to diff
+  against).
+- **Nesting (`parentUid`) is create-only** — MEASURED: `UpdateFolderRequest` has no `parentUid`
+  field (`folder_uid`, `description`, `overwrite`, `title`, `version` only). A declaration whose
+  `parentUid` no longer matches the live folder REFUSES with `GrafanaFolderReparentError` rather
+  than silently doing nothing or deleting-and-recreating under the new parent (which — next
+  bullet — takes every dashboard and alert rule in the folder with it). Move a folder by hand in
+  Grafana, then update the declaration.
+- **Delete defaults to `retain`** — `deleteFolder`'s own operation description says it deletes
+  "all dashboards (and their alerts) stored in the folder... cannot be reverted... also deletes
+  all the subfolders." That is the multi-object cascade `openbao/mount.ts` guards with
+  `defaultRemovalPolicy: 'retain'`, verified there against Alchemy's own `Apply.ts` (not
+  re-verified here; same engine, same option — see `folder.ts`'s header). A stack that wants the
+  cascade opts in with `.pipe(RemovalPolicy.destroy())`; `destroy` still implements the real
+  `DELETE` in full either way (S11). `Grafana.Dashboard` does **not** default to retain — see its
+  own section below.
+
+## `Grafana.Dashboard`
+
+```ts
+import { GrafanaDashboard, grafanaProviders } from '@homeflare/alchemy/grafana';
+
+export class FleetOverview extends GrafanaDashboard('fleet-overview-dashboard', {
+  uid: 'fleet-overview',
+  folderUid: 'infra',
+  dashboard: {
+    title: 'Fleet Overview',
+    panels: [/* … exported straight from Grafana's own "Export as JSON" … */],
+  },
+}) {}
+```
+
+- **The declared content is the dashboard JSON model** — the same shape Grafana's own "Export as
+  JSON" produces. `dashboard-model.ts`'s `normalizeModel` strips `id`/`version`/`iteration`
+  (Grafana-managed, injected/incremented on every save) and forces `uid` to this resource's own
+  value regardless of where — or whether — the source model carried one, before ANY comparison.
+  That is what makes a pasted export (which always embeds the OLD live uid) and a freshly-read
+  live model compare equal, and what makes a no-change plan a true noop despite those fields
+  moving on every live save.
+- **Array order is significant, and nothing here needs a `sortedSet`** — `panels` (screen layout
+  via its own `gridPos`, but the array order also drives Grafana's internal panel indexing and
+  `repeat` behavior) and each panel's `targets` (query execution/legend order) are compared
+  positionally, never reordered. Nothing in a dashboard model is a genuinely unordered SET the way
+  UniFi's `trustedDhcpServerIpAddresses` is (`unifi/network-form.ts`'s `sortedSet`) — this family
+  has no field that needs one. `schemaVersion` is deliberately left comparing as-is — NOT MEASURED
+  whether Grafana rewrites it on a plain save, so normalizing it away on a guess risked hiding a
+  genuine schema mismatch instead of a false diff; see `dashboard-model.ts` for the exact reasoning
+  and what evidence would justify adding it to the volatile-field list.
+- **`matches` compares "is the declaration a subset of what is live", not plain equality** —
+  `dashboard-model.ts`'s `declaredContentMatches`, added after an adversarial review of this PR
+  found plain structural equality (`alchemy/Diff`'s `deepEqual`, used in an earlier version of this
+  PR) made an ordinary, never-edited dashboard show `update` FOREVER: Grafana's own schema
+  migration on save decorates any panel or target whose `datasource` is absent with an explicit
+  `{type, uid}` reference — documented Grafana behavior, not re-measured against a live instance in
+  this PR. A declared panel that never sets `datasource` therefore read back with that field
+  populated, disagreed with the declaration, got written back undecorated, and got redecorated
+  again — non-convergent. `declaredContentMatches` instead asks only whether every field the
+  DECLARATION mentions, at any depth, still matches what is live; `live` may carry additional
+  fields Grafana injected that the declaration never mentioned. Real content drift (a field the
+  declaration DOES mention changing, or vanishing) is still caught exactly as before. The
+  trade-off, deliberate: **removing** a field from the declaration can no longer force Grafana to
+  drop a value it — or a previous declaration — set; only an explicit replacement value changes
+  one. This is the same "undeclared means don't care, never means force-to-default" convention this
+  whole kit already uses for a plain optional prop, now applied inside the JSON model too.
+- **412 version conflicts fail loudly, never overwritten blindly.** `update` injects the version
+  this resource just read (from the same `fetchLive` call `reconcile` already made) into the model
+  it sends, and `overwrite` is never set. If Grafana's own check still fails — someone saved in the
+  gap between that read and this write — `PreconditionFailed` is left uncaught: the whole reconcile
+  fails and nothing is written. The next `plan`/`deploy` re-reads the new live version fresh; there
+  is no separate retry loop in this file, because that next run already is the re-read.
+- **No retain default**, unlike `Grafana.Folder`. Deleting one dashboard is a single-object blast
+  radius — the same class `Grafana.Datasource` already accepts without a retain guard, not
+  `Grafana.Folder`'s multi-object cascade.
+
+## Provisioned objects — refused for writes, adoption is fine
+
+A folder or dashboard that a provisioning FILE manages (rather than this API) carries a live
+signal — `Folder.managedBy` (non-empty) and `DashboardMeta.provisioned`/`provisionedExternalId` —
+that `update`/`destroy` check before ever calling the SDK; `GrafanaProvisionedObjectError` names
+the owning file when Grafana reports one (dashboards only — a folder's `managedBy` value is
+reported as-is, since the SDK does not separately expose a folder's owning file). `create` is
+never at risk: it only runs when `fetchLive` already found nothing.
+
+`matches` still compares structurally regardless of provisioned status, so a mismatched
+declaration against a provisioned object shows `update` in a plan — never a silent, permanently
+hidden noop — and only fails, loudly, when reconcile actually tries to write. A declaration that
+already matches what is live never reaches `update`/`destroy` at all (the shared engine's
+observe-before-write path), so **adopting a provisioned object read-only is safe.**
+
+⚠️ **Measured vs inferred (no live call in this PR).** `DashboardMeta.provisioned`/
+`provisionedExternalId` are exactly the fields Grafana's classic dashboard-read response types for
+this purpose — high confidence, standard shape. `Folder.managedBy` is INFERRED from the SDK's
+schema only: no live instance in this house currently has a file-provisioned FOLDER to read against
+(`teslamate-grafana` has none at all — see grafana.md). Treating any non-empty `managedBy` as
+provisioned, rather than matching specific string values that were never observed live, is the
+conservative reading; confirm against a real provisioned folder before relying on the exact value in
+an error message. The panel/target `datasource` auto-decoration `declaredContentMatches` (above)
+exists to tolerate is documented Grafana schema-migration behavior, also not re-measured live in
+this PR. And `updateFolder`'s `version` field — sent optimistically for concurrency — carries the
+SDK's own caveat "only used by the legacy folder implementation"; whether Grafana's newer
+unified-storage folder backend honors it at all is unverified (`folder.ts`'s `update`).
+
+## Tests
+
+`folder.test.ts`, `dashboard.test.ts` and `dashboard-model.test.ts` mirror `datasource.test.ts`'s
+fake-Grafana harness (`fake-grafana.ts` — the real distilled protocol, only the wire responses
+faked). Each proves: a GET never carries a body (`fake.bodies[0]` is `undefined` — the exact
+"distilled JSON-encodes unknown keys as a body" trap this family's shared memory names); a
+provisioned object refuses update and destroy with no write sent; a transient failure (403/401)
+propagates rather than folding to absent; an unchanged declaration is a noop despite `id`/
+`version`/`iteration` differing; a 412 propagates uncaught; and the folder `parentUid` reparent
+refusal sends no write.

package/docs/grafana.md

@@ -6,15 +6,14 @@ any status check. Built 2026-09-24 against the live target `teslamate-grafana.se
 measured version **13.1.3** (`teslamate/grafana:4.2.0`), listening on `127.0.0.1:3100`, served
 publicly at `tesla.homeflare.dev/dash/`.
 
-## The SDK gap — why only `Datasource` ships
+## The SDK gap — history, and what shipped on top of the fix
 
 ✅ **SDK-level gap fixed 2026-09-24** (`@distilled.cloud/grafana`, aliased onto
-`@homeflare/distilled-grafana` — 0.1.0 pre-release, 0.2.0 once its `minor` changeset publishes it;
-see [docs/distilled-interim.md](./distilled-interim.md)).
-The gap below is otherwise unchanged and left as evidence of what was measured and why; only its
-status line moved. **Still true today:** only `Grafana.Datasource` ships as a house _resource_ —
-`Grafana.Folder`, `Grafana.Dashboard`, `Grafana.AlertRule` and friends are follow-up work on top of
-the now-available SDK operations, not part of this fix.
+`@homeflare/distilled-grafana` — 0.2.0; see [docs/distilled-interim.md](./distilled-interim.md)).
+The gap below is left as evidence of what was measured and why. `Grafana.Folder` and
+`Grafana.Dashboard` now ship on top of the unblocked operations —
+[grafana-folder-dashboard.md](./grafana-folder-dashboard.md) covers both in full. `Grafana.AlertRule`,
+`ContactPoint`, `NotificationPolicy` and `MuteTiming` remain follow-up work, not part of this PR.
 
 Measured 2026-09-24 against the published `@distilled.cloud/grafana@1.0.0-rc.12` tarball (its
 `lib/services/grafana.d.ts`, 4,938 lines): the package had **no create/read/update/delete
@@ -125,8 +124,10 @@ export class TeslaMateDatasource extends GrafanaDatasource('teslamate-datasource
 
 ## Not covered
 
-- **Folders, dashboards, alert rules, contact points, notification policies, mute timings.** The
-  SDK-level blocker is fixed (above); no house `Resource` calls these operations yet — follow-up
-  work, not blocked on anything.
+- **`Grafana.Folder` and `Grafana.Dashboard` ship** — see
+  [grafana-folder-dashboard.md](./grafana-folder-dashboard.md), not repeated here.
+- **Alert rules, contact points, notification policies, mute timings.** The SDK-level blocker is
+  fixed (above); no house `Resource` calls these operations yet — follow-up work, not blocked on
+  anything.
 - **`read` never answers `Unowned`** — the same open gap forgejo's and netbox's own families
   still carry (see upstream-conformance.md); a maintainer decision on the ownership-check shape.

package/docs/upstream-conformance.md

@@ -259,10 +259,15 @@ HttpClient` client. The old status-carrying `NetboxError` and its `cause.status
     `@homeflare/distilled-grafana` (0.1.0 pre-release, 0.2.0 once this PR's `minor` changeset
     releases it), aliased onto `@distilled.cloud/grafana` the same S22 route
     `@homeflare/distilled-netbox` established. `Grafana.Datasource`'s props/attributes/generated code
-    are unchanged (diffed operation-by-operation against the prior commit). **Still open, and not
-    this PR's scope:** no `Grafana.Folder`/`Dashboard`/`AlertRule`/`ContactPoint`/
-    `NotificationPolicy`/`MuteTiming` resource calls the newly-available operations yet — follow-up
-    PRs, no longer blocked on the SDK.
+    are unchanged (diffed operation-by-operation against the prior commit).
+
+    ✅ **`Grafana.Folder`/`Grafana.Dashboard` shipped** (this PR, on top of the same
+    `@distilled.cloud/grafana` operations S22 unblocked) — the uid-required doctrine, the
+    provisioned-object refusal, the parentUid-is-create-only refusal and the volatile-field
+    normalization that makes an unchanged dashboard a true noop are all in
+    [grafana-folder-dashboard.md](./grafana-folder-dashboard.md), not repeated here. **Still open,
+    and not this PR's scope:** `Grafana.AlertRule`/`ContactPoint`/`NotificationPolicy`/`MuteTiming`
+    — follow-up PRs, no longer blocked on the SDK.
     - ⛔ **Same open gaps as `forgejo/*` and `netbox/*` above:** `read` never answers `Unowned`
       (H1), and credentials come from an explicit env var NAME at call time rather than an
       `alchemy/Auth` provider (S24) — here the house's own `grafanaCredentials(target)`, not the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@homeflare/alchemy",
-  "version": "0.32.0",
+  "version": "0.33.0",
   "description": "Custom Alchemy providers for Cloudflare, Proxmox, OpenBao, Forgejo, Talos, launchd and Caddy, and a verifier that proves adoptions are no-ops.",
   "homepage": "https://github.com/taslabs-net/homeflare-kit/tree/main/packages/alchemy#readme",
   "bugs": "https://github.com/taslabs-net/homeflare-kit/issues",