{
  "version": "0.3.1",
  "contractChanges": {
    "MIG-001": "Rephrase the Sentry non-goal to preserve synthetic-only qualification and pending owner-export qualification in wording accepted by the Site claim guard. No importer or guard behavior changes.",
    "SDK-009": "Partial implementation: accept Sentry events without a release, auto-create optional release identities, preview ordering and strict-registration policy, and support plain resolution with revision-fenced bulk previews. Preserve independent release-resolution boundaries in sliced private archives. Remaining limits are documented in docs/SENTRY-RELEASES.md.",
    "GROUP-001": "Partial implementation: preview and activate project stack and fingerprint rules for later Sentry intake, retain immutable admission policy snapshots and grouping explanations, and preserve rules in private archives. Existing occurrences are not regrouped; remaining limits are documented in docs/GROUPING-RULES.md."
  },
  "extensionPointChanges": [],
  "migrations": [
    "migrations/core/0042_grouping_rules.sql",
    "migrations/core/0043_sentry_releases.sql"
  ],
  "breaking": false,
  "agentUpdateInstructions": "From 0.3.0: export a private archive first (Settings > Download private archive, or rer export with local dev stopped). Run git pull in the existing checkout, then rer dev locally or rer deploy from the original deploying checkout for a hosted installation. Additive migrations 0042-0043 apply automatically; existing projects, evidence, triage states and project keys are preserved. Keep the existing database, local settings, project keys and deployment receipts; do not reset or restore into the populated installation. Earlier upgrades must also apply the migrations described in CHANGELOG.md. The import door remains off by default and requires the installation's owner-claim trust bindings (RER_OWNER_CLAIM_*); self-hosted rer deploy does not declare them. Local dev opens through its private RER_OPEN owner entry and suppresses mail. The application pins rer 0.2.49. SDK 0.2.0 remains unpublished on npm and is not published by this app release.",
  "publicReleaseNotes": "Spool 0.3.1 rephrases the Sentry non-goal for the RunEditRun Site import while keeping its limitation: organization import has been exercised with synthetic fixtures only, and owner-export qualification is pending. Since 0.3.0, project stack and fingerprint rules can be previewed and activated for later Sentry intake, with immutable event policy snapshots and grouping explanations. Sentry events can omit a release or auto-create one; release ordering and strict-registration settings have previews, plain resolution reopens on the next accepted unsuppressed event, bulk previews are revision-fenced, and sliced private archives retain release-resolution records. These remain partial GROUP-001 and SDK-009 implementations with documented gaps. Select chevrons have consistent spacing and disabled styling; the measured verification disk floor is 4 GiB. Upgrading from 0.3.0 applies additive migrations 0042-0043. The importer and Site guard are unchanged. This app release does not publish the SDK or extend the hosted/import qualification recorded for 0.3.0."
}