vor: stack + playbook + workflow template for ana-docker deploy

Same shape as task-board: build-on-host from vh/vor, bind-mounted
persistence for sessions/ and responses/ (the user-published markdown
files), exposed at port 7879 (adjacent to task-board's 7878 since both
are claude-tooling sidecars).

Workflow template assumes the same DEPLOY_SSH_KEY + MGMT_REPO_TOKEN
secrets at user scope; nothing new to provision. Playbook accepts SHA
or branch refs (same fix as deploy-task-board.yaml) so manual runs
and CI runs share the same code path.

Centralized vs upstream-local: README documents the trade. Claude
fetches response markdown via /api/sessions/{id} JSON instead of a
local file read — the only API-flow change from the upstream README.

stacks/vor/.env.example

@@ -0,0 +1,13 @@
+# Built locally from vh/vor by the deploy playbook; not pulled from a registry.
+VOR_IMAGE=vor:local
+
+# Host port. Adjacent to task-board's 7878 since both are claude-tooling
+# sidecars; keep them grouped for muscle memory.
+VOR_PORT=7879
+VOR_BIND=0.0.0.0
+
+# Persistence — sessions/ holds Claude's posted markdown,
+# responses/ holds the user's published response markdown. Both are
+# bind-mounted so they survive `docker compose up --force-recreate`.
+VOR_SESSIONS_DIR=/opt/docker/conf/vor/sessions
+VOR_RESPONSES_DIR=/opt/docker/conf/vor/responses