Release Flowlight 0.15.1

[blessdyb]

Summary

• keep managed-pack Review and activation as local drafts until an explicit Save succeeds
• route selected-app field submission to Add instead of the sheet Save action
• observe committed managed-pack state directly so cards refresh after asynchronous persistence
• release the app as 0.15.1 build 37 while keeping the Network Extension pinned at 0.15.0 build 23

Verification

• proved the new focused regression gate fails before the editor draft/action seam existed (xcodebuild exit 65)
• 31 focused managed-pack and installed-app tests passed with zero failures
• full suite: 694 tests passed with zero failures
• localization parity: 1,588/1,588 keys in all ten catalogs
• static site: 53 pages checked, zero problems; generated docs reproduce cleanly
• release-note extraction for 0.15.1 passed
• local Release build succeeded as a universal binary; strict deep signature verification passed
• built metadata: app 0.15.1/37, embedded extension unchanged at 0.15.0/23
• installed-app exercise confirmed Review stays open, Cancel leaves both packs durably off, and no exceptions or managed activity are created
• delayed high-level review found and the candidate now covers app-scan readiness, overlapping card saves, in-flight dismissal/editing, concrete persistence failures, and stale preview invalidation
• independent re-review found no remaining release blockers
• restored signed public app and confirmed it reconnects to the enabled 0.15.0/23 filter

Supersedes #49: public 0.15.0 installed-artifact verification exposed the editor activation defect after publication, so this replacement keeps immutable v0.15.0 as ancestry without merging the failed acceptance candidate.

🤖 Generated with Claude Code

[blessdyb]

Superseded by #51. The immutable public 0.15.1 artifacts passed signature, notarization, Gatekeeper, editor, and Homebrew checks, but installed-artifact acceptance then exposed an upgraded-database defect: rule_pack_event_rollups could carry migration marker 2 while its physical UNIQUE key still omitted match, causing the production event upsert to fail with ON CONFLICT clause does not match any PRIMARY KEY or UNIQUE constraint. 0.15.1 remains immutable; the physical-schema repair and carried-forward editor fixes are reviewed in 0.15.2.