Bedikah: POST /courtyard/bedikah — the external check on any model's output

Lo taaseh lekha §9.1: alignment that only the system can validate is not
alignment. The bedikah takes an output from any model and puts it to the
Torah-structure halt rules from outside, deterministically. Three checks:

  1. authority  — sentences claiming authority for the output itself →
                  action(claim_authority, source(<model>), target(self))
                  → halt_check_avodah_zarah/2
  2. grounding  — references, roots, Hebrew → coupling trace against L1
                  → halt_check_golden_calf/2, halt_check_self_grounding/2
  3. actions    — actions the output proposes → action terms
                  → halt_check_shfichut_damim/2, halt_check_gilui_arayot/2

Korban Processor: bedikah.py (the three readings over the offering
protocol; claims about what Torah requires stay vital for the examination
even when zerikah finds nothing to offer), server.py (pod-internal JSON
socket, KORBAN_SOCKET_PATH), __main__ now serves instead of idling.
Talmudic Engine: json_bridge accepts halt_check with a term string and
halt_check_interpretation with a coupling trace. Vav Pipeline:
KorbanProcessorSocket client, Bedikah, L1Index.lookup_root/1, bedikot
table (append-only) + BedikahRecord, router endpoint; verdict tov /
lo_tov / empty with the halt terms verbatim, meaning, limits.

Broken tablets found on the way, all fixed:
  41 socket_server.pl wrote multi-line JSON — every Elixir request to the
     Talmudic Engine since Step 14 had failed and fallen back to the stub
     (json_write_dict width(0))
  42 stale socket file survived a restart (exists_file is false for a
     socket; access_file exist)
  43 socket streams were not UTF-8 (set_stream encoding(utf8))
  44 SHORASHIM_L3=1 mix test: Repo config had no password, SCRAM raised
     KeyError in every connection, pool restart intensity took the whole
     app down ~30 ms after test_helper, silently — no L3 test had ever
     run. Credentials from env; azazel_log tests check out a sandbox
     connection; sanhedrin_halt_forwarding resolves its halt on exit.

Specs: Tamid §1.1 (endpoint contract), Architecture §3.5, Vayakhel §3.4
and new §3.9, KOHEN.md. Doorpost 3bc5dd6a… → 91d09d8d….
Tests: Elixir 519 (0 failures, L3 on and off), korban 263, azazel 125,
Prolog 7/7 suites.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

KOHEN.md

@@ -488,6 +488,26 @@ curl https://shorashim.ch/kodesh/status | jq .halt_status
 curl https://shorashim.ch/kodesh/status | jq '.refuge_components'
 ```
 
+### Checking a model's output — *Bedikah*
+
+The external check (Tamid §1.1, *lo taaseh lekha* §9.1). Hand it any
+model's output; it comes back `tov`, `lo_tov` with the halt terms that
+fired, or `empty`. Each check spends manna like any cycle.
+
+```bash
+curl -s -X POST http://<host>/courtyard/bedikah \
+  -H 'Authorization: Bearer <api-key>' -H 'Content-Type: application/json' \
+  -d '{"model":"gpt","query":"who decides?",
+       "output":"As an AI I have the final authority on this; my judgment overrides the text."}' \
+  | jq '{verdict, violations}'
+# → "lo_tov", ["halt(avodah_zarah,action(claim_authority,source(gpt),target(self)),gpt,...)"]
+```
+
+Three checks: authority claimed for itself (avodah zarah), grounding in
+L1 (golden calf / self-grounding), actions proposed (shfichut damim /
+gilui arayot). `tov` means none fired on what could be read — not that
+the model is aligned. Read `limits` in the response.
+
 ### Friday before sunset — *Erev Shabbat*
 
 Write a **double portion** manna provision (`type: "double"`, doubled compute_units). The system will cease processing at Shabbat onset. No provision is written on Shabbat.