Release DeckDoc v3.4.0 model-aware, public-safe diagnostics

[deucebucket]

Outcome

Release DeckDoc v3.4.0 as a broader Deck-wide diagnostic foundation.

What changed

• add a schema-v1 model/capability manifest for Jupiter LCD, Galileo OLED, unknown hardware, applicability, absence, and inaccessible evidence;
• route first hardware consumers through discovered display, backlight, battery, storage, and Wi-Fi paths;
• add shared public-safe filtering before every normal full-report, probe, remediation, and Rescue disk write, with no intentionally raw DeckDoc artifact;
• minimize coredump, Steam, filesystem, mount, and device evidence to diagnostic fields;
• add the first application-specific adapter: privacy-safe RyuDeck lifecycle/progress/cache/renderer diagnosis;
• expand README, roadmap, wiki, module reference, Pages release metadata, and changelog;
• update the suite to 19 diagnostic modules plus two guarded remediation modules.

RyuDeck failure classes

The new adapter distinguishes:

• install/profile absent;
• active process without structured runtime;
• guest startup at sustained zero FPS;
• stale title-cache suspicion;
• active runtime telemetry stalled;
• renderer/device-loss, OOM, guest/process fatal;
• current nonzero-FPS rendering;
• indeterminate or historical-only evidence.

It emits counters/signatures only—no titles, title IDs, paths, filenames, arguments, account/controller IDs, or raw app-log lines. Follow-up adapter work is scoped in #27.

Validation

• all 31 regression/safety tests pass;
• shell syntax, shellcheck (when available), whitespace, and documentation links pass;
• live Galileo OLED full report: correct model semantics and LCD backlight marked not applicable;
• live Jupiter LCD full report: correct model and LCD backlight capability;
• adversarial privacy fixtures cover credentials, emails, IP/MAC addresses, user paths, UUIDs, Steam/account IDs, and exact 32-character identifiers;
• live RyuDeck adapter classified the repaired session as rendering with current telemetry and no device-loss/OOM/fatal markers.

Safety

• collection remains read-only apart from its own filtered reports;
• app cache testing remains advisory, exact-target, backed up, and reversible;
• firmware version/file count is evidence, not a compatibility verdict;
• physical pixels and hardware health still require independent confirmation.

Tracks and advances #15, #22, and #27.