FAILURE MAP

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 ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

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

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-39601

Tree accessibility snapshot consistency audit: Unknown sibling set size is treated as a numeric bound · case 01

Unknown sibling set size is treated as a numeric bound produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39602

Tree accessibility snapshot consistency audit: Unknown sibling set size is treated as a numeric bound · case 02

Unknown sibling set size is treated as a numeric bound produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39603

Tree accessibility snapshot consistency audit: Unknown sibling set size is treated as a numeric bound · case 03

Unknown sibling set size is treated as a numeric bound produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39604

Tree accessibility snapshot consistency audit: Unknown sibling set size is treated as a numeric bound · case 04

Unknown sibling set size is treated as a numeric bound produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39605

Tree accessibility snapshot consistency audit: Unknown sibling set size is treated as a numeric bound · case 05

Unknown sibling set size is treated as a numeric bound produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39606

Tree accessibility snapshot consistency audit: Root parent absence is mistaken for an orphan · case 01

Root parent absence is mistaken for an orphan produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39607

Tree accessibility snapshot consistency audit: Root parent absence is mistaken for an orphan · case 02

Root parent absence is mistaken for an orphan produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39608

Tree accessibility snapshot consistency audit: Root parent absence is mistaken for an orphan · case 03

Root parent absence is mistaken for an orphan produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39609

Tree accessibility snapshot consistency audit: Root parent absence is mistaken for an orphan · case 04

Root parent absence is mistaken for an orphan produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39610

Tree accessibility snapshot consistency audit: Root parent absence is mistaken for an orphan · case 05

Root parent absence is mistaken for an orphan produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39611

Tree accessibility snapshot consistency audit: Parent-child level jump is not validated · case 01

Parent-child level jump is not validated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39612

Tree accessibility snapshot consistency audit: Parent-child level jump is not validated · case 02

Parent-child level jump is not validated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39613

Tree accessibility snapshot consistency audit: Parent-child level jump is not validated · case 03

Parent-child level jump is not validated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39614

Tree accessibility snapshot consistency audit: Parent-child level jump is not validated · case 04

Parent-child level jump is not validated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39615

Tree accessibility snapshot consistency audit: Parent-child level jump is not validated · case 05

Parent-child level jump is not validated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39616

Tree accessibility snapshot consistency audit: Collapsed leaf expansion attribute escapes audit · case 01

Collapsed leaf expansion attribute escapes audit produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39617

Tree accessibility snapshot consistency audit: Collapsed leaf expansion attribute escapes audit · case 02

Collapsed leaf expansion attribute escapes audit produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39618

Tree accessibility snapshot consistency audit: Collapsed leaf expansion attribute escapes audit · case 03

Collapsed leaf expansion attribute escapes audit produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39619

Tree accessibility snapshot consistency audit: Collapsed leaf expansion attribute escapes audit · case 04

Collapsed leaf expansion attribute escapes audit produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39620

Tree accessibility snapshot consistency audit: Collapsed leaf expansion attribute escapes audit · case 05

Collapsed leaf expansion attribute escapes audit produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39621

Tree accessibility snapshot consistency audit: Null active descendant is rejected or stale ID accepted · case 01

Null active descendant is rejected or stale ID accepted produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39622

Tree accessibility snapshot consistency audit: Null active descendant is rejected or stale ID accepted · case 02

Null active descendant is rejected or stale ID accepted produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39623

Tree accessibility snapshot consistency audit: Null active descendant is rejected or stale ID accepted · case 03

Null active descendant is rejected or stale ID accepted produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39624

Tree accessibility snapshot consistency audit: Null active descendant is rejected or stale ID accepted · case 04

Null active descendant is rejected or stale ID accepted produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39625

Tree accessibility snapshot consistency audit: Null active descendant is rejected or stale ID accepted · case 05

Null active descendant is rejected or stale ID accepted produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39626

Tree accessibility snapshot consistency audit: Selection audit misses absent or nonselectable row · case 01

Selection audit misses absent or nonselectable row produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39627

Tree accessibility snapshot consistency audit: Selection audit misses absent or nonselectable row · case 02

Selection audit misses absent or nonselectable row produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39628

Tree accessibility snapshot consistency audit: Selection audit misses absent or nonselectable row · case 03

Selection audit misses absent or nonselectable row produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39629

Tree accessibility snapshot consistency audit: Selection audit misses absent or nonselectable row · case 04

Selection audit misses absent or nonselectable row produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39630

Tree accessibility snapshot consistency audit: Selection audit misses absent or nonselectable row · case 05

Selection audit misses absent or nonselectable row produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39631

Tree accessibility snapshot consistency audit: Busy-leaf contract is skipped or busy branches rejected · case 01

Busy-leaf contract is skipped or busy branches rejected produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39632

Tree accessibility snapshot consistency audit: Busy-leaf contract is skipped or busy branches rejected · case 02

Busy-leaf contract is skipped or busy branches rejected produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39633

Tree accessibility snapshot consistency audit: Busy-leaf contract is skipped or busy branches rejected · case 03

Busy-leaf contract is skipped or busy branches rejected produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39634

Tree accessibility snapshot consistency audit: Busy-leaf contract is skipped or busy branches rejected · case 04

Busy-leaf contract is skipped or busy branches rejected produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39635

Tree accessibility snapshot consistency audit: Busy-leaf contract is skipped or busy branches rejected · case 05

Busy-leaf contract is skipped or busy branches rejected produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39636

Tree accessibility snapshot consistency audit: Root level consistency accepts an indented root · case 01

Root level consistency accepts an indented root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39637

Tree accessibility snapshot consistency audit: Root level consistency accepts an indented root · case 02

Root level consistency accepts an indented root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39638

Tree accessibility snapshot consistency audit: Root level consistency accepts an indented root · case 03

Root level consistency accepts an indented root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39639

Tree accessibility snapshot consistency audit: Root level consistency accepts an indented root · case 04

Root level consistency accepts an indented root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39640

Tree accessibility snapshot consistency audit: Root level consistency accepts an indented root · case 05

Root level consistency accepts an indented root produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39641

Hierarchical sibling sort and stable identity: Sibling sort includes descendants as independent roots · case 01

Sibling sort includes descendants as independent roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39642

Hierarchical sibling sort and stable identity: Sibling sort includes descendants as independent roots · case 02

Sibling sort includes descendants as independent roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39643

Hierarchical sibling sort and stable identity: Sibling sort includes descendants as independent roots · case 03

Sibling sort includes descendants as independent roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39644

Hierarchical sibling sort and stable identity: Sibling sort includes descendants as independent roots · case 04

Sibling sort includes descendants as independent roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39645

Hierarchical sibling sort and stable identity: Sibling sort includes descendants as independent roots · case 05

Sibling sort includes descendants as independent roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39646

Hierarchical sibling sort and stable identity: Unlabelled sibling sorts before labelled siblings · case 01

Unlabelled sibling sorts before labelled siblings produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39647

Hierarchical sibling sort and stable identity: Unlabelled sibling sorts before labelled siblings · case 02

Unlabelled sibling sorts before labelled siblings produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39648

Hierarchical sibling sort and stable identity: Unlabelled sibling sorts before labelled siblings · case 03

Unlabelled sibling sorts before labelled siblings produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39649

Hierarchical sibling sort and stable identity: Unlabelled sibling sorts before labelled siblings · case 04

Unlabelled sibling sorts before labelled siblings produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39650

Hierarchical sibling sort and stable identity: Unlabelled sibling sorts before labelled siblings · case 05

Unlabelled sibling sorts before labelled siblings produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39651

Hierarchical sibling sort and stable identity: Sibling label comparison ignores stipulated casefold equivalence · case 01

Sibling label comparison ignores stipulated casefold equivalence produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39652

Hierarchical sibling sort and stable identity: Sibling label comparison ignores stipulated casefold equivalence · case 02

Sibling label comparison ignores stipulated casefold equivalence produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39653

Hierarchical sibling sort and stable identity: Sibling label comparison ignores stipulated casefold equivalence · case 03

Sibling label comparison ignores stipulated casefold equivalence produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39654

Hierarchical sibling sort and stable identity: Sibling label comparison ignores stipulated casefold equivalence · case 04

Sibling label comparison ignores stipulated casefold equivalence produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39655

Hierarchical sibling sort and stable identity: Sibling label comparison ignores stipulated casefold equivalence · case 05

Sibling label comparison ignores stipulated casefold equivalence produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39656

Hierarchical sibling sort and stable identity: Sort tie break destroys stable order or ignores descending mode · case 01

Sort tie break destroys stable order or ignores descending mode produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39657

Hierarchical sibling sort and stable identity: Sort tie break destroys stable order or ignores descending mode · case 02

Sort tie break destroys stable order or ignores descending mode produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39658

Hierarchical sibling sort and stable identity: Sort tie break destroys stable order or ignores descending mode · case 03

Sort tie break destroys stable order or ignores descending mode produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39659

Hierarchical sibling sort and stable identity: Sort tie break destroys stable order or ignores descending mode · case 04

Sort tie break destroys stable order or ignores descending mode produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39660

Hierarchical sibling sort and stable identity: Sort tie break destroys stable order or ignores descending mode · case 05

Sort tie break destroys stable order or ignores descending mode produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39661

Hierarchical sibling sort and stable identity: Sorting detaches deep descendants from their child subtree · case 01

Sorting detaches deep descendants from their child subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39662

Hierarchical sibling sort and stable identity: Sorting detaches deep descendants from their child subtree · case 02

Sorting detaches deep descendants from their child subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39663

Hierarchical sibling sort and stable identity: Sorting detaches deep descendants from their child subtree · case 03

Sorting detaches deep descendants from their child subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39664

Hierarchical sibling sort and stable identity: Sorting detaches deep descendants from their child subtree · case 04

Sorting detaches deep descendants from their child subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39665

Hierarchical sibling sort and stable identity: Sorting detaches deep descendants from their child subtree · case 05

Sorting detaches deep descendants from their child subtree produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39666

Hierarchical sibling sort and stable identity: Sort replacement closure duplicates descendants or deletes unrelated roots · case 01

Sort replacement closure duplicates descendants or deletes unrelated roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39667

Hierarchical sibling sort and stable identity: Sort replacement closure duplicates descendants or deletes unrelated roots · case 02

Sort replacement closure duplicates descendants or deletes unrelated roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39668

Hierarchical sibling sort and stable identity: Sort replacement closure duplicates descendants or deletes unrelated roots · case 03

Sort replacement closure duplicates descendants or deletes unrelated roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39669

Hierarchical sibling sort and stable identity: Sort replacement closure duplicates descendants or deletes unrelated roots · case 04

Sort replacement closure duplicates descendants or deletes unrelated roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39670

Hierarchical sibling sort and stable identity: Sort replacement closure duplicates descendants or deletes unrelated roots · case 05

Sort replacement closure duplicates descendants or deletes unrelated roots produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39671

Hierarchical sibling sort and stable identity: Sorted subtree is inserted at wrong forest position · case 01

Sorted subtree is inserted at wrong forest position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39672

Hierarchical sibling sort and stable identity: Sorted subtree is inserted at wrong forest position · case 02

Sorted subtree is inserted at wrong forest position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39673

Hierarchical sibling sort and stable identity: Sorted subtree is inserted at wrong forest position · case 03

Sorted subtree is inserted at wrong forest position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39674

Hierarchical sibling sort and stable identity: Sorted subtree is inserted at wrong forest position · case 04

Sorted subtree is inserted at wrong forest position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39675

Hierarchical sibling sort and stable identity: Sorted subtree is inserted at wrong forest position · case 05

Sorted subtree is inserted at wrong forest position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39676

Hierarchical sibling sort and stable identity: Sorted block flattens or reverses internal preorder · case 01

Sorted block flattens or reverses internal preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39677

Hierarchical sibling sort and stable identity: Sorted block flattens or reverses internal preorder · case 02

Sorted block flattens or reverses internal preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39678

Hierarchical sibling sort and stable identity: Sorted block flattens or reverses internal preorder · case 03

Sorted block flattens or reverses internal preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39679

Hierarchical sibling sort and stable identity: Sorted block flattens or reverses internal preorder · case 04

Sorted block flattens or reverses internal preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39680

Hierarchical sibling sort and stable identity: Sorted block flattens or reverses internal preorder · case 05

Sorted block flattens or reverses internal preorder produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39681

Hierarchical sibling sort and stable identity: Sibling position metadata retains pre-sort order · case 01

Sibling position metadata retains pre-sort order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39682

Hierarchical sibling sort and stable identity: Sibling position metadata retains pre-sort order · case 02

Sibling position metadata retains pre-sort order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39683

Hierarchical sibling sort and stable identity: Sibling position metadata retains pre-sort order · case 03

Sibling position metadata retains pre-sort order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39684

Hierarchical sibling sort and stable identity: Sibling position metadata retains pre-sort order · case 04

Sibling position metadata retains pre-sort order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39685

Hierarchical sibling sort and stable identity: Sibling position metadata retains pre-sort order · case 05

Sibling position metadata retains pre-sort order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39686

Hierarchical sibling sort and stable identity: Focus follows pre-sort index instead of row identity · case 01

Focus follows pre-sort index instead of row identity produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39687

Hierarchical sibling sort and stable identity: Focus follows pre-sort index instead of row identity · case 02

Focus follows pre-sort index instead of row identity produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39688

Hierarchical sibling sort and stable identity: Focus follows pre-sort index instead of row identity · case 03

Focus follows pre-sort index instead of row identity produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39689

Hierarchical sibling sort and stable identity: Focus follows pre-sort index instead of row identity · case 04

Focus follows pre-sort index instead of row identity produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39690

Hierarchical sibling sort and stable identity: Focus follows pre-sort index instead of row identity · case 05

Focus follows pre-sort index instead of row identity produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39691

Hierarchical branch command lock: Command lock lookup drops ancestor locks · case 01

Command lock lookup drops ancestor locks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39692

Hierarchical branch command lock: Command lock lookup drops ancestor locks · case 02

Command lock lookup drops ancestor locks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39693

Hierarchical branch command lock: Command lock lookup drops ancestor locks · case 03

Command lock lookup drops ancestor locks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39694

Hierarchical branch command lock: Command lock lookup drops ancestor locks · case 04

Command lock lookup drops ancestor locks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39695

Hierarchical branch command lock: Command lock lookup drops ancestor locks · case 05

Command lock lookup drops ancestor locks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39696

Hierarchical branch command lock: Old completion releases replacement subtree lock · case 01

Old completion releases replacement subtree lock produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-39697

Hierarchical branch command lock: Old completion releases replacement subtree lock · case 02

Old completion releases replacement subtree lock produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39698

Hierarchical branch command lock: Old completion releases replacement subtree lock · case 03

Old completion releases replacement subtree lock produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39699

Hierarchical branch command lock: Old completion releases replacement subtree lock · case 04

Old completion releases replacement subtree lock produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39700

Hierarchical branch command lock: Old completion releases replacement subtree lock · case 05

Old completion releases replacement subtree lock produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗

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 ↗