feat(Designer): Direct standalone initialization

[rllyy97]

Commit Type

• [x] feature - New functionality

Risk Level

• [x] Low - Minor changes, limited scope
• [ ] Medium - Moderate changes, some user impact
• [ ] High - Major changes, significant user/system impact

What & Why

Can now load standalone designer from url search params.

• plan - Standard / Consumption
• id - Remote workflow id
• runId - Remote workflow run id
• localId - Local workflow id
• localRunId - Local workflow run id

The intention of this is to speed up workflow initialization during our automated testing to avoid waiting on all LA / workflow resources to load before the proper workflow can be selected.

Impact of Change

• Users: N/A
• Developers: Faster PR integration due to decreased E2E test durations
• System: Decreased E2E test suite durations

Test Plan

• [ ] Unit tests added/updated
• [x] E2E tests added/updated
• [x] Manual testing completed
• [ ] Tested in:

Contributors

@rllyy97

Screenshots/Videos

N/A

[github-actions[bot]]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: feat(Designer): Direct standalone initialization
• Issue: Title accurately summarizes the PR. It is clear, scoped, and descriptive.
• Recommendation: No changes needed. Good job being explicit and concise!

---

✅ Commit Type

• Properly selected (feature)
• Only one selected, which is correct.

---

✅ Risk Level

• Risk level marked as Low and matches the code change and risk label.

---

✅ What & Why

• Current:

  Can now load standalone designer from url search params.

  • plan - Standard / Consumption
  • id - Remote workflow id
  • runId - Remote workflow run id
  • localId - Local workflow id
  • localRunId - Local workflow run id The intention of this is to speed up workflow initialization during our automated testing to avoid waiting on all LA / workflow resources to load before the proper workflow can be selected.

• Issue: Well written, clear explanation of what is being changed and why.
• Recommendation: No changes needed. Good context and brevity.

---

✅ Impact of Change

• Clearly scoped:
  • Users: N/A
  • Developers: Faster PR integration due to decreased E2E test durations
  • System: Decreased E2E test suite durations
• Recommendation: No change needed.

---

✅ Test Plan

• E2E tests and manual testing confirmed. Unit and environment specific testing not checked, which is fine for current context.

---

⚠️ Contributors

• Only self-tagged. To strengthen this section, consider acknowledging PMs or designers if relevant, especially if contributed feedback.

---

✅ Screenshots/Videos

• Marked N/A and appropriate for non-visual change.

---

Summary Table

Section	Status	Recommendation
Title	✅	None
Commit Type	✅	None
Risk Level	✅	None
What & Why	✅	None
Impact of Change	✅	None
Test Plan	✅	None
Contributors	⚠️	Nudge to mention others if relevant
Screenshots/Videos	✅	None

---

PR passes all required checks and matches the assigned risk level. If you worked with other contributors, consider tagging them for visibility and recognition. Well done! 🎉

---

Last updated: Thu, 06 Nov 2025 19:30:53 GMT