You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dbf66ab
Browse filesBrowse the repository at this point in the historyBrowse files
Ratchet the corpus benchmark recall 3/9 -> 4/9 by making the
screentogif-loaded-subscription fixture self-contained. It is a subscription leak
(our strongest class) that scored a miss only because the reduction's before.cs
referenced VideoSourceViewModel without declaring it — so the type-aware extractor
could not bind the `+=` to an event and honestly emitted OWN050 (a note, not a
verdict). Adding a minimal VideoSourceViewModel (the three events) + a StatusBand
stub, mirrored in after.cs, lets the extractor resolve and flag the leak
(warning-tier: an injected DataContext source) exactly as on the full repo; the
matching `-=` in after.cs keeps the fix silent.
Benchmark scorecard (CI): screentogif-loaded-subscription before[caught: OWN001]
after[clean]; 4/9 caught, 9/9 clean, 0 FP. The corpus-benchmark floor is raised to
--min-recall 4. Lesson recorded: a fixture referencing an undeclared type silently
degrades to OWN050; self-contained fixtures measure honestly. The remaining 5
misses are genuine frontend extraction gaps (pool double-return/use-after-return,
interprocedural handoff, cross-method use-after-dispose, a region-escape shape) —
the tracked recall backlog.
0 commit comments