[REFINE:OPS-7.c] Execute the OPS-7.b decision

[Ranelkin]

Step

ID: OPS-7.c
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

If decision = publish: trigger gh workflow run release.yml -f tag=v0.1.2 --repo logscale-it/bookie (or flip the existing draft with gh release edit v0.1.2 --draft=false); confirm the three platform artifacts are attached. If decision = pin: gh release delete v0.1.2 --yes, git tag -d v0.1.2 && git push origin :refs/tags/v0.1.2, and edit docs/operations.md §2 to link https://github.com/logscale-it/bookie/releases/tag/v0.1.1 (or whichever version is current).

Verification

If publish: gh release view v0.1.2 --json isDraft,isLatest,assets -q '"draft=\(.isDraft) latest=\(.isLatest) assets=\(.assets|length)"' returns draft=false latest=true assets=3. If pin: gh release list --repo logscale-it/bookie --json tagName | jq -r '.[].tagName' does not contain v0.1.2; grep -c 'releases/latest' docs/operations.md returns 0; grep -c 'releases/tag/v' docs/operations.md returns >=1.

Dependencies

Depends on: #225 (OPS-7.b).

Audit

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