Skip to content

docs(spec): define negative fixture taxonomy#830

Merged
EffortlessSteven merged 1 commit into
mainfrom
docs/spec-negative-fixture-taxonomy
May 18, 2026
Merged

docs(spec): define negative fixture taxonomy#830
EffortlessSteven merged 1 commit into
mainfrom
docs/spec-negative-fixture-taxonomy

Conversation

@EffortlessSteven

Copy link
Copy Markdown
Member

Summary

  • add USELESSKEY-SPEC-0016 to make negative fixtures a first-class taxonomy
  • define stable classes for JWK, JWKS, JWT/token, webhook, and X.509/TLS negatives
  • update lane metadata so the JWK/JWKS implementation wave is the next ready item

User path

This improves the user job of finding deterministic bad artifacts that map to realistic parser/verifier failures instead of generic broken strings.

Boundary

This is a docs/spec slice only. It does not implement all taxonomy classes, add a contract pack, claim provider compatibility, claim production security, claim scanner evasion, or move repo-local proof into the installed CLI.

Proof

  • cargo xtask spec-check --strict
  • cargo xtask docs-sync --check
  • cargo xtask typos
  • git diff --check

Receipts

  • docs/specs/USELESSKEY-SPEC-0016-negative-fixture-taxonomy.md
  • active goal now marks the taxonomy spec done and the JWK/JWKS negative wave ready

Risk

No fixture generation, deterministic identity, bundle schema, or public API behavior changes.

Rollback

This PR is revertable without invalidating generated receipts because it only defines taxonomy and updates lane metadata.

@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!

@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.

@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 3 minutes and 2 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: 836316f3-af40-48b1-9998-e5c70c121c4d

📥 Commits

Reviewing files that changed from the base of the PR and between 555f0dd and 62fe9fa.

📒 Files selected for processing (4)
  • .uselesskey/goals/active.toml
  • docs/specs/README.md
  • docs/specs/USELESSKEY-SPEC-0016-negative-fixture-taxonomy.md
  • plans/real-workflow-closure/implementation-plan.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/spec-negative-fixture-taxonomy

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.

@EffortlessSteven EffortlessSteven merged commit f0a23da into main May 18, 2026
5 checks passed
@EffortlessSteven EffortlessSteven deleted the docs/spec-negative-fixture-taxonomy branch May 18, 2026 20:47
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