fix(forgejo-logs): speak the UI log-cursor route + add a ward verb #478
No reviewers
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/agentic-os!478
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/actions-logs-bridge"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 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