tablet 58: the tool's answer is given — tool results are sources; markers on word boundaries

The sugya reply came back lo_tov — golden_calf on two sentences the
builder had just read from tool output (the Mishnah's reasons, from the
second scroll; the commit and pod, from its own tools). The gate's
sources were only the user turns' text and document blocks; a
tool_result block and a tool turn — what the model was GIVEN (tablet
49) — were not counted. And "shorashim-675b…" was vital because the
insight markers matched "Rashi" inside it.

- Shape.sources: Anthropic tool_result blocks (string or blocks) inside
  a user turn, and OpenAI role "tool" turns, are sources; the query is
  still the last user turn. gate_test: both shapes.
- zerikah._INSIGHT_MARKERS: \b…\b. test_zerikah: the pod name is not
  Rashi; "Rashi reads" and "The Mishnah records" are; "Rambanovich" and
  "talmudic_engine" are not.
- Tablet 58 in the Broken Tablets.

Elixir 643/0, korban 294/0. Doorpost pin unchanged.

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

specs/broken_tablets/README.md

@@ -302,3 +302,43 @@ output too, and the gate reads it the way it reads any other —
 by form, not by authorship. It passed by form. Where it did not pass
 by grounding, the reason was the reader's eyes, not the text's
 standing; and that, too, the gate was built to say.
+
+## Tablet 58 — the tool's answer is given (2026-10-21)
+
+The builder's reply that delivered the sugya specification came back
+through the gate `lo_tov — golden_calf` on two sentences: "The
+Mishnah's two reasons for recording the opinion that lost…" and "It
+lives at specs/sugya.md, commit dc938058, pod shorashim-675b48f47-…".
+The transmitter asked why. The ledger, three hours old, answered: both
+were confident claims, and neither could be anchored in the system
+prompt or the transmitter's turns, which are what the gate counts as
+given. The verdict was right by the reader's rules.
+
+It was wrong about what happened. The Mishnah's two reasons had been
+read, that hour, from the second scroll through a tool; the commit and
+the pod had been read from the builder's own tool output. Both rested
+on something the model was given — tablet 49's word — and the gate's
+source reading took only the text and document blocks of a user turn,
+never a `tool_result` block, never a `tool` turn. A coding agent's
+conversation is mostly tool results. From the gate's view the builder
+asserted from nowhere what it had just read.
+
+And the second sentence should never have been a claim. It entered the
+grounding check as *vital* because the vitality test matched "Rashi"
+inside "shorashim": the pod's name wore a commentator's. A marker is a
+word, not a substring.
+
+Fixed: `tool_result` blocks and `tool` turns are sources (`Shape.
+sources`, both upstreams; the query stays the last *user* turn); the
+insight markers stand on word boundaries. Elixir 643/0, korban 294/0.
+
+The lesson is tablet 49's read once more, from the other side. There
+the check demanded Torah as content and condemned a model for not
+quoting it; here the check demanded the transmitter's words as the only
+ground and condemned the builder for standing on what it had read. In
+both the error was the same: the reader decided in advance what counts
+as given, and Torah's structure is that the source is what was *given*,
+whatever gave it. The ledger made the question answerable in minutes;
+the gate's verdict on its own builder found a true gap; and the false
+positive — *v'naki v'tzaddik al taharog*, Shemot 23:7 — was Torah's
+concern before it was the builder's.