@@ -107,9 +107,10 @@
  *   flows.<flow>.screens.<node_id>.title                       (#7646 / #11287)
  *   flows.<flow>.screens.<node_id>.fields.<field>.label
  *   flows.<flow>.screens.<node_id>.fields.<field>.placeholder
- *     ^ gated: `flows` is `planned` + `authorWarn` in the liveness ledger, so
- *       these are walked only once the row goes `live` (#11624 — see
- *       `authorWarnedTranslationGroups`)
+ *   flows.<flow>.screens.<node_id>.fields.<field>.inlineHelpText
+ *     ^ walked because the ledger's `flows` row is `live` and warns no
+ *       author; a group the ledger does warn on is left out of the walk
+ *       (see `authorWarnedTranslationGroups`)
  *   metadataForms.<type>.label / .description
  *   metadataForms.<type>.sections.<section>.label / .description
  *   metadataForms.<type>.fields.<dotPath>.label / .helpText / .placeholder
@@ -1067,8 +1068,9 @@ function walkObjectTabs(config: any, out: ExpectedEntry[]): void {
 }
 
 /**
- * Translation groups the shipped liveness ledger warns an author for authoring
- * — today exactly `flows` (`status: planned`, `authorWarn: true`).
+ * Translation groups the shipped liveness ledger warns an author for authoring.
+ * Today the set is empty: `flows`, the one group ever warned, is `live` now
+ * that both its halves are read, so nothing is gated.
  *
  * ## Why the walk surface is gated on this at all (#11624)
  *
@@ -1083,20 +1085,20 @@ function walkObjectTabs(config: any, out: ExpectedEntry[]): void {
  * `i18n/missing-*` family. Under `--i18n-strict` the demand side is an error,
  * so a project could be *forced* to author keys it is then warned for.
  *
- * ⛔ The warn side is not the bug and must not be softened. Only part of the
- * group is read: the console's screen-flow runner reads `screens`, but the
- * flow's own `label` is read by nothing yet (#20318), so a translated flow
- * label really is stored and never shown. The warn is group-level, so it still
- * covers the whole group. The demand is the half that is premature.
+ * ⛔ The warn side was not the bug, and it was not softened. While the
+ * console's screen-flow runner read only `screens`, a translated flow `label`
+ * really was stored and never shown, and the group-level warn said so. The
+ * demand was the premature half, and it is the half this gate holds back.
+ * The runner now names the flow by `flows.<flow>.label` too, so the row is
+ * `live` and the warn and the gate are gone together.
  *
  * ## Shape
  *
  * Group-general, not `flows`-specific, and read from the ledger rather than a
- * switch of our own: the day the row flips to `live` (dropping its
- * `authorWarn`; for `flows` that waits on #20318), the bucket turns itself back
- * on with no edit here — and any FUTURE group that acquires a warn is covered on
- * the day it is marked, rather than re-opening this collision one group at a
- * time.
+ * switch of our own: when the `flows` row flipped to `live` and dropped its
+ * `authorWarn`, the bucket turned itself back on with no edit here — and any
+ * FUTURE group that acquires a warn is covered on the day it is marked, rather
+ * than re-opening this collision one group at a time.
  *
  * The join is on the group (`path[0]`) and stops there deliberately: for
  * file-authored bundles the warn side only ever fires at that depth. Its
 
@@ -29,26 +29,24 @@
 // the spec-exported key face` test below pins list↔walker on this side, so a
 // hand-copied list here fails rather than silently offering a key nothing reads.
 
-// ## Why this file simulates a `live` ledger row (#11624)
+// ## Why this file simulates a `live` ledger row
 //
 // Everything below is the behaviour of the flow bucket ITSELF — which keys the
 // walker harvests, how the coverage report attributes them, what the skeleton
-// looks like. None of it changed in #11624. What changed is WHEN it runs: the
-// `flows` row in `@objectstack/spec/liveness/translation.json` is `planned` +
-// `authorWarn`, and `os lint` runs this bucket in the SAME pass as
-// `lintLivenessProperties`, so demanding the keys while the ledger warns
-// authors for writing them left the author with no move that satisfies both.
-// The bucket is now gated on that row, and it turns itself back on the day the
-// row flips to `live` (dropping its `authorWarn`; for `flows` that waits on
-// #20318).
+// looks like. WHEN it runs is the ledger's call: the bucket is gated on the
+// `flows` row in `@objectstack/spec/liveness/translation.json`. While that row
+// was `planned` + `authorWarn`, `os lint` would have demanded the keys in the
+// same pass that warned authors for writing them, leaving no move that
+// satisfies both, so the walk left the group out. The row is `live` now (the
+// runner reads the flow's own `label` as well as `screens`), and the bucket is
+// back on with no edit to the walker.
 //
-// So these pins are re-anchored, not retired: the mock below is the ledger
-// warning on nothing, i.e. exactly the post-flip world. Retiring them instead
-// would have left the flip with no proof the bucket still works, and a pin that
-// "passes" because the walker now emits nothing is the worst of both. The
-// GATED half — that none of this reaches an author while the row is `planned`
-// — is pinned next door in `i18n-flow-liveness-gate.test.ts`, against the real
-// shipped ledger.
+// The mock below pins the ledger to "warns on nothing", which today is also
+// the real ledger's state. It stays so that these pins keep measuring the
+// bucket whatever the shipped ledger says next: a pin that "passes" because
+// the walker emits nothing is the worst of both. The GATED half — what the
+// walk does for a group the ledger DOES warn on — is pinned next door in
+// `i18n-flow-liveness-gate.test.ts`, which also pins the real shipped ledger.
 //
 // The mock is fail-loud: if it stopped applying, every `expect(...).toContain`
 // below would go red rather than silently assert over an empty walk.
 
@@ -3991,10 +3991,11 @@ export function resolveFlowScreenTitle(
  * draws, read at the `.objectui-sha` pin `f8a9d0fb`, and the ledger's
  * `flows.screens` row is `live` citing it. This function stays unregistered
  * because the server-side route is not the one taken. `flows.<flow>.label`
- * takes the same client side: the authored label it falls back to reaches the
- * runner on every run result as `AutomationResult.flowLabel`, but nothing reads
- * the translation key on either side yet (the objectui runner half is still to
- * land), so its ledger row stays `planned`.
+ * takes the same client side: `FlowRunner` hands this function the authored
+ * label the engine serves on every run result as `AutomationResult.flowLabel`,
+ * and draws the answer (the API name when no label was served) in its header
+ * and its completion toast, read at the `.objectui-sha` pin `0abd4f9f8`. Both
+ * `flows` rows in the ledger are `live`.
  */
 export function translateFlow<T extends FlowLike>(
   flow: T,