⬆️ Upgrade maybe to 0.6.0

[github-actions]

Maybe is on 0.4.3; upstream released 0.6.0 on 2025-07-24 (minor bump).

Changes to apply

• hub/maybe/stack.yaml
  • version: "0.4.3" → version: "0.6.0"
• hub/maybe/stack.yaml
  • updated_at: 2025-03-01 → updated_at: 2025-07-24
• hub/maybe/compose.yaml
  • ${MAYBE_VERSION:-0.4.3} → ${MAYBE_VERSION:-0.6.0}

Warning

No published container tag was found for this version. Confirm the image exists before doing anything else — a release without an image is not shippable.

Warnings

• no image tag found for 0.6.0 on ghcr

Required before merging

A newer release is not evidence that the new version still works with our
compose file, our .env and our volumes. Establish a baseline first, then
prove the bump did not regress it:

# 1. baseline: does it pass today, before any change?
./packages/scripts/maintenance/test-stack.sh maybe

# 2. apply the edits above, then:
./packages/scripts/maintenance/test-stack.sh maybe

The test pulls every image, waits for all services to become healthy, checks
that nothing crash-loops during a settle window, and makes a real HTTP request
to the app's entry point.

• If the baseline fails too, this app was already broken: fix that first or say
  so in the PR — it is not a regression from this bump.
• If the baseline passes and the bump fails, do not merge. Read the release
  notes: a required new env var or a migration usually needs .env or
  compose.yaml changes alongside the version.
• Attach the test output to the PR.

_{Filed automatically from work/version-drift.json.}