feat(usage): the meters' pace is a setting, off by default

[devswha]

Change

The usage meters' pace (#513: the mark of an even pace on each bar, the rate under it, "Runs out in …" and the chip's red hairline for a low share) becomes a setting, Settings → Subscription usage → Show pace, off by default. With it off the meters read as they did before #513; with it on, as #513 made them.

#513 is not released yet, so nobody loses anything: this decides how it first ships.

• usagePace in src/lib/settings.ts (default false), read by UsageMeters in the three places the pace showed: the chip's hairline, the popover's rows, and the strip's label.
• The row sits under Limit shown, shown only while Show plan limits is on, with Korean, Japanese, Chinese and Turkish text.
• No changelog change here: the release PR (chore(release): prepare 0.4.7 and remote runtime v26 #833) words feat(usage): show each limit's pace and when it runs out before its reset #513's entry with the setting.

Validation

• bun run typecheck: pass. settings.test.ts, i18n.test.ts, usage.test.ts: 85 pass.
• scripts/usage-regression.ts (run through its exported check against a real server and Chrome): pass. New: with plan limits on and the pace not chosen, the strip's label has no "Runs out", no chip is is-fast, and the popover has no mark or rate; turning Show pace on brings them, and the existing pace checks run from there.
• scripts/settings-pages-demo-regression.ts: 13 PASS (the Subscription usage page with its new row fits 390px and 320px phones in en, ko, ja and zh).

Release

Client-side only.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: devswha/herdr-web-ui/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 3398a092-78cc-459f-b144-094d0240a98b

---

📥 Commits

Reviewing files that changed from the base of the PR and between f6244ff and 6ab8356.

---

📒 Files selected for processing (9)

• scripts/usage-regression.ts
• src/components/SettingsDialog.tsx
• src/components/UsageMeters.tsx
• src/lib/i18n.ja.ts
• src/lib/i18n.ko.ts
• src/lib/i18n.tr.ts
• src/lib/i18n.zh.ts
• src/lib/settings.test.ts
• src/lib/settings.ts

---

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 0 remain after this review.

---

---

📝 Summary

Summary by CodeRabbit

• New Features
  • Added a “Show pace” setting for subscription usage meters. It’s off by default; enable it to see pace indicators, current usage rates, and warnings when a limit may run out before reset.
  • Added translations for the setting in Japanese, Korean, Turkish, and Simplified Chinese.

Walkthrough

Adds a usagePace setting that defaults to false. The settings dialog exposes the option, and usage meters show pace markers, rate text, and run-out warnings only when it is enabled. Translations and regression checks cover the setting.

Changes

Usage pace setting

Layer / File(s)	Summary
Define and sanitize the setting src/lib/settings.ts, src/lib/settings.test.ts	Settings includes usagePace, which defaults to false. Sanitization retains only the boolean value true; tests cover the default and sanitization.
Expose the setting and gate pace display src/components/SettingsDialog.tsx, src/components/UsageMeters.tsx, src/lib/i18n.*.ts	The settings dialog adds a Show pace option. Usage meters gate pace indicators and run-out details on usagePace. Japanese, Korean, Turkish, and Simplified Chinese translations add the setting label and description.
Verify default and enabled display scripts/usage-regression.ts	The regression script checks that pace details are absent by default and that enabling Show pace displays a fast usage chip.

Priority: ⬇️ Low

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

Change: Feature

Suggested reviewers: haeminway1

---

Merge Risk: ⚪ Minimal · up to 6ab83

Pace indicators remain off unless enabled, and the reviewed changes show no actionable user-facing issue. The change is mergeable after normal checks.

Pre-merge checks | 4 | 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 42.86% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 7 functions across 9 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: making usage-meter pace indicators configurable and disabled by default.
Description check		The description includes the required Change and Validation sections, explains the resulting behavior, identifies affected components and translations, and reports relevant test results. The additiona…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

---

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

---

---

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}