[20] Add Sentry error tracking to all modules

[EmeditWeb]

Problem

@sentry/nestjs is installed in package.json but SentryModule.forRoot() is not registered in app.module.ts, and main.ts does not initialize Sentry. Unhandled exceptions are logged to stdout only — invisible in production.

Context

Render's free-tier logs roll over fast. Without an external error sink, real production issues vanish before the team sees them. Sentry is the table-stakes minimum.

Before Starting

Read these context files first:

• context/architecture-context.md
• context/code-standards.md
• context/progress-tracker.md
• package.json
• src/main.ts
• src/app.module.ts

What To Build

1. Call Sentry.init({ dsn: process.env.SENTRY_DSN, environment: process.env.NODE_ENV, tracesSampleRate: 0.1 }) at the very top of main.ts, before NestFactory.create.
2. Register SentryModule.forRoot() in app.module.ts.
3. Add SentryGlobalFilter to APP_FILTER so all unhandled exceptions report to Sentry.
4. Add SENTRY_DSN= and NODE_ENV=development to .env.example.
5. Verify integration locally with a deliberate throw new Error('sentry test') in a test endpoint — confirm event lands in Sentry.
6. Add a README section "Error tracking" describing how to enable Sentry.

Files To Touch

• src/main.ts
• src/app.module.ts
• .env.example
• README.md

Acceptance Criteria

• Sentry initializes before Nest bootstrap
• Unhandled exceptions in any controller reach Sentry
• App still starts when SENTRY_DSN is empty (no-op fallback)
• traces_sample_rate is configurable via env
• README documents the env vars
• No any types introduced

Mandatory Checks Before PR

• npm run build passes with zero TypeScript errors
• No new any types introduced anywhere
• Full Swagger @apioperation + @apiresponse decorators on any new endpoints
• New migration file created for any schema changes
• context/progress-tracker.md updated

[Truphile]

Hi ,

I would like to take this on. Having integrated Sentry telemetry matrices across distributed NestJS applications in past roles, I am intimately familiar with setting up production error sinks without introducing initialization blocks or disrupting local developer workflows.

Here is the exact, clean pattern I will implement to resolve our telemetry gaps:

⚡ Architectural Implementation Plan

• Decoupled Bootstrapping (main.ts): Sentry will be initialized at the absolute top of the execution stack to ensure early NestJS bootstrap exceptions are captured. To protect local development and CI/CD pipelines, I will implement a strict conditional guard: if the environment variable is missing, Sentry will fall back to a silent no-op mode rather than halting application startup.
• Pipeline Exception Interception (app.module.ts): I will register the native global filter using Nest’s standard exception filter injection token inside the root module. This intercepts all unhandled controller-level exceptions, automatically shipping the stack traces and metadata contexts to your dashboard before gracefully returning the standard error payload to the client.
• Configuration & Context Maintenance: I will add the telemetry and sample rate environment variables directly to .env.example. To keep repository documentation perfectly synchronized, I will write a concise "Error Tracking" section in the README.md and log the completion milestone directly in context/progress-tracker.md.

🧪 Verification & Defect Strategy

• Zero-Downtime Fallback Validation: I will explicitly test the application's boot cycle with an empty environment variable to ensure it degrades gracefully with zero runtime friction.
• Fault-Injection Test: I will verify the pipeline locally by triggering a controlled exception from a test route, confirming that environment tags, stack traces, and request contexts route accurately to the remote sink.

Please assign this issue to me! I will ensure the PR passes your build pipelines with strict type-safety, zero any types, and total alignment with your project's architectural standards.

[grantfox-oss]

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

Next steps:

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

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Truphile's PR #55 was approved and merged by @EmeditWeb.

🏆 @Truphile: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (153 total points). Track your full progress on GrantFox.

👏 Great work, @Truphile! Keep contributing to StepFi-app.