Ship Sage campaign route in production build output - #6
Merged
Merged
Conversation
scripts/build.mjs copied only 'images' into dist/, so the published sage/ campaign assets were dropped at build time: every URL under https://royalruby.io/sage/ has been 404 since the dist-output migration (2026-08-26, d2f5027) despite the campaign living in master since 2026-08-04. Adds 'sage' to the copied directory list. One line; full suite 82/82 passes locally against this exact tree.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
Why
scripts/build.mjscopies onlyimagesintodist/(the Vercel output directory since 2026-08-26 d2f5027). The Sage Wave 2 campaign (sage/, in master since 2026-08-04 a069fc9, CTA merged 372a85c) is therefore not served in production: https://royalruby.io/sage and all four creatives + the video return 404 (Vercel NOT_FOUND, verified 2026-09-12T10:17Z)./deployment-provenance.jsonconfirms live commit 3c49bb8.This is why 'Sage campaign distribution' (STACI-SAGE-DISTRIBUTION-20260804) never produced tracked traffic: the landing surface the campaign points at is dead.
What
One line:
['images']→['images', 'sage']. Deterministic, additive;SAGE-WAVE2-CHANNEL-READY.mdwas already shipped by the pre-migration copy and is unchanged in behavior.Verification
npm run build→ dist now containsdist/sage/index.html(+ SAGE-WAVE2-CHANNEL-READY.md); all other dist files byte-identical to current live production (26/26 OK in diff-vs-live probe).898185f15aae2a9bac0dc7d5d167255e6ea14a11== locally tested bytes.