docs(agent-guides): fix section references after numbering sync
This commit is contained in:
parent
d7277a3b40
commit
9410e4e78e
2 changed files with 2 additions and 2 deletions
|
|
@ -232,7 +232,7 @@ Use Git worktrees to isolate concurrent agent/human tracks safely and predictabl
|
|||
- Keep each worktree on a single branch; do not mix unrelated edits in one worktree.
|
||||
- Run validation commands inside the corresponding worktree before commit/PR.
|
||||
- Name worktrees clearly by scope (for example: `wt/ci-hardening`, `wt/provider-fix`) and remove stale worktrees when no longer needed.
|
||||
- PR checkpoint rules from section 6.3 still apply to worktree-based development.
|
||||
- PR checkpoint rules from section 6.1 still apply to worktree-based development.
|
||||
|
||||
### 6.3 Code Naming Contract (Required)
|
||||
|
||||
|
|
|
|||
|
|
@ -232,7 +232,7 @@ Use Git worktrees to isolate concurrent agent/human tracks safely and predictabl
|
|||
- Keep each worktree on a single branch; do not mix unrelated edits in one worktree.
|
||||
- Run validation commands inside the corresponding worktree before commit/PR.
|
||||
- Name worktrees clearly by scope (for example: `wt/ci-hardening`, `wt/provider-fix`) and remove stale worktrees when no longer needed.
|
||||
- PR checkpoint rules from section 6.3 still apply to worktree-based development.
|
||||
- PR checkpoint rules from section 6.1 still apply to worktree-based development.
|
||||
|
||||
### 6.3 Code Naming Contract (Required)
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue