Skip to content

CA2: catalyst-commerce becomes an Orun baseline - #3

Merged
pullely merged 1 commit into
mainfrom
orun/CA-3-becomes-a-baseline
Oct 28, 2026
Merged

pullely merged 1 commit into
mainfrom
orun/CA-3-becomes-a-baseline

Conversation

@pullely

@pullely pullely commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

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

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
@pullely
pullely merged commit fbf9a74 into main Oct 28, 2026
5 checks passed
@pullely
pullely deleted the orun/CA-3-becomes-a-baseline branch October 28, 2026 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants