docs(workspace): add branching strategy and CI guidelines

AGENTS.md

@@ -175,6 +175,12 @@ Things to be aware of when writing rendering or import code (these are *not* con
 - **Blender is Z-up, right-handed.** Models exported from Blender need a coordinate swap on import (rotate −90° around X, or swap Y/Z with sign). Decide once where that swap happens — at export, at import, or never (by adopting Blender's convention) — and stick to it. Doing it in two places will eventually produce a model that's mirrored or upside-down and you'll spend an afternoon on it.
 - **glTF is Y-up, right-handed** — matches your engine convention, so it's the most friction-free model format if you have a choice.
 
+## Branching Strategy & Workflow
+
+- **`main` vs `dev`**: The repository follows a strict workflow. The `main` branch is reserved purely for stable releases. All active development happens on the **`dev`** branch.
+- **Feature Branches**: For any large feature, always create a new branch off of `dev` (e.g., `feat/new-worldgen`). Do not commit large, work-in-progress features directly to `dev`. Once the feature is complete and verified, merge it back into `dev`.
+- **Continuous Integration**: The project enforces strict linting and formatting via GitHub Actions. This includes workspace-level `clippy` rules (banning `unwrap` and `println!`), `cargo fmt`, `selene` for Lua, and `stylua`. Always ensure your code passes these tools locally before pushing.
+
 ## Commit conventions
 
 [**Conventional Commits**](https://www.conventionalcommits.org/) with **mandatory crate-name scope**.

CLAUDE.md

@@ -175,6 +175,12 @@ Things to be aware of when writing rendering or import code (these are *not* con
 - **Blender is Z-up, right-handed.** Models exported from Blender need a coordinate swap on import (rotate −90° around X, or swap Y/Z with sign). Decide once where that swap happens — at export, at import, or never (by adopting Blender's convention) — and stick to it. Doing it in two places will eventually produce a model that's mirrored or upside-down and you'll spend an afternoon on it.
 - **glTF is Y-up, right-handed** — matches your engine convention, so it's the most friction-free model format if you have a choice.
 
+## Branching Strategy & Workflow
+
+- **`main` vs `dev`**: The repository follows a strict workflow. The `main` branch is reserved purely for stable releases. All active development happens on the **`dev`** branch.
+- **Feature Branches**: For any large feature, always create a new branch off of `dev` (e.g., `feat/new-worldgen`). Do not commit large, work-in-progress features directly to `dev`. Once the feature is complete and verified, merge it back into `dev`.
+- **Continuous Integration**: The project enforces strict linting and formatting via GitHub Actions. This includes workspace-level `clippy` rules (banning `unwrap` and `println!`), `cargo fmt`, `selene` for Lua, and `stylua`. Always ensure your code passes these tools locally before pushing.
+
 ## Commit conventions
 
 [**Conventional Commits**](https://www.conventionalcommits.org/) with **mandatory crate-name scope**.