This looks like the correct place for this, Marcus.

Its placement here seems a bit unintuitive, though. We have this code we want to execute one time, and we're placing it in this code path that only after careful inspection appears to be hit only at startup.

It's not like we have a better option with the way things are, though! This is the first case where the application has needed to know when the asynchronous `navigate` operation is complete. I would recommend extending `App.navigate` to accept an optional second `done` parameter, and invoking it after (and outside of) the `if (currentIndex !== -1)` branch. Then we could modify `App.init` instead:

```diff
- this.navigate({ hash: '#alarm-panel' });
+ this.navigate(
+   { hash: '#alam-panel' },
+   PerformanceTestingHelper.dispatch.bind(PerformanceTestingHelper, 'statup-path-done')
+ );
  return this;
```

which much more clearly conveys the intention.

You could argue that is outside the scope of this bug. If you feel that way, could you create a ticket, "Implement `done` callback for App.navigate" and assign it to me?