[Feature]: Load project file trees one directory at a time

[burnmandont]

Problem

Opening the Files panel currently loads the project's complete indexed file tree before it can render. That is convenient for small repositories, but large monorepos can make the initial response, client state, and tree construction much larger than the part of the workspace the user is actually browsing. The cost is especially noticeable over remote connections.

Proposed direction

Add a project-scoped directory-listing RPC and have the Files panel request only the root directory initially. Expanding a folder would load that folder's immediate children on demand.

Each directory response could include:

• immediate files and directories
• file type and relevant Git status
• enough metadata for the existing tree interactions

Search and content search would remain backed by the existing workspace index, so users could still find unopened files without recursively expanding the tree.

For compatibility, clients could fall back to the existing full-tree endpoint when connected to an older server.

Why this shape

This keeps the normal Files-panel payload proportional to what the user opens, avoids eagerly transferring and materializing an entire monorepo, and preserves the current full-project search experience. It should benefit local use, but the primary motivation is predictable behavior for large projects over remote connections.

Questions

• Does one-directory-at-a-time loading fit the intended direction of the Files panel?
• Should Git status be returned with each directory page, or remain a separate concern?
• Is compatibility with older servers worth retaining in the first implementation?