Verify a lockfile

Check canonical content integrity, catalog release drift and missing deployment IDs.

Request

const verification = await allm.lockfiles.verify({
  content: lockfile,
  expectedSha256: process.env.ALLM_LOCKFILE_SHA256,
  idempotencyKey: "ci-lockfile-verify-1842",
});

if (!verification.valid) process.exit(1);

Response

The response distinguishes digest mismatch, catalog release drift and deployment removal. A changed release alone is a review signal, while valid=false is a blocking verification result.