the name: Bikoret — code, contracts, images

Headers X-Bikoret-Key / -Rebuke / -Verdict / -Bedikah; the `bikoret`
object and the "— bikoret …" fringe on a gate reply; environment
variables BIKORET_*; the image user and paths (/home/bikoret,
/tmp/bikoret, /var/lib/bikoret/manna, /etc/bikoret/secrets,
/opt/bikoret/spec); the tmp-bikoret pod volume; local databases
bikoret_dev/_test. Kubernetes resource names, the shorashim_app role and
the domain are unchanged (Tamid §1.1, "the names that still carry the
old word"). Doorpost c963c4fe…. Elixir 604/0, L3 10/0, korban 295,
Prolog bedikah 44/44. Gitea repo renamed heaviness510/bikoret (old URL
redirects).

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

talmudic_engine/src/interface/json_bridge.pl

@@ -17,7 +17,7 @@
 %  library(http/json) is the canonical module path and resolves on
 %  SWI-Prolog 9.x AND 10.x. The bare alias library(json) resolves only
 %  on 10.x, which is what the dev workstation runs; the image is built
-%  on swipl 9.2.2 as pinned by specs/shorashim_vayakhel.md §1.1, where
+%  on swipl 9.2.2 as pinned by specs/bikoret_vayakhel.md §1.1, where
 %  it does NOT resolve. The consequence was invisible to the test
 %  suite (212 tests green on the host) and fatal in the container:
 %    ERROR: source_sink `library(json)' does not exist