release: 0.7.1-rc.2

[lorem-dev]

Cuts a second release candidate for 0.7.1, and moves the changelog's rules into the file they govern.

The rules block

CHANGES.md now opens with a comment stating what earns an entry and what does not. Everything else defers to it rather than restating it.

The rules had been living in three places that drifted apart: CONTRIBUTING.md carried a 25-word cap, check-changes asked for a bullet per feat/fix/refactor/perf commit, and nothing anywhere said what does not belong. The result was predictable -- refactors, CI work and bugs that never shipped all earned entries, and the file drifted from "a reason to upgrade" toward a commit log with worse formatting.

The rule that changes most in practice: a fix earns an entry only when the bug was broken in a released version. A defect introduced and fixed on the same branch never reached anyone, so the changelog has nothing to say about it. On a long branch that is most fixes -- and it is exactly the case check-changes was most likely to report as a missing entry.

What that does to this release

Applying the block to the entries already staged for 0.7.1 removed two of three:

Entry	Verdict
The add-repository dialog now stays open and states the reason	kept -- a behaviour change a user would be surprised by
Dependency bumps (SHA-256, Argon2, AES, TOML)	cut -- "no user-visible effect", by its own wording
The new end-to-end suite	cut -- "test changes"

That also retires the ### Internal section this branch briefly introduced: the block leaves no room for it, and a file whose header forbids its own contents is worse than either rule alone.

One bullet for the release. That is what this release actually contains that a user can see.

Aligned

• CONTRIBUTING.md -- points at the block as authoritative; keeps the 25-word cap, which the block does not cover.
• .agents/skills/check-changes/SKILL.md -- no longer demands an entry per refactor; encodes the released-version rule; checks the block's soft (10) and hard (50) bullet limits.
• .agents/skills/check-docs/SKILL.md -- ## Development is no longer the first heading.
• AGENTS.md -- entries are planned against the block, and most of a plan's tasks earn none.
• CLAUDE.md -- no changelog rules to align; left alone.

Verified

$ node scripts/check-version.mjs v0.7.1-rc.2
check-version: all packages at 0.7.1-rc.2, matches v0.7.1-rc.2

$ node scripts/release-notes.mjs v0.7.1-rc.2
### Changed
- Adding a repository that fails now keeps the dialog open and states the
  reason, instead of closing and leaving only a notification.

The block sits above ## Development deliberately: release-notes.mjs extracts from a ## Version heading to the next ## , so nothing above the first one can reach a GitHub release. Confirmed it does not leak, on this version and on 0.7.0. bump-version.mjs still finds ^## Development$.

The previous v0.7.1-rc.1 tag and its pre-release have been deleted; v0.7.0 is Latest again.