mutation-model: indirect-ownership self-test pins a test that stopped reaching scroll-edge-state
まだ誰も着手していません。
評価
- 難易度
- 2/5
- 見積もり時間
- 1〜3時間
- 初心者へのやさしさ
- 88/100
- issue の種類
- バグ
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- typescript
- 領域
- testing
調査の方向性
scripts/mutation/ownership.test.ts から始め、特に 40-44 行付近の間接 Ownership のアサーションと、37-38 行の対応する失敗メッセージを確認します。pnpm mutation:test を実行し、検証済みの scroll-runtime テスト候補と ownershipDeriver().ownersOf を調べてから、pnpm check:affected --run を実行します。間接到達可能性のチェックが引き続き意味を持ち、古くなったペアについて有用なメッセージを報告し、両方のコマンドが成功すれば完了です。
索引モデルが issue の本文から書いたものです。
説明
Purpose
mutation-model — the mutation harness self-test inside pnpm check:affected — fails on a clean origin/main checkout, so any contributor whose diff selects that check sees a red local gate for a reason unrelated to their work. It hit #2533 and #2521 during wave 1 of #2531.
Reproduce
pnpm install --frozen-lockfile
pnpm mutation:test
# or, as check:affected selects it:
pnpm check:affected --run # → check:affected: mutation-model failed.
ℹ pass 39
ℹ fail 1
✖ a kernel is owned by tests that reach it indirectly
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
at scripts/mutation/ownership.test.ts:40:10
The other 39 assertions in that file pass, including ownership is complete: every test reaching a kernel owns it.
Root cause
scripts/mutation/ownership.test.ts:40-44 pins src/commands/interaction/runtime/gestures.test.ts as an indirect owner of the scroll-edge-state kernel. That kernel is packages/capture-kit/src/snapshot/scroll-edge-state.ts plus packages/capture-kit/src/snapshot/scroll-edge-state/selection.ts.
gestures.test.ts no longer imports anything on the scroll path: its resolved import graph is 257 modules and contains neither kernel source, so ownersOf returns kernel-errors, interaction-settle, selectors, target-annotation-serde, snapshot-occlusion and no scroll-edge-state. Scroll moved out of the interaction command family — src/daemon/scroll-runtime.ts was added by bcca714a07 ("refactor: move gesture family to platform runtime", #1952) and the snapshot zone relocation landed in 1f9d940bff (#2385) — and the ownership assertion was never moved with it.
The kernel itself is not uncovered: it has 82 owning test files, including the mirrored packages/capture-kit/src/snapshot/__tests__/scroll-edge-state-*.test.ts set, and the ownership is complete: every test reaching a kernel owns it test passes. Only this hand-pinned pair is stale.
Required behavior
- The indirect-reachability assertion keeps its purpose — proving the deriver credits a test that exercises a kernel without importing it by name — while naming a pair that is true today.
- Verified live replacement pair:
src/daemon/__tests__/scroll-runtime.test.ts. It never contains the stringscroll-edge-state, reaches both kernel sources throughsrc/daemon/scroll-runtime.ts, andownershipDeriver(...).ownersOfincludesscroll-edge-state.src/daemon/scroll-until.test.tsis a second verified candidate. - Give the assertion a failure message in the style of its sibling at
:37-38, so the next relocation reports which pair went stale instead of printing a bare falsy expression.
Observable completion conditions
pnpm mutation:testpasses on a clean tree with no other assertion weakened.pnpm check:affected --runreports nomutation-modelfailure on a docs- or config-only diff.- The replacement assertion still fails when the deriver stops crediting indirect reach, i.e. it is not converted into a direct-import assertion.
Dependencies and blast radius
- No CI job runs
mutation:testorcheck:affected:mutation-affected.ymltriggers onscripts/mutation/**,scripts/lib/**,stryker.config.json, or its own workflow file, andmutation-weekly.ymlis a Sunday schedule plusworkflow_dispatch. This issue therefore gates local contribution, not PRs, and no PR label or re-run depends on it. - Contained in
scripts/mutation/**; no runtime or kernel source changes are implied.
- 主要言語
- TypeScript
- スター
- 4.7k
- フォーク
- 304
- 平均マージ
- 12時間 42分
- マージ済み PR(30日)
- 463
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
callstack/agent-device のほかの issue
-
refactor
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
callstack/agent-device#2530 · コメント 1 件 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
callstack/agent-device#1869 ·
-
enhancement ready-for-agent
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
callstack/agent-device#2731 ·
-
bug ready-for-agent
難易度 3/5 1〜2日 初心者へのやさしさ 72/100
callstack/agent-device#2729 ·
-
bug ready-for-agent
難易度 5/5 1週間以上 初心者へのやさしさ 38/100
callstack/agent-device#2728 ·
callstack/agent-device の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
calcite-components needs triage refactor
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
Esri/calcite-design-system#15203 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 90/100
danielmiessler/LifeOS#2218 ·