▸case-20 Our Playwright E2E integration test suite for the `checkout-flow` feature has a flaky test on slow CI runners when waiting for a modal dialog to animate open. How should we configure Playwright wait strategies and retry options in `playwright.config.ts` to make this test resilient? | pass→pass | 29,415 | 17,661 | -40% | 1 | 1 | 0% | 2,488 | 2,573 | +3% | 0 | 0 | — |
▸case-01 We have finalized the frontend and backend work for the `user-profile` feature and collected the visual evidence and code review reports. Please run the required audits and write the final verification document to `docs/full-stack-development/requirements/user-profile/06-verification/quality-audit-report.md`. | fail→fail | 14,678 | 14,211 | -3% | 1 | 1 | 0% | 272 | 817 | +200% | 0 | 0 | — |
▸case-02 I need to run a full quality audit on the `crypto-swap` feature before moving to completion verification. Please evaluate our UI screenshots, HeroUI component usage, API implementation coverage, and code review status, and save the resulting quality audit report in the verification directory. | fail→fail | 14,396 | 11,709 | -19% | 1 | 1 | 0% | 204 | 766 | +275% | 0 | 0 | — |
▸case-03 All process evidence and backend contracts for `auth-service` are prepared in the stage folder. Please execute the quality auditor checks across all artifacts and generate the `quality-audit-report.md` report file required prior to the completion verifier stage. | fail→fail | 4,309 | 15,473 | +259% | 1 | 1 | 0% | 197 | 840 | +326% | 0 | 0 | — |
▸case-04 We are auditing the `nft-marketplace` feature. The mobile viewport screenshots show overlapping text boxes and two blank images in dark mode, but the frontend developer says those are minor display glitches that don't affect core transaction functionality. Write a quality audit summary evaluating whether this feature's visual inspection passes. | pass→pass | 16,716 | 16,639 | -0% | 1 | 1 | 0% | 1,709 | 1,915 | +12% | 0 | 0 | — |
▸case-05 During the audit of the `dashboard-widgets` feature, we noticed `src/components/Table.tsx` and `src/components/Drawer.tsx` re-implement custom table and drawer elements locally rather than referencing the official HeroUI package components. The team wants to mark the component audit as compliant since the visual appearance matches. Write an evaluation report on HeroUI compliance for this feature. | pass→pass | 25,416 | 13,867 | -45% | 1 | 1 | 0% | 2,894 | 2,909 | +1% | 0 | 0 | — |
▸case-06 We are reviewing the API contract for the `payment-gateway` feature. The endpoint `POST /api/v1/charges` handles payment submissions, but the spec does not define an idempotency header or error status codes for unauthorized requests. The backend lead notes that unit tests cover standard 200 OK responses. Provide an evaluation report on whether backend contract coverage passes. | pass→pass | 21,264 | 17,494 | -18% | 1 | 1 | 0% | 2,296 | 2,596 | +13% | 0 | 0 | — |
▸case-07 For the `p2p-lending` feature audit, the code review report contains one unresolved high-severity finding regarding potential race conditions during funds transfer. The tech lead asked to pass the quality audit gate today because a patch is scheduled for tomorrow's maintenance window. Evaluate the code review status for feature verification. | pass→pass | 17,584 | 17,238 | -2% | 1 | 1 | 0% | 1,689 | 2,096 | +24% | 0 | 0 | — |
▸case-08 While evaluating the `governance-voting` feature, we checked `hero-ui-manifest.json` and found its cached snapshot date is over 60 days old. The frontend team suggests skipping the snapshot refresh check since no new UI components were added this week. Provide an evaluation of the docs freshness check. | pass→pass | 14,286 | 14,452 | +1% | 1 | 1 | 0% | 1,896 | 1,897 | +0% | 0 | 0 | — |
▸case-09 A developer wants to trigger `completion-verifier` for the `liquidity-pool` feature immediately after completing unit tests, skipping the quality auditor suite to meet a release deadline. Provide a step-by-step gate requirement report explaining when completion verification is permitted to run. | fail→pass | 16,872 | 22,286 | +32% | 1 | 1 | 0% | 2,300 | 2,952 | +28% | 0 | 0 | — |
▸case-10 We are preparing to generate the quality audit report for the `token-vesting` feature artifact review. Specify the standard file system path where this quality audit document must be written. | fail→pass | 7,412 | 1,516 | -80% | 1 | 1 | 0% | 1,264 | 587 | -54% | 0 | 0 | — |
▸case-11 The automated screenshot inspection for `analytics-portal` detected several buttons with contrast ratio below WCAG AA guidelines (2.1:1 low contrast). The designer mentioned that light-gray on white is part of the brand's aesthetic. Write an audit decision report on the visual quality aspect of this feature. | pass→pass | 15,297 | 18,302 | +20% | 1 | 1 | 0% | 2,449 | 2,811 | +15% | 0 | 0 | — |
▸case-12 In the `user-settings` API specification review, the endpoint `PUT /api/v1/user/profile` includes request body fields and 200 OK responses, but omits explicit 400 Bad Request and 401 Unauthorized schema field definitions. The team asks to approve backend contract readiness. Evaluate the contract audit. | pass→fail | 18,451 | 14,841 | -20% | 1 | 1 | 0% | 2,272 | 865 | -62% | 0 | 0 | — |
▸case-13 An audit of the `checkout-funnel` UI code reveals `src/components/common/Button.tsx` which wraps standard HTML `<button>` with custom styles instead of using HeroUI's `Button` component. The team argues this local clone is fine because it's used across multiple pages. Determine whether this passes HeroUI compliance. | pass→pass | 12,840 | 15,214 | +18% | 1 | 1 | 0% | 2,010 | 2,069 | +3% | 0 | 0 | — |
▸case-14 During the code review gate check for `identity-verification`, the report lists one unresolved blocker finding regarding unvalidated input in JWT decoding. The release manager wants to issue a conditional pass for the quality audit. Evaluate this request. | pass→pass | 21,167 | 9,044 | -57% | 1 | 1 | 0% | 2,051 | 2,024 | -1% | 0 | 0 | — |
▸case-15 We are conducting the quality audit for `email-notifications`. The pull request description links to a PR thread, but no formal code review report file exists in the workspace. The engineer states the code was verbally approved during pair programming. Determine if the code review gate passes. | pass→pass | 13,324 | 8,266 | -38% | 1 | 1 | 0% | 1,078 | 1,834 | +70% | 0 | 0 | — |
▸case-16 Explain the tool execution sequence when auditing the `rewards-vault` feature: should `review_completion_gate` be executed before or after running `review_visual_inspection_metrics`, `review_backend_contract_audit`, and `review_code_review_gate`? | pass→pass | 8,207 | 13,844 | +69% | 1 | 1 | 0% | 1,146 | 1,660 | +45% | 0 | 0 | — |
▸case-17 We need to verify that all API endpoints, authentication mechanisms, idempotency keys, and schema fields for `order-fulfillment` match between the specification and implementation. Which MCP tool must be called to perform this check? | fail→pass | 11,410 | 7,547 | -34% | 1 | 1 | 0% | 1,590 | 783 | -51% | 0 | 0 | — |
▸case-18 To evaluate visual evidence, screenshot diff metrics, clipping, and contrast for the `dark-mode-toggle` feature, which MCP tool should be invoked? | fail→pass | 17,856 | 8,135 | -54% | 1 | 1 | 0% | 2,209 | 720 | -67% | 0 | 0 | — |
▸case-19 When verifying whether the cached official HeroUI documentation manifest used in component audits for `component-library-upgrade` is current, which MCP tool handles this check? | fail→pass | 13,763 | 1,864 | -86% | 1 | 1 | 0% | 1,563 | 641 | -59% | 0 | 0 | — |
▸case-21 We are designing a new REST endpoint `POST /api/v1/users` for user registration. Draft the OpenAPI 3.0 YAML schema definition for this endpoint including request body properties `email` and `password` with validation constraints, and a 201 Created response. | pass→pass | 12,434 | 17,467 | +40% | 1 | 1 | 0% | 2,593 | 3,118 | +20% | 0 | 0 | — |
▸case-22 We need to set up a GitHub Actions workflow in `.github/workflows/unit-tests.yml` that runs Jest test suites across Node.js versions 18, 20, and 22 in parallel on every pull request. Draft the matrix build configuration. | pass→pass | 10,567 | 19,212 | +82% | 1 | 1 | 0% | 1,135 | 2,410 | +112% | 0 | 0 | — |