Feature Request: Prevent score regression on publishing

[lucasavila00]

Thanks for building jsr, I loved the score feature.

I wonder if the CLI could prevent score regressions, or prevent publishing if certain requirements are not met.

For instance, I have a published package where all symbols have documentation and all entry points have documentation. I would like it to continue to have the docs for all symbols, but I can see myself forgetting to add them.

So, I'm proposing the CLI add a mechanism to either prevent score decrease or a --require-docs-percentage 100 parameter. This would work similarly to test coverage tools.

[lucasavila00]

Related: #199

[lucacasonato]

The real solution would be to compute the score locally and check (see #199). For now we are thinking we can just upload this flag together with the publish tarball when a user runs jsr publish and then check server-side. If the docs percentage (or other parts of the score) are not high enough, we can just fail the publish and the user can try again.