The jump-to-log-line affordance in #1157 is blocked on data, not on UI work. GET /api/tasks/{id}/logs answers entries, truncated, file, components, attempt, found (internal/webui/api_tasks_logs.go) and internal/logging/reader.go's Entry carries only ID/Time/Level/Message/Fields, so the client has no line index and no park-site position to jump to. The missing layer is internal/webui plus the logging reader. Do not substitute 'scroll to the first ERROR row in the loaded page' - the failure may not be in that page, which makes the affordance sometimes wrong rather than absent. Decide the wire shape (a park-site line index, or an absolute entry ordinal) before building the UI on it.
Close reason
Verified against the current transport and UI by the live local task-diagnostics browser check: persisted line IDs reach the client, Jump to log line selects the error filter and focuses the matching row. Missing logs report an explicit explanation. Regression check committed in 57456b3e.
Imported from beads archie-core-4pv3 · GitHub #1340 · type task · priority P2 · created 2026-09-30 · closed 2026-10-16
The jump-to-log-line affordance in #1157 is blocked on data, not on UI work. GET /api/tasks/{id}/logs answers entries, truncated, file, components, attempt, found (internal/webui/api_tasks_logs.go) and internal/logging/reader.go's Entry carries only ID/Time/Level/Message/Fields, so the client has no line index and no park-site position to jump to. The missing layer is internal/webui plus the logging reader. Do not substitute 'scroll to the first ERROR row in the loaded page' - the failure may not be in that page, which makes the affordance sometimes wrong rather than absent. Decide the wire shape (a park-site line index, or an absolute entry ordinal) before building the UI on it.
### Close reason
Verified against the current transport and UI by the live local task-diagnostics browser check: persisted line IDs reach the client, Jump to log line selects the error filter and focuses the matching row. Missing logs report an explicit explanation. Regression check committed in 57456b3e.
---
_Imported from beads `archie-core-4pv3` · GitHub #1340 · type task · priority P2 · created 2026-09-30 · closed 2026-10-16_
sam
added the mediumtask labels 2026-10-27 13:38:52 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The jump-to-log-line affordance in #1157 is blocked on data, not on UI work. GET /api/tasks/{id}/logs answers entries, truncated, file, components, attempt, found (internal/webui/api_tasks_logs.go) and internal/logging/reader.go's Entry carries only ID/Time/Level/Message/Fields, so the client has no line index and no park-site position to jump to. The missing layer is internal/webui plus the logging reader. Do not substitute 'scroll to the first ERROR row in the loaded page' - the failure may not be in that page, which makes the affordance sometimes wrong rather than absent. Decide the wire shape (a park-site line index, or an absolute entry ordinal) before building the UI on it.
Close reason
Verified against the current transport and UI by the live local task-diagnostics browser check: persisted line IDs reach the client, Jump to log line selects the error filter and focuses the matching row. Missing logs report an explicit explanation. Regression check committed in
57456b3e.Imported from beads
archie-core-4pv3· GitHub #1340 · type task · priority P2 · created 2026-09-30 · closed 2026-10-16