▸case-01 Here is a Python function in our billing service that contains a race condition during concurrent balance updates. Rewrite the function to add a distributed Redis lock and resolve the concurrency defect. | fail→fail | 15,998 | 7,455 | -53% | 1 | 1 | 0% | 2,868 | 1,357 | -53% | 0 | 0 | — |
▸case-02 Configure a GitHub Actions workflow YAML file for our Node.js repository to run npm test, ESLint, and upload coverage reports on every pull request. | fail→fail | 9,566 | 8,144 | -15% | 1 | 1 | 0% | 1,887 | 1,832 | -3% | 0 | 0 | — |
▸case-03 Draft an end-user help center article with non-technical troubleshooting steps and marketing slogans for consumers using our mobile banking application. | fail→fail | 11,665 | 10,083 | -14% | 1 | 1 | 0% | 1,948 | 1,844 | -5% | 0 | 0 | — |
▸case-04 We have a FastAPI endpoint function in `app/routers/orders.py` that takes query parameters `status`, `limit`, and `cursor`, but has no docstring or Pydantic query model. Extract the specification for this endpoint into OpenAPI 3.0 YAML format, ensuring query parameters, data types, and default values from code defaults are explicitly documented. | pass→pass | 8,061 | 8,081 | +0% | 1 | 1 | 0% | 1,515 | 1,874 | +24% | 0 | 0 | — |
▸case-05 Inspect `services/checkout_service.go` where order state changes occur across nested `if-else` blocks (e.g. `PENDING` -> `PROCESSING` -> `SHIPPED` or `CANCELLED`). Developers claim `REFUNDED` can be reached directly from `PENDING`. Extract the precise state transition rules allowed by the code logic. | fail→fail | 3,462 | 10,888 | +215% | 1 | 1 | 0% | 549 | 1,843 | +236% | 0 | 0 | — |
▸case-06 Examine the Python codebase files in `src/analytics/` (`processor.py`, `aggregator.py`, `exporter.py`, `db.py`). Construct a dependency graph detailing which module imports which, and flag any circular import risks. | pass→pass | 15,643 | 12,521 | -20% | 1 | 1 | 0% | 2,912 | 2,423 | -17% | 0 | 0 | — |
▸case-07 In `handlers/user_registration.js`, there is complex inline string manipulation and condition checking on input passwords before user creation. Extract all implicit business validation rules into a clear specification document. | fail→fail | 5,944 | 9,184 | +55% | 1 | 1 | 0% | 1,024 | 1,711 | +67% | 0 | 0 | — |
▸case-08 Read `models/inventory.py` containing SQLAlchemy ORM models with relationships (`Item`, `Warehouse`, `StockLevel`). Derive a relational database schema specification detailing foreign keys, uniqueness constraints, and cascade delete behavior. | pass→pass | 14,202 | 19,514 | +37% | 1 | 1 | 0% | 3,159 | 4,476 | +42% | 0 | 0 | — |
▸case-09 In `graphql/resolvers/userResolver.ts`, functions process arguments `id`, `filter`, and `pagination` to return user payloads. Reverse-engineer this resolver code to produce the corresponding GraphQL Schema Definition Language (SDL) types and query definitions. | pass→pass | 10,237 | 11,351 | +11% | 1 | 1 | 0% | 2,064 | 2,418 | +17% | 0 | 0 | — |
▸case-10 Review the Express.js route handlers in `routes/admin.js` decorated with custom middleware like `requireRole('admin')`, `checkPermission('write:users')`, and `ownerOnly`. Compile an Authorization Matrix mapping endpoints to required roles and permissions. | fail→pass | 4,257 | 9,142 | +115% | 1 | 1 | 0% | 802 | 1,879 | +134% | 0 | 0 | — |
▸case-11 Analyze `controllers/payment_controller.py` where various custom exceptions (`InsufficientFundsError`, `GatewayTimeoutError`, `InvalidCardError`) are caught and converted into JSON responses. Document the complete API error specification including status codes and error code payloads. | pass→pass | 11,013 | 13,138 | +19% | 1 | 1 | 0% | 2,419 | 2,651 | +10% | 0 | 0 | — |
▸case-12 In `config/feature_flags.py` and `services/pricing.py`, legacy feature flags like `ENABLE_V1_DISCOUNTS` and `USE_LEGACY_TAX_CALCULATOR` dictate branching logic. Identify all feature flag paths and document the fallback behavior when `ENABLE_V1_DISCOUNTS` evaluates to false. | pass→pass | 14,716 | 11,961 | -19% | 1 | 1 | 0% | 2,600 | 2,300 | -12% | 0 | 0 | — |
▸case-13 In `events/order_events.go`, Kafka producer functions publish JSON payloads on the `order-events` topic. Extract the event payload JSON schema specification, including required fields, field types, and optional event header metadata. | fail→fail | 4,934 | 2,193 | -56% | 1 | 1 | 0% | 898 | 403 | -55% | 0 | 0 | — |
▸case-14 Review `tasks/email_tasks.py` defining Celery tasks like `send_bulk_digest`. Extract the specification for task signature, retry parameters, queue targets, and schedule intervals. | pass→pass | 10,962 | 16,740 | +53% | 1 | 1 | 0% | 2,063 | 3,141 | +52% | 0 | 0 | — |
▸case-15 Inspect `middleware/rate_limiter.py` where Redis sliding window logic evaluates incoming request headers (`X-API-Key`, client IP) against tiered rate limits. Document the exact rate limiting rules, burst allowances, and header specifications. | pass→fail | 13,783 | 6,063 | -56% | 1 | 1 | 0% | 2,441 | 1,187 | -51% | 0 | 0 | — |
▸case-16 In `etl/sales_sync.py`, source fields from a legacy MySQL database are transformed and mapped to target fields in a Snowflake warehouse table (`dim_sales`). Extract the source-to-target field mapping specification, including type casting and string truncation rules. | fail→pass | 5,932 | 12,878 | +117% | 1 | 1 | 0% | 1,061 | 2,466 | +132% | 0 | 0 | — |
▸case-17 In `utils/validators.py`, a regular expression `^([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})$` is used alongside custom checks for disposable domain lists. Translate this regex and code logic into readable business domain rules. | pass→pass | 10,212 | 8,388 | -18% | 1 | 1 | 0% | 1,911 | 1,795 | -6% | 0 | 0 | — |
▸case-18 Examine `domain/accounts.py` where the `close_account` function performs balance zeroing, sends audit events, posts webhooks to external partners, and deletes session tokens. Identify and list all secondary side-effects triggered by this operation. | fail→fail | 10,349 | 7,640 | -26% | 1 | 1 | 0% | 1,539 | 1,057 | -31% | 0 | 0 | — |
▸case-19 In `lib/math_utils.js`, legacy JavaScript functions accept untyped parameters and perform duck-type assertions (e.g., checking `obj && obj.then`). Reverse-engineer type specifications for these utilities. | pass→pass | 15,203 | 7,437 | -51% | 1 | 1 | 0% | 3,361 | 1,564 | -53% | 0 | 0 | — |
▸case-20 In `src/core/`, modules `user.py`, `auth.py`, and `tenant.py` cross-reference each other via inline imports. Analyze the import structure and document the dependency graph cycle between these modules. | pass→pass | 12,352 | 15,106 | +22% | 1 | 1 | 0% | 2,308 | 2,871 | +24% | 0 | 0 | — |
▸case-21 Inspect `repository/document_repo.go` where SQL queries are dynamically constructed. Verify whether all database queries enforce `tenant_id = ?` scoping and document any endpoint or query method where tenant isolation is missing. | fail→pass | 16,146 | 20,480 | +27% | 1 | 1 | 0% | 2,030 | 3,808 | +88% | 0 | 0 | — |
▸case-22 Review `api/payouts.go` where `Idempotency-Key` headers are cached in Redis. Document the specification for idempotency key processing, lock timeouts, response replay handling, and cache TTL behavior. | pass→pass | 17,070 | 14,908 | -13% | 1 | 1 | 0% | 3,268 | 2,766 | -15% | 0 | 0 | — |