feat(entitlement): pre-release switch so Release builds can test 60 fps

The frame-rate boundary is correct as a product rule, but it only bites in a
Release build, where DevBuild.IsDevelopment is false and DeveloperMode cannot
unlock anything — exactly the build whose performance numbers are worth reading
(see docs/ai/environment.md: Debug pixel paths are several times slower). 60 fps
could not be tested at all.

OutputProfile.EntitlementEnforced is false: every shipped tier is selectable by
any build, and HasProOutput — the one property the tier setter, the dropdown's
strikethrough and the locked-item style all read — answers yes regardless of
ownership. static readonly rather than const, so the consumed `||` does not fold
into unreachable operand code (same reason as DevBuild.IsDevelopment).

The licence indicator row is suppressed while the switch is off: it exists to
explain what the boundary costs, and claiming "Steam ID Limit: 60fps" to an
unowned build would be a false statement. Docs corrected in place — the enforced
rule is unchanged, only its state is recorded.

Tests: one integration case covers both switch states (unowned build reaches
1080p60 with the switch off, 1080p30 with it on), so flipping at launch leaves no
red test behind. The two suites that anchor on the pinned licence row early-return
while it is absent; EntitlementTests covers that state meanwhile.

667 pass, build 0 warnings.

docs/ai/commercial.md

@@ -46,9 +46,12 @@ The product rule is frame rate, not pixel count or a resolution label:
 | Landscape | 1280×720 @30 · 1920×1080 @30 | all Free tiers + 1280×720 @60 · 1920×1080 @60 |
 | Vertical 9:16 | 1080×1920 @30 | all Free tiers + 1080×1920 @60 |
 
-- **Implementation gap (2026-11-04):** `Models/OutputProfile.cs` still gates by pixel budget plus
-  frame rate. Update that rule and its tests to use frame rate alone; this docs unit records the
-  product decision but does not change code.
+- **Pre-release: the boundary is not enforced yet (2026-11-12).** `OutputProfile.EntitlementEnforced`
+  is `false`, so every shipped tier — 60 fps included — is selectable by any build until the paid
+  edition ships. It is needed because 60 fps can only be performance-tested in a **Release** build,
+  where `DevBuild.IsDevelopment` is false and `DeveloperMode` cannot unlock anything. Flip the switch
+  at launch: the rule, the resolver and their tests already implement the enforced state, and the
+  `EntitlementTests` case asserts both states so it does not go red on the flip.
 
 - **Records too.** The frame-rate rule governs the file the creator keeps as well as the stream;
   otherwise free 60-fps recording is a re-upload hole. **There is one ffmpeg process with two output blocks**