Jesper Schulz-Wedde d0e4298518 Define mandatory suggested-code classes ... Follow-up to BCQuality#22. The previous contract made suggested-code expected for mechanical findings, but still left too much judgement to the model. In the synthetic benchmark, BCQ produced omission reasons for 11 mechanical-looking findings instead of suggestions. Add explicit must-suggest classes where omission is not allowed when location points to the affected line/range and the replacement can be expressed as one contiguous block: - missing OptionCaption - missing ToolTip - formatter-only casing/spacing defects - Count() existence/repeated-count fixes - unreachable/dead contiguous blocks - over-broad permission tokens with an obvious narrower token - obvious DataClassification additions - local Label moves when the target range includes both old and new declaration locations Update all AL leaf skills and al-code-review to reference these must-suggest classes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>		2026-05-28 16:40:14 +02:00
..
knowledge	Drop the two new KB articles from this PR	2026-05-28 10:57:23 +02:00
skills	Define mandatory suggested-code classes	2026-05-28 16:40:14 +02:00