[pelikhan]

Why

Azure hosting now uses Container Apps. Keeping the retired Functions backend, local emulation and maintenance jobs creates unnecessary upkeep and misleading deployment guidance.

Changes

• Remove the Functions runtime, deployment CLI/backend, ARM templates, Core Tools/Azurite harness and associated CI/simulator coverage.
• Make Container Apps the default Azure topology and update source bundles, Docker targets, host policy and documentation. Preserve shared hosted HTTP/proxy behavior and provisioning/ingestion jobs.
• Update architecture-maintenance guidance and regenerate its workflow lock with the policy-pinned compiler.

Compatibility

This intentionally removes cao-dashboard azure-functions, gh cao deploy azure, evidence release --azure-receipt, and the azure-functions host/topology selection. Azure deployment uses the existing offline deploy init --deployment azure-container-apps, generate and check workflow followed by separately reviewed operator-run deployment. This does not add automated Container Apps apply or establish real Azure acceptance.

Validation

• Passed root and server Go tests, Go vet, 110 focused contract tests, committed-source Azure asset tests, lint, type checks, documentation build and workflow compilation.
• Maintained CI workflows pass actionlint; the generated lock triggers existing unsupported-syntax diagnostics in the installed actionlint.
• Full npm validation is not green: unit tests encounter local PostgreSQL/PTY/macOS prerequisites and unrelated failures. Integration tests pass 296/299; remaining failures concern an existing credential-verification contract, the installed gh-aw version mismatch, and a missing inventory export.