feat: associate runs with remote pipelines

[Mbeaulne]

Description

• Link each remote pipeline's Runs action to the existing run list, filtered by stable pipeline ID rather than name.
• Include backend-created saved-pipeline runs and editor submissions without automatically restricting history to the current user.
• Link both run viewers back to the current source pipeline. The compact Open pipeline link navigates in the same tab through the app router, without reloading the document. Run Info values share aligned columns.
• Wait for a local or pending pipeline's first upload before submitting a run; failed uploads block submission. Existing remote pipelines still execute the editor snapshot without waiting for autosave.
• Preserve the source association on reruns. Clones have independent IDs and histories.

Related Issue and Pull requests

Stacked directly on #2780. Base branch: mb/batch-remote-pipeline-autosave.

Type of Change

• New feature
• Improvement
• Documentation update

Checklist

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

Screenshots (if applicable)

Desktop and mobile Run Info screenshots were inspected in light and dark modes. Screenshots are generated by the browser tests; none are attached here.

Test Instructions

Prerequisites: VITE_REMOTE_PIPELINES_ENABLED=true, a working backend, and a small runnable test pipeline. Manual submissions execute real runs.

1. Run a remote pipeline, then open its Runs action from My Pipelines. Confirm the new run appears in the ID-filtered history.
2. Open that run and click Open pipeline in Run Info. Confirm the source editor opens in the same tab without a page reload.
3. Rename the source pipeline and verify its existing history remains associated. Clone it with Save as and verify the clone starts with independent history.
4. Rerun an associated run and verify the new run appears in the same pipeline history.
5. Run an existing browser-local pipeline without editing it first. Confirm upload completes before submission and the editor changes to its server-ID URL. A failed initial upload must not submit a run.

Automated verification:

• Complete-stack remote browser suite: 22 tests passed, including source navigation, upload-before-submit, pagination, and catalog-wide name search. Two additional focused browser runs verified equal full-width tables at 1280px and 1920px; a local-only smoke also passed.
• pnpm run test: 2,827 tests passed; three tests could not download their remote JSON schema. pnpm exec vitest run src/components/shared/ComponentEditor/ComponentEditorDialog.test.tsx passed all 11 tests when rerun with network access.
• pnpm run typecheck, pnpm run lint, pnpm run format:check, and pnpm run knip: passed. Targeted lint/format and whitespace checks passed after the width and documentation changes.
• The final merged tree matches the tested implementation. The rollout layer separately passed all 18 browser tests with pnpm test:e2e:remote --reporter=line after the stack update.

Additional Comments

• No backend changes or new dependencies. The existing deployment-level remote-pipelines flag controls availability.
• Source association is run metadata, not a claim that an editor snapshot matches a saved version. Links open the current definition, not a historical version.
• Old unannotated runs are not backfilled or matched by name. Clone ancestry is not tracked. Deleted source pipelines cannot be opened.
• Local-only and connected filesystem/Drive submissions remain unassociated. No live backend writes or staging tests were performed during automated verification.
• The existing narrow-screen dashboard clipping issue is unchanged.

Change Size

Relative to mb/batch-remote-pipeline-autosave for this PR only. Changed lines = additions + deletions.

Category	Files	Added	Removed	Changed
Application code	20	+318	-35	353
Tests	12	+1532	-25	1557
Documentation / configuration	1	+3	-0	3
Total	33	+1853	-60	1913

Application code excludes test files. Tests include unit, component, and browser test source; test-runner configuration, CI, package scripts, compiler configuration, and documentation are counted separately.

[github-actions]

🎩 Preview

A preview build has been created at: mb/associated-pipeline-runs/d8750e3