[REFINE:OPS-7.d] Confirm releases/latest resolves correctly + CHANGELOG entry

[Ranelkin]

Step

ID: OPS-7.d
Source refinement task: OPS-7 Publish v0.1.2 or pin releases/latest back to v0.1.1
Directory: .github/workflows/, GitHub Releases UI
Execution tier: deterministic

Why this matters for prod

gh release list shows Bookie v0.1.2 in Draft state since 2026-05-11; v0.1.1 (2026-03-15) is still tagged Latest. docs/operations.md §2 instructs non-technical users to install from https://github.com/logscale-it/bookie/releases/latest, which currently resolves to the two-month-old v0.1.1 — i.e. the GoBD compliance work, the boot_check command, the migration-out-of-date recovery dialog, the DSGVO Auskunft/Löschung flows, the single-instance lock, and the invoice_audit SQL-side immutability are all merged on master but unreachable for users.

What to do

Verify that https://github.com/logscale-it/bookie/releases/latest resolves to the chosen target version (v0.1.2 if published, v0.1.1 if pinned). Add a CHANGELOG.md line under the 2026-05-14 (or new) date explaining the release outcome and any operations.md change.

Verification

curl -sLI -o /dev/null -w '%{url_effective}' https://github.com/logscale-it/bookie/releases/latest ends with the chosen /tag/vX.Y.Z; CHANGELOG entry references the decision.

Dependencies

Depends on: #226 (OPS-7.c).

Audit

• Step ID: OPS-7.d
• Source task: OPS-7 (see REFINEMENT.md)
• Generated from refinement.decomposition.json on 2026-05-14
• Created by: Sandcastle (production-refinement skill)