When two Claude sessions edit the same docs-strategy file in parallel, the second-writer’s git add -A will silently scoop up the first-writer’s changes under the second-writer’s commit message — producing a misleading commit-message that violates global CLAUDE.md §13 No-Lies.
Why: Real incident on 2026-04-28T18:00. While running the test-suite doc-reconciliation pass, a concurrent docs-strategy session bumped arch-state to v3.5 with master-plan-v1.6 + state-vs-orchestration boundary work + a new outreach/mlp-stephen-attree-mockups.md file. My git add -A packaged all of that under my commit message “arch-state v3.5 + test-suite-pointer canonical pin → 1.2 — code-inheritv2-test-suite doc-reconciliation pass” (commit 2cf917f). The actual test-suite doc-reconciliation arch-state row was never written until the corrective v3.6 commit (2b81b1a). The lie was caught immediately on inspection (3 files changed = wrong stat for what I claimed) and corrected via a v3.6 row explicitly acknowledging the misrepresentation. The active-work-log convention (per global CLAUDE.md §7) is the correct mitigation but only works if both sessions actually use it; this session did not scaffold/use one for docs-strategy.
How to apply: When working in any repo where other Claude sessions might be running (especially shared/cross-cutting repos like docs-strategy, docs-admin, brand-architecture):
- Always scaffold + use
~/.claude/projects/<project-slug>/memory/project_active_work.mdper global CLAUDE.md §7 parallel-sessions discipline - Use specific
git add docs/file1.md docs/file2.md(named files only); nevergit add -Aorgit add . - Before commit: run
git status --shortand confirm only your intended files are staged - After commit:
git show --stat HEADand verify the file count matches your intent - If the count is wrong: corrective commit with explicit acknowledgement of the misrepresentation in the message body (per CLAUDE.md §13 No-Lies)