Skip to content

refactor(concurrency): pitfalls as instructions, no bracket directive - #2120

Open
braboj wants to merge 1 commit into
mainfrom
refactor/concurrency-score
Open

braboj wants to merge 1 commit into
mainfrom
refactor/concurrency-score

Conversation

@braboj

@braboj braboj commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

Raises backend/concurrency from 94.8 to 98.1. Its weak criterion was hedging, and its lead-in broke a repository rule.

Section Change
Lead-in [EXTEND: backend-concurrency] written in prose → "a stack template extends this one"; AGENTS.md 2.4 forbids the bracket form in prose
Pitfalls Five bold labels (deadlock, livelock, race, starvation, thread-local leak) → five instructions naming the fix and the failure
Pitfalls "fair scheduling where possible" → "where the runtime allows"
Observability Task-count rule shortened

Checks

  • Smoke 35/35; conformance 12 passed, 0 failed, 1 not applicable; readings read
  • Fork sync, redundancy audit, score ratchet, markdownlint, pre-commit hooks

No CHANGELOG entry: the rules are unchanged in meaning.

🤖 Generated with Claude Code

The pitfalls list names each fix as an instruction instead of a bold
label, and "where possible" names its condition. The lead-in states the
extension in prose instead of the directive's bracket form.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant