You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[AW Top 10] 02 Fix brittle safe-outputs conformance checks #70817
Several conformance checks fail because they match literal source substrings that harmless refactors changed, or flag telemetry-only fields and missing description markers.
Implementation scope
Update the checks to use structural matching for the enforceCommentLimits signature and retry guard ordering, scope the cross-repo rule away from telemetry renderers, add the constraints marker to the add_comment tool description, and address the low usability gaps.
Done when
The checker passes on the current code for SEC-005, TYPE-016, PTI-005 and MCE-001.
The add_comment tool description contains the required constraints disclosure.
Why now
Five reports from one conformance run share a cause of checker versus implementation drift, and one coordinated change clears the recurring failures; severity labels may overstate the actual risk.
No corroborating AW discussion; evidence comes from the source issues.
Unchanged AW sources close only after this summary is completed. Newer source activity and not-planned retirement do not trigger source closure. Assigned summaries are frozen; unassign to allow reclustering.
Activity