Skip to content

Update Usage Limits to 2.0.0 - #2

Merged
Norbert515 merged 2 commits into
mainfrom
codex/usage-limits-1.1.0-20260806
Aug 6, 2026
Merged

Update Usage Limits to 2.0.0#2
Norbert515 merged 2 commits into
mainfrom
codex/usage-limits-1.1.0-20260806

Conversation

@Norbert515

Copy link
Copy Markdown
Collaborator

Summary

  • replace the combined Usage Limits dashboard with independent 420 px Claude and Codex cards matching the locally developed extension;
  • show receipt timestamps in the owner’s current local offset and replace stale values with a fixed-sheen loading skeleton while refreshes are in flight;
  • switch collection from a Codex child process plus Claude external action to host-brokered Anthropic and ChatGPT connector reads;
  • publish this as 2.0.0 because the persisted usage.dashboard surface is replaced; existing 1.0 tiles must be recreated after update.

The generated publication will require Campus 1.91.0, the first release containing the receipt clock and intermediate refresh-snapshot host behavior.

Authority review

  • No authority increase
  • Authority increase is intentional and documented
  • Raw secret plus filesystem/HTTP/process/native exfiltration risk is called out

The guest adds connector.http.request, but removes the scoped codex process resource and the Claude external action. It retains only shared-state and scene writes. There is no filesystem, process, native, task, external-action, or arbitrary-origin authority.

  • anthropic: exact https://api.anthropic.com origin, GET only, /api/oauth/usage path prefix, 256 KiB response cap, 20 s timeout.
  • openai: exact https://chatgpt.com origin, GET only, /backend-api/wham/usage path prefix, 256 KiB response cap, 20 s timeout.

Path-prefix authority includes descendants and bounded query parameters; the shipped guest calls only the named paths without queries. Campus injects the existing local bearer credential inside the host broker, so guest JavaScript never receives a raw secret. Only bounded display projections enter shared state, and both refresh actions remain owner-only.

Verification

  • python3 -m unittest discover -s tool/tests -v
  • node --test extensions/*/test/*.test.mjs
  • python3 tool/registry.py validate --root .
  • README and CHANGELOG updated
  • No credentials, user data, downloaded dependencies, or install hooks added
  • Trusted publication simulation produced sha256:aa00700f903477c875a8e2ce39d4a8c95339f9232cd55ef82ab8eac230b95649 and a catalog/artifact-only diff

@Norbert515
Norbert515 requested a review from a team as a code owner August 6, 2026 12:54
@Norbert515
Norbert515 merged commit b606f9b into main Aug 6, 2026
1 check passed
@Norbert515
Norbert515 deleted the codex/usage-limits-1.1.0-20260806 branch August 6, 2026 12:54
Norbert515 added a commit that referenced this pull request Aug 6, 2026
Generated from validated source already merged to `main` in #2.

- Canonical artifact:
`sha256:aa00700f903477c875a8e2ce39d4a8c95339f9232cd55ef82ab8eac230b95649`
- Release: `io.flutterflow.campus.usage-limits` 2.0.0
- Minimum Campus version: 1.91.0
- Compatibility: macOS, arm64 and x86_64, `manifest.v3`
- Diff contains only `campus.registry.json` and the content-addressed
artifact.

The trusted workflow independently produced and verified the same
artifact, but this WIP repository does not yet have the optional
publication GitHub App secrets configured. This maintainer-created
branch preserves the same generated two-path publication boundary and
runs the normal required PR validation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant