Skip to content

refactor(errors): one instruction per rule, no fixed layer names - #2113

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

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

Conversation

@braboj

@braboj braboj commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

Raises backend/errors from 91.7 to 98.3 with one instruction per rule.

Section Change
Lead-in Five broken lines naming two file paths → one sentence naming the templates
Classification Lead-in and both mapping rules shortened; table unchanged
Propagation Repository / service / handler layer labels → data-access code, domain errors, one central mapper
Recovery Timeout, circuit breaker, degradation, consistency each one instruction; MUST kept
External failures 504 vs 502 stated directly; retry rule shortened
Unexpected errors MUST kept on the outermost catch

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

Rules with trailing explanations become single instructions. The
propagation rules name data-access code, domain errors and one central
mapper instead of a repository, service and handler layering. Both MUST
rules stay.

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