docs(prs): supply the PR-doc PR#53 was merged without #53

Merged
mi merged 1 commits from docs/pr53-doc-and-release-1.8.1 into main 2026-09-11 09:09:35 +02:00
Owner

PR#53 went to main squashed and without its document, which AGENTS.md
requires for every pull request. Its commit message was thorough, but a
commit message is not where the next reader looks.

The document describes exactly what bbb892f did — nothing added, nothing
reinterpreted — and says so at the top, because a PR-doc written after
the merge is a different kind of evidence than one written with the
change.

As an additional change it also supplies what PR#53 did not bring: the
version, now 1.8.1, and its release-notes entry. The rule that every PR
carries its own version landed in PR#52, one commit earlier, and
ReleaseVersionConsistencyTest could not catch the omission — it compares
the version against the top release note, and both still said 1.8.0.
That gap is PR#52's own Open Question, and this is it happening.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

PR#53 went to main squashed and without its document, which AGENTS.md requires for every pull request. Its commit message was thorough, but a commit message is not where the next reader looks. The document describes exactly what bbb892f did — nothing added, nothing reinterpreted — and says so at the top, because a PR-doc written after the merge is a different kind of evidence than one written with the change. As an additional change it also supplies what PR#53 did not bring: the version, now 1.8.1, and its release-notes entry. The rule that every PR carries its own version landed in PR#52, one commit earlier, and ReleaseVersionConsistencyTest could not catch the omission — it compares the version against the top release note, and both still said 1.8.0. That gap is PR#52's own Open Question, and this is it happening. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mi added 1 commit 2026-09-11 09:09:30 +02:00
PR#53 went to main squashed and without its document, which AGENTS.md
requires for every pull request. Its commit message was thorough, but a
commit message is not where the next reader looks.

The document describes exactly what bbb892f did — nothing added, nothing
reinterpreted — and says so at the top, because a PR-doc written after
the merge is a different kind of evidence than one written with the
change.

As an additional change it also supplies what PR#53 did not bring: the
version, now 1.8.1, and its release-notes entry. The rule that every PR
carries its own version landed in PR#52, one commit earlier, and
ReleaseVersionConsistencyTest could not catch the omission — it compares
the version against the top release note, and both still said 1.8.0.
That gap is PR#52's own Open Question, and this is it happening.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mi merged commit 07785a6e14 into main 2026-09-11 09:09:35 +02:00
mi deleted branch docs/pr53-doc-and-release-1.8.1 2026-09-11 09:09:35 +02:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mi/werkator#53