Move Git Worktrees documentation to Ways-of-Working directory and update links

Author: MariusStorhaug

docs/Agents/Workflow.md

@@ -30,12 +30,12 @@ See [Issue Format](../Ways-of-Working/Issue-Format.md) and [Issue Hierarchy](../
 Covers the **Build** and **Ship** phases. Takes a planned issue and delivers a merge-ready pull request. Owns the full loop:
 
 1. **Orient** — read the issue, README, contribution guide, and standards.
-2. **Branch and draft PR** — create a [worktree](Git-Worktrees.md) for the issue, push early so CI attaches and progress is visible. Assign to the user. Link to the issue.
+2. **Branch and draft PR** — create a [worktree](../Ways-of-Working/Git-Worktrees.md) for the issue, push early so CI attaches and progress is visible. Assign to the user. Link to the issue.
 3. **Build** — micro-commits, one logical change each. Update the issue as each task completes (not in bulk).
 4. **Respond** — process reviewer feedback and CI failures. One thread at a time.
 5. **Finalize** — update PR title, labels, and description as a user-facing release note.
 
-See [Git Worktrees](Git-Worktrees.md), [PR Format](../Ways-of-Working/PR-Format.md), [Commit Conventions](../Ways-of-Working/Commit-Conventions.md), and [Standards](Standards/index.md).
+See [Git Worktrees](../Ways-of-Working/Git-Worktrees.md), [PR Format](../Ways-of-Working/PR-Format.md), [Commit Conventions](../Ways-of-Working/Commit-Conventions.md), and [Standards](Standards/index.md).
 
 ### Reviewer
 

docs/Agents/index.md

@@ -37,7 +37,7 @@ The full workflow — phases, the loop, and how they connect — is documented i
 ## What lives here
 
 - **[Workflow](Workflow.md)** — How the roles connect, the Context Development Lifecycle, and where it meets DevOps.
-- **[Git Worktrees](Git-Worktrees.md)** — Bare-clone + worktree layout for parallel work with agents.
+- **[Git Worktrees](../Ways-of-Working/Git-Worktrees.md)** — Bare-clone + worktree layout for parallel work with agents.
 - **[Standards](Standards/index.md)** — Per-language and per-platform standards referenced by the agents.
 
 ## Guiding intent

docs/Agents/Git-Worktrees.md docs/Ways-of-Working/Git-Worktrees.mddocs/Agents/Git-Worktrees.md renamed to docs/Ways-of-Working/Git-Worktrees.md

@@ -97,34 +97,3 @@ git -C .bare worktree remove 42-add-pagination
 # Prune if needed (removes stale worktree references)
 git -C .bare worktree prune
 ```
-
-The sync script handles this automatically — worktrees whose branch no longer exists on any remote are removed during the next sync.
-
-## Parallel agents
-
-The worktree model enables multiple agents to work in the same repository at the same time:
-
-- Each agent operates in its own worktree (its own issue folder).
-- No merge conflicts during development — conflicts only surface at PR merge time.
-- The default branch worktree provides a stable reference for all agents to read from.
-- CI runs independently per PR, so agents don't block each other.
-
-```text
-Agent A: working in  42-add-pagination/
-Agent B: working in  43-fix-auth-flow/
-Human:   reviewing in main/ or reading docs
-```
-
-## VS Code integration
-
-- **Open the worktree folder directly** — VS Code's Git extension auto-detects the git context.
-- **Multi-root workspace** — add multiple worktrees to one window (`File → Add Folder to Workspace`) to reference `main/` while coding in another.
-- **Terminal cwd** — ensure the integrated terminal is in the worktree folder, not the bare root.
-
-## Rules
-
-1. **Never commit directly to the default branch worktree.** It exists for reference only.
-2. **One worktree per issue.** The folder name matches the branch name: `<N>-<slug>`.
-3. **Clean up after merge.** Remove the worktree and let the sync script prune stale branches.
-4. **All git config lives in `.bare/`** — it applies to every worktree automatically.
-5. **Only `origin` and `upstream` remotes.** No other remotes. `upstream` only exists for forks.

docs/Ways-of-Working/Workflow.md

@@ -90,7 +90,7 @@ See [Issue Format § Sections 2–3](Issue-Format.md), [Issue Hierarchy](Issue-H
 
 Execute the plan:
 
-1. **Branch** — create a branch (and [worktree](../Agents/Git-Worktrees.md)) for the issue.
+1. **Branch** — create a branch (and [worktree](Git-Worktrees.md)) for the issue.
 2. **Draft PR** — push early and open a draft pull request. Link it to the issue. This makes progress visible and attaches CI from the start.
 3. **Implement** — work through the checklist. One logical change per commit. Update the issue as each task completes.
 4. **Test locally** — don't push known failures to CI. Push work as far inward as it can go.

docs/Ways-of-Working/index.md

@@ -13,6 +13,7 @@ This section documents the principles, processes, and norms that every contribut
 - **[PR Format](PR-Format.md)** — Pull request title, description, change types, and labels.
 - **[Commit Conventions](Commit-Conventions.md)** — How we write commit messages.
 - **[Review Etiquette](Review-Etiquette.md)** — Tone, scope, severity prefixes, and how to disagree well.
+- **[Git Worktrees](Git-Worktrees.md)** — Bare-clone + worktree layout for parallel, conflict-free development.
 - **[README-Driven Context](Readme-Driven-Context.md)** — Why the README is the front door and the source of truth.
 
 ## Who this is for