Foremerge v0.3.1

What's Changed

• Fix four HIGH findings from the v0.3.0 review by @naw103 in #1
• Protect the acceptance gate table and define what authoritative asserts by @naw103 in #2
• Close the event replace gap, widen duplicate repair, and cut 0.3.1 by @naw103 in #3

New Contributors

• @naw103 made their first contribution in #1

Full Changelog: v0.3.0...v0.3.1

Foremerge v0.3.0

Known defect: use 0.3.1 instead

Every time this version opens a coordination store it writes a duplicate
"detection" row for any conflict that already recorded one, so a single
detection shows two observations while the event log records one. The
duplicate cannot be deleted afterwards, because the append-only trigger that
protects those rows blocks removal.

This version also has three further defects fixed in 0.3.1: a validation could
pass using an excluded generated file that is not in the accepted commit, an
interrupted upgrade could silently drop intents from scope queries, and the
documented 30 second shutdown was not an exit bound.

Upgrade to 0.3.1, which repairs affected stores automatically the first
time it opens them. No manual cleanup is needed, and observations that
genuinely differ are preserved.

Full Changelog: v0.2.0...v0.3.0

Foremerge v0.2.0

Full Changelog: v0.1.0...v0.2.0

Foremerge v0.1.0

Full Changelog: https://github.com/naw103/foremerge/commits/v0.1.0