📖About

The SST scanner records its run only in the SST scans table, not as a droid_runs row, so the Daily Process Sweep (which reads droid_runs) sees sst-scan-01 as never-ran. Wrap the scanner main() to call create_run at start and update_run(completed/failed) at end, keyed to droid sst-scan-01, best-effort so audit never breaks the scan.

✅Success criteria

• SST scanner writes a droid_runs row (started) on run and updates it to completed/failed at end, keyed to sst-scan-01 (must_have)
• A real droid_runs row for sst-scan-01 with status=completed is observed after a scan (must_have)