Record D&D deployment blockers

docs/roadmap/features/0016-deploy-dnd-pipeline-to-pipeline-dnd.md

@@ -1,6 +1,6 @@
 # Feature 0016: Deploy the D&D Pipeline to `pipeline-dnd`
 
-Status: ready
+Status: blocked
 
 ## Summary
 

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implementation Plan 0016: Deploy the D&D Pipeline to `pipeline-dnd`
 
-Status: ready
+Status: blocked
 
 Target executor: GPT-5.6-Terra
 
@@ -341,8 +341,16 @@ independent review.
 
 ## Progress Notes
 
-Plan approved; no Feature 0016 implementation or deployment has begun.
-Architecture is settled; the operational inputs below remain to be supplied.
+Execution began on 2026-09-21 but Stage 1 is blocked before any consumer or
+deployment change. The available `devbench-02.lxd` checkout is not the
+operational controller: Ansible is not installed and `/etc/ansible` does not
+exist. The public Gitea sources and Ansible Galaxy are reachable, but no
+operational controller hostname or checkout workflow has been supplied. Direct
+SSH to `pipeline-dnd.rakestrawhome.com` reaches the host but the available
+identity is rejected, so the Ubuntu release, `eric` access, and sudo access
+cannot be confirmed. The Vault selection mechanism and operator-populated
+credentials are unavailable, and no acceptance campaign/session/audio input
+has been selected. No stage is complete and no dependent work has begun.
 
 ## Open Questions