Skip to content
This repository was archived by the owner on Apr 5, 2026. It is now read-only.

Commit 258062e

Browse files
HerbHallclaude
andcommitted
docs(rules): add KG#111 ext (MD029 list break) and KG#184 (URL label drift)
Also fixes pre-existing MD022 violation at KG#25 subsection. Closes #577 Co-Authored-By: Claude <noreply@anthropic.com>
1 parent b61bd03 commit 258062e

1 file changed

Lines changed: 15 additions & 1 deletion

File tree

claude/rules/known-gotchas.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: Known gotchas and platform-specific issues. Read when debugging unexpected behavior.
33
tier: 2
4-
entry_count: 52
4+
entry_count: 54
55
last_updated: "2026-03-30"
66
---
77

@@ -143,6 +143,7 @@ All parallel agents write to the same working directory. Sort into branches via
143143

144144
**Issue:** Two parallel worktree agents both modifying a shared registration file (e.g. `tools.go`, `router.go`, `routes.go`, skill routing tables) create a two-block rebase conflict when the second branch is rebased onto main after the first merges.
145145
**Fix:** When planning parallel agents that all add to a shared registration file, assign file ownership -- only ONE agent touches the shared file. Others wait or use a different integration point. Extends the general parallel-agent rule with the most common specific case.
146+
146147
### Worktree isolation is partial when launching 5+ agents simultaneously
147148

148149
**Issue:** When launching 5+ parallel agents with `isolation: "worktree"`, not all agents receive isolated worktrees. In observed sessions, only 2-3 of 5 agents got proper worktree directories. The other agents worked in the shared main working directory, causing cross-contamination (commits appearing in wrong branches, agents needing stash-based sorting).
@@ -327,6 +328,11 @@ Windows CRLF (`\r\n`) causes silent failures across multiple tools. Three known
327328
**Issue:** Agent markdown tables have MD056 errors: pipes in code spans parsed as separators, or missing columns.
328329
**Fix:** Run `npx markdownlint-cli2` on agent `.md` files. Use `&#124;` for pipes in cells. Verify column counts.
329330

331+
### MD029 ordered list numbering breaks after fenced code blocks
332+
333+
**Issue:** When writing step-by-step workflows with embedded fenced code blocks (common in CONTRIBUTING.md), the list item after the code block is renumbered to `1.` by the parser. MD029 (ordered-list-item-prefix) flags it as misnumbered because the code block breaks list context.
334+
**Fix:** Convert the post-code-block step to prose paragraph instead of a numbered list item. Alternative: ensure blank line + correct next number after the code fence closing.
335+
330336
## 115. TypeScript API Interface Phantom Field Drift from Go Backend
331337

332338
**Added:** 2026-03-09 | **Source:** Samverk | **Status:** active
@@ -684,3 +690,11 @@ curl -X POST "http://<gitea>/api/v1/repos/<owner>/<repo>/pulls/<N>/merge" \
684690

685691
Alternatively, use branch protection rules that match check run names instead of commit status contexts — but the mismatch is architectural and `force_merge` is the practical workaround.
686692
**See also:** KG#123 (Gitea API and Actions gotchas)
693+
694+
## 184. URL Migration Leaves Surrounding Text Labels Stale
695+
696+
**Added:** 2026-03-30 | **Source:** DevKit | **Status:** active
697+
698+
**Platform:** All (text processing)
699+
**Issue:** Bulk URL replacement (e.g., `github.com` -> `gitea.herbhall.net`) changes the URL but leaves surrounding text labels unchanged. "Check GitHub Issues" becomes misleading when the link points to Gitea.
700+
**Fix:** After URL migration, grep for the old service name near new URLs to catch stale labels: `grep -n "GitHub" <file> | grep -i "gitea"`.

0 commit comments

Comments
 (0)