fix: WS shutdown, cacheWarm count, eventParser flat data, webhook validation

[chukwuemekarita]

Closes

Closes #411
Closes #412
Closes #413
Closes #414

What changed

• [enhancement] No graceful shutdown for WebSocket server #414 — Added shutdown(wss, drainTimeoutMs) to src/ws/priceWebSocket.js that calls subscriptionManager.drain() to gracefully close all connections before closing the server. Exported for use in process shutdown handlers.

• [bug] cacheWarm reports 0 succeeded when timeout fires even if some succeeded #413 — Fixed src/startup/cacheWarm.js to track succeededSoFar incrementally as each fetch resolves, so the timeout handler reports the real success count instead of hardcoding succeeded: 0.

• [bug] eventParser dataFromValue fallback returns { value } for non-array non-object values #412 — Fixed src/indexer/eventParser.js dataFromValue to return the value directly instead of wrapping in { value } for non-array non-object decoded values (strings, numbers, bigints).

• [bug] deliveryRepository create does not validate webhook_id exists #411 — Added webhookRepository.findById(webhook_id) validation in src/repositories/deliveryRepository.js create() to reject delivery records for non-existent webhooks.

How to test

1. [enhancement] No graceful shutdown for WebSocket server #414: Call shutdown(wss) with active connections — connections should close with code 1001 and heartbeat should stop
2. [bug] cacheWarm reports 0 succeeded when timeout fires even if some succeeded #413: Trigger cache warm with a short timeout — summary should show actual succeeded count, not 0
3. [bug] eventParser dataFromValue fallback returns { value } for non-array non-object values #412: Parse an event with a non-object/non-array value — data field should be the value directly, not { value }
4. [bug] deliveryRepository create does not validate webhook_id exists #411: Call deliveryRepository.create() with a non-existent webhook_id — should throw an error

[drips-wave]

@chukwuemekarita Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits