Repository navigation
CA2: catalyst-commerce becomes an Orun baseline - #3
Merged
Merged
Conversation
The commerce baseline's machinery on this tree: blueprint.yaml (the console card: one Cloudflare provider, the subdomain read from the connection, no domain asked, Workers Paid stated) and repo-blueprint.yaml (one landing, 01-product — the R2 and KV roots, the storefront's packages, the storefront and its tests — then the record, 02-docs; task set-up in the background, landings checked in the box, a 5 s watch, one secrets reconcile minting workers-deploy, r2-data and the account id). .baseline/ (identity — slug catalyst-commerce, the Catalyst Store seam — the store's README with Connecting BigCommerce, and the task contracts), the rename engine, the bootstrap helpers, the deployment-record renderer probing / and /api/health, the phase pages, the context pack, and the baseline's tests: manifest, phases, coverage, rebrand, retouch, bootstrap-defer, wire, generated component docs, the leak gate (the slug only as the identity, the store's name only at its seam, Catalyst's licence shipped), the offline bootstrap with the product's own plan (both roots applied at level 0, the Worker waiting on both), and the end-to-end tier: the stage lane's steps in a staged tree, the product served as born (its smoke, asked to connect a store, Auth.js signing with the key generated in KV, never a 500), then rebuilt with a stand-in BigCommerce connected (testing/lib/fake-bigcommerce.mjs, graphql-js over the published schema) and a canary storefront token no build artifact may carry, and browsed — a second visit reads BigCommerce not at all, a change stays cached inside its window and is re-read in the background after it. Every tier passes locally on orun v2.89.0. Co-Authored-By: Claude <noreply@anthropic.com> Orun-Task: CA-3
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.
The commerce baseline's machinery on this tree: blueprint.yaml (the console card: one Cloudflare provider, the subdomain read from the connection, no domain asked, Workers Paid stated) and repo-blueprint.yaml (one landing, 01-product — the R2 and KV roots, the storefront's packages, the storefront and its tests — then the record, 02-docs; task set-up in the background, landings checked in the box, a 5 s watch, one secrets reconcile minting workers-deploy, r2-data and the account id). .baseline/ (identity — slug catalyst-commerce, the Catalyst Store seam — the store's README with Connecting BigCommerce, and the task contracts), the rename engine, the bootstrap helpers, the deployment-record renderer probing / and /api/health, the phase pages, the context pack, and the baseline's tests: manifest, phases, coverage, rebrand, retouch, bootstrap-defer, wire, generated component docs, the leak gate (the slug only as the identity, the store's name only at its seam, Catalyst's licence shipped), the offline bootstrap with the product's own plan (both roots applied at level 0, the Worker waiting on both), and the end-to-end tier: the stage lane's steps in a staged tree, the product served as born (its smoke, asked to connect a store, Auth.js signing with the key generated in KV, never a 500), then rebuilt with a stand-in BigCommerce connected (testing/lib/fake-bigcommerce.mjs, graphql-js over the published schema) and a canary storefront token no build artifact may carry, and browsed — a second visit reads BigCommerce not at all, a change stays cached inside its window and is re-read in the background after it. Every tier passes locally on orun v2.89.0.
🤖 Generated with Claude Code