Popup pair button + OpenRouter placeholder + green CI + rewritten Pages homepage#7
Merged
Conversation
…enRouter key placeholder Three small UX additions that round out the v0 onboarding: - Popup now has a "📱 Pair phone" secondary button under the doomscroll toggle. Click → opens dashboard.html#pair in a new tab. If a phone is already paired, button reads "Phone paired — re-pair" and a small green note confirms. - Dashboard treats #pair hash as a deep link: if no phone is paired and no in-flight pairing, auto-runs startPairing() on load. So the popup button is one-click to QR. - New "⚙ Advanced" card on the dashboard with an OpenRouter API key field. Currently a no-op placeholder — copy explains "no effect yet — feature in flight". Lets power users plant their key now so it's picked up the moment LLM-roast push payloads ship. Adds two Playwright tests covering the deep-link auto-start and the OpenRouter key persistence. 9/9 in extension-only.spec.ts pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…spec The previous workflow ran docker compose to bring up the Deno server and a Playwright container, then executed e2e.spec.ts which tests the old "extension syncs cookies → server polls InnerTube → server sends push" flow. After the local-only architecture pivot, that spec's assumptions (visible #serverUrl in popup; InnerTube poll path) no longer hold and CI has been failing on every PR. Replaces the workflow with a lean native Playwright run: - setup-node@v4 with cached test/package-lock.json - Materialize cookies.json from the YT_COOKIES_JSON repo secret - npm ci + playwright install --with-deps chromium - Run extension-only.spec.ts (9 tests, ~15s locally) No docker, no compose, no container builds — runs in ~2min vs the previous ~5min, and actually tests the path users now follow. The old e2e.spec.ts (BYO-server flow) is left in the repo for manual runs but no longer gates CI; updating it for the new popup ⚙-gated config form is a separate piece of work. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The old homepage was entirely stale — described the BYO-server flow (install ext → run server → cookie sync → server polls) which is now an *optional* advanced path. The default user flow is dramatically simpler: 1. Load unpacked from a git clone (Web Store coming). 2. Click extension icon → popup populates with shorts count in ~1s. 3. Tick "Doomscroll notifications" → laptop alerts work. 4. Optional: click "Pair phone" → scan QR → phone alerts work. New page reflects that ordering. Drops the Mac-specific Deno install and ngrok tunnel sections (no longer needed for the default path). Adds a brief "BYO server (advanced)" section pointing power users to the ⚙ panel for the cross-device cookie-sync use case. Trust model section adapted to describe what data leaves the machine in each opt-in mode (none in default; ~300 bytes through ntfy.sh once at phone pairing; cookies to your own server in BYO). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
amiller
added a commit
that referenced
this pull request
May 3, 2026
…tecture Old description still mentioned "Sync your YouTube cookies to your self-hosted OpenFeedling server" which is now an optional advanced path, not the default. New description (99 chars, well under Web Store's 132-char limit) reflects the actual local-only flow. Version bump to 0.2.0 reflects the substantial architecture change shipped over PRs #3-#7: HTML+ytInitialData fetch path, ID-set delta activity detection, popup-as-status + dashboard split, QR-pair phone flow with VAPID push, OpenRouter placeholder. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
c |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three loosely-related improvements bundled because they're all small.
1. Extension UX (commit d3714cd)
#pairhash → auto-starts QR flow on load.2. CI fix (commit f4d923c)
The previous workflow ran the old
e2e.spec.ts(BYO-server flow) under docker compose. After the architecture pivot, that spec's assumptions (visible#serverUrlin popup, InnerTube poll path) are stale and CI has failed on every PR since.Replaced with a lean native-Playwright run of
extension-only.spec.ts:The BYO-server
e2e.spec.tsstays in the repo for manual runs; updating it for the ⚙-gated popup form is separate work.3. Docs rewrite (commit b2f4b5b)
The Pages homepage described the BYO-server flow as the default. After the pivot, the canonical flow is:
Trust model section now itemizes what (if anything) leaves the machine per opt-in mode.
🤖 Generated with Claude Code