[shiny-code-app]

Why

CM previews inherit Website settings from the testing lane, but some preview databases do not have the Website module. The bootstrap then raised Website bootstrap supplied, but the website module is not installed., which failed the whole data workflow. Hand overrides with null intent made those previews serve, so skipping the bootstrap is enough.

What changed

apply_website_bootstrap keeps raising when LAUNCHPLANE_WEBSITE_BOOTSTRAP_REQUIRED is enabled. Without the flag, a payload for a database that lacks Website logs the skip and returns. Launchplane already sends the flag for stable lanes and exact preview intent, and stops sending it for template-inherited preview intent in cbusillo/launchplane#5829.

Safe to land first: until Launchplane changes, every Launchplane-managed runtime that renders this payload still sends the flag and stays strict. Local runtimes without the flag now skip instead of failing.

Refs cbusillo/launchplane#5828.

Verification

• tests/test_odoo_website_bootstrap.py (31) and tests/test_odoo_startup.py (48) pass. The optional-case test raises without the fix.
• ruff format --check . and ruff check . pass.
• JetBrains inspection: UNKNOWN, native_python_support_plugin_unavailable, native PyCharm, 2 files, no findings reported; tracked on Headless inspection workers: confirm project interpreter and Pydantic plugin so type findings stop being noise codex-skills#3363. Not a clean result.
• OpenAI reviewed this diff directly and found none.

Removed: the unconditional failure when Website is absent and the bootstrap is optional.
Net lines: +13.

[shiny-code-app]

Review result: weighed
Head: aaacacb

Review by another model, weighed for head aaacacb.

Reviewer: OpenAI through the model-review helper (model not reported by the CLI). Asked whether a run that should fail can now pass silently in startup, data workflows or local runtimes, and whether the skip breaks later settings or readback steps. Answer: none. Nothing to act on.