Release v1.2.4

Closes #135

Fixed

• Ante now publishes each fact to its outbox once per event it handles, even when Chronicle delivers that event again. Chronicle redelivers after an Ante instance stops after publishing but before acknowledging, for example in a rolling deploy with two instances. Before this change:
  • LegalTermsAccepted and OrganizationRegistrationCompleted could reach the host twice.
  • A redelivered acceptance was refused by its one-use constraint but failed the forwarding reactor, which kept retrying.
  • Rejections were republished on redelivery.
• How: each forward checks whether the outbox already holds the fact for this delivery, using the same check token issuance has used since #110. A scoped append keeps two instances from both publishing, and a fact that is already published counts as success. Live status notifications still run.

Hosts should still handle facts idempotently, because delivery from Ante's outbox to a host inbox is at least once.

Local: Tier 1 PASS, Integration 309/309. The new two-instance mid-forward specs fail without the fix. Reviewed with Anthropic models only (same-provider review, no cross-provider check).