Repository navigation
WP2: cms-wordpress becomes an Orun baseline - #3
Merged
Merged
Conversation
cms-sanity's machinery on this tree, in the turso v8 shape: blueprint.yaml (the console card: one Cloudflare provider, the subdomain read from the connection, no domain asked, WordPress connected by its owner afterwards) and repo-blueprint.yaml (one landing, 01-product, then the record, 02-docs; task set-up in the background, landings checked in the box, a 5 s watch, one secrets reconcile). .baseline/ (identity, the product's README with Connecting WordPress and Deploy by hand, task contracts), the rename engine, the bootstrap helpers, the deployment-record renderer probing /, /posts (sample or connected) and the webhook, the phase pages with minutes, the context pack, and the baseline's tests: manifest, phases, coverage, rebrand, retouch, bootstrap-defer, generated component docs, the leak gate, the offline bootstrap with the site's own plan, and the end-to-end tier that builds the site in the stage lane's staged tree and reads every route it promises, unconnected. Every tier passes locally on orun v2.89.0. Co-Authored-By: Claude <noreply@anthropic.com> Orun-Task: WP-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.
cms-sanity's machinery on this tree, in the turso v8 shape: blueprint.yaml (the console card: one Cloudflare provider, the subdomain read from the connection, no domain asked, WordPress connected by its owner afterwards) and repo-blueprint.yaml (one landing, 01-product, then the record, 02-docs; task set-up in the background, landings checked in the box, a 5 s watch, one secrets reconcile). .baseline/ (identity, the product's README with Connecting WordPress and Deploy by hand, task contracts), the rename engine, the bootstrap helpers, the deployment-record renderer probing /, /posts (sample or connected) and the webhook, the phase pages with minutes, the context pack, and the baseline's tests: manifest, phases, coverage, rebrand, retouch, bootstrap-defer, generated component docs, the leak gate, the offline bootstrap with the site's own plan, and the end-to-end tier that builds the site in the stage lane's staged tree and reads every route it promises, unconnected. Every tier passes locally on orun v2.89.0.
🤖 Generated with Claude Code