fix: make long-history submission merges bounded

[chsong1]

AI로 작성된 내용입니다.

Summary

Fixes #93.

Long-history re-submissions no longer perform one sequential daily_breakdowns write per day or race those uncancelled writes against a 25-second application timer. A 270-day merge now performs one conflict-safe bulk upsert, so the API does not report failure while the same submission continues and commits in the background.

This includes the timeout-response correction from #80 and fixes the underlying O(days) merge that triggers it.

Changes

• replace the per-day update/insert loop with one upsert on the existing (submission_id, date) unique key
• preserve the existing machine-contribution rules through mergeMachineContribution
• remove the uncancellable Promise.race that could return a false failure after writes continued
• recognize both timeout and timed out database error spellings as 504
• surface failed existing-submission reads, bulk daily writes, and parent submission updates
• treat profile projection errors as post-commit/non-fatal so an accepted submission is not reported as failed
• add route and data-layer regressions to the default test command

Verification

• pnpm test — pass
  • ccusage: 34 tests
  • streaks: 9 tests
  • 270-day merge: exactly one bulk daily write
  • bulk/parent DB errors are surfaced
  • post-commit profile error remains a successful submission
  • Database operation timed out maps to 504
• node test/ccusage.test.mts /Users/chsong/cc.json && node --import tsx test/submissions.test.mts — pass against the real 270-day, 205,565,284,264-token payload from Submit reports generic 500 after long-history merge already committed #93 (37 ccusage checks plus merge-path checks)
• pnpm build — application compiled successfully; page-data collection then stopped because the local checkout has no GITHUB_ID, GITHUB_SECRET, NEXTAUTH_SECRET, or NEXTAUTH_URL

Notes

The bulk upsert relies on the existing unique constraint; no schema migration is required. It removes the observed timeout mechanism but does not attempt to redesign cross-request transaction/concurrency semantics, which predate this change.

[vercel]

@chsong1 is attempting to deploy a commit to the sculpt Team on Vercel.

A member of the Team first needs to authorize it.