Skip to content

docs(spec): define bundle audit JSON schema#794

Merged
EffortlessSteven merged 1 commit into
mainfrom
docs/bundle-audit-json-schema
May 18, 2026
Merged

docs(spec): define bundle audit JSON schema#794
EffortlessSteven merged 1 commit into
mainfrom
docs/bundle-audit-json-schema

Conversation

@EffortlessSteven

Copy link
Copy Markdown
Member

Summary

  • Adds a JSON Schema for installed bundle audit receipts.
  • Adds reference docs for stable fields, check objects, failure classes, and machine-readable CI boundaries.
  • Advances the active downstream CI polish goal from bundle-audit-json-schema to audit-bundle-ci-policy.

Files added/changed

  • docs/schemas/bundle-audit.schema.json
  • docs/reference/bundle-audit-json.md
  • .uselesskey/goals/active.toml

Validation

  • powershell JSON parse for docs/schemas/bundle-audit.schema.json
  • cargo test -p uselesskey-cli --all-features audit_bundle
  • cargo xtask docs-sync --check
  • cargo xtask typos
  • git diff --check

Non-goals

  • No CLI behavior change.
  • No release prep, version bump, tag, publish, new contract pack, or badge.
  • No provider compatibility, production security, or scanner-evasion claim.

What this enables next

  • Downstream CI can target a documented audit receipt shape before the lane adds CI policy controls.

@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai

coderabbitai Bot commented May 18, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 28 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: fc015282-32dd-41f1-976d-e60cf0bc2f17

📥 Commits

Reviewing files that changed from the base of the PR and between 7d4c9ea and dce0b3f.

📒 Files selected for processing (3)
  • .uselesskey/goals/active.toml
  • docs/reference/bundle-audit-json.md
  • docs/schemas/bundle-audit.schema.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/bundle-audit-json-schema

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@EffortlessSteven EffortlessSteven merged commit 772e618 into main May 18, 2026
5 checks passed
@EffortlessSteven EffortlessSteven deleted the docs/bundle-audit-json-schema branch May 18, 2026 06:30
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