@har:checkout warns that no recorded file exists — is there a way to declare it up front?

Writing the scenario before recording the traffic, which I thought was the intended order:

⚠ features/checkout/payment.feature:9  tags/har  @har:checkout has no recorded file under har/<env>/checkout.har (or checkout.api.har) yet.

It is only a warning and I understand why — the file genuinely is not there yet. But we run sdods lint --strict in the pipeline, so the warning is an error there, and the branch cannot merge until somebody records against staging.

Is there something that says "recorded on purpose later", or do we just carve an exception into the pipeline for files under features/checkout/? Recording first would mean writing the scenario twice.