Dependent steps - should they be accessible without their dependencies?

### Question

Should a user be able to explore steps beyond unconfirmed steps?

### Pro

Users get to explore the app.

**Comment:** the same could be achieved by visiting the docs, where we could consider adding a gallery.

### Con

If changes are made in a step beyond an unconfirmed step, the confirmation of the earlier step will reset those changes. This is (for now) intended behavior, but it may be confusing for first-time explorers.

**Comment:** resetting on confirmation change is potentially harsh, but the alternative may require significant development.

### Possible solution

Replace step content with a warning if dependencies aren't met.


### Comments

1. The above will also happen if one confirms a step, then goes back and makes changes. Subsequent steps will revert to the warning
2. This does not actually prevent exploration. It simply limits it to the way the app is meant to be used. So there's a self-documenting value to this solution. Users learn how to use the app by making "mistakes"