Repository navigation
Refresh starter versions and Fullbleed tab icons - #148
Merged
Merged
Conversation
krflol
marked this pull request as ready for review
October 20, 2026 21:37
krflol
changed the title
krflol
changed the title
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.
Neighboring quickstarts and downloads installed different engine versions. Align the browser, React, Vue and Next.js starters with published Fullbleed npm 0.7.1 / engine 2.5.29, and align the HTML/CSS playground, its Python/Node exports and the coupled Rust quickstart with that engine. Refresh guide pins, downloadable projects, runtime assertions and retained provenance.
The browser, React and Vue starters also replace the Facebook-like lowercase f favicon with a cream/orange print page and crop marks. The documentation uses the same SVG as its site favicon. Starter icon URLs are versioned, and the same files flow into the ZIPs, hosted demos and online-editor payloads. Those archives use source
a947db8cd40212ac565652fdc1564121a6a73f21from fullbleed-engine/fullbleed-node#44; the unchanged Next.js archive uses7a79b374784e60998fd163e0f86a76dae37523e5from merged fullbleed-engine/fullbleed-node#43. Source PR #44 is merged with all 22 applicable CI jobs passing; its unchanged Next.js example correctly does not trigger that separate workflow.Preserve framework versions, document templates, the HTML/CSS-first introduction, Python component alpha status, the Rust same-engine guard and output comparisons. Historical 2.5.24 upgrade evidence remains, with separate
upgrade-verification-071.jsonevidence for this refresh. No core engine or npm release is created.Validation: clean installs/builds of all four exact JavaScript ZIPs, actual Chrome PDF downloads and online-launcher payloads, 17 Next.js HTTP checks, 20 native/WASI fixtures, 26 Python and 26 Node export replays, 20 Rust comparisons and 77 standalone Rust download checks. Previous PDF/PNG baselines remain byte-identical. The favicon revision adds clean builds of all three updated ZIPs, three fresh Chrome PDF downloads, exact online-editor payload checks and visual icon review at 16–128 px on light/dark backgrounds. Strict MkDocs and 150-page link checks pass; the unchanged playground passed its 80 browser checks. Desktop/mobile screenshots were inspected.