chore: release azure-host's image to ghcr.io/open-craw

[russoedu]

smith 1.11.0 makes the docker convention configurable (monosmith-app/monosmith#285). As the maintainer chose, it's on again with the org's GitHub Container Registry:

[conventions.docker]
registry = "ghcr.io/open-craw"

[projects.azure-host.docker]
image = "opencraw-azure-host"

• azure-host gets an image task (docker build -f apps/azure-host/Dockerfile …).
• Each release of azure-host pushes ghcr.io/open-craw/opencraw-azure-host:<version> and :latest with the workflow's GITHUB_TOKEN. The generated ci.yml grants packages: write, and no secret is stored.
• On merge, this releases azure-host for the first time. smith release --dry-run shows unreleased → 0.1.0 (3 releasing commit(s)), would push ghcr.io/open-craw/opencraw-azure-host:0.1.0 and …:latest. Every other package is unchanged. A package pushed to ghcr this way starts public under the org; it can be made private in its package settings.
• All workflows pin smith 1.11.0.

Verified locally:

• smith run lint typecheck test build: 61/61 tasks succeeded.
• npm run lint:workspace: passes.
• smith ci generate --check: up to date.
• smith doctor: 29 passed. The one failure is "Docker is running": there's no Docker daemon on this machine. GitHub's Ubuntu runners have one.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TjR6eM2tUwU3NGnKXsmEap

[github-actions]

Release preview

Package	Version	Why	Status
azure-host	new → 0.1.0	3 releasing commit(s)	planned

Unchanged: agent, office-reader, core, probe, studio, cli, mcp, azure-durable, captcha-tesseract, ocr-tesseract, opencraw