v0.6.3

Use Check's default logo, at either level

Branding gains an explicit third logo state alongside "custom logo" and "inherit the instance default": show the Check extension's own built-in logo.

• Per tenant: a Use Check's default logo button on the Branding tab opts the tenant out of the instance default logo entirely. Its asset URL stops serving and generated artifacts carry an empty logoUrl, so the extension falls back to its built-in logo. Uploading a logo, or removing one to go back to inheriting, clears the opt-out; while opted out, an Inherit the instance default logo button returns to normal inheritance.
• Instance-wide: the Settings page now states the no-default-logo state explicitly (tenants without their own logo show Check's built-in logo) and presents default-logo removal as Use Check's default logo.
• The choice is stored in a new use_default_logo column on tenant_branding (migration 0002_use_default_logo.sql), settable through PUT /api/tenants/{id}/branding as use_default_logo: true|false (JSON or form field), and recorded in the audit log.

Covered by an end-to-end API test (opt out -> asset 404 and empty artifact logo URL -> upload clears the flag -> removal returns to inheriting) and an artifact-builder unit test.

Upgrading

This release includes a D1 migration (0002_use_default_logo.sql). From a deploy-button copy, run the Sync upstream workflow from the Actions tab; Workers Builds redeploys with npm run deploy, which applies the migration automatically. Or git pull and npm run deploy. No workflow-file changes.

Full changelog: v0.6.2...v0.6.3