Re-author the deployment view's Archify spec #363

The merge review found PR #357 edited three arc42 diagrams without touching their Archify specs. Two are fixed; the deployment one needs a real layout pass because the new labels no longer fit the boxes. A new session would re-author that spec and the two diagrams that have no spec at all.

Context

Three Archify diagram artifacts fell out of step with their mermaid fences when PR #357 (ADR 0005, Azure-hosted task replica) landed. Two were repaired in the merge-review session; this is the remainder.

Run node tools/diagrams/archify-artifacts.mjs scan from the repository root to see the current state. Expected: 1 stale, 2 missing.

1. STALE ΓÇö .arc42/07-deployment-view.md diagram chore(deps): Bump actions/checkout from 4.2.2 to 7.0.1 #3, spec .arc42/_archify/07-deployment-view.3.architecture.json. The fence now reads "Azure Container Apps / (consumption, scale-to-zero)" instead of "Azure App Service / or Container Apps", "Azure Cosmos DB (serverless) / tasks replica + change feed, sync state, webhook events, machine registry" instead of the shorter Cosmos sublabel, and the AppService->CosmosDB edge gained the label "Managed identity ΓÇö data-plane role". A first attempt at editing the spec to match failed validation and was reverted: the longer Cosmos sublabel needs ~263px and its box provides 202px, and widening the Data-column boxes to 290 pushed cosmos, keyvault and fcm outside the 930x700 viewBox and broke the push-notification connection's via-routing. It needs a real layout pass ΓÇö probably a larger meta.viewBox with the components repositioned, or a shortened sublabel ΓÇö rendered with node tools/diagrams/archify-artifacts.mjs render <spec path> until it reports 9/9 checks with 0 warnings at showcase quality.

2. MISSING ΓÇö .arc42/07-deployment-view.md diagram Add .domain, .arc42, and .backlog knowledge folder structure #4 (the provisioning/delivery flowchart) and .arc42/08-crosscutting-concepts.md diagram Add repository governance scaffolding under .github/ #1 (a sequence diagram). Both were added by PR Plan an Azure-hosted task replica for multi-device sync (ADR 0005) #357 and have no Archify specification at all. node tools/diagrams/archify-artifacts.mjs scaffold <chapter> <ordinal> prints the fence and says where the spec goes; it deliberately writes no stub.

Read tools/diagrams/README.md first ΓÇö it explains the hash matching, the quality profiles, and why render --all will not pick up a spec-only edit (pass the paths instead). Every specification's meta must carry "animation": "trace", which tests/Backlog.ArchitectureTests/ArchifyArtifactMotionTests.cs enforces.

Note there is no CI gate on any of this ΓÇö .github/workflows/ never runs archify-artifacts.mjs verify ΓÇö which is why it rotted silently. Consider whether adding verify to the pull-request workflow is worth proposing.

Filed automatically from a Claude Code suggested task.