Display daily credit grant timestamps in user's timezone

[jurgenwerk]

Update daily credit grant timestamps to display in the user's local timezone instead of a fixed ET timezone.

---

Linear Issue: CS-10043

 

---

Note

Displays credit grant timestamps in the user's local timezone instead of fixed ET.

• Replace formatEtTimestamp with formatLocalTimestamp (uses Intl.DateTimeFormat without a fixed timeZone) in with-subscription-data.gts
• Update dailyGrantNote strings to surface local timestamps for upcoming and last daily credit grants

^{Written by Cursor Bugbot for commit 0c239fb. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[github-actions]

Preview deployments

• Host staging preview
• Host production preview

[github-actions]

Host Test Results

    1 files  ±    0      1 suites  ±0   3h 6m 55s ⏱️ + 48m 32s
1 872 tests +  232  1 856 ✅ +  245  15 💤 ± 0  1 ❌ ± 0 
3 558 runs  +1 904  3 527 ✅ +1 915  30 💤 +15  1 ❌  - 13 

For more details on these failures, see this check.

Results for commit 0c239fb. ± Comparison against base commit 75067cd.

This pull request removes 1 and adds 233 tests. Note that renamed tests count towards both.

Chrome ‑ Global error: Uncaught TypeError: Failed to fetch at http://localhost:7357/assets/chunk.a0f1fa411c6f69fe7c73.js, line 150984  While executing test: Acceptance | index card home resolution > operator submodes: host submode uses hostHome and updates after edit 

Chrome ‑ Acceptance | index card home resolution > operator submodes: host submode uses hostHome and updates after edit
Chrome ‑ Global error: Uncaught TypeError: Failed to fetch at http://localhost:7357/assets/chunk.e5568c9de37711b58fcd.js, line 150984  While executing test: Integration | card-copy: copy button does not appear when right and left stacks are both single cards items 
Chrome ‑ Integration | Store: added instance that was previously not saved will begin to auto save after being added
Chrome ‑ Integration | Store: an instance can be restored after a loader reset
Chrome ‑ Integration | Store: an instance can debounce auto saves
Chrome ‑ Integration | Store: an instance can live update thru an error state
Chrome ‑ Integration | Store: an instance live updates from indexing events for a code update
Chrome ‑ Integration | Store: an instance live updates from indexing events for an instance update
Chrome ‑ Integration | Store: an instance that started out with a local ID can be restored after a loader reset
Chrome ‑ Integration | Store: an instance will NOT auto save when its data changes, if the user does not have write permissions
…

♻️ This comment has been updated with latest results.