feat(play-setup): state the ask-vs-grant gap and the host tuning verdict

[papi-ux]

Summary

• The ask-vs-grant gap is stated where the grant is stated. buildNovaLaunchProfileSummary now takes clientAskedFps (the Settings frame rate) and, when the granted rate sits below it, the Selected line reads "Recovery profile / 30 FPS · you asked 120" and a new grantHoldReason names what is holding it ("Held by History Safe Profile", from preference_blocked_reason, else the limiting issue). The Play Setup Asked/granted fact carries the reason in its detail. This was the one fact no screen said anywhere — exactly what made a 30 FPS launch under a 120 FPS setting read as a mystery.
• The High FPS pin moves into the summary itself (clientFpsPinned): it owns the "Launch 120 FPS · your pick" headline and the "120 FPS pinned (host offered Recovery profile / 30 FPS)" Selected line, and retires the one-shot trial button while active, since the launch already goes out at the asked rate. The button-site special case from feat(play-setup): make High FPS tuning binding via one composed launch blob #246 is removed; the button just reads the summary.
• The Tuning caption states the host's verdict on the asks the host owns: "Applied by host" or "Host declined · History Safe Profile" for quality/stability, via a new pure novaTuningOutcome helper. A host that predates preference_applied gets the default caption — a decline is never fabricated from a missing field. auto asks for nothing and high_fps is binding client-side (feat(play-setup): make High FPS tuning binding via one composed launch blob #246), so neither shows a host verdict.
• issueLabel becomes internal novaLaunchIssueLabel so the outcome helper reuses the one prettifier.
• Design note: the plan's "inline recovery exits in Play Setup" was dropped as already-solved — Reset Game Profile lives on the Overview's fixed four-action rail by deliberate design (its source guard explains Play Setup has no room for a copy), and Try-High-FPS rides the expanded review.

Exact candidate

• Commit: 38aa34dc8bffc376720e78200d013c599ceff34a
• Tree: f632fe1dc7b0e0f5e6cb9afb3eddded9ee771aa6
• Parent: 9ebba7e1846fee3132c479e72424abd45ee951d1
• Base: 9ebba7e1846fee3132c479e72424abd45ee951d1 (origin/master, carries fix(settings): stop presets rewriting fps and share panel culling #245 + feat(play-setup): make High FPS tuning binding via one composed launch blob #246)

Verification

• :app:testNonRoot_gameDebugUnitTest — 1388 tests, 0 failures, 0 errors, 0 skipped (XML-counted; includes 3 new NovaLaunchProfileSummaryTest fixtures and the new NovaTuningOutcomeTest)
• :app:lintNonRoot_gameDebug -PlintFailOnError=true — 0 new errors (baseline noise only)
• :app:assembleNonRoot_gameDebugAndroidTest — compiles
• Device QA on the RP6 (arc's end-to-end pass, next: recovery game shows "you asked 120" + hold reason on Auto; pin flips the button to "your pick"; declined quality/stability asks read "Host declined")