feat: Guided Tours Foundation

[camielvs]

Description

The reactour-based guided tour engine, wired into the dashboard's /learn/tours hub and the v2 editor. Foundation only — the tour registry ships empty, so no tour can run yet. Subsequent PRs in the stack add interaction primitives (#2299), a custom navigation UI (#2340), ephemeral pipelines (#2334), an end-screen (#2339), and the first two registered tours (#2306, #2312).

While the registry is empty, every tour card on the Learning Hub says "Coming soon" and the framework merge is invisible to users.

Architecture

Route (src/routes/Dashboard/Learn/Tour.tsx)

• /tour/$tourId — refreshable, shareable, owns its own lifecycle.
• Resolves the tourId against the registry; redirects to /learn/tours if unknown.
• Renders <TourModeProvider> + <EditorV2> from the first frame; the editor body shows a skeleton while the tour pipeline resolves, so the menu bar stays mounted (no flicker on entry).
• Snapshots the editor's window layout on entry, restores it on exit so the user's saved arrangement isn't disturbed.
• Bridges ?step=N ↔ reactour's currentStep so browser back/forward navigates steps.

Reactour wrapper (src/providers/TourProvider/TourProvider.tsx)

• Tours are modal: showCloseButton={false}, onClickMask={() => undefined}, disableKeyboardNavigation={["esc"]}. The only exits are the explicit Exit Tour button or the Done button on the final step.
• Custom prev/next rendering via renderNextButton; popover viewport clamping via PopoverClampBridge keeps the step-number badge from being clipped near screen edges.

Tour-mode context (src/providers/TourProvider/TourModeContext.tsx)

• useTourMode() exposes { tour, tempPipelineName } to editor components.
• EditorMenuBar reads this to render a Tour badge next to the pipeline name and the central Exit Tour button; destructive file-menu actions (rename / delete) are hidden in tour mode.
• EditorV2Content reads it too: when pipelineRef is null and we're in tour mode, it shows PipelineEditorSkeleton instead of EmptyEditorState.

Editor bridge stub (src/routes/v2/pages/Editor/components/EditorTourBridge.tsx)

• Empty placeholder component; feat: Guided Tours Framework (Navigating the Editor) #2299 fills in the actual interaction handlers. It exists in this PR so EditorV2.tsx can import it.

Layout snapshot (src/routes/v2/shared/windows/windowPersistence.ts)

• snapshotLayout / restoreLayout stash the editor's persisted window arrangement so a tour can mutate it freely and roll back on exit.

Registry types (src/components/Learn/tours/registry.ts)

• TourDefinition + TourStep (extends reactour's StepType). Empty tours: TourDefinition[] = [] array — tours register themselves in their own PRs.

How tours get added

1. Author src/components/Learn/tours/<yourTour>.tour.json matching TourDefinition.
2. Import + push into the tours array in registry.ts.
3. Use stable data-* anchors on the UI elements your steps target. Already available:
   • data-tour="..." — panels and bars
   • data-dock-area, data-dock-window, data-dock-window-content, data-window-id — dock/window system
   • data-tour-anchor="no-spotlight" — center a popover with no highlight

Related Issue and Pull requests

Progresses https://github.com/Shopify/oasis-frontend/issues/583

Type of Change

• New feature

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Test Instructions

The framework is invisible to users until a tour registers, so the only thing to verify is no-regression:

• /learn/tours and the dashboard Featured Tours tile render every tour card as "Coming soon".
• Direct navigation to /tour/anything redirects to /learn/tours.
• Pipelines list, editor menu bar, dockable / floating windows, and task nodes behave identically to master.
• The Window Layout snapshot/restore round-trips cleanly: pre-tour arrangement persists across an entry/exit cycle.

Additional Comments

The remainder of the stack lands the interaction primitives and the first two tours. Once #2306 and #2312 are merged, the Learning Hub has actual tours to walk through.

[github-actions]

🎩 Preview

A preview build has been created at: 06-02-feat_guided_tours_foundation/694e182

[camielvs]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat: Guided Tour - Navigating the Editor #2306 : 2 dependent PRs (#2307 , #2347 )
• feat: Guided Tours Framework (Navigating the Editor) #2299
• feat: Guided Tours End Screen #2339
• feat: Guided Tours Ephemeral Pipelines #2334
• feat: Guided Tours Custom Navigation #2340
• feat: Guided Tours Foundation #2348 👈 (View in Graphite)
• feat: Learning Hub Guided Tours #2297
• feat: Learning Hub - Milestone 1 #2341
• feat: Learning Hub Tip of the Day #2292
• feat: Learning Hub Tip Browser #2291
• feat: Learning Hub Example Pipelines #2283
• feat: Learning Hub Documentation & FAQ #2282
• feat: Learning Hub Dashboard #2281
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.