Preserve query projection on shadowed composite actions #231

New issue

Open

opened 2026-07-15 09:23:58 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-15 09:23:58 +00:00

Member

Needed follow-up: either let composite actions accept the same response projection flag as generated leaves, or add a specverb way to pin fixed query arguments on a generated leaf while preserving the leaf's normal flags. The concrete motivating command was:

ward ops forgejo action-run list coilyco-flight-deck ward --limit 3 --output json --query 'workflow_runs[].{id:id,status:status,commit_sha:commit_sha,html_url:html_url,updated:updated,started:started,stopped:stopped}'

With the safe shadow, the command no longer risks unbounded listing, but --query is rejected.

The aos fix for agentic-os#575 had to shadow the generated Forgejo action-run list leaf with a composite action so calls always include page=1 when --limit is used. That prevents Forgejo from returning the whole Actions run history, but it also drops the generated leaf's universal --query flag because composite actions currently expose --output but not --query. Needed follow-up: either let composite actions accept the same response projection flag as generated leaves, or add a specverb way to pin fixed query arguments on a generated leaf while preserving the leaf's normal flags. The concrete motivating command was: ward ops forgejo action-run list coilyco-flight-deck ward --limit 3 --output json --query 'workflow_runs[].{id:id,status:status,commit_sha:commit_sha,html_url:html_url,updated:updated,started:started,stopped:stopped}' With the safe shadow, the command no longer risks unbounded listing, but --query is rejected.