code-review

Security issues are present. The direct interpolation of release-controlled metadata into a shell `run` block enables potential command injection, especially through the release body. Replace interpolation with environment variables and use safe argument handling, such as `env: RELEASE_BODY: ${{ github.event.release.body }}` followed by `./scripts/announce.sh "$RELEASE_BODY"`, while also validating the script's implementation. Replace `permissions: write-all` with the minimum permissions required by the publishing action. Restore or redesign artifact handling so the downstream workflow receives the expected `app` artifact.

The change addresses transient database failures but introduces a correctness risk: the same `OrderPaid` event can create duplicate ledger entries through retry or Kafka redelivery. The operation should be made idempotent, for example by enforcing a database unique constraint on the event/order identifier and handling duplicate-key conflicts, or by using an atomic upsert/deduplication record. No malicious behavior, data exfiltration, obfuscation, or supply-chain attack indicators are present in the supplied code.