tuile 0.10.0 → 0.11.0

data/DECISIONS.md

@@ -785,18 +785,25 @@ will follow.
   the mixin's split says chrome is `caption`. Tuile has no field-label seam
   yet; when one lands, a checkbox's caption should stay what it is — the
   clickable target, not a caption *for* another widget.
-- **Space toggles; Enter is left unclaimed, but not *promised*.** Space-to-flip
-  is the native gesture (Vaadin's checkbox is Space-only too) and a checkbox has
-  no default action to confirm, so there is nothing for Enter to do here.
-  Claiming a key you don't need is the irreversible direction — teaching Enter a
-  meaning later breaks nobody, taking it back breaks apps — and that, alone, is
-  why `handle_key` ignores it. It is emphatically **not** a promise that a
-  form's Enter-to-submit can bubble past a focused checkbox: no widget owes
-  that (`TextArea` claims Enter for newline, `Button` to activate itself), and
-  book ch5's Enter table states it per widget precisely because it is per
-  widget. A checkable row in a `List` toggles on Enter (`D-checkbox-group`) —
-  `List`'s own *choose the item under the cursor*, not a checkbox gesture, so
-  the two don't read as inconsistent.
+- **Space and Enter both toggle** (Enter added 2026-08-03; unclaimed through
+  0.10.0). Space-to-flip is the native gesture (Vaadin's checkbox is Space-only),
+  and the original ruling left Enter alone on the grounds that claiming a key you
+  don't need is the irreversible direction. What tipped it is *consistency with
+  the group components*: a checkable row inside a `List` toggles on Enter, since
+  Enter is `List`'s own choose-the-item-under-the-cursor gesture
+  (`D-checkbox-group`, `D-radio-group`). So `[ ] Verbose` flipped on Enter when
+  it sat in a `CheckboxGroup` and did nothing when it sat alone in a form — a
+  distinction the user cannot see, and one that reads as a bug in the standalone
+  widget rather than as restraint. One gesture set, both shapes, is worth more
+  than the option value of a key a checkbox has no other use for.
+  The consequence is explicit and accepted: a focused checkbox now **consumes**
+  Enter, so an ancestor's Enter-to-submit does not see it. That was never
+  promised — no widget owes it (`TextArea` claims Enter for newline, `Button` to
+  activate itself), and book ch5's Enter table states it per widget precisely
+  because it is per widget (see the rejected reservation below, which is why the
+  promise doesn't exist to break). An app wanting Enter-anywhere-submits binds it
+  on the ancestor *and* accepts that its focusable widgets each get first refusal.
+  Now that Enter is claimed, taking it back is the breaking direction — don't.
 - **No constructor block, but a `value:` kwarg.** `Button.new(caption,
   &on_click)` and `PickerWindow` are the gem's only ctor blocks, and both exist
   to *produce one outcome* — the callback is mandatory in practice. A checkbox
@@ -854,7 +861,9 @@ will follow.
   `ListDropdown::Menu` shape — a non-focusable `List` subclass plus
   hand-forwarded movement keys — to protect a guarantee nothing relied on
   (`D-checkbox-group`). Enter-reaches-your-form is a per-assembly property the
-  app verifies for its own focusable widgets, not a framework invariant.
+  app verifies for its own focusable widgets, not a framework invariant. Still
+  rejected, and now moot in both directions: the standalone widget claims Enter
+  too, which is what made the two shapes agree.
 - *Hit-test the whole `rect`:* activates clicks that visibly land on nothing,
   and `Rect#contains?` spans every row, so a click two rows below a visible
   `[ ]` would toggle it. Vaadin agrees — a 100%-wide checkbox ignores clicks
@@ -1860,7 +1869,13 @@ than sugar, since the composed label is what reads them — which is why both
 scale through one helper with exact endpoints (a full bar means done, and
 anything above zero lights a cell). And the bar is the first *animated*
 component, which is what turned an ordinary `super` in `repaint` into a
-measurable wire-traffic bug; AGENTS.md carries the resulting rule.
+measurable wire-traffic bug: `super` clears the background first, so
+`Cell#set` saw a real change on every cell of the bar and `flush` re-emitted
+the *entire* row five times a second instead of the one or two cells that had
+moved — **976 block glyphs per 1.2 s on the wire, versus 18** once the clear
+was scoped to the unpainted tail. That measurement is the evidence for the
+rule; AGENTS.md carries the rule itself ("never blank a cell you are about to
+paint over").
 
 ---
 
@@ -1959,3 +1974,593 @@ its row records keep character offsets and `chars_for_column` /
 plan the parked note assumed collapsed to one. Still out of scope and unfixed: a
 lone combining mark remains constructible via `text=` or by typing a mark into
 an empty field, which is input validation, not an axis question.
+
+---
+
+## D-float-field — `FloatField`: named for its Ruby type, and a deliberate copy of `IntegerField` (2026-08-07)
+
+**Status:** Accepted; implemented 2026-08-07 (`Component::FloatField`). The
+`Float` half of `D-integer-field`'s "derived parse" case — same wrapper shape,
+same taxonomy slot, so only what *differs* is recorded here.
+
+**Context.** Vaadin calls this a *Number Field*; the survey in
+`ideas/new-components.md` filed it as an "`IntegerField` twin". A second numeric
+field is where the naming rule and the shared-base temptation both had to be
+settled, because a third (`BigDecimalField`) is foreseeable.
+
+**Decision — name a typed field after the Ruby class its `value` is.**
+`FloatField#value` is a `Float`, so `FloatField`; `IntegerField#value` is an
+`Integer`. The name is then derivable rather than remembered, it says the
+precision out loud at the call site (`Float` is a binary double — the wrong type
+for money), and it leaves the obvious room for `BigDecimalField` /
+`RationalField`. `NumberField` was rejected: it names Vaadin's *widget*
+category, not this field's value, and it would force the eventual sibling to be
+"the other number field."
+
+**Decision — duplicate `IntegerField` rather than grow a base.** The two share
+~90% of their body (the `HasContent` shell, the `on_key` filter interceptor, the
+`fire_if_changed` guard) and differ in exactly the three places that matter: the
+filter, the parse, and the format. An `AbstractNumericField` with abstract
+`parse`/`format` hooks **is** the converter strategy `D-integer-field` kept out,
+reached through inheritance instead of a setter — and the `cop` rule is to
+duplicate rather than fold a shallow commonality into a base. The duplication is
+visible and boring; the base would be machinery.
+
+**Decision — the parse is lenient about partial buffers, the input filter is
+shallow.** `value` is a regexp-gated `String#to_f` — the private `NUMERIC`
+pattern: an optional sign, digits with an optional fractional part (either side
+may be empty, not both), an optional exponent. Not `Float()`, which raises on
+both `"1."` and `".5"`, so a `Float()`-based parse would blink the value to `nil` and back
+on the single keystroke between `"1"` and `"1.5"` — one spurious `nil` per
+decimal point, straight into every `on_value_change` listener. The regexp gate
+is what makes `to_f`'s garbage-tolerance harmless (it never sees garbage). The
+filter is correspondingly shallow — a digit anywhere, `-` only at index 0, `.`
+only if the buffer has none — so it keeps the buffer *typeable*, not always
+valid; `value` decides what parses. (`IntegerField` already worked this way: it
+lets a digit be typed before a leading `-`.)
+
+**Decision — the exponent is parseable but not typeable.** `Float#to_s` writes
+`1.0e-05` for extreme magnitudes, so `value = 1e-5` must read back — the parse
+accepts an exponent. No key types an `e`, though: admitting one would drag in
+"`-` after `e`" and break the "`-` only at index 0" rule for a notation nobody
+types into a form.
+
+**Decision — `value=` coerces with `Float()` and refuses a non-finite.**
+`Float::NAN.to_s` is `"NaN"`, which nothing parses, so writing one would make
+the field silently read back `nil` — a lost value with no error. It raises
+instead. Coercion also means `field.value = 3` shows `"3.0"`, which is the
+honest display of a `Float`-valued field.
+
+**Decision — Up/Down step by exactly `1.0`; there is no `step=`.** Same fixed
+spinner as `IntegerField`. A settable step is not free on a binary float:
+stepping by `0.1` accumulates `0.30000000000000004` straight into the visible
+buffer, so the knob would need a rounding policy (decimals? significant
+digits?), and rounding is formatting — a forms concern, parked with `min`/`max`
+in `D-integer-field`.
+
+**Alternatives rejected.**
+- *`BigDecimal` as the value type:* correct for money, but it needs the
+  `bigdecimal` gem, a decimals/scale policy, and `"0.1"` → `BigDecimal("0.1")`
+  string-round-tripping — a different field with a different name, not this one.
+- *Normalize the buffer on parse (`"007"` → `"7"`, `".5"` → `"0.5"`):*
+  rejected for the same reason as in `IntegerField` — canonicalizing needs a
+  blur/commit point a TUI lacks, and rewriting the buffer under the caret while
+  typing is worse than an ugly buffer.
+- *A locale decimal comma:* no locale seam exists in Tuile, and inventing one
+  for a single field would put i18n in the wrong layer.
+
+---
+
+## D-bigdecimal-field — `BigDecimalField`, and Tuile's first optional dependency (2026-08-07)
+
+**Status:** Accepted; implemented 2026-08-07 (`Component::BigDecimalField`).
+The third numeric field, so it inherits `D-float-field` wholesale (named for
+its Ruby value type, a deliberate copy rather than a shared base) — only the
+two things that are new are recorded here: exactness, and the packaging.
+
+**Context.** `D-float-field` closes with "the wrong field for money — hold that
+as `Integer` cents"; this is the field that makes the honest answer available.
+`BigDecimal`, though, is not a language built-in: it was a *default* gem
+through Ruby 3.3 and became a **bundled** gem in 3.4, so from 3.4 on a Bundler
+app must name it in its `Gemfile` or `require "bigdecimal"` raises.
+
+**Decision — ship it as an optional dependency, not a gemspec entry.**
+RubyGems has no optional/extras scope (no Maven `provided`, no Python extras),
+so the mechanism is convention: `lib/tuile/component/big_decimal_field.rb`
+carries the `require` itself, and Zeitwerk's laziness confines the cost — an
+app that never names the constant never executes the file. Three pieces make
+that hold, and all three are load-bearing:
+- The `require` is wrapped in a `rescue LoadError` that re-raises with the
+  actual fix (`gem "bigdecimal"`), since the bare message ("cannot load such
+  file") explains nothing about a gem that *is* installed but unbundled.
+- `loader.do_not_eager_load` on that one file, so a host app calling
+  `Zeitwerk::Loader.eager_load_all` — which Rails-shaped apps do — doesn't
+  raise on a component it never asked for. Pinned by a subprocess spec that
+  eager-loads everything and asserts `$LOADED_FEATURES` stays free of it.
+- The `require` **must not** be hoisted into `lib/tuile.rb` with the other
+  gem-level requires; that would impose the load on every user and defeat the
+  whole arrangement. This is the exception AGENTS.md's no-requires rule is
+  worded for.
+The accepted cost, stated plainly: the failure moves from `bundle install` to
+first use, so a missing gem surfaces mid-render in a raw-mode terminal rather
+than at boot. Worth it for one opt-in component; **not** a licence to make
+this Tuile's default posture — a second optional dependency needs its own
+argument.
+
+**Decision — normalize and format on both ends, rather than trusting
+`bigdecimal`.** Two of the three inputs behave differently across the versions
+Tuile supports: `bigdecimal` 3.1 (Ruby 3.3's default gem) *rejects*
+`BigDecimal("1.")` and `BigDecimal(0.1)`, while 4.x accepts both. So the field
+does its own work: a half-typed buffer is normalized (`".5"`→`"0.5"`,
+`"1."`→`"1"`) before parsing, and display goes through `to_s("F")` — plain
+notation, since `BigDecimal#to_s` writes `"0.1999e2"` for `19.99` and would put
+engineering notation in a form. The field's behavior is therefore identical on
+both, instead of tracking whichever parser the host resolved. Honest gap: the
+`Gemfile` resolves 4.x, so CI only ever exercises that one — 3.1 was verified
+by hand, and the normalization is what makes the difference unreachable rather
+than merely tested.
+
+**Decision — a `Float` is refused, not converted.** `field.value = 19.99`
+raises with a message naming the fix (`BigDecimal("19.99")`). The literal has
+already lost the decimal by the time it reaches the setter, and a field whose
+entire purpose is exactness should not be the place that quietly papers over
+it. That 4.x *would* accept it (via a shortest-round-trip conversion) and 3.1
+would not is the second reason: silently version-dependent precision is worse
+than a loud refusal. `Integer` and `String` coerce as normal.
+
+**Decision — the buffer is still never rewritten.** `"19.90"` keeps its
+trailing zero and `"007"` its leading ones, exactly as in the other two numeric
+fields: a display *scale* (pad to 2 decimals) is formatting, and formatting is
+the forms layer's, parked with `min`/`max`. Note the one place this shows
+through the value seam: `"1.0"`→`"1.00"` fires nothing, because the two
+`BigDecimal`s compare equal.
+
+**Alternatives rejected.**
+- *A hard `spec.add_dependency "bigdecimal"`:* makes every Tuile app carry a
+  gem for a component most won't use — and Tuile's dependency list is
+  otherwise TTY primitives and a loader.
+- *Accept a `Float` by converting through `to_s`:* that is a precision policy
+  ("shortest decimal that round-trips") hidden inside a setter. If it is ever
+  wanted, it belongs at the call site, where it is visible.
+- *A `scale=` / `decimals=` knob to pad the display:* it would have to rewrite
+  the buffer under the caret while typing (`19.9` → `19.90` mid-edit), which
+  needs a blur/commit point a TUI lacks — the same reason `D-integer-field`
+  gave for not normalizing.
+- *A settable `step=`:* `D-float-field` rejected it over binary-float noise,
+  which genuinely doesn't apply here (`BigDecimal` steps exactly). Kept out
+  anyway, so the three numeric fields stay one shape; this is the field to
+  revisit first if the knob is ever wanted.
+
+---
+
+## D-box-layouts — `Vertical` / `Horizontal`: declarative sugar with no `Auto` (2026-08-07)
+
+**Status:** Accepted; implemented 2026-08-07 (`Component::Layout::Box`,
+`::Vertical`, `::Horizontal`, and the `Fixed` / `Percent` / `Expand` / `Insets`
+value types on `Layout`). Book ch3 pre-approved the shape and named the
+acceptance criterion — "added if and when the convenience pays for itself" —
+so what this entry records is that it did, and every choice inside it.
+
+**Context.** `Layout::Absolute` was the only container: you override `rect=`
+and compute each child's rectangle. That is right for genuinely
+two-dimensional geometry and tedious for a stack. `examples/sampler.rb` carried
+**59 `Rect.new` sites**, dominated by vertical stacks with hand-accumulated
+offsets (`inner.top + 1`, `+ 4`, `+ 6`, `+ 8`, `+ 10`, `+ 12` in the
+PasswordField pane alone — renumbered by hand whenever a prompt gained a line),
+plus hand-rolled expansion (`[inner.height - 8, 2].max`) and hand-rolled cross
+clamps (`[inner.width, 30].min`). The cost was not that hand-rolling is
+impossible but that the code newcomers read to *learn* Tuile demonstrated the
+tedious version. The port took the sampler to 7 `Rect.new`.
+
+**Decision — the vocabulary is `Fixed` / `Percent` / `Expand`, and there is no
+`Auto`.** Shrink-to-fit is the bottom-up `content_size` channel deleted in
+v0.9.0, and AGENTS.md's re-grow rule allows measurement back only as an
+optional, caller-side query. So urwid's `PACK`, CSS `auto`, FTXUI's non-`flex`
+default and Swing's `GroupLayout.PREFERRED_SIZE` are all out by construction.
+**This single omission is what keeps the feature sugar rather than a reopened
+wound:** a box is an `Absolute` subclass with a `rect=` override — no new
+dispatch phase, no framework hook, no child consultation — so it deletes
+cleanly if it ever fails to earn its place.
+
+**Decision — alignment is legal because the cross extent is caller-supplied.**
+`align: :start | :center | :end` *looks* like it needs the child's width, which
+would be `content_size` again. It doesn't: it needs *a* width, and a `cross:`
+constraint provides one, so there is nothing to measure. This is the
+reframing that unblocked the cross axis after it had been parked as
+undesignable. Corollary: `:start/:center/:end` rather than
+`:left/:right` + `:top/:bottom`, because one concept should not have two
+vocabularies across the two classes.
+
+**Decision — `Expand`, not `Fill`.** Every toolkit that models *both* concepts
+reserves *fill* for cross-axis stretch, not for claiming slack: GTK's
+`pack_start(child, expand, fill, padding)` takes them as separate booleans and
+`fill` only acts when `expand` is already true; Swing splits them as `weightx`
+vs `fill`; JavaFX as `setHgrow` vs `fillHeight`. Vaadin 8 names only the first
+and calls it `setExpandRatio`. Naming our main-axis constraint `Fill` would
+therefore use the industry's word for cross-axis stretch — sitting right next to
+`Percent[100]`, the thing that actually stretches. `Expand` also leaves `Fill`
+permanently free, so it can never return as a confusing near-synonym. (ratatui
+does call it `Fill` and CSS `flex-grow`; neither models the stretch concept
+separately, so neither had the collision to avoid.)
+
+**Decision — defaults are `Fixed[1]` on the main axis and `Percent[100]`
+across it.** `Fixed[1]` because forms are the use case and almost every field is
+one row tall — the same reason Vaadin 8 bumps everything to the top by default.
+`Percent[100]` rather than `Expand[1]` because the cross axis holds exactly one
+child per slot, so nothing competes and a weight has nothing to mean there;
+**`Expand` therefore raises when passed as `cross:`**, which makes "what would
+`Expand[2]` mean across the axis?" unaskable rather than merely undocumented.
+JavaFX reached both defaults independently (`VBox.fillWidth` is `true`,
+alignment is `Pos.TOP_LEFT`).
+
+**Decision — `spacing` and `padding` are box-global, never per-child.** Beyond
+brevity: *a gap between two items is a property of the sequence, not of either
+child*, so a per-child gap has an unresolvable ownership question — does child N
+own the gap after it, or child N+1 the gap before it? Both conventions exist and
+both confuse. Non-uniform gaps are expressed by **nesting** instead: a
+`Vertical.new(spacing: 0)` inside a `Vertical.new(spacing: 1)` groups rows
+tightly within a looser stack, which *states* the grouping rather than faking it.
+`GridBagConstraints.ipadx`/`ipady` is the per-child version, and that class —
+eleven fields, and the layout manager everyone agrees is hardest to learn — is
+the named tripwire for this tuple growing past three.
+
+**Decision — `Percent` and `Expand` divide space that is actually available**
+(`extent - padding - spacing * (children - 1)`), so two `Percent[50]` children
+fit exactly instead of overflowing by the gap between them.
+
+**Decision — the weighted-`Expand` remainder goes to the earliest children, one
+cell each.** Five equal `Expand`s in 12 rows give `3,3,2,2,2`. Auditable in one
+sentence, exact sum structural (`base * n + remainder == total`), and leftmost-
+first is the ecosystem convention (CSS `flex-grow`, ratatui `Fill`, urwid
+`weight`) so a user coming from elsewhere guesses right.
+
+**Decision — over-subscription starves in declaration order; it never raises.**
+`Fixed` and `Percent` clamp to what is unassigned, so a child with nothing left
+gets an empty rect and paints nothing (`Rect#empty?` already covers zero *and*
+negative). Padding wider than the layout does the same to every child. No error,
+no solver, no reflow.
+
+**Decision — `Insets` is keyword-only.** `java.awt.Insets` orders the four
+numbers top-left-bottom-right and `javafx.geometry.Insets` top-right-bottom-left
+— the same class name and the same four numbers, silently different: a live
+migration bug between two toolkits *in the same language*. `Insets[top: 1]` has
+no order to get wrong. `Data`'s inherited `[]` never dispatches through a `new`
+override, so both class methods carry the guard (found by the spec, not by
+reading).
+
+**Decision — `Box` is a shared base, against the duplicate-don't-DRY rule.**
+`D-float-field` says duplicate rather than fold a *shallow* commonality into a
+base. This isn't shallow: the greedy pass is substantial and byte-for-byte
+identical except for which of `(left, top)` / `(width, height)` it reads, so
+`Box` parameterizes it behind two private hooks and `Vertical` / `Horizontal`
+are ~10-line concretes. That is the sanctioned cohesive base
+(`AbstractMasterDetail`), not an `AbstractView` junk drawer.
+
+**Alternatives rejected.**
+- *A constraint attribute on `Component` (`child.layout_constraint = …`):*
+  `content_size` wearing a hat. Even with the parent still doing the arithmetic,
+  it re-establishes "the child declares its size wish", and every non-layout
+  parent would have to ignore it. The constraint belongs to the parent–child
+  *relationship*, which is why it lives at the `add` call. **JavaFX is this
+  option in production and confirms the cost:** `HBox.setHgrow(node, …)` stores
+  the constraint on the node (hence `HBox.clearConstraints`), so you must recall
+  which container's static setter applies and a reparented node silently keeps
+  stale constraints.
+- *A block-valued cross constraint (`Left { |avail| [avail, 30].min }`):*
+  permitted by the re-grow rule, but no case needs it — `Fixed` already clamps to
+  available, which is exactly the `[inner.width, 30].min` the sampler wrote by
+  hand. A block is un-inspectable, awkward to spec, and `Absolute` remains the
+  escape hatch for a genuinely computed width.
+- *"Last `Expand` absorbs the remainder":* matches ch3's hand-written idiom and
+  guarantees an exact sum structurally, but degrades badly past two children —
+  five equal `Expand`s in 12 rows floor to 2 each and dump **4** on the last, a
+  visible 2× discrepancy, which is ch3's "one cell off is plainly visible on a
+  character grid" amplified rather than avoided.
+- *Trailing-first one-at-a-time (`2,2,2,3,3`):* same fairness, and it would match
+  ch3's remainder-to-the-right for the two-child case. Genuinely close; lost to
+  ecosystem convention. **Known consequence:** for two children the layout gives
+  the spare cell to the left/top while ch3's hand-written example gives it to the
+  right. Different mechanisms, no shared code; ch3 says so.
+- *Largest-remainder / Hare quota:* fairest, least auditable — reverse-
+  engineering which child got the extra cell is precisely the solver opacity ch3
+  rejects.
+- *Priority tiers instead of weights (JavaFX `Priority.ALWAYS/SOMETIMES/NEVER`):*
+  sidesteps remainder arithmetic entirely, but cannot express a 1:2 split, which
+  is what a sidebar wants. Vaadin 8's ratio and CSS `flex-grow` both chose
+  weights.
+- *`Min` / `Max` constraints:* deliberately not shipped, and the sampler shows
+  what that costs — its main split (`(width / 3).clamp(20, 40)`) and its two
+  sidebars (`min(16, width / 3)`) are caps on a *proportion*, unsayable in three
+  constraints, so they keep a rect-callback `Absolute`. That is the intended
+  division of labour: only the part needing arithmetic has any. Revisit only if
+  capped proportions turn out to be common.
+- *`BorderLayout` / `BorderPane` / Textual's `dock:`:* nesting
+  `Vertical(Fixed, Expand, Fixed)` covers it, and `ScreenPane` (content + status
+  bar) already *is* one, hard-coded.
+- *Swing glue (`Box.createVerticalGlue`, `createRigidArea`, struts):* invisible
+  filler *components*, needed only because `BoxLayout` has no per-child weight
+  and doesn't pack from the start. Packing from the start plus `Expand` needs
+  none, and grouped gaps are handled by nesting.
+- *Baseline alignment (Swing's `anchor` has `BASELINE`, `ABOVE_BASELINE_LEADING`,
+  …):* a text-*rendering* concept. Every row of a character grid shares one
+  baseline, so it is meaningless here.
+- *A full engine (Textual's CSS, Ink's embedded Yoga, ratatui's Cassowary
+  solver):* those frameworks must ship one — Ink and Textual are retained-mode
+  declarative, where the author never sees a rect, and ratatui's `Layout::split`
+  is the only way to obtain one. Tuile hands the author coordinates, so **once
+  `rect=` exists a layout is strictly optional sugar**, declinable per component,
+  which none of them can offer. (This nuances ch3's "validated by the ecosystem":
+  simple layout is validated by TUI *app architecture*, not by framework feature
+  sets.)
+
+**Consequences.**
+- Vaadin 8's perennial support question — *"`setExpandRatio` does nothing"*,
+  answered by "the child also needs `setSizeFull()`" — exists precisely because a
+  Vaadin 8 component has **both** its own size and an expand ratio: two size
+  channels that must agree. Tuile cannot have that bug, because there is no
+  component-side size to disagree with the constraint. The most common confusion
+  in the toolkit we took `Expand` from is a direct consequence of the channel
+  v0.9.0 deleted.
+- A future `Layout::Grid` should reuse `Fixed`/`Percent`/`Expand` verbatim per
+  row and column, as JavaFX's `ColumnConstraints(percentWidth, hgrow)` does,
+  rather than inventing a second vocabulary. That is also the path to the Form
+  Layout `ideas/new-components.md` wants — which is blocked on a field
+  label/helper seam, not on layout.
+
+---
+
+## D-wrap-leading-space — An indent is content; no flag, and no hanging indent (2026-08-12)
+
+**Status:** Accepted; implemented 2026-08-12 (`StyledString#wrap_one`). Fixes
+[issue #2](https://github.com/mvysny/tuile/issues/2). The continuation half —
+hanging indent — is deliberately deferred, see the last section.
+
+**Context.** `wrap_one` dropped a leading whitespace run whenever `line_w` was
+zero, which is equally true at the start of the *first* row as at the start of
+a continuation. So an indent never survived, even when the line fit the width
+and no wrapping happened at all. Since every `TextView` line goes through
+`wrap`, indented text could not be displayed: the downstream report was a
+nested agent/tool tree flattened into an ambiguous list, siblings and children
+indistinguishable and repeated leaf names reading as duplicates.
+
+**Decision — this is a bug, patched in place; no opt-in flag.** `wrap`'s own
+rdoc already promised the fixed semantics ("leading whitespace dropped on
+wrapped *continuations*"), so the code was not implementing a design, it was
+missing a condition. Every widely-used wrapper agrees, and they differ only on
+what happens to continuations — the half Tuile already had right:
+
+| Implementation | First-line indent | Continuation |
+|---|---|---|
+| Python `textwrap` (`drop_whitespace`) | kept — the docs carve it out explicitly | dropped |
+| CSS `pre-wrap` | kept | hangs past the margin |
+| GNU `fmt`, Emacs adaptive-fill | kept | **reused as the prefix** |
+| `fold -s` | kept (whitespace untouched) | kept |
+| Rust `textwrap`, Go wordwrap | kept (`initial_indent`) | `subsequent_indent` |
+
+CSS `white-space: normal` is the one that looks like a counter-example and is
+not: eating the indent happens in the **collapsing** stage, which also squashes
+every interior run to a single space. Tuile does not collapse (`"one  two"`
+keeps both spaces when they fit), so it is in the `pre-wrap` family, and doing
+half of collapsing — eat the indent, keep interior runs — was the incoherence.
+
+**A flag was rejected on three counts.** It has no defensible default
+(default-preserve is the patch plus dead config; default-drop keeps the bug
+reachable and makes every caller learn a piece of trivia); `TextView` calls
+`wrap` itself with the viewport width, so a flag on `StyledString#wrap` is
+useless until mirrored as a `TextView` setter, turning one wart into two knobs
+across two layers; and the blast radius of just fixing it is confined to
+strings whose first row opens with space or tab, with `TextView` the sole
+in-gem caller.
+
+**Decision — an over-wide indent is dropped, not given a row.** An indent that
+alone exceeds `width` folds into the same guard
+(`line_w.zero? && (!result.empty? || w > width)`) rather than falling through
+to the flush branch, which emitted an empty leading row. An indent wider than
+the viewport conveys no nesting, so losing it beats spending a row on it.
+
+**Decision — whitespace-only input is preserved, diverging from Python.**
+`plain("   ").wrap(5)` now returns `["   "]` rather than `[""]`. Python drops
+it (its rule is "not dropped *if non-whitespace follows*"), but matching that
+needs a lookahead and buys nothing visible: `TextView#pad_to` pads to width, so
+the two render identically. The simpler rule — the first row keeps its leading
+run, period — wins.
+
+**Deferred: the hanging indent.** A continuation still starts at column 0, so a
+leaf long enough to wrap re-lies about the tree — worse than the flattening,
+since a wrapped fragment of a deep leaf looks exactly like a new top-level
+entry. There is no app-side workaround (`TextView` owns the width and calls
+`wrap` internally, so a caller cannot wrap at `width - indent` and prefix). It
+is left out of this entry because it is a genuine behavior decision of its own:
+auto-inherit the first row's whitespace run as the continuation prefix, à la
+`fmt`/Emacs, versus an explicit knob that would again need mirroring on
+`TextView`. Current lean is auto with no flag — prose carries no leading space,
+so it is a no-op there, and the indented case is the only one with an opinion.
+
+---
+
+## D-select — `Select`: the enum field, claiming no printable key but Space (2026-08-12)
+
+**Status:** Accepted; `Component::Select` implemented 2026-08-12, demoed in the
+sampler. Builds on `D-has-value`, `D-combobox` (the chrome/value split and the
+resolve-don't-store-an-index rule, both adopted verbatim), `D-radio-group` (the
+cursor-is-chrome rule) and `D-ambiguous-width`.
+
+**Context.** A one-row closed-choice field: a face showing the selected item's
+label plus a `▾`, dropping open a `ListDropdown` of the options. `D-combobox`
+deferred it once ("filterable first"), on the assumption that it needed the
+read-only-field axis `D-has-value` parked for the forms layer. That assumption
+was an artifact of picturing a read-only `TextField` as the face; nothing gates
+this component.
+
+**Decision — the criterion is enum vs. data, not item count.** A Select is for
+labels the *developer* authored: a closed set, stable order, known when the code
+is written (log level, sort order, line endings, Yes/No/Ask). A `ComboBox` is for
+items the app supplies at runtime, open-ended, with labels you don't control
+(countries, users, branches). Count is a *symptom*: a 12-value enum is still a
+Select, and a three-row country list from a DB is still a ComboBox, because next
+release it is 200 rows and the widget choice must not have to change. The
+discarded rule — "≤ 7 items → Select" — is actively harmful: it invites that
+country list in, which is how the type-ahead hole below was found.
+
+**Decision — it claims no printable key but Space.** Enter, Space, ESC,
+`ListDropdown::MOVE_KEYS` and the mouse; *every other* printable bubbles past it
+to the app (key-dispatch rung 3). That is the capability unreachable by
+configuring a `ComboBox`, whose field eats printables unconditionally, and it is
+worth more than the type-ahead it replaces: a form's `s`-to-save and a layout's
+`1`/`2`/`3` pane jumps keep working while focus sits in a Select. Combined with
+having no caret — the strongest affordance a TTY has, not to be spent promising
+free-text entry over a four-value enum — that is the whole case for the
+component existing next to `RadioGroup`.
+
+Space is safe as the single exception because **it was never available as a
+bubble key anyway**: `Button`, `Checkbox` and `RadioGroup` all already claim it,
+so no app can rely on it reaching past an interactive widget. Contrast a letter
+like `g`, which reaches the app from every one of those and is exactly what the
+rule protects. Space mirrors Enter throughout (opens when closed, commits when
+open), as on `Button`/`Checkbox`; `RadioGroup` claiming Space but not Enter is
+inherent — it has no open/closed state to move between — not an inconsistency.
+
+**Decision — Home/End are declined, and `MOVE_KEYS` is unchanged.** They stay
+reaching the app, which `Screen::EDITING_KEYS` deliberately allows ("binding them
+app-wide to scroll the log pane is a real use case"). The PgUp/PgDn asymmetry is
+principled: those arrive *free* inside `MOVE_KEYS` and do real work on a dropdown
+that scrolls, whereas Home/End would need Select-side branches to do what a second
+arrow press already does. This also resolves what read as an open question in
+`ListDropdown`'s rdoc: the *exclusion* survives, the *rationale* doesn't — "they
+belong to the driving field, for caret movement" is a ComboBox policy, not a
+property of dropdowns. The driver decides, and both drivers decline.
+
+**Decision — `Select` paints its own row; it composes no field.** A leaf widget
+(`< Component` + `HasValue`, `tab_stop? = true`, no children) that owns the
+dropdown as an overlay. Two consequences worth naming:
+
+- **The face is *derived* from `value` at paint time, never a synced copy.** A
+  `Label` child would have meant a second copy of the face text to keep in step
+  from `value=`, `item_label=` and construction — the drift `ComboBox` pays for
+  only because its field is genuinely editable and holds a *query*. Nothing here
+  needs that, so nothing here has it. The well is read from the theme each paint
+  for the same reason.
+- **The tab-stop rule stays ordinary.** The composing wrappers (`ComboBox`,
+  `IntegerField`, the groups) leave `tab_stop?` false because their inner widget
+  carries the stop; a Select has no inner widget, so it claims the stop itself,
+  exactly as `Checkbox` does. Had the face been an (inert, non-tab-stop) `Label`
+  child, Select would have been the first composing wrapper needing to claim the
+  stop anyway — the letter of the rule reversed to preserve its purpose. Not
+  having the child removes the wrinkle instead of documenting it.
+
+**Decision — promote `ComboBox#anchor` to `ListDropdown#anchor_to`.** Select needs
+byte-identical vertical geometry, and `D-float-field`'s duplicate-don't-DRY rule
+**does not apply**: that licensed copying a *shell* around three genuine
+differences, whereas this is the same computation with zero differences, so a
+later fix to the flip rule would land in one copy and silently not the other —
+and the symptom appears only near a screen edge, which is invisible under test.
+The promotion threshold is the project's existing one (`D-color-slots`: "a
+*second* built-in needing the same thing"). Two rulings ride along:
+
+- **Width stays a caller-supplied parameter** (defaulting to the anchor's), so
+  `ComboBox` keeps its lines-up-with-the-field policy and Select keeps its
+  measured one, and `anchor_to` never measures content itself. Same shape as
+  `D-box-layouts`' "`align:` is legal only because the cross extent is
+  caller-supplied", and it keeps Select's measuring within the top-down re-grow
+  rule: an optional, caller-side query feeding a rect the caller then assigns.
+- **Horizontally we slide, vertically we flip.** Covering the driver would hide
+  the value being chosen, so vertically there are only above and below; sharing
+  the driver's columns is exactly what's wanted, so an overrun slides left and
+  keeps the left edges aligned. A horizontal flip would either overlap the face
+  or leave a gap. A label wider than the screen clips — `List` has no horizontal
+  scrolling.
+
+This is deliberately *not* the full anchored-Popover extraction, which wants
+generalizing for callers whose anchoring genuinely differs (a context menu
+anchors to a *point*, a submenu to a right edge with horizontal flipping). Build
+Popover when the second *kind* of anchoring appears, not the second caller of the
+same kind; `anchor_to` then moves down to it with nothing thrown away.
+
+**Decision — a scrolling `ListDropdown` gets a scrollbar** (a `ComboBox` fix
+shipped in the same work, and the only non-additive part of it). `anchor_to` owns
+the toggle, being the one place that knows both the row count and the height it
+just chose. *Rejected: an `:auto` mode on `List`.* It looks like the general fix
+and carries a silent corruption — visibility would become a function of
+`rect.height`, but the padded-line cache is rebuilt from `on_width_changed`, a
+width-only hook, so a height-only resize would flip the scrollbar, shrink
+`content_width`, and leave every row padded to the old width: one column off,
+no exception, nothing in the diff to notice. Making it safe means a height-change
+hook and a wider cache-invalidation surface for every `List` in the gem, to serve
+two callers that already know the answer.
+
+**Alternatives rejected.**
+- *Prefix type-ahead, single-key* (`g` jumps to the first item starting with
+  `g`): silently wrong. With Finland / Fiji / Jamaica, typing `fij` selects
+  *Jamaica* — each key is a fresh single-char match — and nothing tells the user
+  anything went wrong.
+- *Prefix type-ahead, timed accumulating buffer* (the standard GUI fix: `JList`,
+  GTK, Finder): it **is** the ComboBox query, hidden. A buffer that filters the
+  candidate set is a query string; concealing it and clearing it on a timer makes
+  it worse, not lighter, and reintroduces the second piece of state Select exists
+  to avoid. If you are holding query state, showing it is strictly better — and
+  showing it is a ComboBox. Worse here than in a GUI for a TUI-specific reason:
+  the timeout leans on inter-keystroke timing, and a terminal degrades exactly
+  that signal (bytes arriving in one read burst merge into a single key; a paste
+  has no gaps at all). Retiring type-ahead also retires the "make labels
+  prefix-unique" workaround that existed only to rescue it.
+- *Cycle-in-place* (`◂ Dark ▸`, Space/Left/Right, no popup) for 2–4 options: you
+  select blindly. The values you are choosing *between* are never on screen — you
+  discover them one at a time by cycling, with no way to see the set or know how
+  many there are. The dropdown is better at every item count, so the
+  `ListDropdown` face is the only face, and the vocabulary does not grow a fourth
+  closed-choice widget (cf. `D-box-layouts`' "there is no `Auto`"). *Re-grow
+  rule:* if it returns it is a **face** on this component (a `dropdown: false`
+  knob over the identical value seam), never a separate component, and it needs a
+  real argument about visibility rather than a row-budget one.
+- *A read-only `TextField` as the face* (the survey's framing): a read-only text
+  field is still a text field — the inherent-bg well, the caret machinery, the
+  horizontal scroll window, and an opt-out from `bg_color` inheritance. None of
+  it is wanted, and none of it has to be reasoned about once the widget paints
+  one row itself.
+- *A shared base with `RadioGroup`* (`AbstractClosedChoiceField`): the ~15-line
+  `items=` / `item_label=` / `label_for` shell is duplicated instead, per
+  `D-float-field`. The test is whether the commonality is a *shell around genuine
+  differences* or the *same computation* — `anchor_to` is the latter (extract), the
+  items shell is the former (duplicate). The three differences a base would have
+  to paper over with hooks: row rendering (`(*) label` glyphs vs. a bare label,
+  since a Select shows its selection on the *face*), cursor semantics (roams and
+  Space commits the row it's on, vs. the highlight *being* the pending selection),
+  and where the rows live (always, in the component's own rect, vs. only while
+  open, in a `Popup`'s). Three hooks over fifteen lines, reached through
+  inheritance, is the converter-strategy-by-inheritance shape `D-float-field`
+  rejected — and it would couple two widgets that should stay free to diverge.
+  This is the third copy of that shell, the same count `IntegerField` /
+  `FloatField` / `BigDecimalField` reached; a *fourth* is when to re-argue it.
+
+**Consequences.**
+- *Empty value* (`value = nil`, items present) is legal and normal — the optional
+  enum field — so there is no placeholder string: a blank face plus the `▾`, and
+  the dropdown opens with the highlight on row 0.
+- *Empty items* does not open a dropdown at all, keeping `ComboBox`'s auto-close
+  behavior: a 10-row empty tinted panel reads as a broken list rather than as
+  "nothing to pick". An item-less Select is almost always a programming bug, not
+  a state to design a UI for, so nothing is spent on it beyond not misleading the
+  user — no placeholder row, no "(no items)" label, no status hint. A
+  `Tuile.logger.warn` on the open attempt was considered and declined: the
+  attempt is keystroke-driven, so it would flood a host's log on autorepeat, and
+  an app may legitimately pass through item-less while loading. Enter/Space/Down
+  are claimed either way — one rule, no branch. (An item-less Select is arguably
+  a *disabled* field, which touches the read-only/disabled axis `D-has-value`
+  parked for the forms layer. Not designed here, not foreclosed either.)
+- The dropdown is measured to the widest label plus `List`'s **two** row gutters
+  (`pad_to_row` ellipsizes to `content_width - 2`, one leading and one trailing
+  column), plus the scrollbar column when the items outnumber the visible rows —
+  and never narrower than the Select itself. The field width is a *floor* rather
+  than an alternative to measuring: a panel narrower than its own face reads as an
+  unrelated widget instead of as that field's menu (a ~8-column menu under a
+  30-column field, in the sampler), so the common case lines both edges up exactly
+  as a `ComboBox`'s does and only an over-long label pushes it wider. A dropdown
+  the *screen* clamps shorter still scrolls without having bought the scrollbar
+  column, so its labels ellipsize one early — the `ComboBox` trade, in the one
+  case measuring cannot predict.
+- A second driver **confirms** three of `ListDropdown`'s speculative rulings
+  rather than straining them: ESC and Enter really do carry driver-specific tails
+  (Select's ESC closes without committing and has no query to revert), the
+  non-focusable `Menu` really does give the same re-entrancy safety
+  `ComboBox#active=` leans on, and filtering / row rendering / the commit action
+  really do vary.