run-record
Installation
SKILL.md
Run record
Reports on the gate in the current repository from the files the runner writes. Read only, except step 6.
Where the records are
| File | What it holds |
|---|---|
gate/latest.json |
The last 100 runs (time, trigger, commit, overall, open findings, warnings) and every finding with its status, in git; requirement_states when the gate has a requirements file |
gate/summary.md |
The last run as a table, open and recently closed findings, recent history |
gate/runs/<timestamp>-<id>.json |
One full record per run: each check's result, detail, evidence and hits, and the sha256 of run.py, the config, every rule file, the requirements file and every reporter. Local runs keep it here; CI runs upload it as the artifact gate-run-<run id>-<attempt> for 90 days. With the OSCAL reporter, <timestamp>-<id>.oscal.json sits next to it |
A finding names its rule under check, and under rule the sub-rule of the hit when the check reports several. Findings written by run.py 0.1 carry the rule id under rule; the next run moves it to check and keeps the old id as former_id.
Fetch a CI record with gh run download <run id> -n gate-run-<run id>-<attempt> -D gate/runs/.