re: finish the --help audit -- a stale percentage and a missing noun, both shipped

The METHOD entry I wrote an hour ago says to read your tool's own --help as if a
stranger wrote it. I had done that for ONE of sixteen leaf commands, which is the
"a rule written down is not a rule applied" failure this corpus already records
twice. Finished it across the whole surface.

One survivor, and it fails in two ways at once. `screen render --settle` said a
narrow window means the bundle never settles, "(42 % of them, mostly loop*
fragments)".

MISSING NOUN: inside `screen render`, "them" reads as the builds you would render.
The 42 % is over composable bundles -- a different and much larger set including
~1 700 two-element fragments a user of that flag never renders. ui-settle-time.md
states its population precisely; the help inherited the number without it.

STALE: recomputed under the corrected reader, the composable figure is 862/2211 =
39 %, not 731/1758 = 42 %. The POPULATION GREW BY 453, which is the keyframe
record-layout fix's signature -- it times a group's final pose, so bundles that
previously showed one timed keyframe now show two and qualify. Third consequence
of that fix not being swept, after fade_quads.py and screen-transitions.md's
0.87-4.08 s fade-in.

And the share a --settle user actually faces is 38 %: 185 of 491 screen builds.

Corrected in the help text with all three numbers and their populations, and in
ui-settle-time.md, whose three-row table is marked pre-fix and superseded rather
than edited in place. Verified by artifact -- the tool's --help output is quoted,
not merely recompiled.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v

crates/sylpheed-cli/src/main.rs

@@ -213,9 +213,15 @@ enum ScreenCommands {
         /// Pose every element at the instant the screen is SETTLED, derived from
         /// the disc: the midpoint of the longest interval containing no keyframe
         /// of any element. Prints the window it used, whose width is how much the
-        /// midpoint is worth — a narrow one means the bundle never settles (42 %
-        /// of them, mostly `loop*` fragments). ⚠️ NOT established as better than the
-        /// resting pose — see the note on `--at`. See
+        /// midpoint is worth — a narrow one means the bundle never settles.
+        /// ⚠️ That is **38 % of the screen builds this command renders** (185 of
+        /// 491 carrying two or more keyframe times) and 39 % of the wider set
+        /// `--all` admits (862 of 2 211), mostly `loop*` fragments. This help used
+        /// to say "42 % of them" without saying of WHAT: 42 % was 731/1 758 over
+        /// composable bundles, computed before the keyframe record-layout fix,
+        /// which times a group's final pose and so admits ~450 bundles that
+        /// previously had only one timed keyframe. ⚠️ NOT established as better
+        /// than the resting pose — see the note on `--at`. See
         /// `docs/re/structures/ui-settle-time.md`.
         #[arg(long)]
         settle: bool,