📖 [Docs]: Emphasize parallel agentic work in the Git Worktrees page

[Marius Storhaug (MariusStorhaug)]

What

Adds a "Why this matters: working agentically in parallel" section to the Git Worktrees page, stating plainly why the bare-clone + worktree layout is the default for local development: running several agents at once, each on a different issue in its own worktree.

Why

Follow-up to #41. That page covered the mechanics (layout, remotes, setup, cleanup) but under-stated why worktrees are the default rather than an occasional convenience. Reviewing how ai-platform uses worktrees in practice — its buildit orchestrator fans out one worktree per topic and dispatches builder agents in parallel, integrating through the normal branch/PR flow — the defining value is parallel agentic work on multiple issues at the same time. This makes that explicit.

Change

• New section framing worktrees around parallelism: one worktree per issue / one agent per worktree; no stashing, branch-switching, or waiting; fan out then integrate.
• Reuses the existing #42/#99 worktree examples and links to Agentic Development and Branching and Merging.
• No nav or structural changes; existing content untouched.

Index check, link check, and markdownlint all pass locally.

[Copilot]

Pull request overview

Adds a new section to the Git Worktrees documentation that explicitly explains why the bare-clone + worktree layout is the default in this repo: enabling safe, parallel agentic work across multiple issues at once.

Changes:

• Adds “Why this matters: working agentically in parallel” to frame worktrees around parallelism (one worktree per issue/agent).
• Connects the parallelism narrative back to the normal branch/PR integration flow via an existing Branching-and-Merging link.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.