Repository navigation
Record verified Router release, QA scope and rollback - #142
Merged
Merged
Conversation
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.
Record PR #141's verified production source 5a681ba, successful CI/publication run 39725320432, READY Vercel deployment, matching manifest and served Router 7.18.4 marker. Close the existing roadmap item and retain the original failed-budget evidence alongside the measured initial-load reduction and cold first-open cost.
Document the real QA boundary: the direct-host route run exited nonzero only at the existing localhost-only language guard; the complete 398-navigation suite then passed against unchanged published assets in a task-owned localhost preview, with 24 asset hashes and manifest checked again. Preserve that failed log and the successful result rather than calling the direct harness a full pass. Real EN/ES desktop/mobile captures, API readback, remaining six moderate build entries and a scoped inverse checked without execution are included.
Only three existing Markdown records change; no runtime, configuration, budget/audit exception, credentials, permissions, ads or data snapshots. No Vercel workflow dispatch or new monitor. CI will run on this record-only PR; merging these paths does not trigger another Vercel publication.