Add Structured Logging with Pino Across the API

[vjuliaife]

Description:
TariffShield currently uses bare console.log calls with no structure, correlation IDs, or log levels, making it impossible to trace requests across services or filter logs by severity in production. Every API request, error, and Soroban RPC call needs a consistent JSON log line with a request-scoped correlation ID so operators can reconstruct the full lifecycle of any transaction. Without structured logging, debugging production incidents requires guesswork rather than log queries.

Acceptance Criteria:

• Install pino and pino-http as production dependencies; install pino-pretty as a dev dependency for local formatting
• Mount pino-http middleware in apps/api/src/index.ts before all route handlers so every HTTP request logs method, path, status code, response time, and correlationId
• Generate a UUID v4 correlationId per request (via pino-http's genReqId option) and attach it to req.log so child loggers in downstream handlers inherit it automatically
• Replace all console.log / console.error calls in apps/api/src/routes/importers.ts and apps/api/src/stellar.ts with req.log.info / req.log.error child loggers
• Set log level via LOG_LEVEL environment variable (default info); support trace, debug, info, warn, error, fatal
• Emit JSON output in production (NODE_ENV=production) and pretty-printed output in development via pino-pretty transport
• Log Soroban RPC call duration in milliseconds on every call in apps/api/src/stellar.ts with fields { rpcMethod, durationMs, success }

Relevant Files:

• apps/api/src/index.ts — mount pino-http middleware here
• apps/api/src/routes/importers.ts — replace console calls with structured child logger
• apps/api/src/stellar.ts — instrument RPC calls with duration logging
• apps/api/src/db.ts — replace any console calls with structured logger

[DavisVT]

@DavisVT has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

pls assign this issue to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DavisVT to this issue.

[Unclebaffa]

@Unclebaffa has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainer,
I’m interested in contributing to this issue and believe I can deliver a clean, well-tested solution that aligns with the project’s standards.
Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Unclebaffa to this issue.

[devmocrea]

@devmocrea has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, will love to work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @devmocrea to this issue.

[drips-wave]

Congratulations, @devmocrea! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @devmocrea: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊