Multi-pool support in `BlendAdapter`

[dubemoyibe-star]

Context

CLAUDE.md tracks YieldBlox as representable via a small multi-pool refactor of blend.ts — it's a Blend V2 pool, not an independent protocol. Generalizing the adapter to target multiple poolIds adds a real second entry with minimal new scoring code.

Scope

In scope: refactor BlendAdapter so one engine handles multiple pools with distinct metadata/poolId, and register the YieldBlox pool as a second entry.
Out of scope: presenting YieldBlox as an independent protocol — it must be clearly labelled as a Blend-deployed pool in both the data and the UI.

Acceptance criteria

• One adapter engine, multiple pool configs — no duplicated scoring logic
• YieldBlox pool registered, scored, and visible end-to-end (indexer → DB → API → UI)
• Labelled in the UI as a Blend V2 pool, not an independent protocol — no misleading presentation
• Existing Blend flagship pool scores unchanged by the refactor (verify before/after)

Difficulty

Intermediate — needs familiarity with the codebase or methodology

Notes / open questions

Check the pool's current status before investing effort — it may be deprecated post-hack. If it turns out to be dead, the refactor is still worth doing for future pools; just don't register a dead pool as a live entry.

[Talentgift24-ux]

📋 Grainlify Application

@Talentgift24-ux has applied to work on this issue as part of the Grainlify program.

i would love to work on this issue

---

Repo Maintainers: To accept this application, review their application or assign @Talentgift24-ux to this issue.