Add an ?anchor= filter to GET /api/v1/liquidity/entries

[Jagadeeshftw]

📌 Description

GET /api/v1/liquidity/entries lists raw per-anchor entries with no filtering per the README, forcing clients to fetch and filter the entire list client-side even when they only care about one anchor's contributions (e.g. for an anchor detail page).

🧩 Requirements and context

• Add an ?anchor= query param filtering entries to one anchor id.
• Return an empty array (not 404) for a valid-format but unknown anchor id, consistent with other list endpoints.
• Keep the unfiltered response shape identical when the param is absent.

🛠️ Suggested execution

• Update routes/liquidity.ts and LiquidityService/LiquidityRepository to accept and apply the filter.
• Add tests in routes/liquidity.test.ts for filtered vs. unfiltered results.
• Update the README and src/openapi.ts.

✅ Acceptance criteria

• ?anchor= returns only that anchor's entries.
• Unfiltered behavior is unchanged.
• Documented in OpenAPI and README.

🔒 Security notes

No new attack surface; read-only filter over already-public entry data.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[GBOYEE]

Hello! I'd love to pick this one up (Add an ?anchor= filter to GET /api/v1/liquidity/entries). I'll implement the helper and integrate it. I'll get a PR up for this as soon as I'm assigned.

[Jagadeeshftw]

@GBOYEE thanks for the interest — you're currently at the 6 open-issue assignment cap for this repo, so I can't assign this one right now (backfill automation). Please finish or release one of your existing assigned issues, then request this one again and it'll be picked up.

[grantfox-oss]

🦊 GrantFox — @GBOYEE has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #92)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.