Skip to content

CRAP: shared packages (capture-kit diffing and overlay, maestro, selectors, limrun) #3423

Closed

Description

@thymikee

Purpose

Burn down part of the coverage-based CRAP list from #3414.

Findings (main 5f84627d8)

Function CRAP CC Coverage
packages/capture-kit/src/png-rgb-difference.ts:19 computePngRgbDifference 42 6 0%
packages/capture-kit/src/react-native-overlay.ts:266 collapsedWarningScores 30 5 0%
packages/maestro/src/internal/facade-execution.ts:273 suggestionQuery 62 14 38%
packages/selectors/src/index.ts:150 values 30 5 0%
packages/provider-limrun/src/runtime.ts:501 getAppState 30 5 0%

Owned files

  • packages/capture-kit/src/png-rgb-difference.ts
  • packages/capture-kit/src/react-native-overlay.ts
  • packages/maestro/src/internal/facade-execution.ts
  • packages/selectors/src/index.ts
  • packages/provider-limrun/src/runtime.ts

Notes

suggestionQuery (CC 14, 38%) may also need a split. Child A owns png-worker.ts in capture-kit; name any new fixture after the module it serves.

Completion

  • Every function above is absent from pnpm check:coverage-crap --all on the PR head (score < 30), or is exempted where this issue says so.
  • Tests go through the owning module's public entry point. No new production exports for tests and no test-only DI (docs/agents/testing.md).
  • Only the owned files, the tests that exercise them, and *.fixtures.ts helpers change. The PR stays under the 1,000-line gross budget, and pnpm check:affected --run passes on the pushed head.

Part of #3414.

Activity

  1. added a commit that references this issue on Oct 12, 2026
    a0f9b0b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions