doorpost: move the pin to tablet 54's spec set (66aa7874…)

Tablet 54 (347f83cf) edited specs/bikoret_tamid.md and
specs/bishearecha.md — both in Doorpost's @spec_files — without
moving @expected_hash. The image built from it (:347f83cf = :latest,
rolled out 2026-10-15 17:19Z) logged DOORPOST_DRIFT_AT_STARTUP,
health went "degraded", readiness 503, and the site and the gate were
dark — every Claude Code session on the dev VM routes through the
gate, so the builder lost Anthropic too.

Reproduced the in-image value from git: the 29 spec files at 347f83cf
hash to 66aa7874fae4875793791ce6ca7bbe55302109d5e4444bcb36d578dfe6e98a0d
(cb18f719 → 58113312…, the old pin). The change is deliberate (tablet
54's text), so the pin moves. doorpost_test + step15_shema_test:
42 tests, 0 failures.

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

vav_pipeline/lib/vav_pipeline/doorpost.ex

@@ -180,7 +180,7 @@ defmodule VavPipeline.Doorpost do
   # changes; the update is a deliberate operator commit. A bare
   # hash-update commit (without a corresponding spec change in the
   # same commit) is itself a drift signal.
-  @expected_hash "581133126c483eea33d3eb79379cf2f0c54e221d8ae705d9e67da987086ed52a"
+  @expected_hash "66aa7874fae4875793791ce6ca7bbe55302109d5e4444bcb36d578dfe6e98a0d"
 
   @doc "Return the list of files that constitute the category-grade specification."
   @spec files() :: [String.t()]