Prepare v0.1.0-beta.97

[callumalpass]

Summary

Prepare the beta97 version identity after the five requested fixes have all merged normally:

• Fix Editor deployment file-intent verification for semantic v2 #412 — semantic-v2 Editor deployment-manifest verifier
• Fix desktop daemon service targeting #404 — installed desktop daemon targeting
• Refine editor loading and quiet visual treatment #405 — quiet Editor loading treatment
• Refine approval and authentication surfaces #392 — minimal portal authorization/authentication views
• Complete Google and GitHub public signup #403 — Google/GitHub public signup

Base: c675d1d. Each selected PR completed full merge-group qualification.

The version edits change only the 14 synchronized npm manifests, Cargo workspace version and the eight owned package versions in each Cargo lock, and the MCP advertised version. Third-party dependencies, engine pin, capability/issuance semantics, migrations, workflows and tests are unchanged. The ordinary predecessor remains exact published beta96; historical beta95 coverage remains separate and mandatory.

Identical test-image registry repair

The first full merge-group run34644607286 failed in files/provider fixture startup: Docker Hub denied anonymous pulls for minio/minio:RELEASE.2025-09-07T16-13-09Z. Independent inspection reproduced the denial. MinIO's official Quay registry serves the identical multi-platform manifest, SHA256 14cea493d9a34af32f524e538b8346cf79f3321eff8e708c1e2960462bd8936e, matching the previously used Docker Hub image's recorded digest. The two system scripts and shared Compose fixture now use that official registry with tag plus exact digest. No mirror infrastructure, changed binary, credential workaround, scenario omission or deadline relaxation. The second full group34647908340 reached the companion minio/mc command and exposed the same Docker Hub denial there; the local cache had hidden that pull. Its official Quay manifest is likewise identical: SHA256 a7fe349ef4bd8521fb8497f55c6042871b2ae640607cf99d9bede5e9bdf11727. All six references across the three files are now audited and digest-pinned, with both remote manifests independently resolved. Registered files/provider suites pass locally at6351f2ade18c45773aff275a028dd3a06ac7763b. A fresh complete merge group remains mandatory; both original failures are retained.

Validation

• Release version/tag consistency and release-version lock regression tests
• Frozen pnpm install and workspace package builds
• Release component contract and architecture checks
• Locked Cargo metadata, Cargo formatting, and whitespace checks
• Normal exact-head checks and full merge-queue qualification remain required

Release boundaries

This PR does not create a tag or authorize deployment/client publication. Beta97 requires its own exact main CI and signed bundle, reviewed supported beta96 rollback relationship (current private41→41 policy does not yet admit it), genuine provider signup acceptance, staging qualification/rollback/soak, protected production promotion, live verification and monitoring. Do not reuse beta96's consumed publication attempts or alter its immutable tag. Client publication remains npm → desktop → production Editor only after exact beta97 production verification.