update docs and websocket source handling

Include the current documentation/site updates and websocket source changes before pushing beta. YouTube WSS now clears failed OAuth state and only treats active session/callback state as pending so stale auth state cannot hide signin_required.

Author: steveseguin

docs/agents/00-inventory-and-plan.md

@@ -12,13 +12,13 @@ This first pass creates the working folder, records what already exists, and lay
 
 All new AI documentation should live under:
 
-`C:\Users\steve\Code\social_stream\docs\agents`
+`docs/agents`
 
 No other files should be edited for this documentation project unless Steve explicitly changes the scope.
 
 ## Existing Source Map
 
-### `C:\Users\steve\Code\social_stream`
+### `<social_stream repo>`
 
 Primary source for the Chrome extension, public web overlays, shared source scripts, and code loaded by the standalone app.
 
@@ -93,9 +93,9 @@ Important repo instruction already present:
 - Remote executable scripts/WASM should not be introduced into extension code.
 - `docs/event-reference.html` is the canonical event payload reference.
 
-### `C:\Users\steve\Code\ssapp`
+### `<ssapp repo>`
 
-Standalone Electron app source. This app uses Social Stream source files from `C:\Users\steve\Code\social_stream` as the primary runtime source. The fallback bundle is disposable and was intentionally not inspected.
+Standalone Electron app source. This app uses Social Stream source files from `<social_stream repo>` as the primary runtime source. The fallback bundle is disposable and was intentionally not inspected.
 
 Observed structure:
 
@@ -130,7 +130,7 @@ Do not mine for normal docs:
 
 - `resources/social_stream_fallback`: disposable fallback bundle, not source of truth.
 
-### `C:\Users\steve\Code\stevesbot`
+### `<stevesbot repo>`
 
 Historical support and knowledge base material. This is a supporting evidence source, not the product source of truth.
 

docs/agents/01-extraction-checklist.md

@@ -6,7 +6,7 @@ Last updated on 2026-06-24.
 
 Use this file to track which source files and support datasets have been processed for the SSN AI documentation set. The goal is to support multiple AI passes without redoing the same work or skipping important resource areas.
 
-Only write extraction notes and status changes inside `C:\Users\steve\Code\social_stream\docs\agents`.
+Only write extraction notes and status changes inside `docs/agents`.
 
 ## Extraction Levels
 

docs/agents/01-product-map.md

@@ -12,7 +12,7 @@ Status: heavy extraction pass started from public repo docs and app docs. This i
 - `docs/commands.html`
 - `docs/ssapp.html`
 - `docs/js/sites.js`
-- `C:\Users\steve\Code\ssapp\AGENTS.md`
+- `<ssapp repo>/AGENTS.md`
 
 ## What Social Stream Ninja Is
 
@@ -60,7 +60,7 @@ Use the standalone app when:
 
 Boundary from `ssapp` instructions:
 
-- Source edits belong in `C:\Users\steve\Code\social_stream`.
+- Source edits belong in `<social_stream repo>`.
 - The standalone app loads Social Stream source files remotely from that repo at app startup.
 - `ssapp/resources/social_stream_fallback` is a rebuilt fallback bundle, not the primary source.
 

docs/agents/02-installation-and-surfaces.md

@@ -10,9 +10,9 @@ For a support-oriented decision guide covering install path choice, safe update
 - `docs/download.html`
 - `docs/ssapp.html`
 - `docs/commands.html`
-- `C:\Users\steve\Code\ssapp\AGENTS.md`
-- `C:\Users\steve\Code\ssapp\package.json`
-- `C:\Users\steve\Code\ssapp\RELEASE.md`
+- `<ssapp repo>/AGENTS.md`
+- `<ssapp repo>/package.json`
+- `<ssapp repo>/RELEASE.md`
 
 ## Install Choices
 
@@ -119,8 +119,8 @@ Download-page notes:
 
 Repo boundary:
 
-- App code lives in `C:\Users\steve\Code\ssapp`.
-- Social Stream source edits still belong in `C:\Users\steve\Code\social_stream`.
+- App code lives in `<ssapp repo>`.
+- Social Stream source edits still belong in `<social_stream repo>`.
 - Do not use `ssapp/resources/social_stream_fallback` as the source of truth.
 
 ## Choosing Extension vs App
@@ -191,14 +191,14 @@ Do not use Lite docs to answer full extension/app questions unless the user is e
 
 For Social Stream extension/source development:
 
-- Work in `C:\Users\steve\Code\social_stream`.
+- Work in `<social_stream repo>`.
 - Load unpacked extension from that folder or a build-specific folder.
 - Use local/localhost source pages where manifest entries support them.
 - Use `scripts/validate-configs.sh` before commits/pushes that touch settings/config JSON.
 
 For standalone app development:
 
-- Work in `C:\Users\steve\Code\ssapp`.
+- Work in `<ssapp repo>`.
 - Read `ssapp/AGENTS.md` and `RELEASE.md` before release work.
 - Run app behavior in the actual Electron app for real validation.
 

docs/agents/02-resource-manifest.md

@@ -8,8 +8,8 @@ This file lists the source material that should be considered for SSN AI documen
 
 Do not use these for extraction unless Steve explicitly changes scope:
 
-- `C:\Users\steve\Code\ssapp\resources\social_stream_fallback`
-- `C:\Users\steve\Code\stevesbot\resources\secrets`
+- `<ssapp repo>/resources/social_stream_fallback`
+- `<stevesbot repo>/resources/secrets`
 - `node_modules`, `.git`, build output, temp folders, logs, and backup databases
 - Non-SSN support material unless it directly affects SSN setup or integration
 
@@ -22,7 +22,7 @@ Do not use these for extraction unless Steve explicitly changes scope:
 
 ## Social Stream Repo
 
-Root: `C:\Users\steve\Code\social_stream`
+Root: `<social_stream repo>`
 
 Observed candidate resource counts:
 
@@ -422,7 +422,7 @@ Track these by directory unless a page depends on a specific file:
 
 ## Standalone App Repo
 
-Root: `C:\Users\steve\Code\ssapp`
+Root: `<ssapp repo>`
 
 Observed candidate resource counts after excluding fallback/build/temp/log output:
 
@@ -537,7 +537,7 @@ Track by directory unless a feature page needs exact asset behavior:
 
 ## Stevesbot Support Data
 
-Root: `C:\Users\steve\Code\stevesbot`
+Root: `<stevesbot repo>`
 
 This repo is support evidence, not product source of truth.
 
@@ -640,12 +640,12 @@ Suggested units:
 Use these commands to refresh this manifest later.
 
 ```powershell
-cd C:\Users\steve\Code\social_stream
+cd <social_stream repo>
 rg --files -g '!node_modules/**' -g '!.git/**' -g '!docs/agents/**' | Sort-Object
 
-cd C:\Users\steve\Code\ssapp
+cd <ssapp repo>
 rg --files -g '!node_modules/**' -g '!.git/**' -g '!resources/social_stream_fallback/**' -g '!dist/**' -g '!tmp/**' | Sort-Object
 
-cd C:\Users\steve\Code\stevesbot
+cd <stevesbot repo>
 rg --files -g '!resources/secrets/**' -g '!logs/**' -g '!data/backups/**' -g '!data/replays/**' | Sort-Object
 ```

docs/agents/04-standalone-app-architecture.md

@@ -21,7 +21,7 @@ For the focused source-window lifecycle and app-vs-extension parity matrix, use
 - `ssapp/tiktok/connection-manager.js`
 - `ssapp/tests/electron/*`
 
-Do not use `ssapp/resources/social_stream_fallback` as source documentation material during normal extraction. The project instructions say Social Stream source edits and runtime source-of-truth work belong in `C:\Users\steve\Code\social_stream`; the fallback folder is disposable build/update output.
+Do not use `ssapp/resources/social_stream_fallback` as source documentation material during normal extraction. The project instructions say Social Stream source edits and runtime source-of-truth work belong in `<social_stream repo>`; the fallback folder is disposable build/update output.
 
 ## Runtime Shape
 

docs/agents/04-standalone-app-source-windows.md

@@ -6,7 +6,7 @@ Status: heavy extraction pass from `ssapp/main.js`, `ssapp/preload.js`, `ssapp/s
 
 Document how standalone app source windows behave, why they can differ from the Chrome extension, and what agents should check before saying a source is "broken in the app."
 
-For Social Stream feature behavior, use `C:\Users\steve\Code\social_stream` as source of truth. For Electron shell behavior, source windows, app auth, local source loading, and state repair, use `C:\Users\steve\Code\ssapp`.
+For Social Stream feature behavior, use `<social_stream repo>` as source of truth. For Electron shell behavior, source windows, app auth, local source loading, and state repair, use `<ssapp repo>`.
 
 ## Source Anchors
 
@@ -203,7 +203,7 @@ Check whether the source or group has auto-activate enabled, whether a saved sou
 Use:
 
 ```text
-Check `--filesource`, saved local source path, ZIP import, beta/stable branch, prefer-local-assets, and any cache/fallback warning. Source edits belong in `C:\Users\steve\Code\social_stream`, not the app fallback mirror.
+Check `--filesource`, saved local source path, ZIP import, beta/stable branch, prefer-local-assets, and any cache/fallback warning. Source edits belong in `<social_stream repo>`, not the app fallback mirror.
 ```
 
 ### "Login works in browser but not app."

docs/agents/07-overlays-and-pages/multi-alerts.md

@@ -22,8 +22,8 @@ On 2026-06-24, `node scripts/playwright-multi-alerts-overlay-e2e.cjs` was run fr
 
 ```text
 frame.waitForFunction: Timeout 30000ms exceeded.
-    at waitForPreviewFrame (C:\Users\steve\Code\social_stream\scripts\playwright-multi-alerts-overlay-e2e.cjs:212:15)
-    at async C:\Users\steve\Code\social_stream\scripts\playwright-multi-alerts-overlay-e2e.cjs:439:24
+    at waitForPreviewFrame (<social_stream repo>/scripts/playwright-multi-alerts-overlay-e2e.cjs:212:15)
+    at async <social_stream repo>/scripts/playwright-multi-alerts-overlay-e2e.cjs:439:24
 ```
 
 The failure happened while waiting for the popup preview iframe to expose `window.__multiAlertsOverlay.getSettings`. Do not use that run as evidence that multi-alert rendering, queueing, audio, filters, or server modes are validated.

docs/agents/08-platform-sources/priority-platform-answer-matrix.md

@@ -28,7 +28,7 @@ For proof status behind these short answers, use `priority-platform-validation-l
 This pass checked the current docs plus source terms in:
 
 - `sources/youtube.js`, `sources/websocket/youtube.js`, `providers/youtube/liveChat.js`
-- `sources/tiktok.js`, `C:\Users\steve\Code\ssapp\tiktok\connection-manager.js`
+- `sources/tiktok.js`, `<ssapp repo>/tiktok/connection-manager.js`
 - `sources/twitch.js`, `sources/websocket/twitch.js`, `providers/twitch/chatClient.js`
 - `sources/kick.js`, `sources/kick_new.js`, `sources/websocket/kick.js`, `providers/kick/core.js`
 - `sources/rumble.js`, `sources/websocket/rumble.js`

docs/agents/10-troubleshooting/desktop-app-issues.md

@@ -6,7 +6,7 @@ Status: heavy extraction pass started.
 
 Document common standalone app support issues and the operational differences between the SSN desktop app and the Chrome extension.
 
-The app is a host for Social Stream source files. For Social Stream feature behavior, use `C:\Users\steve\Code\social_stream` as the source of truth. For desktop shell behavior, use `C:\Users\steve\Code\ssapp`.
+The app is a host for Social Stream source files. For Social Stream feature behavior, use `<social_stream repo>` as the source of truth. For desktop shell behavior, use `<ssapp repo>`.
 
 For source-window lifecycle, custom session, injection, and app-parity routing, use `../04-standalone-app-source-windows.md`. For app-specific TikTok modes, signing providers, fallbacks, replies, and test assets, use `../08-platform-sources/tiktok-standalone-app.md`.
 
@@ -48,7 +48,7 @@ Confirmed from `ssapp/main.js`:
 Important support rule:
 
 - Do not tell users to edit the packaged fallback mirror for normal work.
-- For source edits, use `C:\Users\steve\Code\social_stream`.
+- For source edits, use `<social_stream repo>`.
 - If the app is pointed at the wrong local folder, clear the saved local source or reload with a validated Social Stream source folder.
 
 ## Window And Tray Behavior