Release 3.0.0

What's Changed

• Add configurable write debounce support & new Write smart action to reduce impact by @italo-lombardi in #64
• Refactor write guarded service by @eigger in #65

🚨 Breaking Change: Write Service Segregation

In v3.0.0, the responsibilities of write services have been explicitly separated.
All safety-related logic has been migrated from the standard write service to a new specialized service.

• gicisky.write (Force-Write Only):
  This service is now strictly for direct writes. Internal safeguards—specifically Duplicate Prevention and Write Lock Validation—have been removed from this path. It will now execute writes immediately (unless dry_run: true is set).

• gicisky.write_guarded (New - Protected Path):
  A new service introduced to inherit all safety-critical logic. You must use this service if your workflow requires:

  • Duplicate Prevention (Deduplication)
  • Write Lock Validation
  • Debounce Coalescing

Full Changelog: 2.2.0...3.0.0