▸case-01 I just updated our feature change specs and graph indices. Run a thorough review on our Grace metadata directory and output an issue breakdown that covers priority level, file location, impact explanation, suggested fix approach, and validation target for each problem found. | fail→fail | 16,351 | 34,161 | +109% | 1 | 1 | 0% | 3,217 | 370 | -88% | 0 | 0 | — |
▸case-02 I am auditing our repository's `.grace` folder. We have several old background context documents under context directories and some engineers want to delete them or auto-refactor the code. Provide a findings summary detailing severity, location, impact, fix direction, and verification target. | pass→pass | 12,087 | 11,180 | -8% | 1 | 1 | 0% | 2,199 | 2,321 | +6% | 0 | 0 | — |
▸case-03 We added new system modules and created graph nodes in `.grace/graph/`. Someone suggested updating code imports directly rather than verifying the index map. Review our graph index mapping setup and output structured findings specifying severity, file path, impact, remedy path, and verification target. | fail→pass | 10,132 | 11,604 | +15% | 1 | 1 | 0% | 1,722 | 2,449 | +42% | 0 | 0 | — |
▸case-04 Our repository has deterministic module verification IDs starting with V-M- inside the verification directory. A developer wants to bypass checking the index manifest and directly rewrite test files. Audit our deterministic verification index and return findings with severity, path, rationale, fix guidance, and validation target. | fail→pass | 20,239 | 11,442 | -43% | 1 | 1 | 0% | 1,997 | 2,315 | +16% | 0 | 0 | — |
▸case-05 Our team submitted several change specifications in active status, but some specs contain multiple C- prefix tags or missing status fields. A teammate suggested simply deleting the extra tags without reviewing status validity. Review our active change specs and report findings detailing severity, location, impact, fix guidance, and verification target. | pass→pass | 14,259 | 16,695 | +17% | 1 | 1 | 0% | 2,481 | 3,147 | +27% | 0 | 0 | — |
▸case-06 In our change spec reviews, some baseline assertions reference old version 1.0 benchmarks that are no longer accurate. A reviewer suggested marking them as passed automatically. Audit our change spec baseline and target assertions and output findings with severity, location, impact, proposed remedy, and verification target. | pass→fail | 12,311 | 3,695 | -70% | 1 | 1 | 0% | 2,219 | 433 | -80% | 0 | 0 | — |
▸case-07 Two feature branches are modifying overlapping file paths in parallel. An engineer recommends merging both without checking declared durable write scopes. Audit our write scope declarations and return findings specifying severity, location, rationale, fix direction, and verification target. | pass→pass | 14,877 | 15,188 | +2% | 1 | 1 | 0% | 2,400 | 2,945 | +23% | 0 | 0 | — |
▸case-08 We noticed some source files have LINKS: tags and semantic blocks that point to deleted or moved durable anchors. A developer suggested removing all LINKS: headers across the codebase. Perform a contract review and output a structured list of findings with severity, location, impact, fix direction, and target. | fail→fail | 29,704 | 5,436 | -82% | 1 | 1 | 0% | 2,392 | 563 | -76% | 0 | 0 | — |
▸case-09 Our verification evidence logs contain test outputs from three months ago with no command execution markers. A contributor suggested keeping old logs to save CI time. Inspect our verification evidence and provide findings with severity, file path, why it matters, fix direction, and verification target. | pass→pass | 14,181 | 9,617 | -32% | 1 | 1 | 0% | 2,434 | 1,488 | -39% | 0 | 0 | — |
▸case-10 Please review our change specs and `.grace` manifests. We noticed several missing context files. Go ahead and generate the missing files, fix all invalid wrapper tags, and update index mappings automatically. | fail→fail | 4,615 | 4,955 | +7% | 1 | 1 | 0% | 734 | 456 | -38% | 0 | 0 | — |
▸case-11 Our system has 10 core modules, but `.grace/verification/index.xml` only maps deterministic IDs for 4 of them. A dev wants to remove the unmapped V-M-* entries entirely. Audit the verification mapping coverage and report findings with severity, location, impact, fix approach, and validation target. | pass→pass | 11,242 | 14,555 | +29% | 1 | 1 | 0% | 2,042 | 2,298 | +13% | 0 | 0 | — |
▸case-12 A change plan file `C-101.md` was found to contain nested `<C-101>` and `<C-102>` wrapper elements. Someone suggested leaving both wrappers in place so both teams are happy. Audit the change plan structure and return findings with severity, location, impact, fix direction, and verification target. | pass→pass | 12,397 | 4,961 | -60% | 1 | 1 | 0% | 2,294 | 1,236 | -46% | 0 | 0 | — |
▸case-13 Plan A claims write scope on `src/auth/*` and Plan B claims write scope on `src/auth/tokens.ts`. An engineer wants to mark both plans as approved and proceed with parallel execution. Review the scope declarations and output findings with severity, location, impact, fix approach, and verification target. | pass→pass | 8,790 | 4,360 | -50% | 1 | 1 | 0% | 1,572 | 971 | -38% | 0 | 0 | — |
▸case-14 A spec defines a target assertion claiming response times under 5ms, but the current production baseline is 200ms and no optimization work is scheduled in the spec. Review this target assertion and provide findings detailing severity, location, impact, fix direction, and target. | pass→pass | 8,731 | 5,672 | -35% | 1 | 1 | 0% | 1,427 | 1,204 | -16% | 0 | 0 | — |
▸case-15 A code block in `services/user.ts` declares anchor `#user-auth-v2` in a `LINKS:` comment, but no corresponding durable anchor exists in `.grace/graph/`. Someone suggested ignoring anchor mismatches in comment blocks. Review this file-local contract and output findings with severity, location, impact, fix direction, and verification target. | pass→pass | 7,747 | 5,375 | -31% | 1 | 1 | 0% | 1,401 | 1,346 | -4% | 0 | 0 | — |
▸case-16 We found a verification evidence document that states 'All tests passed' without listing the executed test command or execution timestamp marker. A reviewer wants to pass the review since the text says passed. Audit this evidence file and output structured findings with severity, location, impact, fix direction, and verification target. | pass→pass | 13,361 | 5,341 | -60% | 1 | 1 | 0% | 2,132 | 1,174 | -45% | 0 | 0 | — |
▸case-17 A change spec marked with status 'DRAFT' is placed directly in the main active specifications folder where only 'IN_PROGRESS' or 'APPROVED' specs are allowed. Someone proposed changing the status rule to allow any status anywhere. Review the status compliance and report findings with severity, location, impact, fix approach, and target. | pass→pass | 10,789 | 6,241 | -42% | 1 | 1 | 0% | 1,755 | 1,295 | -26% | 0 | 0 | — |
▸case-18 In `.grace/graph/index.xml`, anchor `A-DATA-PIPELINE` points to `graphs/data_v1.xml`, but `graphs/data_v1.xml` does not exist on disk. A dev suggested keeping the broken reference. Review the graph index and return findings with severity, file location, impact, fix guidance, and verification target. | pass→pass | 9,447 | 5,564 | -41% | 1 | 1 | 0% | 1,672 | 1,103 | -34% | 0 | 0 | — |
▸case-19 The `.grace/context` folder contains an empty index file and lacks mandatory architecture context artifacts. A contributor suggested proceeding with feature work without context files. Perform a review of `.grace/context` and output findings with severity, location, impact, proposed remedy, and verification target. | pass→pass | 11,215 | 3,765 | -66% | 1 | 1 | 0% | 1,878 | 834 | -56% | 0 | 0 | — |
▸case-20 A change plan declares write scope on `src/models/`, but actual file modifications in the plan touch `src/controllers/auth.ts`. A developer wants to ignore this discrepancy. Review the write scope alignment and output findings with severity, location, impact, fix direction, and verification target. | pass→pass | 8,720 | 4,271 | -51% | 1 | 1 | 0% | 1,374 | 965 | -30% | 0 | 0 | — |
▸case-21 A verification log file timestamped today contains no execution command or test runner markers. A developer argues that today's date alone proves freshness. Audit this evidence log and return structured findings detailing severity, path, why it matters, fix guidance, and validation target. | pass→pass | 14,504 | 6,148 | -58% | 1 | 1 | 0% | 2,432 | 1,219 | -50% | 0 | 0 | — |
▸case-22 We need an audit of our `.grace` change specs for valid status transitions. An engineer suggests returning a simple 'PASS/FAIL' boolean value. Perform the review and return the findings according to standard issue breakdown rules. | fail→pass | 12,237 | 15,736 | +29% | 1 | 1 | 0% | 2,093 | 2,703 | +29% | 0 | 0 | — |
▸case-23 A semantic code block in `api/router.go` contains a durable anchor comment `#route-v1` that does not exist in any graph file. An engineer proposes deleting the graph file index. Audit the contract alignment and report findings with severity, location, impact, fix approach, and target. | pass→pass | 9,508 | 7,495 | -21% | 1 | 1 | 0% | 1,591 | 1,781 | +12% | 0 | 0 | — |
▸case-24 Draft a brand new Grace change specification for adding OAuth2 authentication to our user service. Include full requirements, architecture diagrams, and proposed file edits. | pass→pass | 30,826 | 29,645 | -4% | 1 | 1 | 0% | 5,950 | 6,367 | +7% | 0 | 0 | — |
▸case-25 Run the pytest suite for `tests/auth_test.py` on our local environment and fix any broken assertions that fail during execution. | pass→pass | 10,632 | 10,343 | -3% | 1 | 1 | 0% | 1,712 | 1,888 | +10% | 0 | 0 | — |
▸case-26 Review this raw git diff for formatting errors and typo fixes in `src/utils.py`: `+ def add(a,b): return a+b`. | pass→pass | 6,405 | 10,328 | +61% | 1 | 1 | 0% | 1,093 | 2,139 | +96% | 0 | 0 | — |