Accepts ADR-0018, the release workflow record

[johnnyt]

Flips ADR-0018 (the release workflow publishes to Hex on a version tag) from proposed to accepted. The record was to be accepted once the release workflow had published a version of this package; that these records flip together on that first publish, one pull request per repository, was ruled by the operator, 2026-10-06.

What changes

docs/adr/ only:

• 0018-the-release-workflow-publishes-on-a-version-tag.md: the Status line becomes Status: accepted (2026-10-10, statifier_persistence 0.24.1), and a dated foot Note, ## Note (2026-10-10): accepted, is added below the Consequences.
• README.md: the ADR-0018 row's status column reads accepted.

The two removed lines are the old Status line and the old index row; nothing else is removed or reworded.

Evidence

• First publish through the workflow: statifier_persistence 0.24.1, tag v0.24.1 on commit 019710344401bce3a7c3607978b9a0e8b39c8bb5, run https://github.com/riddler/statifier_persistence/actions/runs/37307983702 (tag push, first attempt, every step green). Hex shows the version.
• Later publishes through the workflow: none; that run is the workflow's only run.
• Verified at: main at f14c8a642c684071cc3b679e165072f0b968cbcb. No commit after the tag touches any file the record cites.

Direction check (worker's own, before the conductor's pass)

Every claim was read on main at f14c8a6. Decision 1: release.yml triggers on push of tags v*.*.* only, permissions: contents: read, one job release in concurrency group release-${{ github.ref }} with cancel-in-progress: false. Decision 2: the steps "Check the tagged commit is on the default branch" (git merge-base --is-ancestor against the branch read from github.event.repository.default_branch), "Check the tag names the version in mix.exs" and "Check Hex does not already show this version" all run before erlef/setup-beam; "Full quality gate" runs the command from .claude/wurk.json gate.full (mix quality) with the same postgres:17 service and PG* env, toolchain, cache and dependency steps as ci.yml's gate job. Decision 3: "Publish to Hex" runs mix hex.publish --yes with HEX_API_KEY from the HEX_API_KEY secret in that one step's env: (the secret is an organisation secret visible to this repository by name); the last step prints the Hex and HexDocs addresses. Decision 4: no package-only flag is passed. Decisions 5 and 6: no retry, re-run, revert or retire step exists in the workflow; a Hex-shown version exits 1 at the Hex check. Consequences: CLAUDE.md's release row and "Release preps" paragraph, and .claude/wurk/release.md "What a release here still is not", say an agent never runs mix hex.publish, the workflow publishes on the tag push, and a failed workflow is re-run from its Actions page; the toolchain, cache, dependency and gate steps are textually the same in both workflows. The Context's "Nothing runs on a tag push today" describes the repository when the record was written; decision 1 is the change, and the Note says so without rewording the Context. git diff --numstat origin/main -- docs/adr/ shows 36 1 for the record and 1 1 for the index.

Gate

No Elixir code changes, so there is no gate to run (CLAUDE.md: a change touching no Elixir code has no gate to run and may commit on review of the diff alone). CI runs on the request.

Provenance

That the Note gives the first publish, the later publishes and the verified SHA, and that the Status line names the first version published through the workflow in this repository's accepted shape, were decided by the conductor under a standing consent, 2026-10-10. No changelog fragment: changelog.d/README.md excludes ADRs.