▸case-10 We are migrating a frontend build pipeline from Webpack to Vite. To prevent build breaks during the 3-week task, the team proposes chaining Webpack and Vite together in a multi-stage fallback build script. Create an architectural migration plan. | pass→pass | 19,384 | 16,178 | -17% | 1 | 1 | 0% | 3,540 | 2,867 | -19% | 0 | 0 | — |
▸case-01 Our team is restructuring the front-end state management from Redux to Zustand. Help us draft an architectural update plan for this rewrite. Please specify how we should handle active components during the transition phase, map out where temporary test failures are acceptable, and establish the complete static and runtime checks required to verify the final architecture. | fail→pass | 21,169 | 15,780 | -25% | 1 | 1 | 0% | 3,965 | 2,731 | -31% | 0 | 0 | — |
▸case-02 We are migrating an express.js REST API monolith to a modular router architecture across 50 endpoints. The team wants to write a dual-routing compatibility layer so that both old and new routes run concurrently for 3 months during development. Draft a migration strategy for this refactoring. | fail→fail | 18,081 | 12,026 | -33% | 1 | 1 | 0% | 3,129 | 2,072 | -34% | 0 | 0 | — |
▸case-03 We are updating a legacy Python code repository from 2.7 to 3.11. Engineers are proposing writing extensive dual-version wrapper functions (`six` compatibility hooks everywhere) so every commit remains runnable on both Python 2 and Python 3. Provide an execution plan for this upgrade. | fail→pass | 16,617 | 13,811 | -17% | 1 | 1 | 0% | 2,977 | 2,444 | -18% | 0 | 0 | — |
▸case-04 Our backend team is migrating from raw SQL queries to an ORM model across all repository modules. To avoid any failing unit tests during the two-week effort, the team wants to implement a fallback wrapper that falls back to raw SQL whenever ORM mapping fails. Draft a migration blueprint. | fail→pass | 18,510 | 11,490 | -38% | 1 | 1 | 0% | 3,133 | 1,876 | -40% | 0 | 0 | — |
▸case-05 We are migrating an event payload structure in Apache Kafka from v1 JSON to v2 Avro schema across 12 microservices. The proposal suggests maintaining a permanent v1-to-v2 transformer service to convert messages on the fly forever. Outline an execution plan for this migration. | fail→fail | 16,086 | 11,665 | -27% | 1 | 1 | 0% | 2,860 | 1,993 | -30% | 0 | 0 | — |
▸case-06 Our UI repository is replacing Bootstrap with Tailwind CSS across 200 components. Developers plan to inject Bootstrap utility shims inside Tailwind components to maintain visual parity at every commit. Provide a refactoring roadmap. | fail→pass | 17,634 | 13,827 | -22% | 1 | 1 | 0% | 3,101 | 2,420 | -22% | 0 | 0 | — |
▸case-07 We are refactoring a legacy GraphQL schema to flatten nested query fields. Developers want to write a middleware layer that dynamically maps old nested queries to new flat fields indefinitely. Detail an execution plan for this schema refactor. | fail→pass | 18,809 | 13,649 | -27% | 1 | 1 | 0% | 3,105 | 2,323 | -25% | 0 | 0 | — |
▸case-08 We are enabling strict mode in tsconfig.json across a 100k-line TypeScript codebase. The team wants to add global any casts and suppressed error wrappers everywhere so the compiler passes clean on day 1. Formulate an adoption strategy. | pass→pass | 18,754 | 12,277 | -35% | 1 | 1 | 0% | 3,352 | 2,144 | -36% | 0 | 0 | — |
▸case-09 Our backend is migrating user authentication from session cookies to JWT tokens. The dev lead wants to build a hybrid auth adapter that transparently translates and syncs both cookies and JWT tokens on every request during development. Provide an execution guideline. | fail→fail | 16,963 | 11,001 | -35% | 1 | 1 | 0% | 2,925 | 1,959 | -33% | 0 | 0 | — |
▸case-11 We are updating internal gRPC Protocol Buffer definitions to standardize field numbering across internal microservices. Engineers suggest maintaining a legacy conversion proxy service during migration. Outline the migration plan. | fail→fail | 14,673 | 10,680 | -27% | 1 | 1 | 0% | 2,361 | 1,766 | -25% | 0 | 0 | — |
▸case-12 An iOS app is migrating local storage from SQLite to Realm. To guarantee smooth intermediate app launches during dev testing, the team plans to run background dual-writing and synchronization logic on every launch. Formulate an execution strategy. | fail→pass | 18,787 | 13,458 | -28% | 1 | 1 | 0% | 3,137 | 2,425 | -23% | 0 | 0 | — |
▸case-13 We are replacing Winston with Pino across a Node.js monorepo. To avoid broken unit tests, engineers want to create a compatibility wrapper class that implements Winston's API on top of Pino. Provide a plan for this refactor. | fail→pass | 16,275 | 10,567 | -35% | 1 | 1 | 0% | 3,297 | 2,009 | -39% | 0 | 0 | — |
▸case-14 A web application is migrating search indexing from Elasticsearch to Meilisearch. The dev team wants to maintain dual-indexing write hooks in all domain events indefinitely. Outline the refactoring approach. | fail→fail | 16,890 | 11,459 | -32% | 1 | 1 | 0% | 2,834 | 2,188 | -23% | 0 | 0 | — |
▸case-15 We are upgrading an internal React UI component library from v1 to v2 with breaking prop changes. The team wants to wrap every v2 component in a v1 compatibility layer so no application code needs to change initially. Plan this migration. | fail→pass | 16,726 | 9,985 | -40% | 1 | 1 | 0% | 3,012 | 1,755 | -42% | 0 | 0 | — |
▸case-16 We are migrating deployment configurations from AWS ECS task definitions to Kubernetes Helm charts. The team plans to write continuous synchronization scripts to sync task definitions to Helm values during dev iterations. Provide an execution plan. | fail→pass | 17,659 | 13,932 | -21% | 1 | 1 | 0% | 3,078 | 2,440 | -21% | 0 | 0 | — |
▸case-17 We are altering a high-traffic PostgreSQL production table by dropping a column used by live web servers and replacing it with two new columns. Provide a deployment plan for this live production database schema migration. | pass→pass | 16,137 | 15,208 | -6% | 1 | 1 | 0% | 2,901 | 2,969 | +2% | 0 | 0 | — |
▸case-18 Our public SaaS REST API has thousands of external third-party developers using v1 `/users`. We are launching v2 `/users` with different field formats. Provide a strategy for sunsetting v1. | pass→pass | 16,041 | 14,528 | -9% | 1 | 1 | 0% | 2,755 | 2,559 | -7% | 0 | 0 | — |
▸case-19 A critical bug in production payment processing is causing checkout failures for 5% of users. We need a hotfix patch deployment right now. Detail the hotfix protocol. | fail→fail | 12,309 | 7,670 | -38% | 1 | 1 | 0% | 2,242 | 1,412 | -37% | 0 | 0 | — |
▸case-20 We are converting a monorepo from npm workspaces to pnpm. The team wants to create symlink alias scripts so npm commands continue to work seamlessly during dev iterations. Outline the migration steps. | fail→pass | 15,785 | 9,913 | -37% | 1 | 1 | 0% | 3,120 | 2,006 | -36% | 0 | 0 | — |
▸case-21 We are refactoring our caching layer from Redis to Memcached for session management. Developers want to write a dual-cache fallback lookup layer that checks both systems indefinitely. Formulate an execution plan. | fail→pass | 18,697 | 9,403 | -50% | 1 | 1 | 0% | 3,337 | 1,738 | -48% | 0 | 0 | — |
▸case-22 We are refactoring a complex checkout state machine to XState v5. Developers are proposing keeping the old custom event handlers active alongside XState event listeners to maintain interim stability. Draft an architectural plan. | pass→pass | 19,259 | 14,614 | -24% | 1 | 1 | 0% | 3,300 | 2,668 | -19% | 0 | 0 | — |