feat: introduce API v1 routing under /api/v1

[madisonsc52-del]

1. Findings within the Codebase

Monolithic Server Structure

• All routes, database logic, and utilities were tightly coupled in a single 600+ line server.js.
• Violated separation of concerns and made maintenance difficult.

Circular Dependency Risk

• Modularizing routes introduced potential circular imports between server.js and route files.
• Resulted in runtime errors (e.g., poolGet is not a function) due to CommonJS module caching.

Unversioned Internal Consumers

• Frontend (App.jsx) and backend tests (server.test.js) depended on unversioned endpoints.
• Moving routes to /api/v1 would break these consumers with 404 errors.

Incorrect Stellar Federation Configuration

• stellar.toml pointed to an unversioned /federation endpoint.
• Inconsistent with the new versioned API structure.

---

2. Fix Features Implemented

Database & Service Decoupling

• Extracted DB logic into src/db.js.
• Centralized connection pooling, query helpers, schema setup, and middleware.
• Eliminated circular dependency issues.

Modular Route Architecture

• Introduced versioned route structure under src/routes/v1/:

  • userRoutes.js: /register, /lookup, /users
  • federationRoutes.js: /federation
  • receiptRoutes.js: /receipts/:txHash
  • index.js: Aggregates all routes into one router

Server Refactoring

• Simplified server.js to only core server responsibilities.
• Mounted all routes under /api/v1.
• Retained global middleware (CORS, payload limits, security).
• Kept /health and /.well-known/stellar.toml at root level.
• Updated stellar.toml to use /api/v1/federation.
• Re-exported DB helpers for backward compatibility with tests.

End-to-End Consumer Updates

• Updated frontend (App.jsx) to use versioned endpoints.
• Updated backend tests (server.test.js) accordingly.
• Ensured full compatibility and passing test suite.

CLOSE #54

[vercel]

@madisonsc52-del is attempting to deploy a commit to the Abdulazeem's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@madisonsc52-del 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

[Abdulazeem-code]

Fix check

[madisonsc52-del]

Issue resolved

[Abdulazeem-code]

fix backend build test error

[Abdulazeem-code]

Still the same Backend build test error

[madisonsc52-del]

Hi @Abdulazeem-code sir, I have resolved the backend build errors caused by merge conflict artifacts and cleaned up the temporary files. The repository currently shows '3 workflows awaiting approval'—could you please approve the workflow runs so the new tests can confirm the fix? Thank you!

[Abdulazeem-code]

It is still failing

[madisonsc52-del]

Fixed the error conflict

[madisonsc52-del]

Hi @Abdulazeem-code,

I've fixed the Backend Build & Test failure. The branch had merge corruption from a prior update that left syntax errors and conflict markers in server.js, server.test.js, and src/cleanup-cron.js. I cleaned those up and completed the v1 route extraction:

Moved /register, /lookup, /federation, and /receipts into src/routes/v1/
Mounted the router at both / (backward compatibility) and /api/v1
Restored ci.yml to match main so this PR stays scoped to routing only
All 5 test suites (124 tests) pass locally. Could you please approve the workflow run so the CI can verify the fix? The Vercel authorization check is expected for this PR — I'll leave that to your review.

Thanks!