pub fn write_pending_verification_json(path: &Path) -> Result<(), Error>Expand description
Stamp only the common invocation-bound pending NO-RESULT report. This is
the same fixed operation used by the shared application and saved comparison;
terminal verdicts and their publication remain owned by the common driver.
Publish an explicit NO-RESULT record to path before verification starts.
This is what makes the artifact invocation-bound. write_verification_json
can only run once a verdict exists, but a --verify-json run has several
earlier exits (a run that fails to start, a rejected first-run status, a
SaBRe capture with zero DETLOG, a failed recording). If the caller reuses a
path, every one of those exits would otherwise leave the PREVIOUS
invocation’s record – possibly {"verified":true,"bitwise_parity":true} –
sitting there, readable as if it described the invocation that just failed.
Stamping a no-result first means the file always describes this run: it is
either the terminal verdict or an honest “no verdict reached”.