fix(forgejo-logs): speak the UI log-cursor route + add a ward verb #478

Merged
coilysiren merged 1 commit from fix/actions-logs-bridge into main 2026-07-12 06:39:12 +00:00
Owner

The API log route 404s on Forgejo 15 even for fresh runs (found repeatedly during tonight's stability session). The bridge now GETs the attempt-qualified job page for its step list, POSTs logCursors to the same URL, and renders step-annotated logs. Adds ward exec forgejo-actions-logs. Verified live against ward run 1828. Closes #476.

The API log route 404s on Forgejo 15 even for fresh runs (found repeatedly during tonight's stability session). The bridge now GETs the attempt-qualified job page for its step list, POSTs logCursors to the same URL, and renders step-annotated logs. Adds `ward exec forgejo-actions-logs`. Verified live against ward run 1828. Closes #476.
fix(forgejo-logs): speak the UI log-cursor route + add a ward verb (closes #476)
All checks were successful
ci / gate (pull_request) Successful in 9s
89f066253a
The documented API log route 404s on Forgejo 15 even for fresh runs, so
the bridge now does what the web UI does: GET the attempt-qualified job
page for its embedded step list, POST logCursors to the same URL, and
render every step's lines under a status-annotated header. The
/attempt/{n} segment is load-bearing - without it the handler resolves
attempt 0 and reports the task missing. attempt becomes an optional CLI
arg (default 1), output goes through stdout.buffer so a cp1252 console
cannot crash on log emoji, and `ward exec forgejo-actions-logs` mounts
the bridge as a verb. Verified live against ward run 1828.

closes #476

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016Cym37PsLtA61parAQyeAw
Sign in to join this conversation.
No description provided.