Add Fastify route integration tests

[Lakes41]

Summary

Add integration tests for the access API routes so endpoint behaviour is verified through Fastify rather than only through service-level assumptions.

Current Behaviour

The access API package uses jest --passWithNoTests, so the package can pass CI without route coverage. Core endpoints such as membership lookup, profile lookup, access checks, and member listing are not protected by request-level tests.

Expected Behaviour

Each public API route should have tests that verify request handling, response status codes, payload shapes, and service integration.

Suggested Implementation

Refactor the API bootstrap so tests can create a Fastify instance without binding to a network port. Use app.inject() with either a test database, a mocked Prisma client, or a mocked member service.

Files or Areas Likely Affected

• apps/access-api/src/index.ts
• apps/access-api/src/routes.ts
• apps/access-api/src/services/memberService.ts
• apps/access-api/src/**/*.test.ts
• apps/access-api/package.json

Acceptance Criteria

• Tests cover GET /health
• Tests cover GET /v1/memberships/:wallet
• Tests cover GET /v1/members/:wallet for found and not-found cases
• Tests cover POST /v1/access/check for allow and deny decisions
• Tests cover GET /v1/communities/:communityId/members
• Tests run through npm run -w access-api test

Additional Notes

Keep the tests deterministic. Do not require a live external API or deployed contract.

[Dwifax]

I have experience with Fastify route testing using app.inject() and Jest. I will add request-level tests covering GET /health, GET /v1/memberships/:wallet, GET /v1/members/:wallet (found/not-found), POST /v1/access/check (allow/deny), and GET /v1/communities/:communityId/members. Will mock Prisma client to keep tests deterministic and avoid network ports. Estimated completion: 2-3 days.