Skip to content

docs(spec): define real user workflow contract#829

Merged
EffortlessSteven merged 1 commit into
mainfrom
docs/spec-real-user-workflows
May 18, 2026
Merged

docs(spec): define real user workflow contract#829
EffortlessSteven merged 1 commit into
mainfrom
docs/spec-real-user-workflows

Conversation

@EffortlessSteven

Copy link
Copy Markdown
Member

Summary

  • add USELESSKEY-SPEC-0015 to define the real user workflow contract
  • define Rust developer, CI/platform, and materialization paths with copyable snippets, positive/negative cases, proof commands, receipt paths, and boundaries
  • update the real-workflow lane plan and active goal so the negative fixture taxonomy is the next ready item

User path

A downstream user should be able to start from a job: write Rust tests, run CI/platform bundle workflows, or explicitly materialize fixtures under an output directory.

Boundary

This is a docs/spec slice only. It does not prepare v0.10.0, bump versions, publish, add contract packs, claim provider compatibility, claim production security, 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-0015-real-user-workflows.md
  • active-goal status now marks the real-user-workflow spec done and the negative-fixture taxonomy ready

Risk

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

Rollback

This PR is revertable without invalidating later receipts because it only adds the workflow contract 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!

@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 15 minutes and 17 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: 161616df-c985-4669-9fdb-c323df4b7491

📥 Commits

Reviewing files that changed from the base of the PR and between 95087a7 and cbc9629.

📒 Files selected for processing (4)
  • .uselesskey/goals/active.toml
  • docs/specs/README.md
  • docs/specs/USELESSKEY-SPEC-0015-real-user-workflows.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-real-user-workflows

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 555f0dd into main May 18, 2026
5 checks passed
@EffortlessSteven EffortlessSteven deleted the docs/spec-real-user-workflows branch May 18, 2026 20:35
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