feat(gateway): exact reset time in premium cap error

[smakosh]

Summary

Follow-up to #3074. The DevPass weekly premium-cap 402 error rounded the remaining wait up to whole days: 6 days and a few hours displayed as "Resets in 7 days", and even a 20-minute wait showed "Resets in 1 day".

The message now shows the remaining time as days and hours, e.g. "Resets in 6 days and 3 hours.":

• Rounds up to the next hour so the wait is never understated.
• Drops zero components ("7 days", "5 hours") and pluralizes correctly ("1 day and 1 hour").
• Sub-hour waits display as "Resets in less than an hour."

Changes

• apps/gateway/src/chat/tools/resolve-provider-context.ts: replaced the whole-day ceil with a formatTimeUntilReset() helper used in the 402 message.
• apps/gateway/src/chat/tools/resolve-provider-context.spec.ts: unit tests for the formatter (rounding, zero components, singular/plural, sub-hour).

Testing

• vitest run apps/gateway/src/chat/tools/resolve-provider-context.spec.ts — 10/10 passing
• turbo run build --filter=gateway — builds clean

https://claude.ai/code/session_01NeqtWHWHmyug3BXUv3JmV9

Summary by CodeRabbit

• Bug Fixes
  • Improved premium usage limit messages with more accurate reset wait times.
  • Reset times now display days and hours when applicable, use correct singular/plural wording, and clearly identify waits under one hour.

[coderabbitai]

Walkthrough

Changes

Premium reset formatting

Layer / File(s)	Summary
Reset formatter and premium cap message apps/gateway/src/chat/tools/resolve-provider-context.ts, apps/gateway/src/chat/tools/resolve-provider-context.spec.ts	Adds formatTimeUntilReset for day/hour and sub-hour durations, uses it in the premium cap 402 message, and tests rounding, omitted units, and singular/plural output.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: steebchen

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: more exact premium cap reset timing in the gateway error message.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/premium-cap-exact-reset-time

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

apps/gateway/src/chat/tools/resolve-provider-context.ts (1)

218-233: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Extract the millisecond multiplier to a constant.

You can apply DRY principles by extracting 60 * 60 * 1000 into a local constant, such as HOUR_IN_MS, to avoid duplicating the magic number.

♻️ Proposed refactor

 export function formatTimeUntilReset(ms: number): string {
-	if (ms < 60 * 60 * 1000) {
+	const HOUR_IN_MS = 60 * 60 * 1000;
+	if (ms < HOUR_IN_MS) {
 		return "less than an hour";
 	}
-	const totalHours = Math.ceil(ms / (60 * 60 * 1000));
+	const totalHours = Math.ceil(ms / HOUR_IN_MS);
 	const days = Math.floor(totalHours / 24);
 	const hours = totalHours % 24;

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/gateway/src/chat/tools/resolve-provider-context.ts` around lines 218 -
233, In formatTimeUntilReset, extract the repeated 60 * 60 * 1000 expression
into a local constant such as HOUR_IN_MS, then reuse it for both the threshold
check and totalHours calculation without changing the existing behavior.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/gateway/src/chat/tools/resolve-provider-context.ts`:
- Around line 218-233: In formatTimeUntilReset, extract the repeated 60 * 60 *
1000 expression into a local constant such as HOUR_IN_MS, then reuse it for both
the threshold check and totalHours calculation without changing the existing
behavior.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 78b2b81d-3980-4fd2-8249-4cc694195b0e

📥 Commits

Reviewing files that changed from the base of the PR and between 3bf6604 and 3c09e23.

📒 Files selected for processing (2)

• apps/gateway/src/chat/tools/resolve-provider-context.spec.ts
• apps/gateway/src/chat/tools/resolve-provider-context.ts