From 9410e4e78ec43d9fb4af61569067ef3d673acc34 Mon Sep 17 00:00:00 2001 From: Chummy Date: Wed, 18 Feb 2026 17:30:14 +0800 Subject: [PATCH] docs(agent-guides): fix section references after numbering sync --- AGENTS.md | 2 +- CLAUDE.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 763fe92..d892a60 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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) diff --git a/CLAUDE.md b/CLAUDE.md index 5103fc8..05098f3 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -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)