Restore Roopik-branded root docs from develop

The orphan checkout brought VSCode's upstream versions of these files;
restore the Roopik versions:

- README.md         : 'Roopik IDE' (was 'Visual Studio Code - Open Source')
- CONTRIBUTING.md   : 'Contributing to Roopik IDE'
- LICENSE.txt       : 'Copyright (c) 2025 - present Roopik Labs'
                      (was 'Copyright (c) 2015 - present Microsoft Corporation')
- SECURITY.md       : Roopik vulnerability reporting
- ThirdPartyNotices.txt : Roopik attributions
- CODE_OF_CONDUCT.md : Roopik code of conduct (was missing entirely)

LICENSE.txt is the most critical here — wrong copyright line is a
legal issue. VSCODE_MODIFICATIONS.md 'Files to Replace' already lists
README/CONTRIBUTING/SECURITY/LICENSE; that doc will be updated to also
include CODE_OF_CONDUCT.md and ThirdPartyNotices.txt.

Author: HumbleBee14

CODE_OF_CONDUCT.md

@@ -0,0 +1,25 @@
+# Code of Conduct
+
+## Our Pledge
+
+We are committed to providing a friendly, safe, and welcoming environment for all contributors, regardless of experience level, gender identity, sexual orientation, disability, personal appearance, race, ethnicity, age, religion, or nationality.
+
+## Our Standards
+
+**Expected behavior:**
+- Be respectful and constructive in discussions
+- Accept feedback gracefully
+- Focus on what is best for the community and project
+
+**Unacceptable behavior:**
+- Harassment, trolling, or personal attacks
+- Publishing others' private information
+- Any conduct that would be considered inappropriate in a professional setting
+
+## Enforcement
+
+Instances of unacceptable behavior may be reported to dev@roopik.com. All complaints will be reviewed and investigated. Maintainers have the right to remove, edit, or reject contributions that do not align with this Code of Conduct.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.

CONTRIBUTING.md

@@ -1,99 +1,83 @@
-# Contributing to VS Code
+# Contributing to Roopik IDE
 
-Welcome, and thank you for your interest in contributing to VS Code!
+Welcome, and thank you for your interest in contributing to Roopik!
 
-There are several ways in which you can contribute, beyond writing code. The goal of this document is to provide a high-level overview of how you can get involved.
+## Ways to Contribute
 
-## Asking Questions
-
-
-Have a question? Instead of opening an issue, please ask on [Stack Overflow](https://stackoverflow.com/questions/tagged/visual-studio-code) using the tag `visual-studio-code`.
-
-The active community will be eager to assist you. Your well-worded question will serve as a resource to others searching for help.
-
-## Providing Feedback
-
-Your comments and feedback are welcome, and the development team is available via a handful of different channels.
-
-See the [Feedback Channels](https://github.com/microsoft/vscode/wiki/Feedback-Channels) wiki page for details on how to share your thoughts.
+- Report bugs and request features via [GitHub Issues](https://github.com/RoopikLabs/roopik/issues)
+- Submit pull requests for bug fixes or features
+- Improve documentation
+- Share feedback and ideas in [Discussions](https://github.com/RoopikLabs/roopik/discussions)
 
 ## Reporting Issues
 
-Have you identified a reproducible problem in VS Code? Do you have a feature request? We want to hear about it! Here's how you can report your issue as effectively as possible.
-
-### Identify Where to Report
-
-The VS Code project is distributed across multiple repositories. Try to file the issue against the correct repository. Check the list of [Related Projects](https://github.com/microsoft/vscode/wiki/Related-Projects) if you aren't sure which repo is correct.
-
-Can you recreate the issue even after [disabling all extensions](https://code.visualstudio.com/docs/editor/extension-gallery#_disable-an-extension)? If you find the issue is caused by an extension you have installed, please file an issue on the extension's repo directly.
-
-### Look For an Existing Issue
-
-Before you create a new issue, please do a search in [open issues](https://github.com/microsoft/vscode/issues) to see if the issue or feature request has already been filed.
-
-Be sure to scan through the [most popular](https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc) feature requests.
-
-If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment:
-
-* 👍 - upvote
-* 👎 - downvote
-
-If you cannot find an existing issue that describes your bug or feature, create a new issue using the guidelines below.
-
-### Writing Good Bug Reports and Feature Requests
-
-File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue.
-
-Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar but have different causes.
-
-The more information you can provide, the more likely someone will be successful at reproducing the issue and finding a fix.
-
-The built-in tool for reporting an issue, which you can access by using `Report Issue` in VS Code's Help menu, can help streamline this process by automatically providing the version of VS Code, all your installed extensions, and your system info. Additionally, the tool will search among existing issues to see if a similar issue already exists.
+Before creating a new issue, please search [existing issues](https://github.com/RoopikLabs/roopik/issues) to avoid duplicates.
 
-Please include the following with each issue:
+When reporting a bug, include:
+- Roopik version (Help > About)
+- Operating system
+- Steps to reproduce
+- Expected vs actual behavior
+- Screenshots or screen recordings if applicable
+- Errors from Developer Tools (Help > Toggle Developer Tools)
 
-* Version of VS Code
-* Your operating system
-* List of extensions that you have installed
-* Reproducible steps (1... 2... 3...) that cause the issue
-* What you expected to see, versus what you actually saw
-* Images, animations, or a link to a video showing the issue occurring
-* A code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally
-  * **Note:** Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
-* Errors from the Dev Tools Console (open from the menu: Help > Toggle Developer Tools)
+## Development Setup
 
-### Creating Pull Requests
+### Prerequisites
+- Node.js (see `.nvmrc`)
+- Python 3.11+
+- Git
 
-* Please refer to the article on [creating pull requests](https://github.com/microsoft/vscode/wiki/How-to-Contribute#pull-requests) and contributing to this project.
+### Building from Source
 
-### Final Checklist
+```bash
+# Clone
+git clone https://github.com/RoopikLabs/roopik.git
+cd roopik
 
-Please remember to do the following:
+# Install dependencies
+npm install
 
-* [ ] Search the issue repository to ensure your report is a new issue
-* [ ] Recreate the issue after disabling all extensions
-* [ ] Simplify your code around the issue to better isolate the problem
+# Watch (development)
+npm run watch
 
-Don't feel bad if the developers can't reproduce the issue right away. They will simply ask for more information!
+# Build (production)
+npm run gulp vscode-win32-x64       # Windows
+npm run gulp vscode-darwin-arm64     # macOS
+npm run gulp vscode-linux-x64       # Linux
+```
 
-### Follow Your Issue
+### Building the Agent Dio Extension
 
-Once submitted, your report will go into the [issue tracking](https://github.com/microsoft/vscode/wiki/Issue-Tracking) workflow. Be sure to understand what will happen next, so you know what to expect and how to continue to assist throughout the process.
+```bash
+cd extensions/roopik-roo
+npm install
+cd packages/types && npm install && npm run build && cd ../..
+cd packages/build && npm install && npm run build && cd ../..
+npm run build
+```
 
-## Automated Issue Management
+## Pull Requests
 
-We use GitHub Actions to help us manage issues. These Actions and their descriptions can be [viewed here](https://github.com/microsoft/vscode-github-triage-actions). Some examples of what these Actions do are:
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feat/my-feature`)
+3. Make your changes
+4. Test locally (build + run)
+5. Commit with a clear message
+6. Push and open a Pull Request
 
-* Automatically close any issue marked `info-needed` if there has been no response in the past 7 days.
-* Automatically lock issues 45 days after they are closed.
-* Automatically implement the VS Code [feature request pipeline](https://github.com/microsoft/vscode/wiki/Issues-Triaging#managing-feature-requests).
+### PR Guidelines
 
-If you believe the bot got something wrong, please open a new issue and let us know.
+- Keep PRs focused - one feature or fix per PR
+- Include a clear description of what changed and why
+- Add screenshots for UI changes
+- Ensure the build passes before submitting
 
-## Contributing Fixes
+## Project Structure
 
-If you are interested in writing code to fix issues, please see [How to Contribute](https://github.com/microsoft/vscode/wiki/How-to-Contribute) in the wiki.
+- `src/vs/workbench/contrib/roopik/` — Core Roopik features (Canvas, Project,Browser, MCP, tools)
+- `extensions/roopik-roo/` — Dio agent (built on Roo Code)
 
-## Thank You
+## License
 
-Your contributions to open source, large or small, make great projects like this possible. Thank you for taking the time to contribute.
+By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE.txt).

LICENSE.txt

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2015 - present Microsoft Corporation
+Copyright (c) 2025 - present Roopik Labs
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,78 +1,78 @@
-# Visual Studio Code - Open Source ("Code - OSS")
-[![Feature Requests](https://img.shields.io/github/issues/microsoft/vscode/feature-request.svg)](https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc)
-[![Bugs](https://img.shields.io/github/issues/microsoft/vscode/bug.svg)](https://github.com/microsoft/vscode/issues?utf8=✓&q=is%3Aissue+is%3Aopen+label%3Abug)
-[![Gitter](https://img.shields.io/badge/chat-on%20gitter-yellow.svg)](https://gitter.im/Microsoft/vscode)
+# Roopik IDE
 
-## The Repository
+**A canvas-first, agentic IDE with a built-in browser.** Preview live components, run full projects end-to-end — with AI agents that code, browse, test, and ship autonomously.
 
-This repository ("`Code - OSS`") is where we (Microsoft) develop the [Visual Studio Code](https://code.visualstudio.com) product together with the community. Not only do we work on code and issues here, but we also publish our [roadmap](https://github.com/microsoft/vscode/wiki/Roadmap), [monthly iteration plans](https://github.com/microsoft/vscode/wiki/Iteration-Plans), and our [endgame plans](https://github.com/microsoft/vscode/wiki/Running-the-Endgame). This source code is available to everyone under the standard [MIT license](https://github.com/microsoft/vscode/blob/main/LICENSE.txt).
+[![Build Windows](https://github.com/RoopikLabs/roopik/actions/workflows/build-windows.yml/badge.svg)](https://github.com/RoopikLabs/roopik/actions/workflows/build-windows.yml)
+[![Build macOS](https://github.com/RoopikLabs/roopik/actions/workflows/build-macos.yml/badge.svg)](https://github.com/RoopikLabs/roopik/actions/workflows/build-macos.yml)
+[![Build Linux](https://github.com/RoopikLabs/roopik/actions/workflows/build-linux.yml/badge.svg)](https://github.com/RoopikLabs/roopik/actions/workflows/build-linux.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE.txt)
 
-## Visual Studio Code
+[Website](https://roopik.com) | [Download](https://roopik.com) | [Docs](https://roopik.com/docs) | [Blog](https://roopik.com/blog) | [Contributing](CONTRIBUTING.md)
 
-<p align="center">
-  <img alt="VS Code in action" src="https://user-images.githubusercontent.com/35271042/118224532-3842c400-b438-11eb-923d-a5f66fa6785a.png">
-</p>
+---
 
-[Visual Studio Code](https://code.visualstudio.com) is a distribution of the `Code - OSS` repository with Microsoft-specific customizations released under a traditional [Microsoft product license](https://code.visualstudio.com/License/).
+![Roopik IDE Preview](https://roopik.com/roopik-preview-gif.gif)
 
-[Visual Studio Code](https://code.visualstudio.com) combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.
+## What Makes Roopik Different
 
-Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on [Visual Studio Code's website](https://code.visualstudio.com/Download). To get the latest releases every day, install the [Insiders build](https://code.visualstudio.com/insiders).
+Most AI-powered IDEs are code editors with chat. Roopik goes further — it has a **real browser built in** that AI agents can see and control. Agents don't just write code, they preview it, click through it, test it, and fix what they see. No context switching, no manual testing.
 
-## Contributing
+## Features
 
-There are many ways in which you can participate in this project, for example:
+### Canvas Mode
+An infinite design surface for building UI components across **React, Vue, Svelte, Solid, and Preact**. Each component renders live in its own isolated sandbox — write a Single File Component (SFC) and see it instantly. Compare multiple variations side-by-side, iterate with AI, and ship without ever spinning up a dev server.
 
-* [Submit bugs and feature requests](https://github.com/microsoft/vscode/issues), and help us verify as they are checked in
-* Review [source code changes](https://github.com/microsoft/vscode/pulls)
-* Review the [documentation](https://github.com/microsoft/vscode-docs) and make pull requests for anything from typos to and new content.
+### Project Mode
+Run your full project with a built-in browser. Inspect elements live, click any element to jump to its source code, edit it, and see changes instantly. No more switching between editor and browser.
 
-If you are interested in fixing issues and contributing directly to the code base,
-please see the document [How to Contribute](https://github.com/microsoft/vscode/wiki/How-to-Contribute), which covers the following:
+### Embedded Browser + External Chrome
+The browser supports multiple tabs with full agentic control. Agents can open, navigate, screenshot, click, type, and inspect — all exposed through MCP. External Chrome mode connects to a real Chrome instance via CDP for full extension/profile access.
 
-* [How to build and run from source](https://github.com/microsoft/vscode/wiki/How-to-Contribute)
-* [The development workflow, including debugging and running tests](https://github.com/microsoft/vscode/wiki/How-to-Contribute#debugging)
-* [Coding guidelines](https://github.com/microsoft/vscode/wiki/Coding-Guidelines)
-* [Submitting pull requests](https://github.com/microsoft/vscode/wiki/How-to-Contribute#pull-requests)
-* [Finding an issue to work on](https://github.com/microsoft/vscode/wiki/How-to-Contribute#where-to-contribute)
-* [Contributing to translations](https://aka.ms/vscodeloc)
+### Browser Automation
+Playwright-inspired reliability built into every browser action. Smart selectors (`text=`, `role=`, `css=`, `data-testid=`), automatic waiting for elements to be ready, auto-scroll, and strict locator mode — agents interact with pages the same way a human would, without brittle coordinate-based clicking.
 
-## Feedback
+### Multi-Agent Support
+Multiple AI agents work simultaneously in the same workspace:
+- **Dio** — built-in agent (based on Roo Code)
+- **Claude Code** — extension + CLI via MCP
+- **OpenAI Codex** — extension + CLI via MCP
+- **Cursor** — via MCP
 
-* Ask a question on [Stack Overflow](https://stackoverflow.com/questions/tagged/vscode)
-* [Request a new feature](CONTRIBUTING.md)
-* Upvote [popular feature requests](https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc)
-* [File an issue](https://github.com/microsoft/vscode/issues)
-* Connect with the extension author community on [GitHub Discussions](https://github.com/microsoft/vscode-discussions/discussions) or [Slack](https://aka.ms/vscode-dev-community)
-* Follow [@code](https://x.com/code) and let us know what you think!
+No setup needed — the IDE auto-registers and connects agents via MCP on startup.
 
-See our [wiki](https://github.com/microsoft/vscode/wiki/Feedback-Channels) for a description of each of these channels and information on some other available community-driven channels.
+See [CONTRIBUTING.md](CONTRIBUTING.md) for project structure, build instructions, and development setup.
 
-## Related Projects
+## Quick Start
 
-Many of the core components and extensions to VS Code live in their own repositories on GitHub. For example, the [node debug adapter](https://github.com/microsoft/vscode-node-debug) and the [mono debug adapter](https://github.com/microsoft/vscode-mono-debug) repositories are separate from each other. For a complete list, please visit the [Related Projects](https://github.com/microsoft/vscode/wiki/Related-Projects) page on our [wiki](https://github.com/microsoft/vscode/wiki).
+### Download
+Available for Windows, macOS, and Linux at [roopik.com](https://roopik.com)
 
-## Bundled Extensions
+### Build from Source
 
-VS Code includes a set of built-in extensions located in the [extensions](extensions) folder, including grammars and snippets for many languages. Extensions that provide rich language support (inline suggestions, Go to Definition) for a language have the suffix `language-features`. For example, the `json` extension provides coloring for `JSON` and the `json-language-features` extension provides rich language support for `JSON`.
+```bash
+git clone https://github.com/RoopikLabs/roopik.git
+cd roopik
+npm install
+npm run watch        # Development
+```
 
-## Development Container
+See [CONTRIBUTING.md](CONTRIBUTING.md) for full build instructions including the Dio extension.
 
-This repository includes a Visual Studio Code Dev Containers / GitHub Codespaces development container.
+## Contributing
 
-* For [Dev Containers](https://aka.ms/vscode-remote/download/containers), use the **Dev Containers: Clone Repository in Container Volume...** command which creates a Docker volume for better disk I/O on macOS and Windows.
-  * If you already have VS Code and Docker installed, you can also click [here](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/vscode) to get started. This will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
+We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for:
+- How to build and run from source
+- Project structure overview
+- Pull request guidelines
 
-* For Codespaces, install the [GitHub Codespaces](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension in VS Code, and use the **Codespaces: Create New Codespace** command.
+## Privacy
 
-Docker / the Codespace should have at least **4 cores and 6 GB of RAM (8 GB recommended)** to run a full build. See the [development container README](.devcontainer/README.md) for more information.
+This program does not collect or transfer any user data to external systems unless specifically requested by the user. Telemetry features inherited from upstream dependencies are disabled by default.
 
-## Code of Conduct
+## Acknowledgements
 
-This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
+Built on [Visual Studio Code](https://github.com/microsoft/vscode) (MIT) and [Roo Code](https://github.com/RooCodeInc/Roo-Code) (Apache 2.0).
 
 ## License
 
-Copyright (c) Microsoft Corporation. All rights reserved.
-
-Licensed under the [MIT](LICENSE.txt) license.
+Copyright (c) 2025 - present Roopik Labs. Licensed under the [MIT License](LICENSE.txt).