fix: render value= in the iOS outline for TextArea, Slider, and Button

[onevcat]

Problem

The describe-ui text outline whitelists which roles get a value="…" tag (OutlineFormatter.valueBearingTypes), and the list stopped at TextField / SecureTextField / Switch. A multi-line editor surfaces as role TextArea (UITextView / SwiftUI TextEditor — the shape of real chat message inputs), so text typed into one was invisible in the outline whenever the element carries an accessibility label:

@10  TextArea  "Message editor"  #text-area-field  (16,236 370x160)        ← typed text nowhere

while --json had it all along (entries[].value: "hello textarea"). Agents driving an app via the outline (as the bundled skill recommends) could not confirm a type, paste, or clear landed without hand-rolling JSON spelunking.

Role-vocabulary research

The whitelist additions are grounded in a live probe of the AX bridge rather than the XCUIElementType names — the bridge speaks macOS-style roles, and several familiar names simply never appear. New playground screen Value Roles (SwiftUI + UIKit sections) is the reusable probe; measured on the iOS 26.5 bridge:

Control	Actual role	AXValue
UITextView / TextEditor	TextArea	typed text
UISearchBar	TextField (no SearchField role)	typed text
UISlider	Slider	thumb position
UIPageControl	Slider (no PageIndicator)	page 2 of 3 == label
UIDatePicker (wheels)	Slider ×N	== label
UIProgressView	GenericElement (no ProgressIndicator)	70%
UISwitch	CheckBox (not Switch)	0 / 1
DatePicker (compact)	Button	Sep 9, 2001
UIStepper / SwiftUI Stepper	2 × Button	none / current value

Fix

• valueBearingTypes += TextArea (the bug), Slider (thumb position), Button (compact date pickers / stepper halves whose AXValue is the only readable state).
• New guard: a value that merely echoes the label slot is suppressed — a label-less element already surfaces its value through the rawLabel fallback, so the tag would print the same string twice. Mirrors Android's AndroidClassifier.effectiveValue (text == label → nil). This also fixes the pre-existing TextField "query" value="query" double print, and keeps page controls / picker wheels (Slider with value == label) quiet.
• Not added: GenericElement (would drag every status-bar item's value into the outline) and CheckBox (its 0/1 needs an unchecked-style tag design, not a cryptic value="0" — follow-up material).

Android needs no code change: multi-line EditText keeps className android.widget.EditText → classifies as TextField → already value-bearing.

After (same screen):

@10  TextArea  "Message editor"  #text-area-field  (16,236 370x160)  value="hello textarea"

Fixtures & tests

• Playground iOS: new text-area screen (labeled TextEditor, the regression shape) and value-roles probe screen; Playground Android: labeled multi-line EditText on the text screen.
• Unit: 5 new OutlineFormatterTests pinning labeled/unlabeled TextArea, Slider echo suppression, Button value, and the TextField double-print fix.
• E2E: TypeTests "Typed text surfaces in the text outline for a labeled TextArea" (iOS) and AndroidTypeTests "typed text surfaces as value= on a labeled multiline field" (parity).

Verification

• make build + make test: 1259 passed, 0 failed.
• New iOS E2E test green against a booted iPhone 17 Pro (iOS 26.5); full TypeTests suite green (15 tests).
• New Android E2E test green against emulator (API 36); AndroidTypeTests + AndroidKeyboardStateTests green.
• Live spot-checks of the text-area and value-roles screens: TextArea/Slider/Button values render, page-control and date-wheel Sliders stay quiet, search-bar double print gone, status bar unchanged.

🤖 Generated with Claude Code