[devin-ai-integration]

fix: Revert widget import paths to void-editor-widgets-tsx (deployment fix)

Summary

The previous rebranding PR (#16) renamed void-editor-widgets-tsx to orcide-widgets-tsx in 3 import/config paths. However, the actual build output directory is still void-editor-widgets-tsx — the tsup build produces output at react/out/void-editor-widgets-tsx/, so the renamed imports caused the build to fail with:

Cannot find module './react/out/orcide-widgets-tsx/index.js'

This PR reverts the 3 path references back to their original working values:

• tsup.config.js entry point: ./src2/orcide-widgets-tsx/ → ./src2/void-editor-widgets-tsx/
• voidCommandBarService.ts import: ./react/out/orcide-widgets-tsx/ → ./react/out/void-editor-widgets-tsx/
• voidSelectionHelperWidget.ts import: ./react/out/orcide-widgets-tsx/ → ./react/out/void-editor-widgets-tsx/

Review & Testing Checklist for Human

• Verify that Render deployment succeeds after merging (the previous merge produced a build failure — this is the primary acceptance criterion)
• Confirm that void-editor-widgets-tsx is indeed the correct directory name used by tsup's build output (check react/out/ after a successful build)

Notes

• The void-editor-widgets-tsx name is an internal build artifact directory — it's not user-facing branding, so keeping the original name does not violate the zero-trace rebranding policy
• Requested by: @danialsamiei
• Link to Devin run

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.