feat(webui): add the per-run task detail page
A per-task page at #/tasks/{id} with tabs for the attempt's stages and log, changed
files, configuration and a raw debug view. Reachable from the task list, deep
linkable via ?tab= and ?attempt=, and reload safe. Existing URLs (#/tasks?task=N
and #/tasks?status=...) are unchanged.
- A stage rail per attempt: name, duration, terminal status and error text, with
unattributed events surfaced and the agent's own verdict shown separately.
- No pass/fail badge and no exit code anywhere: the backend has neither, and a stage
that returned nil after producing a poor diff is a success. Status word, duration
and error text are shown instead.
- The log pane filters by attempt, stage and level, states the coverage caveat for
stage filters (agent and tool output records no stage), and keeps the three read
outcomes distinct: no log reader in this deployment, no file for this attempt, and
no entries matching the filter.
- Retry is labelled as a new run and its confirm says the previous attempt's commits
are discarded, because it hard-resets the branch onto the base.
- An absent capture reads "not captured for this run" rather than implying nothing
changed, and no elapsed-run figure is shown since only per-stage durations exist.
- The events cache is invalidated on retry (it previously kept the ended attempt's
events) and the log cache is keyed by attempt, so two attempts cannot be conflated.
- ui/dist is rebuilt and committed: the gate runs the node tests but never rebuilds
the bundle, so a stale one would otherwise ship behind a green gate.
- docs/prds/task-run-detail.md records the surface and its limits, and
docs/architecture/observability.md describes it alongside the read endpoints.
Both new vocabularies are pinned by tests on each side (config schema, change
statuses) so a one-sided rename fails a test instead of silently degrading the page.
This commit is contained in:
1 parent
862ac46e8b
commit
7414713d61
33 files changed
+4195
-91
No files matched your search
@@ -95,6 +95,9 @@ export const api = {
|
||||
tasks: () => request("/api/tasks"),
|
||||
taskMeta: () => request("/api/task-meta"),
|
||||
task: (id) => request(`/api/tasks/${id}`),
|
||||
taskAttempts: (id) => request(`/api/tasks/${id}/attempts`),
|
||||
taskChanges: (id, params) => request(`/api/tasks/${id}/changes` + qs(params)),
|
||||
taskDebug: (id, params) => request(`/api/tasks/${id}/debug` + qs(params)),
|
||||
taskAction: (id, action) => request(`/api/tasks/${id}/action`, { method: "POST", body: { action } }),
|
||||
setup: () => request("/api/setup"),
|
||||
capabilities: () => request("/api/capabilities"),
|
||||
|
||||
@@ -9,6 +9,18 @@ import { el } from "./dom.jsx";
|
||||
* second distinct consumer".
|
||||
*/
|
||||
|
||||
// The level filter vocabulary. Server-side level filtering takes a CSV of
|
||||
// levels (`splitCSV` in internal/webui/api_tasks_logs.go), so the combined
|
||||
// options are a wire concern too, not a display choice. It lives here because
|
||||
// both the daemon log page and a task attempt's log pane filter by level.
|
||||
export const LOG_LEVELS = [
|
||||
{ value: "", label: "All levels" },
|
||||
{ value: "ERROR", label: "Errors" },
|
||||
{ value: "WARN,ERROR", label: "Warnings and errors" },
|
||||
{ value: "INFO,WARN,ERROR", label: "Info and above" },
|
||||
{ value: "DEBUG", label: "Debug only" },
|
||||
];
|
||||
|
||||
export function levelKind(level) {
|
||||
switch ((level || "").toUpperCase()) {
|
||||
case "ERROR":
|
||||
|
||||
Reference in new issue
Block a user