docs: move reviewing sections to main Workspaces page

Move 'Reviewing Code' and 'Reviewing Functionality' sections from
local.md to workspaces.md since they apply to both local and SSH
workspaces.

Changes:
- Add reviewing sections to workspaces.md after 'Key Concepts'
- Remove reviewing sections from local.md (now focuses on worktree
  mechanics and filesystem layout)
- Add note in 'Reviewing Functionality' about detached HEAD being
  specific to local workspaces

This reduces duplication and puts shared concepts in the parent page
where they're easier to find.

Author: ammar-agent

docs/local.md

@@ -20,24 +20,3 @@ Example layout:
     improved-auth-ux/
     fix-ci-flakes/
 ```
-
-## Reviewing Code
-
-Here are a few practical approaches to reviewing changes from workspaces, depending on how much you want your agent to interact with `git`:
-
-- **Agent codes, commits, and pushes**: Ask agent to submit a PR and review changes in your git Web UI (GitHub, GitLab, etc.)
-  - Also see: [Agentic Git Identity](./agentic-git-identity.md)
-  - This is the preferred approach for `cmux` development but requires additional care with repository security.
-- **Agent codes and commits**: Review changes from the main repository via `git diff <workspace-branch>`, push changes when deemed acceptable.
-- **Agent codes**: enter worktree (click Terminal icon in workspace top bar), run `git add -p` and progressively accept changes into a commit.
-
-## Reviewing Functionality
-
-Some changes (especially UI ones) require the Human to determine acceptability. An effective approach for this is:
-
-1. Ask agent to commit WIP when it's ready for Human review
-2. Human, in main repository, checks out the workspace branch in a detached HEAD state: `git checkout --detach <workspace-branch>`
-
-**Note**: This workflow uses the detached HEAD state because the branch is already checked out in the workspace and you cannot check out the same branch multiple times across worktrees.
-
-If you want faster iteration in between commits, you can hop into the worktree directory and run a dev server (e.g. `bun dev`) there directly and observe the agent's work in real-time.

docs/workspaces.md

@@ -24,4 +24,27 @@ The workspace backend is selected when you create a workspace:
 - **Parallel execution**: Run multiple workspaces simultaneously on different tasks
 - **Shared commits**: Local workspaces (using worktrees) share commits with the main repository immediately
 
+## Reviewing Code
+
+Here are a few practical approaches to reviewing changes from workspaces, depending on how much you want your agent to interact with `git`:
+
+- **Agent codes, commits, and pushes**: Ask agent to submit a PR and review changes in your git Web UI (GitHub, GitLab, etc.)
+  - Also see: [Agentic Git Identity](./agentic-git-identity.md)
+  - This is the preferred approach for `cmux` development but requires additional care with repository security.
+- **Agent codes and commits**: Review changes from the main repository via `git diff <workspace-branch>`, push changes when deemed acceptable.
+- **Agent codes**: Enter worktree (click Terminal icon in workspace top bar), run `git add -p` and progressively accept changes into a commit.
+
+## Reviewing Functionality
+
+Some changes (especially UI ones) require the Human to determine acceptability. An effective approach for this is:
+
+1. Ask agent to commit WIP when it's ready for Human review
+2. Human, in main repository, checks out the workspace branch in a detached HEAD state: `git checkout --detach <workspace-branch>` (for local workspaces)
+
+**Note**: For local workspaces, this workflow uses the detached HEAD state because the branch is already checked out in the workspace and you cannot check out the same branch multiple times across worktrees.
+
+If you want faster iteration in between commits, you can hop into the workspace directory and run a dev server (e.g. `bun dev`) there directly and observe the agent's work in real-time.
+
+---
+
 See the specific workspace type pages for detailed setup and usage instructions.