Incident Dossier

Registry Reset Forgets Half the State

A test fixture resets the registry between tests. After the first test inserts an item, the next test sees a non-empty list and gets an id collision because the counter restarted while the array was not cleared.

Initial failing signallistItems is not empty after resetRegistryExpected behavior: listItems() returns [] after resetRegistry and id restarts at 1 · actual behavior: listItems() returns the previous test's items and id still collides

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
List every piece of state that the registry holds.
Compare that list to what resetRegistry() touches.
Reset every piece of state so the next test starts from a clean slate.

Focus Mode

Start

src/registry.js

Likely area

src/registry.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicReliability

DifficultyEasy

Est. time12 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace