fix(actions): explain run_id vs web run number; honor limit=; strip event payloads from listings #227

Merged

hexajon merged 1 commit from issue-157-actions-run-fixes into main

2026-07-17 18:08:24 +00:00

hexajon commented

2026-07-17 18:08:07 +00:00

(Migrated from codeberg.org)

Summary

Three madt_actions fixes. A 404 on run_get now explains that run_id is the API id from action=runs, not the sequential run number the web UI shows - previously the mismatch surfaced as a bare not-found. runs honors limit= with the standard pagination pattern. Raw run listings no longer embed multi-KB event_payload blobs (responses were reaching multi-MB); a single run's full payload stays reachable where the issue's criteria require it. Tests cover the enriched 404, the non-enriched other-error path, limit passthrough, and payload stripping.

Closes #157

## Summary Three madt_actions fixes. A 404 on run_get now explains that run_id is the API id from action=runs, not the sequential run number the web UI shows - previously the mismatch surfaced as a bare not-found. runs honors limit= with the standard pagination pattern. Raw run listings no longer embed multi-KB event_payload blobs (responses were reaching multi-MB); a single run's full payload stays reachable where the issue's criteria require it. Tests cover the enriched 404, the non-enriched other-error path, limit passthrough, and payload stripping. Closes #157