Add graph ql subscriptions for live prices

[mikkyvans0-source]

Summary
Closes #56
Added a priceUpdated(pair: String!) GraphQL subscription that streams live prices over the existing Mercurius/Fastify /graphql endpoint — no separate WebSocket stack.

Changes
src/events.ts — Added a minimal PRICE_PUBLISHED event with a { pair, price, ts } payload and a publishPriceUpdate() helper. Kept the existing priceEmitter/PRICE_UPDATE intact so the REST /ws channel is untouched.

src/api/graphql.ts —

Added a PriceUpdate type and a Subscription.priceUpdated(pair) field.
Enabled Mercurius subscriptions with the graphql-transport-ws subprotocol (fullWsTransport: true) so standard graphql-ws clients connect.
Resolver uses withFilter to forward only the requested pair.
A single app-level bridge listener forwards priceEmitter events onto app.graphql.pubsub, detached on onClose so the listener doesn't leak.
src/ingesters/sdex.ts, amm.ts, soroswap.ts — Each ingester calls publishPriceUpdate({ pair, price, ts }) after recording a new price, alongside the existing webhook dispatch.

README.md — Documented the subscription with a graphql-ws client snippet showing subscribe and the unsubscribe (clean-close) call.

src/tests/graphqlSubscription.test.ts — Integration test over a real ws connection covering all three acceptance criteria: streaming for the subscribed pair, server-side filtering of other pairs, and clean unsubscribe via complete. Also asserts the bridge listener is detached on shutdown.

Verification
Tests: full suite passes — 85/85, including the 3 new subscription tests.
Typecheck: no new errors. The two webhookDispatcher.ts errors are pre-existing (Prisma client isn't generated locally) and unrelated — I confirmed they exist on the unmodified tree via git stash.

[drips-wave]

@mikkyvans0-source 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

[Miracle656]

The priceUpdated GraphQL subscription over the existing Mercurius endpoint is a clean approach (good call keeping the REST /ws channel untouched).

The blocker: this branch is stacked on your JSON-schema-validation work (#75), so it also re-includes schemas.ts / schemaValidation.test.ts / the rest.ts changes. #75 has now been merged to main, so please rebase on the latest main and drop the #75 files — leaving just the subscription work (events.ts, graphql.ts, the ingester publishPriceUpdate calls, and graphqlSubscription.test.ts). I'll merge once it's rebased.

[Miracle656]

Friendly nudge — the GraphQL subscriptions PR is mergeable but still has the earlier change requests outstanding. Please rebase on the latest main and address the review by 2026-07-01 so I can merge it — otherwise I'll close to keep the queue tidy (reopen anytime). Thanks! 🙏

[Miracle656]

Status update, and an apology — this has been open since June.

It now conflicts with main in three files:

src/api/rest.ts
src/api/schemas.ts
src/__tests__/schemaValidation.test.ts

main has moved a long way underneath it: the REST surface and the shared Zod schemas have both been reworked, several new routes landed (basket, benchmark, oracle, price, screener, volumes), and #121 restructured config into a per-network map. schemas.ts is an add/add conflict, meaning the file now exists on both sides independently.

That is more churn than is fair to ask you to absorb blind, so before you spend time rebasing, two things worth knowing:

1. wraith #124 proposes GraphQL subscriptions too, for transfer streams. If both land they should share a subscription/transport approach rather than inventing two. Worth a look before you rebase.
2. Lens is dual-network now (Restructure config.ts into a per-network config map #113/feat: restructure config into per-network map (#113) #121). A live price subscription needs to be network-scoped, or a subscriber on testnet will receive mainnet prices. That is new scope since you opened this.

If you still want it, rebase onto current main and I will review promptly — the feature is wanted. If you would rather not carry that, say so and I will reopen the issue as unassigned with the conflicts and the network-scoping noted, so nobody starts from scratch.

Either way the delay here is ours.