Phase 5 deployment: Dockerfiles, K8s manifests, halt monitor (Steps 33, 36)

Shemot 40:33 — Vay'khal Moshe et ham'lakhah.
The builder completes the work. The vessel is ready for transport.

Step 33 — Deployment configuration:
- Dockerfiles for all 4 components:
  - vav_pipeline: Elixir 1.16.1/OTP 26.2.1 release with Sanhedrin
  - shoresh_engine: GHC 9.6.4 binary
  - talmudic_engine: SWI-Prolog 9.2.2
  - korban_processor: Python 3.12.2 with pydantic
- Kubernetes manifests for Exoscale SKS (ch-gva-2):
  - Namespace, ConfigMap, Secrets template
  - L1 Torah PV/PVC (read-only mount)
  - Manna provision PVC (kohen writes, system reads)
  - Deployment: vav-pipeline + 3 sidecars, shared volumes
  - Service: ClusterIP + LoadBalancer with Exoscale NLB
  - Init container runs Ecto migrations (VavPipeline.Release)

Step 36 — Halt monitor (esh tamid):
- GenServer watches for three cardinal sins
- halt!/3 immediately halts system, sounds Chatzotzrot war signal
- Permanent audit log — halt events never deleted
- resolve/1 requires explicit operator action to resume
- alive?/0 for morning tamid verification
- 13 tests: alive check, 3 halt types, resolution, audit log,
  chatzotzrot war signal integration
- Added to supervision tree

All 219 Elixir + 19 L3 + 195 Prolog + 33 Haskell = 447+ tests, 0 failures

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

deploy/k8s/secrets.yaml

@@ -0,0 +1,17 @@
+# Shorashim Secrets — template only
+# NEVER commit actual secret values to git.
+# Apply with: kubectl apply -f - after filling in values.
+#
+# The DATABASE_URL connects to Exoscale PostgreSQL (temple-council-db)
+# in ch-gva-2 zone. Retrieve credentials from:
+#   exo dbaas show temple-council-db --zone ch-gva-2
+apiVersion: v1
+kind: Secret
+metadata:
+  name: shorashim-secrets
+  namespace: shorashim
+type: Opaque
+stringData:
+  # PostgreSQL connection for L3 Oral Tradition
+  # Format: ecto://user:password@host:port/database?sslmode=require
+  DATABASE_URL: "REPLACE_WITH_ACTUAL_DATABASE_URL"