File deletion: soft-delete + background hard-delete

[codebestia]

Implement soft-delete (files.deletedAt) on message retraction/expiry, and a background job that hard-deletes storage objects with no remaining message references. Ensure ref-counting across multi-device envelopes — a file is dead only when all referencing messages are gone.

Acceptance criteria:

• Soft-delete immediate; hard-delete via background job
• Object removed from storage only when unreferenced
• Job is idempotent + safe to retry

[Emoji-dot]

@Emoji-dot has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emoji-dot to this issue.

[Depo-dev]

@Depo-dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day team, my name is Depodev, I have gone through the issue requirements and i am confident i can deliver and i will like to work on this.

ETA: 24 hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Depo-dev to this issue.

[Chidimj]

@Chidimj has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Clicked maintainers,

My experience includes designing backend services that manage file lifecycles efficiently while ensuring data integrity across distributed systems. I've implemented background processing workflows and storage cleanup mechanisms that safely remove unused resources without affecting active references or user data.

For this issue, I'll introduce a soft-delete workflow by marking files with a deletedAt timestamp while keeping them available until all message references are removed. I'll then implement an idempotent background cleanup job that performs reference counting across devices before permanently deleting storage objects, ensuring retries remain safe and that only truly unreferenced files are removed.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chidimj to this issue.

[drips-wave]

Congratulations, @Chidimj! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Chidimj: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊