fix(vscode): Temporarily remove validatePartial, startRuntimeApi to mitigate designer issues

[andrew-eldridge]

Cherry-pick of the following PR #8350
Fixes #8354, #8355

temporarily remove validatePartial, startRuntimeApi on open designer as mitigation

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

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

What & Why

Cherry-pick designer issue mitigations to hotfix branch

Impact of Change

• Users: Mitigation for issues blocking opening designer and launching debugger
• Developers: N/A
• System: N/A

Test Plan

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

Contributors

@andrew-eldridge

[github-actions]

🤖 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: fix(vscode): Temporarily remove validatePartial, startRuntimeApi to mitigate designer issues
• Issue: Title is clear, scoped, and expresses what is being changed and why
• Recommendation: No changes needed

---

✅ Commit Type

• Properly selected (fix)
• Only one selected, which is correct

---

✅ Risk Level

• Risk level marked as "Medium" in both body and label, matches the impact of code (removes validation/runtime features temporarily for mitigation)

---

✅ What & Why

• Current: Cherry-pick designer issue mitigations to hotfix branch
• Issue: Concise and relevant
• Recommendation: Optionally specify affected designer flows, but the summary is sufficient

---

✅ Impact of Change

• User impact: Mitigates issues blocking designer and debugger launch
• Developers impact: Marked N/A (acceptable)
• System impact: Marked N/A (acceptable)
• Recommendation: No required edits. For best practice, briefly mention which designer scenarios could fail or behave differently, e.g., validation omitted temporarily, runtime behavior affected.

---

✅ Test Plan

• Manual testing completed; Unit/E2E not applicable for hotfix mitigation

---

⚠️ Contributors

• Only @andrew-eldridge listed
• Recommendation: Consider tagging any PMs, Designers, or reviewers who contributed to the solution or original idea.

---

✅ Screenshots/Videos

• Not needed, none included—no clear evidence it is a visual-only change

---

Summary Table

Section	Status	Recommendation
Title	✅
Commit Type	✅
Risk Level	✅
What & Why	✅	Optionally specify exact designer impacts
Impact of Change	✅	Optionally clarify affected scenarios
Test Plan	✅
Contributors	⚠️	Optional: credit more contributors if applicable
Screenshots/Videos	✅

---

PR passes all required sections. Please optionally enhance contributor acknowledgement and consider specifying exact scenarios impacted if you want to improve traceability. Thank you for helping maintain high-quality documentation for your team!

---

Last updated: Thu, 09 Oct 2025 21:25:56 GMT