Updated some .md files and license

Author: Zenwoh

CONTRIBUTING.md

@@ -1,6 +1,13 @@
-# Contributing to OpenCode
+# Contributing to Mammouth Code
 
-We want to make it easy for you to contribute to OpenCode. Here are the most common type of changes that get merged:
+> [!IMPORTANT]
+> Before contributing, please read the section below carefully. Mammouth Code is a fork of OpenCode, and it's important to understand which project your contribution belongs to.
+
+First, we want to make it clear that Mammouth Code is a open fork of the open source OpenCode project. We are building on top of OpenCode and contributing back to it, but we are not affiliated with the OpenCode project or its maintainers in any way. We have our own roadmap and vision for Mammouth Code, which may diverge from OpenCode over time.
+
+Please, before contributing, take a moment to think if your contribution is something that belongs in Mammouth Code specifically, or if it is a more general improvement that would benefit the entire OpenCode ecosystem. If it's the latter, we encourage you to contribute to OpenCode directly. To do so, checkout the [OpenCode repository](https://github.com/anomalyco/opencode) and follow their contributing guidelines. If it's the former, we welcome your contribution to Mammouth Code!
+
+We want to make it easy for you to contribute to Mammouth Code. Here are the most common type of changes that get merged:
 
 - Bug fixes
 - Additional LSPs / Formatters
@@ -14,17 +21,17 @@ However, any UI or core product feature must go through a design review with the
 
 If you are unsure if a PR would be accepted, feel free to ask a maintainer or look for issues with any of the following labels:
 
-- [`help wanted`](https://github.com/anomalyco/opencode/issues?q=is%3Aissue%20state%3Aopen%20label%3Ahelp-wanted)
-- [`good first issue`](https://github.com/anomalyco/opencode/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22)
-- [`bug`](https://github.com/anomalyco/opencode/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug)
-- [`perf`](https://github.com/anomalyco/opencode/issues?q=is%3Aopen%20is%3Aissue%20label%3A%22perf%22)
+- [`help wanted`](https://github.com/mammouth-ai/code/issues?q=is%3Aissue%20state%3Aopen%20label%3Ahelp-wanted)
+- [`good first issue`](https://github.com/mammouth-ai/code/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22)
+- [`bug`](https://github.com/mammouth-ai/code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug)
+- [`perf`](https://github.com/mammouth-ai/code/issues?q=is%3Aopen%20is%3Aissue%20label%3A%22perf%22)
 
 > [!NOTE]
 > PRs that ignore these guardrails will likely be closed.
 
 Want to take on an issue? Leave a comment and a maintainer may assign it to you unless it is something we are already working on.
 
-## Developing OpenCode
+## Developing Mammouth Code
 
 - Requirements: Bun 1.3+
 - Install dependencies and start the dev server from the repo root:
@@ -36,13 +43,13 @@ Want to take on an issue? Leave a comment and a maintainer may assign it to you
 
 ### Running against a different directory
 
-By default, `bun dev` runs OpenCode in the `packages/opencode` directory. To run it against a different directory or repository:
+By default, `bun dev` runs Mammouth Code in the `packages/opencode` directory. To run it against a different directory or repository:
 
 ```bash
 bun dev <directory>
 ```
 
-To run OpenCode in the root of the opencode repo itself:
+To run Mammouth Code in the root of the code repo itself:
 
 ```bash
 bun dev .
@@ -59,7 +66,7 @@ To compile a standalone executable:
 Then run it with:
 
 ```bash
-./packages/opencode/dist/opencode-<platform>/bin/opencode
+./packages/opencode/dist/opencode-<platform>/bin/mammouth
 ```
 
 Replace `<platform>` with your platform (e.g., `darwin-arm64`, `linux-x64`).
@@ -71,9 +78,9 @@ Replace `<platform>` with your platform (e.g., `darwin-arm64`, `linux-x64`).
   - `packages/desktop`: The native desktop app, built with Tauri (wraps `packages/app`)
   - `packages/plugin`: Source for `@opencode-ai/plugin`
 
-### Understanding bun dev vs opencode
+### Understanding bun dev vs mammouth
 
-During development, `bun dev` is the local equivalent of the built `opencode` command. Both run the same CLI interface:
+During development, `bun dev` is the local equivalent of the built `mammouth` command. Both run the same CLI interface:
 
 ```bash
 # Development (from project root)
@@ -91,7 +98,7 @@ opencode <directory>     # Start TUI in specific directory
 
 ### Running the API Server
 
-To start the OpenCode headless API server:
+To start the Mammouth Code headless API server:
 
 ```bash
 bun dev serve
@@ -107,7 +114,7 @@ bun dev serve --port 8080
 
 To test UI changes during development:
 
-1. **First, start the OpenCode server** (see [Running the API Server](#running-the-api-server) section above)
+1. **First, start the Mammouth Code server** (see [Running the API Server](#running-the-api-server) section above)
 2. **Then run the web app:**
 
 ```bash
@@ -154,16 +161,16 @@ Please try to follow the [style guide](./AGENTS.md)
 
 Bun debugging is currently rough around the edges. We hope this guide helps you get set up and avoid some pain points.
 
-The most reliable way to debug OpenCode is to run it manually in a terminal via `bun run --inspect=<url> dev ...` and attach
+The most reliable way to debug Mammouth Code is to run it manually in a terminal via `bun run --inspect=<url> dev ...` and attach
 your debugger via that URL. Other methods can result in breakpoints being mapped incorrectly, at least in VSCode (YMMV).
 
 Caveats:
 
-- If you want to run the OpenCode TUI and have breakpoints triggered in the server code, you might need to run `bun dev spawn` instead of
+- If you want to run the Mammouth Code TUI and have breakpoints triggered in the server code, you might need to run `bun dev spawn` instead of
   the usual `bun dev`. This is because `bun dev` runs the server in a worker thread and breakpoints might not work there.
 - If `spawn` does not work for you, you can debug the server separately:
   - Debug server: `bun run --inspect=ws://localhost:6499/ --cwd packages/opencode ./src/index.ts serve --port 4096`,
-    then attach TUI with `opencode attach http://localhost:4096`
+    then attach TUI with `mammouth attach http://localhost:4096`
   - Debug TUI: `bun run --inspect=ws://localhost:6499/ --cwd packages/opencode --conditions=browser ./src/index.ts`
 
 Other tips and tricks:
@@ -178,7 +185,7 @@ If you use VSCode, you can use our example configurations [.vscode/settings.exam
 Some debug methods that can be problematic:
 
 - Debug configurations with `"request": "launch"` can have breakpoints incorrectly mapped and thus unusable
-- The same problem arises when running OpenCode in the VSCode `JavaScript Debug Terminal`
+- The same problem arises when running Mammouth Code in the VSCode `JavaScript Debug Terminal`
 
 With that said, you may want to try these methods, as they might work for you.
 
@@ -257,7 +264,7 @@ These are not strictly enforced, they are just general guidelines:
 
 ## Feature Requests
 
-For net-new functionality, start with a design conversation. Open an issue describing the problem, your proposed approach (optional), and why it belongs in OpenCode. The core team will help decide whether it should move forward; please wait for that approval instead of opening a feature PR directly.
+For net-new functionality, start with a design conversation. Open an issue describing the problem, your proposed approach (optional), and why it belongs in Mammouth Code. The core team will help decide whether it should move forward; please wait for that approval instead of opening a feature PR directly.
 
 ## Trust & Vouch System
 
@@ -266,7 +273,7 @@ This project uses [vouch](https://github.com/mitchellh/vouch) to manage contribu
 ### How it works
 
 - **Vouched users** are explicitly trusted contributors.
-- **Denounced users** are explicitly blocked. Issues and pull requests from denounced users are automatically closed. If you have been denounced, you can request to be unvouched by reaching out to a maintainer on [Discord](https://opencode.ai/discord)
+- **Denounced users** are explicitly blocked. Issues and pull requests from denounced users are automatically closed. If you have been denounced, you can request to be unvouched by reaching out to a maintainer on [Discord](https://discord.gg/YJg2kX77M3)
 - **Everyone else** can participate normally — you don't need to be vouched to open issues or PRs.
 
 ### For maintainers

LICENSE

@@ -1,6 +1,7 @@
 MIT License
 
 Copyright (c) 2025 opencode
+Copyright (c) 2025 Mammouth AI
 
 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.bs.md

@@ -1,5 +1,7 @@
 # Security
 
+This security file is unrelated to the changes that Mammouth AI made to this fork of OpenCode. It's provided here as is, straight from the original OpenCode repository, for your reference. For any questions about the security of OpenCode, please refer to the original OpenCode repository and its maintainers.
+
 ## Threat Model
 
 ### Overview