- Shipped
- September 23, 2026 at 1:21 PM UTC
- Author
- Kamo
- Commit
- 3a2f95e
Saving or skipping Compliance, the ninth and last Getting Started step, left it on "Loading..." with "Save & continue" greyed out, under the banner saying the organization was set up. The save itself had gone through. Each step seeds its value once, when its own fetches first finish. After a save the shell clears the value and moves on, but the last step has nowhere to go (`nextStepKey` is null), so it stayed on Compliance without remounting it. The seed effect never ran again. Clicking the rail entry for the step you were already on did the same thing to any step. The step body is now keyed on a counter that goes up every time the shell clears the value. The step remounts, fetches again, and shows what was just saved. Tested through the real shell and the real Compliance step with the reporting org's own applied-model and org responses: 3 of 4 cases fail without the change and all 4 pass with it.