The vast majority of comments are not insightful. They either re-state the obvious, or make invalid or useless objections.
Comments with "Error" severity are included under the "Security" tab, where serious static analysis/dependency CVEs on the implementation normally go. This is not the right place for opinions about comments in the spec, even if they were insightful.
Causes spurious CI failures on forks, where we do the majority of our work, for good isolation and safety reasons.
In its current form, this degrades useful signals (CI status, Security notifications), without substantially improving spec comments.
This may be useful as a locally-run, manual pass, in a context where a contributor is looking to spend some time cleaning up the spec comments. But it is unsuitable as a CI step.
Reasons for removal:
In its current form, this degrades useful signals (CI status, Security notifications), without substantially improving spec comments.
This may be useful as a locally-run, manual pass, in a context where a contributor is looking to spend some time cleaning up the spec comments. But it is unsuitable as a CI step.