docs: align guides with 0.7.33 screen-process architecture + recent feature coverage

[GenericJam]

Audit of every guide, the README, and the public moduledocs against current master (0.7.34 + #103). The moduledocs written alongside MOB-108–114 were already accurate; the drift was concentrated in the guides and a few docstrings that predate the work. Sections marked rewrite replaced a wrong model; everything else is a surgical edit.

Per-doc changes

guides/navigation.md

• Tab bar / Drawer sections (rewrite): claimed native chrome (UITabBarController / NavigationBar / ModalNavigationDrawer) that is not drawn — now describe the multi-stack runtime honestly, with the :tab_barwidget + switch_tab/2 as the interim chrome path.
• New Tabs and multi-stack state section: lazy materialization, parking, independent histories, back-at-secondary-root, the orphan stack, MOB-115/116/117 gaps.
• switch_tab/2 semantics (first visit mounts root, no-op cases, no animation); directional resets gain the ArgumentError validation (incl. why :none is rejected) and the transition-survives-coalescing behavior (feat(navigation): allow directional resets #100/fix(navigation): preserve initial transition #103).
• Tap examples fixed from handle_event("tap", %{"tag" => ...}) to handle_info({:tap, tag}) — the shape a real tap delivers.

guides/screen_lifecycle.md (edits — the process-model intro was already updated by #101)

• New Crashes and restarts section: per-screen isolation, restart cap (5/10s), re-mount + load_state/2, per-screen self() and message delivery.
• terminate/2: when it actually runs, persisted-state dump, pop stops only the leaving screen.
• System back: multi-stack semantics (secondary-stack root switches to the first stack; only the first stack's root exits).

guides/testing.md

• New leading section on Mob.ScreenCase (Mob.ScreenCase: blessed in-BEAM screen testing (+ contract check, device backend) #44) — previously undocumented in any guide.
• Removed Mob.Test.screen_pid/1 (does not exist) and the :sys.get_state(:mob_screen) sync-point advice (insufficient since MOB-110/112); replaced with Mob.Test.settle/2 and an explanation of the three processes it drains.
• Unit-test examples corrected for the process model (synchronous dispatch/3 for navigation; get_socket/1 as the natural sync point after send).

guides/components.md

• New :sheet section: Mob.UI.sheet/2 / <Sheet> (0.7.29), presence-is-presentation, intrinsic [:content] detents (0.7.32), exactly-once {:dismiss, tag}, iOS scrim limitation. Only the surface-matrix row covered sheets before.
• New Handle limits section: 256 tap handles per frame (handler silently unwired past the cap, logged) and 256 native component slots ({:error, :component_slots_exhausted}) — 0.7.28 behavior.
• :text gains the font prop row (named font tokens, 0.7.25).

guides/theming.md — fonts were absent entirely; adds the fonts: / font_fallback: token type (0.7.25) with a pointer to Styling → Custom fonts (which already covered the mechanics).

guides/agentic_coding.md (restructure into two halves, existing content order preserved)

• Working with one agent: existing content plus verify-effects-not-exit-codes, the honesty contract (assert on state change; settle-window caveat), match-the-evidence-to-the-question, lifecycle-event simulation recipes (simctl push .apns, adb broadcast / cmd notification post), environment discipline (.tool-versions completeness, MOB_DIR/MOB_DEV_DIR/MOB_NEW_DIR). The standard loop gains a settle/2 step; the worked example's handle_event slip fixed.
• Working with agent teams (new): one driver per device + lease discipline, unique node names (mob.connect --name), per-task worktrees, the mob.push/mob.watch fan-out hazard (verified: no device scoping — switches are --all/--cookie only), durable artifacts.

README.md — counter example handled taps in handle_event("tap", ...), which a device tap never reaches; now handle_info({:tap, :increment}) with a sentence on delivery. Diagram node updated to Mob.Screen.Server (one per live screen). Testing snippet moved to Mob.ScreenCase.

guides/device_capabilities.md — four handle_event("tap", ...) examples → handle_info({:tap, ...}).

guides/getting_started.md — referenced Mob.Nav.push/2, which does not exist; now Mob.Socket.push_screen/2,3.

guides/event_audit.md — list-select re-emitter is Mob.Screen.Server since MOB-113.

lib/mob/app.ex — tab_bar/1/drawer/1 docstrings no longer claim chrome that is not drawn.

lib/mob/test.ex — moduledoc claimed tap/2 goes through handle_event/3; it sends {:tap, tag} to handle_info/2.

mix.exs — Mob.Router, Mob.Screen.Server, Mob.Listener, Mob.Sender, Mob.ScreenCase were shipping ungrouped in the hexdocs sidebar.

Deliberately not documented

• Mob.Sender.activate/2's one-shot transition reservation (fix(navigation): preserve initial transition #103) and other sender/listener internals — user-visible effect ("a navigation's animation survives coalescing") is stated in navigation.md; the mechanism lives in the moduledocs/ADRs.
• Tap-honesty error tuples — iOS harness: stop tap_xy reporting phantom successes; add pixel sampling for colour #80 has not mergedUpdated after iOS harness: stop tap_xy reporting phantom successes; add pixel sampling for colour #80 and fix: cold-start launch notifications dropped before nif_load (Android + iOS) #77 merged and the branch was rebased onto them: the honesty-contract section now documents tap_xy/3/tap_id/2's observed-effect contract (:ok only when an event reached the BEAM within 300 ms; {:error, :no_view_at_point | :no_element_at_point | :no_effect} otherwise, with the platform limits that make :no_effect legitimate), and the evidence-matching guidance now points exact-color decisions at Mob.Test.sample_color/2 (real pixels, :dominant/:average as 0xAARRGGBB, iOS debug-build only) with screenshots-with-tolerance reserved for holistic visual parity. testing.md gains matching sections. fix: cold-start launch notifications dropped before nif_load (Android + iOS) #77 required no doc change: push_notifications.md already described tap-to-open from a killed app, which that fix made true.
• event_model.md — an explicitly forward-looking design contract, left as such.
• 0.7.27–0.7.31 fixes (component-event binaries, frame-registry races, launch deadlock) — bug fixes to already-documented behavior; the changelog covers them.

Gates

• mix docs — clean build; reference warnings 103 → 99 (removed the nonexistent Mob.Nav.push/2 refs; the rest pre-date this PR)
• mix format --check-formatted — clean
• mix compile --warnings-as-errors — clean
• mix test — 1280 passed (27 doctests), 38 excluded (re-run after rebasing onto iOS harness: stop tap_xy reporting phantom successes; add pixel sampling for colour #80/fix: cold-start launch notifications dropped before nif_load (Android + iOS) #77)
• mix credo --strict — no issues

🤖 Generated with Claude Code

[GenericJam]

Review record: spot-verified the highest-consequence claims against master source (Mob.Nav is the state struct — no push/2 navigation API ever existed; screen_pid/1 absent; taps deliver {:tap, tag} to handle_info; tab_bar/1 layout draws no chrome while the :tab_bar widget path renders MobTabView — the guide's distinction is exactly right). Structure matches the requested single-agent/agent-teams split. Gates green on the rebased tree. Merged.