Repository navigation
Release comparison sharing, guide-to-waits and working favorites - #106
Merged
Merged
Conversation
This was referenced Sep 30, 2026
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
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.
Prepare the free-product improvements from #102 and #104 for one GitHub Pages release, independently of the Vercel move in #103/#101. Comparison links open current data; guides link to waits and share with channel-level UTMs; crossing stars persist in the dashboard’s existing local favorites. A denied storage write now reports an EN/ES error instead of a false saved confirmation.
Validation: local production build passed; existing npm test passed including 406 desktop/mobile route navigations, audit and bundle gates. New desktop/mobile EN/ES interaction checks passed for favorite persistence/removal, blocked storage, copy failure, canonical comparison links, guide UTMs, fixed feedback and guide-to-waits events. These interaction checks now run in the release suite. CI fetches full history while this Pages build still uses Git-derived aggregates.
No hosting, ad-placement, credential, billing or domain changes. Production deployment awaits Sebastian’s explicit approval. Merge this release with a merge commit to retain #102/#104 ancestry.