Trim comments across Rust and webapp source to direct one-liners (ticket 030)

Pass over src/*.rs, webapp/src/**, and the in-app "?" docs prose:
condensed multi-paragraph doc comments to single lines that state the
non-obvious why, deleted comments that only restated adjacent code, and
tightened the Docs.tsx help-panel wording. No logic, structure, or code
formatting changed — verified via cargo test (143 passed) and
tsc -b && vite build.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XFUNZwCvz3kcod3352ZR2o

webapp/src/components/CollapsibleSection.tsx

@@ -1,10 +1,7 @@
 import { useState } from 'react'
 import type { TimeRange } from './LogTimeline'
 
-/// localStorage key for which of the four primary sections (log viewer,
-/// params, metrics, dashboards) are collapsed (ticket 035). Mirrors
-/// LogPreview's VISIBLE_PARAM_COLUMNS_STORAGE_KEY pattern — one key holding
-/// a record of section id -> collapsed.
+/// localStorage key holding a record of section id -> collapsed, mirroring LogPreview's VISIBLE_PARAM_COLUMNS_STORAGE_KEY pattern.
 const COLLAPSED_SECTIONS_STORAGE_KEY = 'ottyl.collapsedSections'
 
 function loadCollapsedSections(): Record<string, boolean> {
@@ -27,10 +24,7 @@ function saveCollapsedSections(sections: Record<string, boolean>) {
   }
 }
 
-/// Persists a section's collapsed state across reloads. Deliberately
-/// returns only the boolean + setter — callers keep rendering their
-/// subtree, just hide it with CSS (`hidden`), so collapsing never unmounts
-/// in-progress form state.
+/// Returns only the boolean + setter, not a conditional-render helper — callers keep rendering their subtree and hide it with CSS (`hidden`), so collapsing never unmounts in-progress form state.
 export function useSectionCollapsed(sectionId: string): [boolean, (next: boolean) => void] {
   const [collapsed, setCollapsedState] = useState(() => loadCollapsedSections()[sectionId] ?? false)
 
@@ -59,8 +53,7 @@ export function CollapseToggle({ collapsed, onToggle }: { collapsed: boolean; on
   )
 }
 
-/// The four primary sections that can be popped out into their own tab
-/// (ticket 036) — matches the `?section=` query param a standalone page reads.
+/// The four primary sections poppable into their own tab; matches the `?section=` query param a standalone page reads.
 export type PopOutSectionId = 'log' | 'params' | 'metrics' | 'dashboards'
 
 function popOutUrl(section: PopOutSectionId, range?: TimeRange | null): string {
@@ -72,10 +65,7 @@ function popOutUrl(section: PopOutSectionId, range?: TimeRange | null): string {
   return `?${query.toString()}`
 }
 
-/// Opens this section, full-page and with no surrounding chrome, in a new
-/// tab. `range` is only needed for sections without their own LogTimeline —
-/// the popped-out page has no way to pick a range itself, so the current one
-/// is carried over via query params (see `App.tsx`'s standalone rendering).
+/// `range` is only needed for sections without their own LogTimeline — the popped-out page can't pick a range itself, so the current one is carried over via query params.
 export function PopOutButton({ section, range }: { section: PopOutSectionId; range?: TimeRange | null }) {
   return (
     <button