Run manifest verifier
Check whether an input, output, and saved settings still match the SHA-256 receipts from one DevAwesome workbench run.
Choose all three files. They stay in this browser tab.
—
Start with MATCH. Then break the output.
Load the manifest, original input, and expected output together. The verifier should return MATCH. Replace only the output with the changed fixture to reproduce OUTPUT CHANGED.
This is a synthetic fixture. The manifest stores hashes and settings, not the CSV contents.
How it works
Use the example first, then replace it with your own input. Check the result before you copy or download it.
- 01
Choose the run manifest downloaded from a DevAwesome workflow.
- 02
Choose the exact original input and generated output files.
- 03
Verify the three receipts. MATCH means the input, output, and embedded settings match this manifest.
What the tool changes
- DevAwesome run-manifest schema version 1
- Supported keyword, crawl-list, indexability, MCP payload, and MCP session workflow versions
- UTF-8 text with CRLF and CR normalized to LF before hashing
- Separate input, output, and settings results
What to check yourself
- A matching receipt shows content equivalence under the declared normalization. It does not prove authorship, creation time, or that the workflow result was correct.
- The verifier cannot reconstruct a missing input or output from a hash.
- A manifest from an unsupported workflow version is not silently accepted.
Technical reference
These are the specifications used for the tool's rules and terminology.