`push_subscriptions` schema + VAPID config

[codebestia]

Create push_subscriptions (id, deviceId → user_devices.id, endpoint, p256dh, auth, createdAt, lastUsedAt, disabledAt). Generate VAPID keys, store private key in env (VAPID_PRIVATE_KEY, VAPID_PUBLIC_KEY, VAPID_SUBJECT). Subscriptions are per device. Add the web-push dependency.

Acceptance criteria:

• Subscription rows tied to a device
• VAPID keys configured via env, public key exposed to the client
• Migration generated

[Bellamzy]

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

I'd really like the chance to work on this issue — I've been actively looking to contribute and gain real experience, and I have hands-on skills in debugging and GitHub workflows to back it up.
My plan: reproduce the problem, implement and test a clean fix, then open a focused PR for review.
This opportunity means a lot to me right now, and I'd put in the time to get it done right and quickly.

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

[solidsole]

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

I'd like to claim this issue. I have reviewed the details and can begin working on a fix right away. Please assign it to me if it's still available. Thanks!

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

[TheWeirdDee]

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

Hi, I'd love to work on this because push subscription storage needs to be set up correctly from the start — tying subscriptions to devices rather than users is the right model for multi-device support. I'll create the migration, set up the schema with the correct foreign key, configure VAPID env vars, expose the public key to the client, and add the web-push dependency.

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

[directorfloo]

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

please i will love to work on this issue professionally, please assign it to me

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

[drips-wave]

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

🧑‍💻 @Bellamzy: 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 🌊