Skip to content

fix(rules): supersede #4710 with md004 fix on top (Copilot P0)#4711

Merged
AceHack merged 2 commits into
mainfrom
fix/pr-4710-md004-continuation-line-2026-05-23
May 23, 2026
Merged

fix(rules): supersede #4710 with md004 fix on top (Copilot P0)#4711
AceHack merged 2 commits into
mainfrom
fix/pr-4710-md004-continuation-line-2026-05-23

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented May 23, 2026

Supersedes #4710 — carries its commit + an md004 fix on top.

Copilot P0 review on PR #4710 flagged that the new "Narrow exception" paragraph in .claude/rules/claim-acquire-before-worktree-work.md:402 had a continuation line beginning with `+ \`git branch -D \``. Per markdownlint MD004/ul-style guidance, `+` at line start inside an indented paragraph parses as a nested unordered list item and can fail CI.

What this PR contains

Closing #4710

#4710 will be closed once this PR lands — it's not redundant in terms of policy intent (this PR contains its commit), only in terms of the PR-as-mergeable-unit.

Test plan

🤖 Generated with Claude Code

AceHack and others added 2 commits May 22, 2026 22:29
…row forced-#6 exception (addresses PR #4709 P2 thread)

Codex P2 review on PR #4709 flagged a contradiction between three
statements in .claude/rules/claim-acquire-before-worktree-work.md:

1. The new 2026-05-23 "Non-deterministic under same conditions"
   paragraph authorizes single-retry-after-orphan-cleanup
2. The existing "no working mitigation today" line said no mitigation
   exists at all
3. The composite operational discipline step 7 said ABANDON when
   sub-case 4 is hit

Operational ambiguity: some agents would retry, others would abort.

Reconciliation makes the policy unambiguous:

- Default = ABANDON when sub-case 4 fires (preserved as authoritative
  in the composite discipline; preserved in the sub-case 4 mitigation
  block reframed as "no STRUCTURAL mitigation today")
- Narrow exception = single-retry-after-orphan-cleanup, AUTHORIZED
  ONLY at forced-#6 decomposition per holding-without-named-dependency
  counter, for sub-case 4 specifically (not sub-case 3), one retry
  only, and ABANDON applies absolutely if retry also fails
- The exception does NOT generalize to brief-ack #1-#5 (other
  pre-empt artifact shapes are available there; default ABANDON is
  correct)
- The exception does NOT generalize to sub-case 3 (pack-dir
  contention has no analogous timing-dependence evidence)

Both edits cross-reference each other so future-Otto reading either
location sees the full policy.

Co-Authored-By: Claude <noreply@anthropic.com>
…rses as nested list (MD004/ul-style)

Copilot P0 review on PR #4710 flagged line 402 of
.claude/rules/claim-acquire-before-worktree-work.md where the
continuation of the parenthetical "(rm -rf <wt-path>" began with
"+ git branch -D <branch>)". Per markdownlint MD004/ul-style
guidance in .github/copilot-instructions.md, a continuation line
starting with "+ " inside an indented paragraph parses as a
nested unordered list item and can fail CI.

Fix: reword the two-command sequence to use prose connectives
("run X then Y") instead of the "+" infix operator. Preserves
semantics: still a sequenced two-command cleanup.

Co-Authored-By: Claude <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 23, 2026 02:35
@AceHack AceHack enabled auto-merge (squash) May 23, 2026 02:36
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates .claude/rules/claim-acquire-before-worktree-work.md to reconcile the documented retry/abandon policy for saturation “sub-case 4” while also addressing a markdownlint MD004 (ul-style) failure mode caused by a continuation line starting with +.

Changes:

  • Reframes sub-case 4 mitigation as “default = ABANDON” with a clearly scoped forced-#6-only single-retry exception.
  • Rewords the orphan-cleanup parenthetical to use “then …” instead of + … at line start, avoiding MD004 nested-list parsing.

@AceHack AceHack merged commit 429d416 into main May 23, 2026
27 checks passed
@AceHack AceHack deleted the fix/pr-4710-md004-continuation-line-2026-05-23 branch May 23, 2026 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants