feat: structured logging and error tracking (#99)

[timo126]

closes #99

[drips-wave]

@timo126 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

[vercel]

@samlogy1 is attempting to deploy a commit to the ACCENSA Team on Vercel.

A member of the Team first needs to authorize it.

[mergekeeper]

MergeKeeper review

Scope: in scope for linked issue #99.
Verdict: clean

Structured logging, sync run persistence, Sentry error tracking, redaction tests, and deployment documentation were successfully implemented.

Reviewed commit: f703c38d6bb6c78e7467c2d33913ee1807d563bd.
CI and merge eligibility are checked separately.

[mergekeeper]

MergeKeeper merge status

Status: blocked
PR state: open
Mergeability: mergeable
Checked commit: f703c38d6bb6c78e7467c2d33913ee1807d563bd.

Reason: One or more required CI checks failed.

Failing checks:

• lint - view details
• test (reconcile-payments) - view details
• typecheck - view details
• build - view details
• format - view details
• test (web) - view details
• test (sdk) - view details
• playwright (web) - view details

Next steps:

1. Open the failing check details above and fix the reported error.
2. Run the same checks locally where possible.
3. Commit and push the fix.
4. MergeKeeper will automatically re-review the updated PR.

[mergekeeper]

MergeKeeper review unavailable

AI provider review response did not contain valid JSON

No approval or merge action was taken.

[mergekeeper]

Needs changes

The PR implements some logging and Sentry configs, but misses several acceptance criteria from #99 such as persisting sync runs, API route error/request logging, PII docs, LOG_LEVEL docs, and DEPLOYMENT.md.

• apps/web/src/lib/log.ts: Sync run results are not persisted to a sync_runs table as required by the issue.
• apps/web/sentry.server.config.ts: Error tracking and structured logging are not wired into API routes or error boundaries.
• Review finding: Missing DEPLOYMENT.md explaining log querying and where logs go.
• Review finding: Missing documentation for LOG_LEVEL configuration and PII scrubbing.

Reviewed commit: dd737396ce80928b1d0dd77ed80d42c2cf27b64f.

[mergekeeper]

Needs changes

The PR implements structured logging, redaction tests, and Sentry configuration, but misses persisting sync history to a sync_runs table, logging sync runs, wiring Sentry into API routes, adding API route request tracking, PII documentation, LOG_LEVEL documentation, and DEPLOYMENT.md.

• apps/web/src/lib/log.ts: Missing persistence of sync run results to a sync_runs table as specified in issue #99.
• apps/web/src/lib/log.ts: Missing wiring of Sentry error tracking and structured logging into API routes and request correlation.
• Review finding: Missing DEPLOYMENT.md explaining where logs go and how to query them, and documentation for LOG_LEVEL and PII scrubbing.

Reviewed commit: 88fc4311242fc9701128e440cf4fc46e9ef568b2.

[mergekeeper]

Needs changes

The PR implements some logging and Sentry configs, but misses several acceptance criteria from #99 such as persisting sync runs, API route error/request logging, PII docs, LOG_LEVEL docs, and DEPLOYMENT.md.

• apps/web/src/lib/log.ts: Sync run results are not persisted to a sync_runs table as required by the issue.
• apps/web/sentry.server.config.ts: Error tracking and structured logging are not wired into API routes or error boundaries.
• Review finding: Missing DEPLOYMENT.md explaining log querying and where logs go.
• Review finding: Missing documentation for LOG_LEVEL configuration and PII scrubbing.

Reviewed commit: dd737396ce80928b1d0dd77ed80d42c2cf27b64f.