Build the Cold Front staging commerce loop - #3
Draft
superposition wants to merge 5 commits into
Draft
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.
What changed
topcoat-blocksregistry commitShared block source is reviewed separately in superposition/topcoat-blocks#3. Cold Front keeps all styling, copy, data, provider policy, and mutations in this host.
Safety boundary
This is a staging workflow. It does not transfer real USDC, calculate provider-backed tax, buy real postage, or authorize operators for production. Production fails closed for checkout, catalog seeding, simulator routes, and missing persistent database/cookie configuration.
Validation
./scripts/checknode --check crates/coldfront-ui/src/auth.jsnode --check crates/coldfront-ui/src/wallet.js/health,/shop, and its generated stylesheet from the bundled assetsReview focus