Task: Extract the application shell user journeys

Every journey a person had in ores.qt application shell is documented as a user journey, and every action its legacy Qt screens offered is covered by a journey or recorded as dropped. Order 13 of 13.

• Every item of the User Journey Extraction Standard passes, with its evidence recorded below.
• Every Qt action has a disposition: kept, changed or dropped.
• Every defect found is captured, and every recurring gap is recorded.

Work the User Journey Extraction Standard in its section order and record each item below.

1. Inventory (I01 to I05).
2. Legacy Qt screens (Q01 to Q05).
3. Vocabulary and screen rules (V01 to V03).
4. Journeys (J01 to J08), ending with the catalogue agreed.
5. Documents (D01 to D05).
6. Verification and gaps (X01 to X05).

• Legacy screens: ores.qt/application at /home/marco/Development/OreStudio/ores.qt, or git show af67db3062^:projects/ores.qt/.... Survey on 2026-09-23: 2 .ui files and 22 headers declaring a window, dialog, wizard, widget, view, panel or page.
• Starts after the component stories for the journeys it composes.
• Not a component of its own: the Qt main window, sign-in, navigation, notifications and settings. The entry and setup journeys exist already. This task covers what remains of the shell and how a person moves between journeys, and runs last because it composes the others.
• Read api alongside it: the shared widgets carry behaviour every screen had.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.