Tablet 45: the courtyard gate checks the key, not the shape of the header

/courtyard/* and /chatzer/* admitted any `Authorization: Bearer <x>`.
Every test sent `Bearer test-token`; none sent a wrong one. Every
admitted request spends the day's manna.

VavPipeline.BigdeiKodesh.Gate: keys are a file (Construction §4.6 —
never env, never config, never git), one `tier key` per line, tiers
courtyard < chatzer (the inner ring opens the outer). Constant-time
compare against every line; no file / empty / unreadable → nobody
passes, GATE_NO_KEYS in the log, the caller told only "missing or
invalid". 403 FORBIDDEN for an outer key at an inner gate. Read on
every request so a rotated key is live in ~1 min without a rollout.

Deploy: Secret shorashim-api-keys projected at
/etc/shorashim/secrets/api_keys (vav-pipeline only, 0440),
API_KEYS_FILE in the configmap, template + issue/rotate recipe in
secrets.yaml and KOHEN.md "Issuing a key". Spec: tamid §1.1 (gate,
403), vayakhel §4.6. Doorpost 91d09d8d… → 42b38626….
Tests: tablet45_gate_test (parse, tiers, wrong/near/empty/no key, no
file) — Elixir 527/0.

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

deploy/k8s/configmap.yaml

@@ -20,6 +20,11 @@ data:
   # shared tmp-shorashim volume. Pod-internal; never on the network.
   KORBAN_SOCKET_PATH: "/tmp/shorashim/korban.sock"
 
+  # Courtyard / chatzer keys — a FILE (Construction §4.6), projected from
+  # the shorashim-api-keys Secret (secrets.yaml). The path is config; the
+  # keys never are.
+  API_KEYS_FILE: "/etc/shorashim/secrets/api_keys"
+
   # Shoresh Engine binary — staged onto the shared shoresh-bin volume
   # by the shoresh-engine-install init container (see deployment.yaml).
   # vav_pipeline spawns it as an Erlang Port, i.e. as a child process of