docs(evidence): orchestrator surfaces — rendered + recorded + live task lifecycle evidence (2026-07 campaign) - #11650
Merged
Conversation
…sk lifecycle evidence (2026-07 campaign) Evidence bundle for the #11028 orchestrator campaign: - desktop/ + mobile/ screenshots of springboard, orchestrator, task-coordinator, and coding-cockpit surfaces (1440x900 and 390x844) - flow/ series: a real task driven through the cockpit in Claude subscription mode — starting -> open -> active (sub-agent Kira executing "Write hello.txt") -> validating - video/orchestrator-walkthrough.webm: 9m03s recording of the full walk (losslessly remuxed to finalize the container) - logs/: structured backend logs correlating to the original flow and the mobile re-capture, plus the mobile browser console - capture.mjs: the Playwright tooling that produced everything - README.md: per-artifact manifest, honest about the duplicated flow frames, the missing terminal-status frame, and the lost desktop console log Mobile shots were taken after a stack reboot and show the same task persisted (validating, 1.9K tokens) — cross-restart persistence proof. Refs #11028 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…bundle The logs/ correlating artifacts (backend structured logs + browser console) were silently excluded by the repo *.log ignore rule; they are part of the evidence manifest and must ship with it. Refs #11028 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
Contributor
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
lalalune
added a commit
that referenced
this pull request
Jul 2, 2026
…eted-state evidence (#11028) (#11699) * fix(orchestrator): register the task-detail + control route templates that 404'd over HTTP While driving a real coding task to completion for #11028 evidence, the task- detail pane hung on "Loading task…": the orchestrator UI's fetchDetail does Promise.all([getCodingAgentTaskThread, listOrchestratorTaskTimeline]), and GET /api/orchestrator/tasks/:taskId/timeline 404'd — rejecting the whole fetch so Approve/Reject/Restart controls were unreachable. Root cause: the handlers for timeline, auto-validate, retry-turn, rerun-from-event, restart, restart-with-edited-plan, and plan-revisions exist in api/orchestrator-routes.ts but were never listed in CODING_AGENT_ROUTE_PATHS, which the runtime route matcher needs as exact path templates to reach them. Same class of gap already fixed for credential paths (setup-routes-credential- paths.test.ts); this adds the missing task-scoped templates + a guard test. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(evidence): orchestrator task reaches terminal 'done' state — screenshots + recording + deliverable (#11028) Closes the gap #11650 left (its task stalled in 'validating'). A real coding task 'Write hello.txt' driven through the live orchestrator on the claude ACP sub-agent reached finalStatus:done: UI shows the green 'done' badge + task/sub- agent completion checks; task-result.json shows artifactsVerified:true, all 3 acceptance criteria met, a live grilling test (wc -c hello.txt = 3 bytes 'hi\n'); backend log shows [swarm-synthesis] '1 completed'; the deliverable hello.txt is committed. Includes the walkthrough .webm + backend/console logs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
7 tasks
Contributor
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
UI evidence bundle for the 2026-07 orchestrator campaign. Everything below is real rendered UI from a live
bun run devstack (based9d1a47ccd), driven with Playwright via the committedcapture.mjs— including a live orchestrator task executed by a real Claude-subscription sub-agent. Full per-artifact manifest (with every honest gap called out):README.md.Live task lifecycle (the crown jewel)
A real task — "Create a file named hello.txt containing exactly the text 'hi' in the workspace. Nothing else." — created through the Coding Cockpit in Claude · subscription mode, then screenshotted at each server-reported status flip (
GET /api/orchestrator/tasks).1. Form filled, Claude mode selected
2. Start agent clicked → "Starting…" (task + session landing server-side)
3. Status
active— Task rooms "1 live", sub-agent Kira[claude]executing the deliverable ("Write hello.txt")4. Status
validating— sub-agent moved to a tool call while the orchestrator validatesHonesty notes:
flow/03andflow/04-…-1-openare byte-identical to frame 2 (shot before the pane re-rendered); the original capture process died mid-poll so there is no terminal-status frame. The loop is closed by two independent artifacts:logs/backend.logshows[swarm-synthesis] … (1 completed, 0 stopped, 0 errored)for this run, and the mobile shots below show the same task persisted across a full stack reboot.Rendered surfaces — desktop (1440x900)
Rendered surfaces — mobile (390x844, dpr 2) — captured AFTER a stack reboot
The same task from the flow above is still there:
validating, 1.9K tokens · $0.00, sub-agent trace intact — real cross-restart persistence evidence.Video + logs
video/orchestrator-walkthrough.webm— 9m03s, 1440x900 VP8, the full desktop walk + live task run (losslessly remuxed to finalize the container; all 13,575 frames decode cleanly).logs/backend.log— structured backend log of the original flow sitting ([boot] @elizaos/plugin-agent-orchestrator loaded,[swarm-synthesis] … 1 completed,[TaskWatchdogService] … prodding).logs/backend.mobile-recapture.log+logs/console.log— backend + browser console for the mobile re-capture sitting.Refs #11028
🤖 Generated with Claude Code