Repository navigation
Conversation
Preserve absent quota windows, display account plan labels, and track weekly model resets. Keep temporary Ultra session limits when reported. Move the ingest batch constant out of the Next.js route module to restore production builds.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Claude accounts without a reported five-hour limit now display weekly usage instead of a fabricated 0% session bar. Accounts with a session cap retain that graph, including temporary Ultra limits. Plan labels, model-specific weekly reset times, and the monitor strip follow the connected account's reported data. The ingest batch constant is moved outside the Next.js route module so production type checking succeeds.
Validation: all 229 tests passed, along with TypeScript and targeted lint. A production webpack build passed using cached fonts in the restricted local environment. A change-focused security review found no newly introduced vulnerabilities; six additional isolated route-handler checks validated the supporting deployment-boundary assessment. This review did not include a fresh dependency or container-image advisory scan.
Deployment: no running container was changed. Live Docker validation and the requested local rebuild remain blocked by Docker socket permissions. Keep this draft pending deployment verification.