docs: PCD-9784 spec correction and plan execution notes

Author: PF9-pushkar

docs/superpowers/plans/2026-09-03-pcd-9784-docs.md

@@ -442,3 +442,35 @@ Check: no OpenStack project names in prose (`cinder` appears only inside code an
 - [ ] **Step 1:** On the PR branch, `chore: release v0.1.11` commit turning `## [Unreleased]` into `## [0.1.11] - <date>`; push.
 - [ ] **Step 2:** `gh pr merge --merge`; then `git push origin --delete pushkar/pcd-9784-docs` (the worktree quirk skips remote deletion).
 - [ ] **Step 3:** `git fetch origin main && git tag -a v0.1.11 -m v0.1.11 origin/main && git push origin v0.1.11`; `gh run watch` the release; confirm `https://registry.terraform.io/providers/platform9/pcd/0.1.11/docs/guides/importing` renders.
+
+---
+
+## Execution notes (2026-09-04)
+
+Tasks 1 to 6 are done; Task 7 waits for the merge decision. What the lab run changed
+relative to the plan:
+
+- The first apply stalled: with `backends = ["nfs"]` (the top-level key) resmgr computed an
+  empty backend set, `cinder-volume` could not start, and the host looped in
+  `auth-converging`, where resmgr refuses every role change (409). Terraform was
+  interrupted; the tainted storage role was replaced with `backends = ["nfs-primary"]`
+  (resmgr accepted the removal after 51 s), which produced the correct settings. The
+  `backends` description, both examples, the guide, and the handoff were corrected.
+- Convergence then still failed silently because the NFS options were quoted strings
+  (`"true"`); the host agent reads them back as booleans. Unquoting them in the blueprint
+  (an in-place `pcd_cluster_blueprint` update) made the host reach `ok` within a minute.
+  Documented in the guide, both examples, the blueprint description, and the handoff.
+- `terraform untaint` was needed on the three roles after the interrupted apply so the
+  full apply added only the six remaining resources (network, subnet, image, instance,
+  volume, attachment): image 1m21s, instance 1m31s, volume 3s, attachment 9s; VM
+  pingable at 172.16.122.11; plan clean.
+- Teardown took three `terraform destroy` runs: 422 on the storage role (the deleted
+  image's backing volume `image-<id>` stays behind; deleted by hand), 500 on the cluster
+  and 403 `HostInAuthState` on the host-config unassignment while deauthorizations
+  landed. Recorded in the guide's Destroy section and the example README.
+- The image endpoint needs no override for LAN users: the provider already prefers the
+  image-library host's admin endpoint (`https://<host>:9494`); the guide states the
+  reachability requirement instead.
+- Lab left as the testsuite expects: host `136fc11a` authorized with no roles, region
+  empty, host NIC restored, cinder pre-enabled; the NFS export on the hypervisor VM
+  (`/srv/nfs/pcd`) remains and is harmless.

docs/superpowers/specs/2026-09-03-pcd-9784-docs-design.md

@@ -44,10 +44,17 @@ docs below.
   `storage_backends_json` is written as `null # sensitive`, so generated HCL never carries
   backend credentials, and leaving it unset on an imported blueprint preserves the
   backends.
-- In the live blueprint, `imageLibraryStorage` holds the volume type's *name*, and
-  `pcd_host_cluster_role.backends` lists the top-level keys of `storage_backends_json`.
-  The lab's Synology backend uses the full driver class path
+- In the live blueprint, `imageLibraryStorage` holds the volume type's *name*. The lab's
+  Synology backend uses the full driver class path
   `cinder.volume.drivers.synology.synology_iscsi.SynoISCSIDriver`.
+- Corrected during execution (the lab run used differing key names): the top-level key of
+  `storage_backends_json` becomes `volume_backend_name` on the host, so it is what a
+  volume type's `volume_backend_name` must equal; the second-level key is the driver
+  configuration name, which `pcd_host_cluster_role.backends` lists and which becomes the
+  Cinder backend section (`<host-uuid>@<config>`). The provider's `backends` description
+  said "top-level keys"; it was wrong and is fixed in this change. Boolean driver options
+  must be JSON booleans: a quoted `"true"` never validates on the host, which then
+  converges forever while resmgr refuses every role change.
 
 ## Decisions