Finish PrompterOne rename and reader runtime updates

Author: KSemenenko

AGENTS.md

@@ -302,6 +302,9 @@ Repo-specific design rules:
 - Third-party runtime JavaScript SDKs MUST be sourced only from explicitly pinned GitHub Release tags and assets, copied into the repo, bundled locally with their runtime dependencies, and never loaded from CDNs, package registries, `latest` endpoints, or ad-hoc remote downloads at app runtime.
 - Repo-owned manifests, scripts, workflows, and project files that track third-party runtime JavaScript SDKs MUST point to concrete GitHub release versions and asset URLs, never floating references.
 - Any vendored runtime JavaScript SDK that tracks an upstream GitHub repo MUST have an automated watcher job that checks new GitHub releases and opens a repo issue describing the required update when a newer release appears.
+- Teleprompter TPS speed modifiers MUST affect both playback timing and subtle word-level letter spacing, so slower spans open up slightly and faster spans tighten slightly without hurting readability.
+- Teleprompter block transitions MUST stay visually consistent: outgoing cards move upward and incoming cards rise from below in the same direction every time; alternating up/down travel is forbidden.
+- User preferences persistence MUST sit behind a platform-agnostic user-settings abstraction, with browser storage implemented via local storage and room for other platform-specific implementations; theme, teleprompter layout preferences, camera/scene preferences, and similar saved settings belong there instead of ad-hoc feature stores.
 - Build quality gates must stay green under `-warnaserror`.
 - GitHub Pages is the expected CI publish target for the standalone WebAssembly app; publish automation must keep the app browser-only and Pages-compatible.
 - GitHub Actions MUST keep separate, clearly named workflows for pull-request validation and release automation; vague workflow names are forbidden.

docs/Architecture.md

@@ -172,7 +172,7 @@ flowchart LR
     Settings["SettingsCloudSection"]
     BrowserStore["BrowserCloudStorageStore"]
     Preferences["CloudStoragePreferences"]
-    BrowserKeys["BrowserSettingsStore<br/>localStorage keys only"]
+    UserSettings["IUserSettingsStore<br/>BrowserSettingsStore localStorage implementation"]
     Transfer["CloudStorageTransferService"]
     ProviderFactory["CloudStorageProviderFactory"]
     LocalRepo["BrowserScriptRepository + BrowserLibraryFolderRepository"]
@@ -185,7 +185,7 @@ flowchart LR
     Settings --> BrowserStore
     Settings --> Transfer
     BrowserStore --> Preferences
-    BrowserStore --> BrowserKeys
+    BrowserStore --> UserSettings
     Transfer --> ProviderFactory
     Transfer --> LocalVfs
     ScriptRepo --> LocalRepo
@@ -196,6 +196,7 @@ flowchart LR
 
 - Scripts and folders persist through authoritative browser repositories backed by versioned JSON/localStorage materialization.
 - Browser `localStorage` is reserved for provider credentials, provider metadata, and lightweight settings values that must survive reloads.
+- Routed pages and browser services should depend on `IUserSettingsStore` for persisted user preferences; `BrowserSettingsStore` is the browser-only implementation detail behind that contract.
 - Browser storage plus VFS stay registered for cloud import/export and future stream-export work, but they are not the primary editor/library persistence path today.
 - Cloud import/export currently moves one scripts-and-settings snapshot at a time; it is not a live sync engine and does not own recorded video upload.
 
@@ -236,14 +237,14 @@ flowchart LR
     Connectivity["BrowserConnectivityService"]
     Diagnostics["UiDiagnosticsService"]
     Pages["Library / Editor / Learn / Teleprompter / Go Live / Settings"]
-    Browser["BrowserSettingsStore"]
+    UserSettings["IUserSettingsStore"]
     Session["ScriptSessionService"]
 
     WasmHost --> Bootstrap
     WasmHost --> Diagnostics
     Pages --> Diagnostics
     Pages --> Connectivity
-    Browser --> WasmHost
+    UserSettings --> WasmHost
     Session --> WasmHost
     Diagnostics --> Layout
     Connectivity --> Layout
@@ -332,11 +333,13 @@ If a native embedded browser host returns later, media access must not rely on s
 - exact design shell and imported `new-design` assets
 - shared UI localization catalog for supported browser cultures
 - browser interop and app DI wiring
+- browser-backed `IUserSettingsStore` wiring for persisted reader, theme, scene, and studio preferences
 - dynamic library folder components and folder/document browser storage adapters
 - UI diagnostics banner and global error boundary
 - debounced editor autosave and body-only TPS source authoring
 - centered RSVP ORP playback in `learn`
 - single background camera layer under text in `teleprompter`
+- teleprompter reader preferences persist through `IUserSettingsStore`, including font scale, text width, focal position, and camera auto-start preference
 - dedicated `go-live` routing surface that arms multiple live destinations while reusing the same browser-composed scene
 - settings split between device setup (`settings`) and destination routing (`go-live`)
 

docs/Features/ReaderRuntime.md

@@ -13,20 +13,25 @@ The important contracts are:
 - Teleprompter word groups stay short enough to avoid run-on lines.
 - Teleprompter preserves TPS word presentation details such as pronunciation guides, inline colors, emotion styling, and speed-derived spacing/timing.
 - Teleprompter pre-centers the next card before it slides in, so block transitions do not jump at the focal line.
+- Teleprompter block transitions always move in one upward direction: the outgoing card exits up and the incoming card rises from below.
 - Teleprompter controls stay readable at rest; they must not fade until they become unusable.
+- Teleprompter user-adjusted font size, text width, focal position, and camera preference survive reloads through the shared user-settings contract.
 
 ## Flow
 
 ```mermaid
 flowchart LR
     Session["IScriptSessionService"]
+    UserSettings["IUserSettingsStore"]
     Learn["LearnPage"]
     Reader["TeleprompterPage"]
     Js["design/app.js"]
     Browser["DOM + media APIs"]
 
     Session --> Learn
     Session --> Reader
+    UserSettings --> Learn
+    UserSettings --> Reader
     Learn --> Js
     Reader --> Js
     Js --> Browser
@@ -43,15 +48,24 @@ flowchart LR
 - `teleprompter` groups words by pauses, sentence endings, clause endings, and short phrase limits.
 - `teleprompter` forwards TPS pronunciation metadata to word-level `title` / `data-pronunciation` attributes.
 - `teleprompter` derives word-level pacing from the compiled TPS duration and carries effective WPM into the DOM for testable parity.
+- `teleprompter` preserves TPS front-matter speed offsets and `[normal]` resets when rebuilding reader blocks, so relative speed tags keep both their timing math and subtle word-level spacing cues.
 - `teleprompter` keeps TPS inline colors visible even when a phrase group is active or the active word is highlighted.
+- `teleprompter` persists font scale, text width, focal point, and camera auto-start changes through `IUserSettingsStore` and restores them from stored `ReaderSettings` during bootstrap.
+- `teleprompter` prepositions the next card below the focal line before activation, so forward and backward block jumps both animate upward instead of alternating direction.
 
 ## Verification
 
 - bUnit verifies teleprompter background-camera markup and readable phrase groups.
 - bUnit verifies product-launch TPS modifiers survive into teleprompter word markup, timing, and pronunciation metadata.
+- bUnit verifies custom TPS `speed_offsets` front matter and `[normal]` resets survive into teleprompter word classes, styles, and effective-WPM metadata.
+- bUnit verifies teleprompter restores persisted reader width, focal position, and font size and saves reader layout/camera preference changes back to stored `ReaderSettings`.
 - Core tests verify TPS scripts generate RSVP phrase groups.
 - Core tests verify shorthand inline WPM scopes such as `[180WPM]...[/180WPM]` survive nested tags.
+- Core tests verify nested `speed_offsets:` front matter is parsed and applied to `xslow` / `slow` / `fast` / `xfast` scope math.
+- Core tests verify legacy reader-settings payloads without `FocalPointPercent` deserialize with the default focal-point value.
 - Playwright verifies ORP centering and the `security-incident` phrase-aware flow in `learn`.
 - Playwright verifies there is no teleprompter overlay camera box and that phrase groups do not overflow.
 - Playwright verifies the teleprompter camera button attaches and detaches a real synthetic `MediaStream` on the background video layer.
 - Playwright verifies the full `Product Launch` teleprompter scenario, including visible controls, TPS formatting parity, screenshot artifacts, and aligned post-transition playback.
+- Playwright verifies custom TPS speed offsets change computed teleprompter `letter-spacing` while `[normal]` words reset back to neutral spacing and timing.
+- Playwright verifies teleprompter width and focal settings survive a real browser reload and that backward block jumps keep the outgoing card on the upward exit path during the transition.

legacy-product-prefix-cleanup.plan.md

@@ -0,0 +1,131 @@
+# Legacy Product Prefix Cleanup Plan
+
+## Goal
+
+Finish the product rename by replacing every remaining repo-owned legacy product prefix with the `PrompterOne` and `prompterOne` naming, without regressing the standalone Blazor WebAssembly runtime, JS interop, or browser acceptance suite.
+
+## Scope
+
+### In Scope
+
+- rename remaining repo-owned runtime identifiers that still use the old product prefix in tracked source files
+- rename matching browser-test constants and harness globals so the browser suite stays aligned with production contracts
+- rename local ignored IDE artifacts that still use the old product name when that can be done safely without changing tracked repo state
+- re-scan tracked content and relevant local metadata for any residual legacy product-prefix references after the code changes
+
+### Out Of Scope
+
+- broad refactors unrelated to the rename cleanup
+- changes to third-party brand names such as `LiveKit` where `Live` is part of the vendor or protocol name rather than the old product name
+- generated `bin/`, `obj/`, or other rebuild output
+
+## Current State
+
+- The main solution, projects, namespaces, and docs already use `PrompterOne`.
+- Remaining tracked hits are limited to browser JS globals, interop method names, and browser-test harness constants.
+- Remaining filesystem-name hits are in ignored local IDE artifacts such as `.idea/` state and `*.DotSettings.user`.
+
+## Constraints And Risks
+
+- The repo mandates a root-level plan file and a full baseline before non-trivial edits.
+- Browser acceptance is the primary gate, so any renamed JS global or interop string must be changed consistently in production and tests.
+- `LiveKit` identifiers must stay intact where they refer to the external SDK rather than the product prefix.
+- Ignored IDE files are local-only and must not distract from tracked source correctness, but renaming them is acceptable if it is safe and improves workspace consistency.
+
+## Testing Methodology
+
+- Establish a full repo baseline with the required `build` and `test` commands before edits.
+- After the rename changes, run targeted source scans to confirm the legacy product prefix is gone from tracked content.
+- Run the full repo quality pass in repo order: `build`, `test`, `coverage`, then `format`.
+- Quality bar:
+  - no tracked legacy product-prefix references remain unless documented as an intentional vendor name
+  - `dotnet build /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx -warnaserror` succeeds
+  - `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx` succeeds
+  - `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx --collect:"XPlat Code Coverage"` succeeds
+  - `dotnet format /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx` succeeds
+
+## Ordered Steps
+
+### 1. Freeze Scope And Inventory The Remaining Hits
+
+- [x] Search tracked file contents for the legacy product prefix and related case variants while excluding generated output.
+- [x] Search file paths for legacy-name leftovers and classify which ones are tracked repo content versus ignored local metadata.
+- [x] Record the rename target set and validation sequence in this plan file.
+- Verify before moving on:
+  - the remaining hit list is concrete and small enough to change intentionally rather than with blind global replacement
+  - vendor names such as `LiveKit` are explicitly excluded from the rename
+
+### 2. Establish The Full Baseline Before Edits
+
+- [x] Run `dotnet build /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx -warnaserror`.
+- [x] Run `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx`.
+- [x] Record each baseline failure below with symptom, suspected cause, and intended fix path before changing source.
+- Verify before moving on:
+  - baseline build status is captured
+  - baseline test status is captured
+  - every failing baseline test, if any, is tracked below as a checklist item
+
+## Baseline Failures
+
+- [x] No baseline failures.
+  - Symptom: none. `dotnet build /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx -warnaserror` and `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx` both passed before edits.
+  - Suspected cause: not applicable.
+  - Intended fix path: preserve the green baseline through the rename cleanup and rerun the same required gates afterward.
+
+### 3. Rename Tracked Repo-Owned Contracts
+
+- [x] Update production browser interop identifiers in `/Users/ksemenenko/Developer/PrompterOne/src/PrompterOne.Shared/wwwroot/media/browser-media.js`, `/Users/ksemenenko/Developer/PrompterOne/src/PrompterOne.Shared/wwwroot/theme/browser-theme.js`, and `/Users/ksemenenko/Developer/PrompterOne/src/PrompterOne.Shared/Settings/Services/BrowserThemeInteropMethodNames.cs`.
+- [x] Update the matching browser-test constants and synthetic harness globals in `/Users/ksemenenko/Developer/PrompterOne/tests/PrompterOne.App.UITests/Media/synthetic-media-harness.js`, `/Users/ksemenenko/Developer/PrompterOne/tests/PrompterOne.App.UITests/Media/BrowserTestConstants.Media.cs`, `/Users/ksemenenko/Developer/PrompterOne/tests/PrompterOne.App.UITests/Support/BrowserTestConstants.cs`, and `/Users/ksemenenko/Developer/PrompterOne/tests/PrompterOne.App.Tests/Support/AppTestData.cs`.
+- [x] Re-scan tracked source for legacy product-prefix references to confirm only intentional vendor names remain.
+- Verify before moving on:
+  - each renamed production contract has a matching test-side update
+  - the remaining tracked hits, if any, are intentional and documented
+- Outcome:
+  - tracked source scans are clean for the legacy product prefix after the contract rename
+  - `LiveKit` vendor identifiers remain intact while only the repo-owned harness global prefix changed
+
+### 4. Rename Safe Local Metadata Leftovers
+
+- [x] Rename or remove ignored local IDE artifacts that still use the old product name, including the legacy solution `.DotSettings.user` file and the stale Rider `.idea` directory, if they still exist after source changes.
+- [x] Re-scan local file paths for old-product-name leftovers outside generated output.
+- Verify before moving on:
+  - the rename does not modify tracked repo content unexpectedly
+  - local-only leftovers are either renamed or explicitly called out as intentionally untouched
+- Outcome:
+  - the stale Rider `.idea` directory was removed because a current `.idea.PrompterOne` directory already existed
+  - the local solution settings file now follows the current solution name as `PrompterOne.slnx.DotSettings.user`
+  - the local filesystem scan is clean for the old product name outside excluded generated output
+
+### 5. Final Validation And Plan Closeout
+
+- [x] Run `dotnet build /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx -warnaserror`.
+- [x] Run `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx`.
+- [x] Run `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx --collect:"XPlat Code Coverage"`.
+- [x] Run `dotnet format /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx`.
+- [x] Update this plan with the final scan results, validation outcomes, and any intentionally untouched local-only residue.
+- Verify before moving on:
+  - all required repo commands pass
+  - scans are clean for tracked repo-owned old-name prefixes
+  - this plan reflects the actual end state
+- Final outcome:
+  - `dotnet build /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx -warnaserror` passed after the cleanup
+  - focused `PrompterOne.App.Tests` and `PrompterOne.App.UITests` runs passed after the contract rename
+  - `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx` passed after the cleanup
+  - `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx --collect:"XPlat Code Coverage"` passed and produced coverage artifacts for core, component, and browser suites
+  - `dotnet format /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx` completed successfully
+  - tracked source scans and local filesystem-name scans are clean for the legacy product prefix
+
+## Final Validation Skills And Commands
+
+1. `dotnet-blazor`
+   - Action: verify the Blazor WebAssembly host and JS interop contract names still line up after the rename cleanup.
+   - Outcome: production browser scripts and C# interop constants stay consistent.
+2. `playwright`
+   - Action: rely on the browser acceptance suite executed through the repo `dotnet test` workflow to validate real-browser behavior after the renamed JS globals.
+   - Outcome: browser flows keep working with the updated test harness contract names.
+3. Repo quality commands
+   - `dotnet build /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx -warnaserror`
+   - `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx`
+   - `dotnet test /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx --collect:"XPlat Code Coverage"`
+   - `dotnet format /Users/ksemenenko/Developer/PrompterOne/PrompterOne.slnx`
+   - Reason: these are the mandatory repo-defined gates for this task.