Repository navigation
PREWAVE-BE-018 — Converge Duplicate Notification Module Implementations #613
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
- Audit
notifications.module.new.tsagainst the active notification module. - Preserve reviewed functionality, remove obsolete duplicate wiring, and publish one module entrypoint.
- Document migrations for any retained model changes.
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
- Nest module bootstrap test.
- Provider uniqueness and queue-consumer uniqueness tests.
- Regression tests for each retained channel.
Acceptance criteria
- Exactly one production notification module is registered.
- No provider or worker is instantiated twice.
- Obsolete
.newimplementation paths are removed or explicitly test-only. - Startup and shutdown complete without leaked handles.
Dependencies
- STAB-BE-005 — Restore the Post-Wave-9 Install and CI Baseline #584
- fix(ci): align API dependencies and Node runtime #608
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
drips-wave commentedon Oct 16, 2026
Congratulations, @habeebullahabubakar61-debug! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @habeebullahabubakar61-debug: 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 🌊
gtrefe commentedon Oct 20, 2026
@gtrefe 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 @gtrefe to this issue.
d3vobed commentedon Oct 20, 2026
@d3vobed 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 @d3vobed to this issue.