benchmarks: record Cursor skill invocation results - #37
Merged
Conversation
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.
Outcome
Records the 2026-08-15 Cursor benchmark for automatic GraphKeeper skill invocation across Composer 2.5 and Grok 4.6. The change is limited to one Markdown result file under
benchmarks/results/.Evidence
No failing test applies to this documentation-only benchmark record. The staged diff passed
git diff --cached --check, and the final diff was inspected before commit.Checklist
npm run buildpasses. (Not run: documentation-only change.)npm run typecheckpasses. (Not run: documentation-only change.)npm testpasses with no hidden skips. (Not run: documentation-only change.)npm run package:smokepasses and the tarball contains intended assets only. (Not run: documentation-only change.)sh -n scripts/validate.shpasses when the legacy fallback changes, andnode --check templates/pre-commitpasses when the hook changes. (Not applicable.)Compatibility and recovery
No runtime, platform, schema, diagnostic, or packaging behavior changes. Rollback consists of reverting the single documentation commit; no manual recovery is required.