OCT-1396: Implement an onscreen route back to onboarding if users accidentally close it

[jmikolajczyk]

Description

Definition of Done

1. Acceptance criteria are met.
2. PR is manually tested before the merge by developer(s).
   • Happy path is manually checked.
3. PR is manually tested by QA when their assistance is required (1).
   • Octant Areas & Test Cases are checked for impact and updated if required (2).
4. Unit tests are added unless there is a reason to omit them.
5. Automated tests are added when required.
6. The code is merged.
7. Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files).
   • BE: Swagger documentation is updated.
8. When required by QA:
   • Deployed to the relevant environment.
   • Passed system tests.

---

(1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required.

(2) Octant Areas & Test Cases.

[aziolek]

Starting from around ~460px OnboardingStepper shows up over the navbar. It shouldn't be under it, but still accessible and not in a way of navigation. If designs do not cover this scenario please coordinate with Matt on the best way of solving this problem.

[jmikolajczyk]

Starting from around ~460px OnboardingStepper shows up over the navbar. It shouldn't be under it, but still accessible and not in a way of navigation. If designs do not cover this scenario please coordinate with Matt on the best way of solving this problem.

@aziolek done

[aziolek]

https://linear.app/golemfoundation/issue/OCT-1396/implement-an-onscreen-route-back-to-onboarding-if-users-accidentally#comment-6c2f3cf0

[jmikolajczyk]

/deploy

[jmikolajczyk]

/deploy

[jmikolajczyk]

/deploy