docs(deck): rewrite Steam Deck setup container-first

[mabry1985]

Why

The Deck docs were bare-metal-first — manual BlackArch strap, a venv, a hand-built libhackrf, and a required Infisical account. None of that survives a SteamOS update, and all of it is now baked into the runtime image. The docs no longer matched how pwnDeck actually installs.

What

• docs/tutorials/steam-deck-setup.md — rewritten as the single container-first path: clone for the deck/ scripts → deck/bootstrap.sh (idempotent host prep, re-run after every OS update) → deck/install.sh (image + systemd unit, the container is THE runtime) → add-to-Steam + kiosk → the in-app BYO-key setup wizard. New sections:
  • Surviving SteamOS updates — a survives/wiped table (/home vs /etc).
  • Fleet / Infisical (optional) — --with-infisical for the gateway path.
  • Container-aware troubleshooting.
  • Slimmed HackRF/PortaPack — power + enumeration only; the patched libhackrf + --privileged USB passthrough come from the image. Drops the manual strap/venv/distrobox/libhackrf-build steps.
• docs/steam-deck-setup.md — the orphaned bare-metal duplicate collapses into a short container-first quickstart that points at the tutorial.

Testing

npm run docs:build clean — no dead links.

Pairs with #270 (setup wizard backend) and #271 (bootstrap + container-default). Describes the end state those two deliver.

🤖 Generated with Claude Code

[protoquinn]

👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow.

[coderabbitai]

Warning

Review limit reached

@mabry1985, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 36 minutes and 32 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: d294ecc3-d532-4338-aaff-36aada1d1640

📥 Commits

Reviewing files that changed from the base of the PR and between 9d278c3 and b31e3c0.

📒 Files selected for processing (2)

• docs/steam-deck-setup.md
• docs/tutorials/steam-deck-setup.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/deck-container-first

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[protoquinn]

QA Audit — PR #272 | docs(deck): rewrite Steam Deck setup container-first

VERDICT: PENDING (CI non-terminal — Lint queued, Verify workspace config in_progress)

---

CI Status

• Lint: queued
• Verify workspace config: in_progress

Diff Review

• docs/steam-deck-setup.md: Collapsed from ~204-line bare-metal guide to a 47-line container-first quickstart. Clear, actionable, delegates to the full tutorial without losing discoverability.
• docs/tutorials/steam-deck-setup.md: Rewritten as the definitive container-first path — bootstrap → install → kiosk → in-app wizard. New sections: OS update survival table, optional Infisical fleet path, container-aware troubleshooting, slimmed HackRF/PortaPack enumeration. The bare-metal strap/venv/distrobox/libhackrf-build steps are correctly removed.

Observations

• GAP: Docs reference deck/bootstrap.sh, deck/install.sh, deck/install-deck-launcher.sh, and deck/steam-art.sh — these land in paired PR #271. If #271 merges after #272, readers will find missing scripts. Merge-order coordination note, not a defect in the docs.
• LOW: Clawpatch structural review unavailable — repo not in project registry. Reviewed manually; docs-only change, no code paths to audit.
• NOTE: npm run docs:build reported clean per PR description. No unresolved CodeRabbit threads.

— Quinn, QA Engineer

[protoquinn]

Submitted COMMENT review on #272.

[protoquinn]

CI terminal-green, no blockers on prior review — auto-approving on green (#748).