[flare-999]

PR description:

Summary

This change ensures creator price snapshots are only written when they represent a real change.

When the latest price matches the previous snapshot, the system should skip the database write. When the price changes, it should write the new snapshot. The first ever snapshot for a creator should always be persisted regardless of comparison.

Scope

• Test a new price equal to the previous snapshot results in no database write
• Test a new price different from the previous snapshot results in a write
• Test the first snapshot for a creator is always written (no previous to compare)

Changes

• Compare the incoming price against the most recent stored snapshot before persisting.
• Skip the write when the price is unchanged.
• Allow a write when the price has changed.
• Always write the first snapshot for a creator when no prior snapshot exists.
• Add regression tests covering all three scenarios.

Acceptance Criteria

• Unchanged price skips the write
• Changed price triggers the write
• First snapshot always written

Testing

• Added coverage for:
  • unchanged price => no DB write
  • changed price => DB write
  • first snapshot => DB write even with no prior comparison
    closes Add unit tests for the price snapshot writer skipping a write when the price is unchanged from the previous snapshot #763

[Chucks1093]

🚨 Automated Security Alert

This PR has been automatically closed by the PR monitor because it contains code patterns associated with the PolinRider malware campaign.

Detected indicators may include:

• Obfuscated payloads hidden after long whitespace in config files
• eval() or spawn() calls in config files
• VS Code auto-task on folder open (runOn: folderOpen)
• Suspicious font files or dist/setup.js loader
• Known PolinRider marker strings

Please do not reopen this PR or run the code locally. If you believe this is a false positive, contact a maintainer directly.