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
Autocomplete query activation policy: empty-query browse incorrectly requests typed-query results · case 01
The recent completion transition produces an incorrect observable state.
Autocomplete query activation policy: empty-query browse incorrectly requests typed-query results · case 02
The recent completion transition produces an incorrect observable state.
Autocomplete query activation policy: empty-query browse incorrectly requests typed-query results · case 03
The recent completion transition produces an incorrect observable state.
Autocomplete query activation policy: empty-query browse incorrectly requests typed-query results · case 04
The recent completion transition produces an incorrect observable state.
Autocomplete query activation policy: empty-query browse incorrectly requests typed-query results · case 05
The recent completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse activation under composition discards the pending browse intent · case 01
The deferred-browse completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse activation under composition discards the pending browse intent · case 02
The deferred-browse completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse activation under composition discards the pending browse intent · case 03
The deferred-browse completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse activation under composition discards the pending browse intent · case 04
The deferred-browse completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse activation under composition discards the pending browse intent · case 05
The deferred-browse completion transition produces an incorrect observable state.
Autocomplete query activation policy: disabled picker initiates new suggestion searches · case 01
The disabled completion transition produces an incorrect observable state.
Autocomplete query activation policy: disabled picker initiates new suggestion searches · case 02
The disabled completion transition produces an incorrect observable state.
Autocomplete query activation policy: disabled picker initiates new suggestion searches · case 03
The disabled completion transition produces an incorrect observable state.
Autocomplete query activation policy: disabled picker initiates new suggestion searches · case 04
The disabled completion transition produces an incorrect observable state.
Autocomplete query activation policy: disabled picker initiates new suggestion searches · case 05
The disabled completion transition produces an incorrect observable state.
Autocomplete query activation policy: read-only completion launches editable search requests · case 01
The readonly completion transition produces an incorrect observable state.
Autocomplete query activation policy: read-only completion launches editable search requests · case 02
The readonly completion transition produces an incorrect observable state.
Autocomplete query activation policy: read-only completion launches editable search requests · case 03
The readonly completion transition produces an incorrect observable state.
Autocomplete query activation policy: read-only completion launches editable search requests · case 04
The readonly completion transition produces an incorrect observable state.
Autocomplete query activation policy: read-only completion launches editable search requests · case 05
The readonly completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query leaves the previous completion timer armed · case 01
The erase-pending completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query leaves the previous completion timer armed · case 02
The erase-pending completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query leaves the previous completion timer armed · case 03
The erase-pending completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query leaves the previous completion timer armed · case 04
The erase-pending completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query leaves the previous completion timer armed · case 05
The erase-pending completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query retains results tied to the prior fragment · case 01
The erase-results completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query retains results tied to the prior fragment · case 02
The erase-results completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query retains results tied to the prior fragment · case 03
The erase-results completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query retains results tied to the prior fragment · case 04
The erase-results completion transition produces an incorrect observable state.
Autocomplete query activation policy: erasing query retains results tied to the prior fragment · case 05
The erase-results completion transition produces an incorrect observable state.
Autocomplete query activation policy: zero-character browse uses the minimum-length prompt instead of recent choices · case 01
The empty-query-mode completion transition produces an incorrect observable state.
Autocomplete query activation policy: zero-character browse uses the minimum-length prompt instead of recent choices · case 02
The empty-query-mode completion transition produces an incorrect observable state.
Autocomplete query activation policy: zero-character browse uses the minimum-length prompt instead of recent choices · case 03
The empty-query-mode completion transition produces an incorrect observable state.
Autocomplete query activation policy: zero-character browse uses the minimum-length prompt instead of recent choices · case 04
The empty-query-mode completion transition produces an incorrect observable state.
Autocomplete query activation policy: zero-character browse uses the minimum-length prompt instead of recent choices · case 05
The empty-query-mode completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse request is indistinguishable from an ordinary typed search · case 01
The browse-descriptor completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse request is indistinguishable from an ordinary typed search · case 02
The browse-descriptor completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse request is indistinguishable from an ordinary typed search · case 03
The browse-descriptor completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse request is indistinguishable from an ordinary typed search · case 04
The browse-descriptor completion transition produces an incorrect observable state.
Autocomplete query activation policy: browse request is indistinguishable from an ordinary typed search · case 05
The browse-descriptor completion transition produces an incorrect observable state.
Locking an active autocomplete: locking a picker clears its committed identity · case 01
The retain-value completion transition produces an incorrect observable state.
Locking an active autocomplete: locking a picker clears its committed identity · case 02
The retain-value completion transition produces an incorrect observable state.
Locking an active autocomplete: locking a picker clears its committed identity · case 03
The retain-value completion transition produces an incorrect observable state.
Locking an active autocomplete: locking a picker clears its committed identity · case 04
The retain-value completion transition produces an incorrect observable state.
Locking an active autocomplete: locking a picker clears its committed identity · case 05
The retain-value completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only display uses unfinished search text · case 01
The retain-label completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only display uses unfinished search text · case 02
The retain-label completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only display uses unfinished search text · case 03
The retain-label completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only display uses unfinished search text · case 04
The retain-label completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only display uses unfinished search text · case 05
The retain-label completion transition produces an incorrect observable state.
Locking an active autocomplete: locked picker keeps an editable suggestion query pending · case 01
The query-cancel completion transition produces an incorrect observable state.
Locking an active autocomplete: locked picker keeps an editable suggestion query pending · case 02
The query-cancel completion transition produces an incorrect observable state.
Locking an active autocomplete: locked picker keeps an editable suggestion query pending · case 03
The query-cancel completion transition produces an incorrect observable state.
Locking an active autocomplete: locked picker keeps an editable suggestion query pending · case 04
The query-cancel completion transition produces an incorrect observable state.
Locking an active autocomplete: locked picker keeps an editable suggestion query pending · case 05
The query-cancel completion transition produces an incorrect observable state.
Locking an active autocomplete: late create completion can still mutate a locked picker · case 01
The create-detach completion transition produces an incorrect observable state.
Locking an active autocomplete: late create completion can still mutate a locked picker · case 02
The create-detach completion transition produces an incorrect observable state.
Locking an active autocomplete: late create completion can still mutate a locked picker · case 03
The create-detach completion transition produces an incorrect observable state.
Locking an active autocomplete: late create completion can still mutate a locked picker · case 04
The create-detach completion transition produces an incorrect observable state.
Locking an active autocomplete: late create completion can still mutate a locked picker · case 05
The create-detach completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only selected-label rendering exposes the highlighted suggestion identifier · case 01
The selected-row completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only selected-label rendering exposes the highlighted suggestion identifier · case 02
The selected-row completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only selected-label rendering exposes the highlighted suggestion identifier · case 03
The selected-row completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only selected-label rendering exposes the highlighted suggestion identifier · case 04
The selected-row completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only selected-label rendering exposes the highlighted suggestion identifier · case 05
The selected-row completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only copy includes an unaccepted completion suffix · case 01
The copy-selected-label completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only copy includes an unaccepted completion suffix · case 02
The copy-selected-label completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only copy includes an unaccepted completion suffix · case 03
The copy-selected-label completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only copy includes an unaccepted completion suffix · case 04
The copy-selected-label completion transition produces an incorrect observable state.
Locking an active autocomplete: read-only copy includes an unaccepted completion suffix · case 05
The copy-selected-label completion transition produces an incorrect observable state.
Locking an active autocomplete: locking leaks an unpersisted create draft into the read-only selection display · case 01
The create-display completion transition produces an incorrect observable state.
Locking an active autocomplete: locking leaks an unpersisted create draft into the read-only selection display · case 02
The create-display completion transition produces an incorrect observable state.
Locking an active autocomplete: locking leaks an unpersisted create draft into the read-only selection display · case 03
The create-display completion transition produces an incorrect observable state.
Locking an active autocomplete: locking leaks an unpersisted create draft into the read-only selection display · case 04
The create-display completion transition produces an incorrect observable state.
Locking an active autocomplete: locking leaks an unpersisted create draft into the read-only selection display · case 05
The create-display completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock replays a suggestion acceptance captured before locking · case 01
The deferred-drop completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock replays a suggestion acceptance captured before locking · case 02
The deferred-drop completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock replays a suggestion acceptance captured before locking · case 03
The deferred-drop completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock replays a suggestion acceptance captured before locking · case 04
The deferred-drop completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock replays a suggestion acceptance captured before locking · case 05
The deferred-drop completion transition produces an incorrect observable state.
Locking an active autocomplete: a locked suggestion can still change the selected identifier · case 01
The allow-accept completion transition produces an incorrect observable state.
Locking an active autocomplete: a locked suggestion can still change the selected identifier · case 02
The allow-accept completion transition produces an incorrect observable state.
Locking an active autocomplete: a locked suggestion can still change the selected identifier · case 03
The allow-accept completion transition produces an incorrect observable state.
Locking an active autocomplete: a locked suggestion can still change the selected identifier · case 04
The allow-accept completion transition produces an incorrect observable state.
Locking an active autocomplete: a locked suggestion can still change the selected identifier · case 05
The allow-accept completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock resurrects an abandoned search instead of selected display · case 01
The unlock-draft completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock resurrects an abandoned search instead of selected display · case 02
The unlock-draft completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock resurrects an abandoned search instead of selected display · case 03
The unlock-draft completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock resurrects an abandoned search instead of selected display · case 04
The unlock-draft completion transition produces an incorrect observable state.
Locking an active autocomplete: unlock resurrects an abandoned search instead of selected display · case 05
The unlock-draft completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: suggestion lookup sends case-sensitive padded display text · case 01
The lookup completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: suggestion lookup sends case-sensitive padded display text · case 02
The lookup completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: suggestion lookup sends case-sensitive padded display text · case 03
The lookup completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: suggestion lookup sends case-sensitive padded display text · case 04
The lookup completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: suggestion lookup sends case-sensitive padded display text · case 05
The lookup completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: query normalization visibly rewrites user-entered text · case 01
The display completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: query normalization visibly rewrites user-entered text · case 02
The display completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: query normalization visibly rewrites user-entered text · case 03
The display completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: query normalization visibly rewrites user-entered text · case 04
The display completion transition produces an incorrect observable state.
Search normalization versus displayed autocomplete text: query normalization visibly rewrites user-entered text · case 05
The display completion transition produces an incorrect observable state.
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 ↗