⬆️ Upgrade shiori to 1.8.0

[github-actions]

Shiori is on 1.7.4; upstream released 1.8.0 on 2025-09-26 (minor bump).

Changes to apply

• hub/shiori/stack.yaml
  • version: "1.7.4" → version: "1.8.0"
• hub/shiori/stack.yaml
  • updated_at: 2025-01-03 → updated_at: 2025-09-26
• hub/shiori/compose.yaml
  • ${SHIORI_VERSION:-1.7.4} → ${SHIORI_VERSION:-1.8.0}

Container tag v1.8.0 was verified to exist upstream.

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 shiori

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

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.}