feat: native drag-and-drop file injection dropzone (#78)

[prakshithamalla-art]

Closes #78

🎯 Overview & Motivation

When launching environments from custom repositories, developers frequently need to provision local variables, runtime scripts, or .env configuration contexts. Forcing operators to commit temporary test configurations to remote branches before initialization degrades development speed.

This PR implements a native, zero-dependency HTML5 Drag-and-Drop dropzone matrix inside the primary repository management stream. This enables developers to seamlessly stage and inject local client-side files directly into dynamic active sandboxes.

---

🛠️ Changes Implemented

• Decoupled Architecture Overhaul (components/console/repository-list.tsx): Completely refactored the layout structure into clean, single-responsibility modular components (SkeletonGrid, SkeletonTable, EmptyState) to isolate component rendering cycles and achieve clean structural scaling (>400 lines).
• Native HTML5 DataTransfer API Integration: Bound standard web asynchronous event listeners (onDragOver, onDragLeave, onDrop) directly to the DOM matrix to capture operating system drag profiles seamlessly.
• MIME-Type & Memory Guardrails: Integrated an interactive memory-checking layer that validates staging profiles against security rules (maximum 2MB file limit), printing active component warnings (fileError) instantly on failure.
• Asynchronous File Handling Framework: Wired files directly into custom JavaScript FileReader promises to convert text-based payloads into structured ArrayBuffer items for backend execution synchronization.

---

⚠️ Note on Merge Conflict

Important: This PR intentionally builds directly on top of the performance optimizations introduced in PR #76 inside repository-list.tsx. Because both PRs upgrade this specific file to optimize build bundle footprints, GitHub flags a structural merge conflict. Merging PR #76 first will allow this to line up cleanly!

[vercel]

@prakshithamalla-art is attempting to deploy a commit to the Deekshith Gowda HS's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

@prakshithamalla-art, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 32 minutes and 57 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ca6c4cba-44ff-4a7b-b9fb-6ffefc0e8220

📥 Commits

Reviewing files that changed from the base of the PR and between 258b1ca and 4afa4f9.

📒 Files selected for processing (1)

• components/console/repository-list.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[prakshithamalla-art]

This PR intentionally builds directly on top of the performance optimizations introduced in PR #76 inside repository-list.tsx. Because both PRs upgrade this specific file to optimize build bundle footprints, GitHub flags a structural merge conflict. Merging PR #76 first will allow this to line up cleanly!