[Jacksondr5]

Problem

From 2026-11-01, UsageService.test.ts › "reports saved usage of a removed directory only for windows it reaches" fails on j5/main and on every PR. The test runs on the wall clock with a transcript dated 2026-08-01. The usage service prunes saved usage older than 92 days, so from today the first read returns nothing.

What changed

• apps/server/src/usage/UsageService.test.ts: upstream's fix, cherry-picked unchanged. It's 1280ccd0d2, "test(server): pin clock in saved-usage window test" (test(server): pin clock in saved-usage window test pingdotgg/t3code#28603). The test sets TestClock to 2026-08-15, near the write, and provides TestClock.layer(). The hunk is identical to upstream's.
• FORK.md: a "Temporary in-place patches" entry and a ledger row. Exit condition: drop the entry at the next upstream advance, which brings the same commit; the file then equals upstream's.

It touches nothing else. The Captain approved taking upstream's own test-only fix unchanged, the same pattern as #877.

Live testing

None: this is a test-only change. vp test run src/usage/UsageService.test.ts passes (40 tests) at the head.

Upstream impact

Edits upstream's test file only, with upstream's own change; recorded in FORK.md as a temporary patch.

Checklist

• One concern: the description has no "also"
• Tests cover the changed behavior: the fixed test passes
• UI changes: none
• Live testing: none needed
• Upstream-owned files: recorded in FORK.md (temporary patch entry and ledger row)
• Upstream product: no change
• Surfaces: server tests only
• Docs: FORK.md only

Built by Claude Opus 5.5 in J5 Code (Claude Code harness).

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
j5-code	Ready	Preview	Nov 1, 2026 8:02pm UTC

[coderabbitai]

Warning

Review limit reached

• Run on-demand review

_{This review includes 2 billable files and costs up to $0.50.}

• Ask an admin to make reviews automatic

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Or wait 24 minutes for your next included review.

Check out review usage here.

View limit details

Limit details: You’ve used all 3 included reviews currently available. Your 43 included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Jacksondr5/j5code
• Branch: j5code/upstream-usage-test-clock-pin
• File: .coderabbit.config.ts
• Commit: 3b9910b
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Essentials
• Run ID: 9d29449f-70fc-4b82-9a91-c96e766236ba

Commits

Reviewing files that changed from the base of the PR and between c2b7939 and 3b9910b.

Files selected for processing: 2

• FORK.md
• apps/server/src/usage/UsageService.test.ts

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

[Jacksondr5]

Combined panel review (reviewer-opus + reviewer-sol) at 3b9910b

Verdict: no findings, and the panel approves this test-only PR.

• The PR range from the merge base touches exactly FORK.md and apps/server/src/usage/UsageService.test.ts.
• The test hunk is upstream's, unchanged. Its added and removed lines are byte-identical to 1280ccd0d2 (pingdotgg#28603), which touches only that file. It sets TestClock to 2026-08-15, near the transcript's write, and provides TestClock.layer(). That ends the wall-clock dependency that broke the test once the 2026-08-01 transcript fell outside the 92-day window. We're approving the identical hunk only, not claiming the whole file equals upstream's: other parts differ because of the pin.
• FORK.md adds one "Temporary in-place patches" bullet, with the exit "take upstream's at the next advance", and one ledger row.
• Reviewer-run: UsageService.test.ts passes (40).

Reviewed by Claude Opus 5.5 (reviewer-opus) and Sol 6.1 (reviewer-sol) in J5 Code.