docs: make the component sections executable in one pass

Expands 3.1 and 3.2 so the work can be done without re-deriving anything.

3.1 now records what 0.8.6 already fixed, separated into the ten components
that were miswired and the five that gained outputs they had been firing
undeclared, with the caveat that Map's three were converted but never confirmed
in a browser. For the 22 that remain it adds the finding that changes the
decision: all nine are pure scaffolds with no state, functions or handlers, and
five of them duplicate a component that already works -- FileUpload against
FileInput and FileUploadProgress, Toast and ToastNotifications against Toaster,
AdvancedDatePicker against DatePicker, AdvancedRangeSlider against RangeSlider.
Superseding those is a migration entry rather than new code, and leaves Chart,
TreeView, Confetti and CopyMarkup as the only ones needing to be built.

3.2 corrects the scaffold count from 23 to 28; the earlier figure used a looser
rule. Nine of the 28 are the 3.1 components, so the two items must be planned
together, and several of the rest are primitives that need only their styles
moved out of ui.css rather than any behaviour.

Also corrects the dead-output component count from 11 to 9 in both documents.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/ui-library-audit-2026-08-08.md

@@ -82,8 +82,9 @@ do arrive.
 
 A test pins this at 22 as a ceiling that only moves down.
 
-**23 components are still on the `wire-next` scaffold pattern** — no style
-block, no functions, and for 19 of them an outputs block they never honour.
+**28 components are still scaffolds** — no style block, no functions and no
+handlers. Nine of them also declare outputs nothing emits. (An earlier figure of
+23 here used a looser rule; see §3.2 of the remediation plan.)
 These are the same shape as the Table scaffold that was removed and the
 LayoutSplitter scaffold that was rebuilt.