Spec Kitty

Mission Run: Sleep-count assertions survive concurrent sleepers

Make the tracker retry tests assert on their own sleeps, not on every thread's

Two or more tests in the tracker cone fail intermittently on CI with absurd sleep counts (71 instead of 3; 556 instead of 1). The cause is not a flaky test or a bad retry implementation: the patch target resolves to the shared standard-library timer, so the recorder counts every pause taken anywhere in the worker process, by any concurrent activity, for as long as the patch is open. The victim is simply whichever count assertion happens to be open at the time, which is why the failing test name changes between runs. This mission makes those assertions observe only the code under test, so the checks become trustworthy in both directions rather than merely quieter.