cycle: the Talmudic routing sends roots the engine can read

route_if_unresolved sent the roots' Hebrew (ברא) to the Talmudic
Engine, whose verse facts name roots by letter (bet_resh_aleph, read
from "bet-resh-aleph"). Since Step 14 every interpretation the cycle
took from the engine was "resolved" over an empty trace — 0 verses,
0 mitzvot — and so was every case it escalated to the Sanhedrin. Now
the names go up (BereishitCycle.engine_root_name/1, from tablet 55's
third commit), on both the interpretation and the escalation.

Proven against the engine running locally on its socket, with the
roots the cycle itself activates for bereishit 1:1:
  HEBREW (as before): status=resolved verses=0  mitzvot=0
  NAMES  (now):       status=resolved verses=11 mitzvot=4
Elixir 632/0. The unresolved route cannot be driven in the test env
(it needs the Shoresh Engine to leave a root ungrounded); the live
proof is a pe'ah question with an ungroundable Hebrew word.

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

vav_pipeline/lib/vav_pipeline/bereishit_cycle.ex

@@ -740,7 +740,10 @@ defmodule VavPipeline.BereishitCycle do
   @doc false
   defp route_if_unresolved(data, context) do
     roots = Map.get(data, :roots_activated, [])
-    context_roots = Enum.map(roots, & &1.shoresh)
+    # Tablet 55: the engine names roots by letter (bet_resh_aleph); the
+    # Hebrew was sent since Step 14 and never matched a verse fact, so
+    # every Talmudic interpretation was "resolved" over an empty trace.
+    context_roots = roots |> Enum.map(&engine_root_name/1) |> Enum.reject(&is_nil/1)
 
     case_ref = Map.get(data, :case_ref, generate_case_ref())