Repository navigation
PREWAVE-BE-020 — Normalize Notification Preference Storage and Quiet-Hours Semantics #616
Description
Problem context
Draft PR #608 proves deterministic installation under the pinned Node runtime, but hosted Gate B still fails at source compilation. This issue isolates one concrete failure family from the 77-error baseline.
Technical scope
- Reconcile stale
settings,enabledChannels,disabledCategories, and split quiet-hours fields with the canonicalNotificationPreferenceentity. - Define migration/default behavior for existing rows.
- Validate timezone and category/channel precedence.
Security and architecture constraints
- Contracts and finalized canonical events remain authoritative for protocol state.
- Do not conceal errors with broad casts, disabled strictness, skipped tests, or duplicate compatibility models.
- Treat wallet, request, notification, support, and chain-derived inputs as untrusted.
- Preserve fail-closed behavior for missing configuration and interface mismatches.
Required tests
- Migration tests from each legacy shape.
- Quiet-hours tests across DST, invalid timezone, overnight ranges, and boundaries.
- Category/channel opt-out precedence tests.
Acceptance criteria
- One documented preference schema remains.
- Existing records migrate deterministically.
- Quiet hours use an explicit timezone and boundary rule.
- Mandatory security notices cannot be disabled unintentionally.
Dependencies
- STAB-BE-005 — Restore the Post-Wave-9 Install and CI Baseline #584
- PREWAVE-BE-010 — Rehearse PostgreSQL Migration, Rollback, and Zero-Data-Loss Recovery #605
Non-goals
- Bundling unrelated compile repairs.
- Weakening TypeScript, lint, security, or container gates.
- Mainnet deployment.
- Applying
Stellar Wavebefore maintainer activation.
Complexity and points
- Medium — 150 points
Candidate only; activation remains maintainer-controlled.
Activity
Ikechukwu-Patrick commentedon Oct 15, 2026
@Ikechukwu-Patrick has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ikechukwu-Patrick to this issue.
kodinaka30-ship-it commentedon Oct 15, 2026
@kodinaka30-ship-it has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @kodinaka30-ship-it to this issue.
drips-wave commentedon Oct 16, 2026
Congratulations, @Ikechukwu-Patrick! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Ikechukwu-Patrick: 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 🌊
Merge pull request #783 from Ikechukwu-Patrick/fix/616-notification-p…
drips-wave commentedon Oct 19, 2026
This issue has been completed by @Ikechukwu-Patrick as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Ikechukwu-Patrick: You earned 150 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.