[lweberru]

Model Serving outages currently block every Configurator release. Add an explicit release_mode=dev-skip-assistant-qualification choice to the manual GitHub UI workflow so Dev can advance without the live Assistant qualification job. LZC_ASSISTANT_ENABLED retains its existing environment value: the Assistant stays enabled when configured. Runtime behavior, UI and API are unchanged. The default qualified release still requires the complete repeated source-bound Assistant qualification.

The exception is limited to fresh main builds and the existing protected Dev destination. Every other build, database, browser, packaging, publication, migration and runtime check remains required. The source-bound manifest records Dev scope and assistantQualified=false; the distinct build job and manifest guards prevent either qualified or unqualified promotion using release_run_id. Skipped qualification is never reported as successful, and earlier failed receipts remain evidence. Existing conversations/proposals and runtime validation/authorization are untouched. Model availability still determines whether inference works.

After merge, use Actions → Configurator Release → Run workflow → main, release_mode=dev-skip-assistant-qualification, build_only=false, empty release_run_id, runner_pool_size=1. Review the exact source/run and approve lzc-dev-release after applicable checks. English/German workflow, operator and knowledge-contract documentation describe the explicit Dev exception. A deployment-only failure requires inspection and a fresh run; these unqualified artifacts cannot subsequently be promoted.

Validation of the final implementation:

• Pinned Node 24.21.0 / npm 11.19.0 npm run check: 977 passed, 69 existing default-gated skips.
• Release preparation, artifact, buildpack and image-staging guards: 33 passed, including preservation of both runtime Assistant opt-in and opt-out, main-only scope, and rejection of unqualified promotion/cross-mode manifests.
• actionlint v1.7.7: passed (shellcheck unavailable and disabled); git diff --check: passed.
• The final diff contains no app/UI/API changes. GitHub application CI reruns the complete integration/browser flow on the updated source.

No live-model qualification is claimed for this Dev mode. No Dev deployment, production operation or customer infrastructure Apply has been performed. Hosted exact-source verification, including warm Runner handoff/replacement with pool size 1, remains required after deployment.