chore: reset the initial server release to 0.0.1

[Eoic]

Summary

Use 0.0.1 for the initial testing baseline in package metadata, the lockfile, and deployment defaults. Permit an initial version reset when no release tags exist, while retaining monotonic version checks for published releases.

After publishing the replacement 0.0.1 image and release, perform a one-time cleanup of the obsolete 1.0.0 container by its exact manifest digest. Delete its architecture/attestation manifests before the index, preserve shared replacement manifests, and refuse to remove unrelated tags. Keep the public package itself. Cleanup is restricted to this repository and version, using the publishing workflow's package admin access.

Validation

• 10 focused release-gate and 6 cleanup tests passed.
• Ruff lint/format checks and strict Mypy passed on changed tooling.
• Release workflow passed Actionlint.
• Read-only inspection confirmed the old image is public and its manifest graph contains five versions.
• The committed-version gate emits release=true and v0.0.1 for this change.

Deployment

The obsolete GitHub v1.0.0 release and tag have been removed. No application containers are running on Hetzner, and no database migration has run there. Merge this PR first, verify the replacement container and cleanup, then install the matching client web artifact before deployment. Existing VM secrets and signing keys must be preserved.

The live package deletion will execute after merge; it cannot run with the current local GitHub token, which lacks package management scopes.

Related: client version reset, coordinated workspace release.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-05T21:11:53.058190Z	ee48df9	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.