fix(07-06): launch-gate decisions — KV cron retune to 720/day (the $0 law holds), brand sweep araharah→arah² across user-facing copy, menu button text

docs/BUDGETS.md

@@ -215,3 +215,12 @@ The launch gate (07-06) signs this record after the redeploy re-run:
 
 - Maintainer: __________________
 - Date: __________________
+
+## RESOLUTION (launch-gate decision, 2025-10-25)
+
+**KV-list over-ceiling: RESOLVED via the $0-safe retune.** Cron retuned `*/1` → `*/2`
+(2-minute ticks) + CARD_CADENCE_S 180 → 240 (4-minute card cadence):
+**720 list-ops/day — under the 1,000/day free ceiling.** The $0 law holds; no paid
+tier. Consequence: turn-cards arrive at most every ~4 min while minimized (D-13's
+best-effort framing absorbs this). Tests retuned (GC1/GC2/GC4/GC5*/GC-C timeline);
+126/126 green.

docs/KNOWN-LIMITATIONS.md

@@ -2,17 +2,17 @@
 
 # Known limitations
 
-araharah is a turn-by-turn navigator for the Kuala Lumpur metro, delivered inside
+arah² is a turn-by-turn navigator for the Kuala Lumpur metro, delivered inside
 Telegram: you search a destination with the bot (`/cari KLCC`), open the Mini App,
 and follow live route guidance built on OpenStreetMap data. It works today for real
-drivers, and it has real limits. This page lists what araharah does **not** do well —
-stated plainly, for two readers: a driver deciding whether araharah fits today's trip,
+drivers, and it has real limits. This page lists what arah² does **not** do well —
+stated plainly, for two readers: a driver deciding whether arah² fits today's trip,
 and a fork deciding what they are inheriting. Nothing here is a hidden defect; every
 claim names its evidence, and none of it is fixed by asking harder.
 
 ## Data coverage
 
-araharah routes over a snapshot of OpenStreetMap, and inherits OSM's gaps honestly:
+arah² routes over a snapshot of OpenStreetMap, and inherits OSM's gaps honestly:
 
 - **No traffic awareness.** There is no live traffic feed; the ETA is a
   distance-and-speed estimate from the route model, not a prediction.