Understand the failure.
Verify the repair.
Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.
Explore the cases ↓How results are verified ↗WHAT THE ARCHIVE CONTAINS
100840 executable cases. 20168 are open.
Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.
The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗
A RECORD OF WHAT WENT WRONG
Browse the archive / 100840
Subtree deletion state cleanup: Expansion records outlive removed branch IDs · case 01
Expansion records outlive removed branch IDs produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Expansion records outlive removed branch IDs · case 02
Expansion records outlive removed branch IDs produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Expansion records outlive removed branch IDs · case 03
Expansion records outlive removed branch IDs produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Expansion records outlive removed branch IDs · case 04
Expansion records outlive removed branch IDs produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Expansion records outlive removed branch IDs · case 05
Expansion records outlive removed branch IDs produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Removed subtree requests are not cancelled selectively · case 01
Removed subtree requests are not cancelled selectively produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Removed subtree requests are not cancelled selectively · case 02
Removed subtree requests are not cancelled selectively produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Removed subtree requests are not cancelled selectively · case 03
Removed subtree requests are not cancelled selectively produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Removed subtree requests are not cancelled selectively · case 04
Removed subtree requests are not cancelled selectively produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Removed subtree requests are not cancelled selectively · case 05
Removed subtree requests are not cancelled selectively produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Focus recovery chooses removed or distant next sibling · case 01
Focus recovery chooses removed or distant next sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Focus recovery chooses removed or distant next sibling · case 02
Focus recovery chooses removed or distant next sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Focus recovery chooses removed or distant next sibling · case 03
Focus recovery chooses removed or distant next sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Focus recovery chooses removed or distant next sibling · case 04
Focus recovery chooses removed or distant next sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Focus recovery chooses removed or distant next sibling · case 05
Focus recovery chooses removed or distant next sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Previous sibling recovery chooses farthest sibling · case 01
Previous sibling recovery chooses farthest sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Previous sibling recovery chooses farthest sibling · case 02
Previous sibling recovery chooses farthest sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Previous sibling recovery chooses farthest sibling · case 03
Previous sibling recovery chooses farthest sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Previous sibling recovery chooses farthest sibling · case 04
Previous sibling recovery chooses farthest sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Previous sibling recovery chooses farthest sibling · case 05
Previous sibling recovery chooses farthest sibling produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion fallback priority skips surviving parent · case 01
Deletion fallback priority skips surviving parent produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion fallback priority skips surviving parent · case 02
Deletion fallback priority skips surviving parent produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion fallback priority skips surviving parent · case 03
Deletion fallback priority skips surviving parent produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion fallback priority skips surviving parent · case 04
Deletion fallback priority skips surviving parent produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion fallback priority skips surviving parent · case 05
Deletion fallback priority skips surviving parent produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion steals unaffected focus or strands removed focus · case 01
Deletion steals unaffected focus or strands removed focus produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion steals unaffected focus or strands removed focus · case 02
Deletion steals unaffected focus or strands removed focus produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion steals unaffected focus or strands removed focus · case 03
Deletion steals unaffected focus or strands removed focus produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion steals unaffected focus or strands removed focus · case 04
Deletion steals unaffected focus or strands removed focus produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Deletion steals unaffected focus or strands removed focus · case 05
Deletion steals unaffected focus or strands removed focus produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Range anchor cleanup crosses subtree boundary · case 01
Range anchor cleanup crosses subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Range anchor cleanup crosses subtree boundary · case 02
Range anchor cleanup crosses subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Range anchor cleanup crosses subtree boundary · case 03
Range anchor cleanup crosses subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Range anchor cleanup crosses subtree boundary · case 04
Range anchor cleanup crosses subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Range anchor cleanup crosses subtree boundary · case 05
Range anchor cleanup crosses subtree boundary produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Inline edit remains bound to removed row · case 01
Inline edit remains bound to removed row produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Inline edit remains bound to removed row · case 02
Inline edit remains bound to removed row produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Inline edit remains bound to removed row · case 03
Inline edit remains bound to removed row produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Inline edit remains bound to removed row · case 04
Inline edit remains bound to removed row produces the wrong hierarchical widget state in a regression fixture.
Subtree deletion state cleanup: Inline edit remains bound to removed row · case 05
Inline edit remains bound to removed row produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop validation permits descendant cycles or protected parents · case 01
Drop validation permits descendant cycles or protected parents produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop validation permits descendant cycles or protected parents · case 02
Drop validation permits descendant cycles or protected parents produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop validation permits descendant cycles or protected parents · case 03
Drop validation permits descendant cycles or protected parents produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop validation permits descendant cycles or protected parents · case 04
Drop validation permits descendant cycles or protected parents produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop validation permits descendant cycles or protected parents · case 05
Drop validation permits descendant cycles or protected parents produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Moved root retains its old accessible parent · case 01
Moved root retains its old accessible parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Moved root retains its old accessible parent · case 02
Moved root retains its old accessible parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Moved root retains its old accessible parent · case 03
Moved root retains its old accessible parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Moved root retains its old accessible parent · case 04
Moved root retains its old accessible parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Moved root retains its old accessible parent · case 05
Moved root retains its old accessible parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent depth shift uses absolute depth · case 01
Reparent depth shift uses absolute depth produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent depth shift uses absolute depth · case 02
Reparent depth shift uses absolute depth produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent depth shift uses absolute depth · case 03
Reparent depth shift uses absolute depth produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent depth shift uses absolute depth · case 04
Reparent depth shift uses absolute depth produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent depth shift uses absolute depth · case 05
Reparent depth shift uses absolute depth produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Depth shift misses descendants or changes unrelated rows · case 01
Depth shift misses descendants or changes unrelated rows produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Depth shift misses descendants or changes unrelated rows · case 02
Depth shift misses descendants or changes unrelated rows produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Depth shift misses descendants or changes unrelated rows · case 03
Depth shift misses descendants or changes unrelated rows produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Depth shift misses descendants or changes unrelated rows · case 04
Depth shift misses descendants or changes unrelated rows produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Depth shift misses descendants or changes unrelated rows · case 05
Depth shift misses descendants or changes unrelated rows produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Old sibling list keeps moved root or mutates rejected drop · case 01
Old sibling list keeps moved root or mutates rejected drop produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Old sibling list keeps moved root or mutates rejected drop · case 02
Old sibling list keeps moved root or mutates rejected drop produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Old sibling list keeps moved root or mutates rejected drop · case 03
Old sibling list keeps moved root or mutates rejected drop produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Old sibling list keeps moved root or mutates rejected drop · case 04
Old sibling list keeps moved root or mutates rejected drop produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Old sibling list keeps moved root or mutates rejected drop · case 05
Old sibling list keeps moved root or mutates rejected drop produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop insertion ignores requested sibling position · case 01
Drop insertion ignores requested sibling position produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop insertion ignores requested sibling position · case 02
Drop insertion ignores requested sibling position produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop insertion ignores requested sibling position · case 03
Drop insertion ignores requested sibling position produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop insertion ignores requested sibling position · case 04
Drop insertion ignores requested sibling position produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Drop insertion ignores requested sibling position · case 05
Drop insertion ignores requested sibling position produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Sibling metadata invalidation omits old or rejected parent · case 01
Sibling metadata invalidation omits old or rejected parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Sibling metadata invalidation omits old or rejected parent · case 02
Sibling metadata invalidation omits old or rejected parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Sibling metadata invalidation omits old or rejected parent · case 03
Sibling metadata invalidation omits old or rejected parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Sibling metadata invalidation omits old or rejected parent · case 04
Sibling metadata invalidation omits old or rejected parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Sibling metadata invalidation omits old or rejected parent · case 05
Sibling metadata invalidation omits old or rejected parent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent version invalidation touches unrelated branches · case 01
Reparent version invalidation touches unrelated branches produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent version invalidation touches unrelated branches · case 02
Reparent version invalidation touches unrelated branches produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent version invalidation touches unrelated branches · case 03
Reparent version invalidation touches unrelated branches produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent version invalidation touches unrelated branches · case 04
Reparent version invalidation touches unrelated branches produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent version invalidation touches unrelated branches · case 05
Reparent version invalidation touches unrelated branches produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Stable focused descendant is replaced during reparent · case 01
Stable focused descendant is replaced during reparent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Stable focused descendant is replaced during reparent · case 02
Stable focused descendant is replaced during reparent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Stable focused descendant is replaced during reparent · case 03
Stable focused descendant is replaced during reparent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Stable focused descendant is replaced during reparent · case 04
Stable focused descendant is replaced during reparent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Stable focused descendant is replaced during reparent · case 05
Stable focused descendant is replaced during reparent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent reveal option ignores expansion intent · case 01
Reparent reveal option ignores expansion intent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent reveal option ignores expansion intent · case 02
Reparent reveal option ignores expansion intent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent reveal option ignores expansion intent · case 03
Reparent reveal option ignores expansion intent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent reveal option ignores expansion intent · case 04
Reparent reveal option ignores expansion intent produces the wrong hierarchical widget state in a regression fixture.
Accessible subtree reparent transaction: Reparent reveal option ignores expansion intent · case 05
Reparent reveal option ignores expansion intent produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: Descendant drop incorrectly escapes self-drop check · case 01
Descendant drop incorrectly escapes self-drop check produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: Descendant drop incorrectly escapes self-drop check · case 02
Descendant drop incorrectly escapes self-drop check produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: Descendant drop incorrectly escapes self-drop check · case 03
Descendant drop incorrectly escapes self-drop check produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: Descendant drop incorrectly escapes self-drop check · case 04
Descendant drop incorrectly escapes self-drop check produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: Descendant drop incorrectly escapes self-drop check · case 05
Descendant drop incorrectly escapes self-drop check produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: After placement is confused with nesting · case 01
After placement is confused with nesting produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: After placement is confused with nesting · case 02
After placement is confused with nesting produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: After placement is confused with nesting · case 03
After placement is confused with nesting produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: After placement is confused with nesting · case 04
After placement is confused with nesting produces the wrong hierarchical widget state in a regression fixture.
Tree drop accessibility descriptor: After placement is confused with nesting · case 05
After placement is confused with nesting produces the wrong hierarchical widget state in a regression fixture.
INSPECTABLE BY DESIGN
Every result has a runnable source.
Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.
Read the methodology ↗