docs: the four flow rulings, compare unparked, and the beta premise superseded

All four ruled, all four taking design-dev's recommendation, relayed via Miranda
with booth-dev as sole relay. Verbatim copy committed at docs/rulings/ because
the booth holding it will sweep.

Which is the observation worth keeping: answering a pick removes the hold that
was protecting the record. A booth is held while its question is OPEN, so its
lifetime is shortest exactly when it has just become valuable — before the
answer it is a question, after it is the record of a decision, and only the
first state is protected. Both design booths hit this by different routes, one
withdrawn and one answered. Raised to design-dev as a flow question rather than
patched, since flow is his now.

Compare mode leaves the parking lot: our deferral, his overrule, recorded as his
call so nobody re-parks it by reading the older rule.

And v1.0.0b1's 'no new features' promise no longer describes the arc. The tag
stays as written — rewriting a released tag to flatter the present is how a
version stops being evidence — an alpha drop-back is illegal because 1.0.0a2
sorts below 1.0.0b1, and no further pre-release is cut until the arc lands.

persistent-memory.md

@@ -59,6 +59,22 @@ _As of 2026-09-22:_
   ⚠ **Calibration for the next round: his bar is "did anything change when I
   opened it".** He said the Booth "kind of looks the same" about our own U7
   navigation work, before ever seeing the design round.
+- ✅ **ALL FOUR FLOW RULINGS ARE IN — A+B, compare THIS ARC, plain voice, no
+  emblem** (operator via Miranda D-0016, 2026-09-23 08:07). Every one took
+  design-dev's recommendation; no notes attached. **booth-dev is the SOLE RELAY
+  — the operator will not brief design-dev directly.** Verbatim copy at
+  `docs/rulings/2026-09-23-flow-direction.json`.
+  → `persistent-memory.d/2026-09-23-the-flow-rulings-and-what-they-cost-the-beta.md`
+- ⚠ **ANSWERING A PICK REMOVES THE HOLD THAT PROTECTED THE RECORD.** A booth is
+  held while a question is OPEN; the moment it is answered it becomes the record
+  of a decision and stops being held. Both design booths hit this, by different
+  routes (one withdrawn, one answered). **Capture a ruling into git, not into a
+  booth.** Raised to design-dev as a flow question rather than patched.
+- ⚠ **`v1.0.0b1`'s "no new features" PREMISE IS SUPERSEDED.** The arc now
+  contains a flow redesign and compare mode. The tag stays as written (it
+  records what was believed, not a claim about now), an alpha drop-back is
+  ILLEGAL (`1.0.0a2` < `1.0.0b1`), and no further pre-release is cut until the
+  arc lands. **Whether `1.0.0` waits for the redesign is UNDECIDED and his.**
 - 🔶 **ROUND 2 IS UP AND FOUR RULINGS ARE WITH THE OPERATOR** — booth
   `booth-flow-concepts`, ask `flow`: direction / compare / voice / emblem.
   Three directions (Desk, Reel, Bench), six screens each in dark+light, plus a