Release Evidence Gate

What it does

Check a release manifest for valid versions, checksums and recorded passing tests before a human publication decision.

How to use it

Give the assistant the concrete task and required inputs. This fictional request illustrates the contract; use your selected files and parameters for real work.

{
  "artifacts": [
    {
      "name": "demo",
      "version": "1.0.0",
      "sha256": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "testStatus": "passed"
    }
  ]
}

Output and verification

Creates a JSON report and, when applicable, CSV, Markdown or document artifacts in the current workspace. Inputs remain intact. Five offline tests cover the example, invalid input, actual CLI output, path boundaries and non-overwrite behavior. Live account, browser and visual results require separate verification.

Scope

Manifest fields do not prove a file or test is genuine. Verify files, signatures, installation and public downloads separately. Never equate a submitted marketplace version with public availability.