▸case-01 Please inspect our repository's current state and identify which software lifecycle stage we are operating in right now. | fail→fail | 6,501 | 4,015 | -38% | 1 | 1 | 0% | 1,036 | 563 | -46% | 0 | 0 | — |
▸case-02 Our repository has package.json version 0.0.1, no deployment configs, and placeholder files. The team lead claims we are in beta because user testing is scheduled next month. Which stage takes precedence according to repository signal priority rules? | fail→fail | 7,015 | 3,721 | -47% | 1 | 1 | 0% | 1,155 | 607 | -47% | 0 | 0 | — |
▸case-03 We have core domain models written, 40% test coverage, version 0.2.0-alpha, and active daily feature commits, but no external staging environment. A developer marked the release as GA on GitHub. Determine the project stage. | fail→fail | 8,118 | 5,895 | -27% | 1 | 1 | 0% | 1,408 | 976 | -31% | 0 | 0 | — |
▸case-04 The repository contains tag v1.0.0-rc.1, a feature-freeze entry in CHANGELOG.md, active bug-fix PRs, and a staging Kubernetes manifest. Identify the project development phase. | fail→fail | 5,351 | 4,918 | -8% | 1 | 1 | 0% | 887 | 780 | -12% | 0 | 0 | — |
▸case-05 Our repository has tag v2.4.0 deployed to production, automated patch release workflows, stable SLA metrics, and only routine maintenance commits over the past two months. Categorize the project stage. | fail→fail | 4,343 | 3,471 | -20% | 1 | 1 | 0% | 678 | 556 | -18% | 0 | 0 | — |
▸case-06 The repository README displays an EOL notice, security patches are disabled, package registry listing is marked deprecated, and open PRs are archived. Identify the software lifecycle phase. | fail→fail | 3,579 | 3,340 | -7% | 1 | 1 | 0% | 623 | 552 | -11% | 0 | 0 | — |
▸case-07 Our repository contains architectural decision records (ADRs), open PRD issues, wireframe assets, and empty repository folders with no executable code or build scripts. Determine the current project phase. | fail→fail | 6,262 | 5,215 | -17% | 1 | 1 | 0% | 1,090 | 832 | -24% | 0 | 0 | — |
▸case-08 The repository has tag v1.0.0-beta.3, integration tests passing against a staging database, and a pending production deployment approval PR. Identify the project stage. | fail→fail | 5,333 | 4,889 | -8% | 1 | 1 | 0% | 911 | 618 | -32% | 0 | 0 | — |
▸case-09 The codebase consists of a single spike script in a scratch directory evaluating a third-party API, with no test harness or CI workflow. Determine the lifecycle stage. | fail→fail | 3,593 | 3,925 | +9% | 1 | 1 | 0% | 615 | 632 | +3% | 0 | 0 | — |
▸case-10 We released v1.0.0 last week, but our issue tracker is flooded with high-volume user scaling issues, database indexing refactors, and rapid hotfixes on version 1.0.1. Identify the project phase. | fail→fail | 6,713 | 4,492 | -33% | 1 | 1 | 0% | 1,131 | 770 | -32% | 0 | 0 | — |
▸case-11 The main branch has semantic version v1.5.0 with new feature development explicitly paused while 80% of recent PRs focus on migrating from JavaScript to TypeScript. Determine the lifecycle stage. | fail→fail | 6,875 | 4,963 | -28% | 1 | 1 | 0% | 968 | 853 | -12% | 0 | 0 | — |
▸case-12 The repository contains a sunset banner notice, a migration guide redirecting users to v2-repo, and read-only issue settings. Identify the lifecycle stage. | fail→fail | 3,964 | 3,938 | -1% | 1 | 1 | 0% | 663 | 639 | -4% | 0 | 0 | — |
▸case-13 Tag v3.0.0-rc.2 is currently running long-haul load tests in a pre-prod environment with bug fixes cherry-picked from release branches. Identify the project stage. | fail→fail | 5,359 | 33,062 | +517% | 1 | 1 | 0% | 877 | 707 | -19% | 0 | 0 | — |
▸case-14 A repository created 24 hours ago contains hardcoded secret keys, unformatted code, no test suites, and a single commit titled 'demo build'. Determine the development phase. | fail→fail | 5,584 | 3,202 | -43% | 1 | 1 | 0% | 817 | 517 | -37% | 0 | 0 | — |
▸case-15 A production release v2.1.0 was rolled back 2 hours ago due to high error rates, and the repository is currently frozen for a live incident post-mortem analysis. Identify the current stage. | fail→fail | 4,781 | 3,621 | -24% | 1 | 1 | 0% | 874 | 562 | -36% | 0 | 0 | — |
▸case-16 In our monorepo, package-a is at v3.2.0 in production while package-b in `/packages/experimental` is at v0.0.1 with no tests. Determine the development stage of `/packages/experimental` specifically. | fail→fail | 4,799 | 5,188 | +8% | 1 | 1 | 0% | 906 | 878 | -3% | 0 | 0 | — |
▸case-17 The repository uses trunk-based development with automated deployment to production on every merged main branch commit, versioning automatically incremented via semantic releases. Identify the development phase pattern. | fail→fail | 5,445 | 3,700 | -32% | 1 | 1 | 0% | 860 | 592 | -31% | 0 | 0 | — |
▸case-18 All code merges are blocked for a mandatory SOC2 compliance audit, security scanning reports are being generated, and version tag v2.0.0 is held pending auditor approval. Determine the project stage. | fail→fail | 4,368 | 5,429 | +24% | 1 | 1 | 0% | 661 | 928 | +40% | 0 | 0 | — |
▸case-19 The project has working unit tests and a private preview tag v0.9.0 shared exclusively with three design partners for feedback before general availability. Determine the development phase. | fail→fail | 4,767 | 4,842 | +2% | 1 | 1 | 0% | 777 | 782 | +1% | 0 | 0 | — |
▸case-20 Explain how Semantic Versioning 2.0.0 determines precedence between `1.0.0-alpha`, `1.0.0-alpha.1`, `1.0.0-beta`, and `1.0.0`. | pass→pass | 13,483 | 8,223 | -39% | 1 | 1 | 0% | 2,372 | 1,661 | -30% | 0 | 0 | — |
▸case-21 Show how a patch release v1.0.1 entry should be formatted in CHANGELOG.md according to the Keep a Changelog standard, including fixed bugs. | pass→pass | 8,438 | 5,905 | -30% | 1 | 1 | 0% | 1,627 | 1,131 | -30% | 0 | 0 | — |
▸case-22 Write the shell commands to create an annotated Git tag `v2.0.0` with message 'Release 2.0.0' and push it to origin. | pass→pass | 2,425 | 1,777 | -27% | 1 | 1 | 0% | 476 | 293 | -38% | 0 | 0 | — |