Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
13. The compatibility application
test/backend/ is an ASP.NET Core 10 client of public APIs, with a React UI in
test/frontend/. Its Bicep template provisions HTTP services, both SQL engines,
Redis and monitoring resources. It imports official Azure SDKs and native
protocol clients, not emulator implementation classes.
The workflow covers deployment/redeployment, secret/configuration access, Blob transfers/SAS, Queue receipt rotation and recovery, SQL/Redis writes, Application Insights export and Logs Query/Metrics. Each run has explicit steps, cancellation, bounded timeouts and a trace ID. The queue worker is a deterministic workflow step, not a continuously hosted service.
Settings, client secrets, database passwords and server leaf keys stay in private backend configuration. Browser access uses a separate local token exchanged for a Secure/HttpOnly/SameSite session cookie; mutations have origin/header checks. Errors report safe status/type information instead of SDK bodies/connection strings. Frontend state validation and escaped rendering are part of the compatibility test, not conveniences that should be removed for demonstrations.
application-build.py uses locked package graphs and prepares an image context
from published artifacts/license notices. application-env.py owns runtime
identity, CA/DNS setup, labels, subnet/ports and cleanup. Disposable tests use
unique environments; persistent development uses .local/application/development.
Attached clients must leave the network before the owning helper removes it.
application-observability-test verifies real backend correlation and source
redaction, stops an owned PostgreSQL container to observe failure/recovery,
and stops the collector while a complete workflow continues. It does not mutate
unrelated engines. These tests establish the supported subset; they do not
prove full Azure API parity or performance.
Read application operations (source checkout required), application acceptance (source checkout required), and the user C# tutorial. When updating SDKs, update locks and dependency/license evidence together, then run relevant browser and real environment checks.
The live workflow
The result panel from a disposable MySQL run includes real SDK operations, redeployment, queue recovery and Application Insights/Monitor compatibility.
Screenshot regeneration and PDF publication are described in manual publishing (source checkout required).