Move root documentation markdown files into explanations folder

[cto-new]

Moved project documentation markdown files from the repository root into explanations/ to comply with the repo rule that docs live there (keeping README.md and CLAUDE.md at the root). No content changes; pure file moves/renames to reduce root clutter and keep documentation centralized.

Powered by CTO.new

---

Summary by cubic

Moved all root documentation markdown files into explanations/ to centralize docs and follow the repo rule. No content changes; only file moves. README.md and CLAUDE.md remain at the root.

^{Written for commit 0746a57. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
zapdev	Ready	Preview, Comment	Jan 27, 2026 8:09am

[codecapyai]

CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎

• PR: Move root documentation markdown files into explanations folder #216
• Commit: 0746a57

Codebase Summary

ZapDev is an AI-powered development platform that allows users to create web applications by interacting with AI agents in real-time development sandboxes. The application features a live preview interface, a file explorer with syntax highlighting, and conversational project development with robust backend integration using Next.js, React, tRPC, and various other modern technologies.

PR Changes

This pull request moves several project documentation markdown files from the repository root into the 'explanations/' folder to reduce root clutter and enforce documentation centralization. The only markdown files that remain at the root are README.md and CLAUDE.md. There are no content changes, only file relocations.

Setup Instructions

1. Install pnpm globally: sudo npm install -g pnpm
2. Navigate to the repository directory: cd <repository_directory>
3. Install all dependencies: pnpm install
4. Start the development server: pnpm dev
5. Open a browser and navigate to http://localhost:3000 to access the application

Generated Test Cases

1: Verify Root Documentation Files Visibility ❗️❗️❗️

Description: Checks that the two markdown files that are meant to remain at the repository root (README.md and CLAUDE.md) are still visible and accessible in the UI, ensuring that users can readily find essential documentation on the landing or file explorer page.

Prerequisites:

• Application is running (pnpm dev has been executed)
• User is on the main page or file explorer view

Steps:

1. Launch the application in the browser by navigating to http://localhost:3000.
2. Locate the file explorer panel (or a navigation menu) that displays the repository files.
3. Verify that the files README.md and CLAUDE.md appear at the root level.
4. Click on README.md to open and render its content.
5. Repeat for CLAUDE.md to ensure that it also opens and displays correctly.

Expected Result: Both README.md and CLAUDE.md should be visible at the repository root and, when clicked, should render their markdown content accurately without errors.

2: Verify Moved Documentation Files in Explanations Folder ❗️❗️❗️

Description: Ensures that the documentation files that were moved from the root to the 'explanations/' folder are still accessible via the file explorer, maintaining user access to detailed guides and documentation.

Prerequisites:

• Application is running (pnpm dev has been executed)
• User has access to the file explorer or documentation navigation area

Steps:

1. Open the application in the browser by navigating to http://localhost:3000.
2. In the file explorer, locate and click on the 'explanations' folder.
3. Verify that the folder expands and lists several markdown files (for example, files like AUTH_FIX_2025-11-13.md, CONVEX_SETUP.md, etc.).
4. Select one of the markdown files (e.g., CONVEX_SETUP.md) from the list.
5. Confirm that the selected file opens and displays its markdown content correctly.

Expected Result: The 'explanations' folder should correctly list all moved documentation markdown files and clicking any file should render its content properly without navigation or loading errors.

3: Verify File Explorer Layout and Navigation Post-Documentation Move ❗️❗️

Description: Tests that the visual appearance and navigation flow within the file explorer remains consistent after moving the documentation files. This ensures that users experience a predictable and organized interface.

Prerequisites:

• Application is running (pnpm dev has been executed)
• User is familiar with using the file explorer in the application

Steps:

1. Navigate to http://localhost:3000 in the browser.
2. Examine the file explorer to verify that the root level shows only files intended to remain (such as README.md and CLAUDE.md) and folders.
3. Locate the 'explanations' folder and click on it.
4. Ensure that the folder view is user-friendly, displays folder icons or labels properly, and that each markdown file is clearly listed.
5. Optionally, navigate back to the root view to see that navigation remains consistent.

Expected Result: The file explorer should display a clean and organized structure with the 'explanations' folder clearly separated from the root-level documents. All files should be accessible, and the navigation should work seamlessly.

Raw Changes Analyzed

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

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

[cubic-dev-ai]

No issues found across 27 files

[codecapyai]

🚀 Launching Scrapybara desktop...

[codecapyai]

❌ Something went wrong:

status_code: 500, body: {'detail': 'Error creating instance: HTTPSConnectionPool(host=\'dd71ce9e4c14175cfb2d4b4d613159f4.sk1.us-west-1.eks.amazonaws.com\', port=443): Max retries exceeded with url: /api/v1/namespaces/scrapybara-instances/services (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7fd78892e1d0>: Failed to resolve \'dd71ce9e4c14175cfb2d4b4d613159f4.sk1.us-west-1.eks.amazonaws.com\' ([Errno -2] Name or service not known)"))'}