cargo test shouldn't need the --locked flag (here & other places)

it would suffice to verify cargo lock updatodateness once in single job

Yes, I added it everywhere to let all these jobs fail early when the lock file needs to be updated (to save CI resources), because in that case all those jobs are going to have to run again when the lock file is updated. But I'm also fine with only keeping it for one check.

Fail-fast is not unreasonable, i didn't think about this.

otoh one could say same thing about formatting issues. there is definitely tradeoff between conserving CI resources and maxing our single PR feedback signal.
let's put cargo.lock consistency in the "formatting bucket", ie reuse previous design decision for now. i am open to revisiting it.

Ok, I'll just keep it for

Edit: I meant to link:

thanks!
can you please add a code comment there why --locked is useful?

152f1cf

this is a nice idea to only use --locked in one test 👍