Repository navigation
feat(workflows): schedule workflows and inspect each occurrence's run - #36
Conversation
5e86941 to
f09807b
Compare
f09807b to
6f05f0a
Compare
6f05f0a to
fdd61b1
Compare
|
Primary browser evidence for #29 at eae10a9. Parent-client before image is EDF; ordinary scheduling/Graph captures are source-qualified FDD reuse, and corrected read-only captures use the exact tested/committed EAE bytes. External provider turns/forge are replay; auth, services, scheduler receipts, workspaces, actual Bun check and native/gate state remain real. No live provider/forge, second physical device, hardware-touch or uninterrupted reconnect claim. Before: approved #28 host offered prompt schedules, captured from EDF client.
After: workflow target, project/workspace and task inputs; dispatch-time revision wording.
Accepted3/3 reports with2/3 reviewers settled: scheduled join still waiting.
Scheduled parallel Graph repeated once and reached the actual bounded Human gate.
Dispatch succeeded while workflow awaited a human decision.
Actual HTTPS revision2 occurrence completed after UI approval.
Restored plugin: failed dispatch/no run, completed revision2 and older running revision1.
390CSS history wraps saved revision evidence and exact run links.
Plugin removed: retained schedule with actionable unavailable-target text.
Before permission correction: read-only Actions trigger incorrectly blocked history.
Original24second Run now/dispatched/navigation recording; loaded history is pictured separately. pr36-run-now-history.mp4After permission correction: read-only history is available; mutation items are disabled. The normal re-pairing permission notification remains visible.
Corrected read-only history at390CSS: authoritative statuses, revisions and exact links remain accessible.
Implementation: Claude Opus5.5 / Claude Code and GPT-6.1-Sol / Codex. Primary integration, verification and publication: GPT-6.1-Sol / Codex in T3 Code. Independent current review: GPT-6-Astra / Codex with Gilfoyle, R2 APPROVED Final approval: independent GPT-6-Astra/Gilfoyle R2 and ROOT approve |
Adds a generic plugin schedule-target contribution to the existing Scheduled tasks controls, which the workflows plugin fills with a saved workflow, workspace, and bounded task. Each occurrence starts through the same saved-workflow start service keyed by its durable occurrence identity, and a bounded occurrence history links each dispatch to its exact run with dispatch and workflow status kept separate. The host scheduler remains the only timing owner. Refs #29 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Link schedule history to each occurrence's recorded project, refresh history only on real receipt or run state changes with a lighter read, cover the host dialog's target routing, keep recreated schedules from inheriting old receipts, and align the unavailable-target guidance. Refs #29 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…real seams Redact titles, reasons, and receipt errors in schedule history, move the host dialog's plugin submission decision into tested pure logic, keep the server as the owner of existing dispatch targets, and withhold Open run for runs whose project was removed. Refs #29 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preserve scheduling target identity when capabilities disappear and retain focused history, permission and editor compatibility proofs. Co-authored-by: GPT-6.1-Sol <noreply@openai.com>
5e21740 to
a134a23
Compare















Summary
Scheduled tasks can select a saved workflow, and each occurrence links to its exact run.
Refs #29 and parent #3. Final layer of #30 → #31 → #34 → #35 → #36. Head
5e21740b47a2b9dc4e82043751699e9f68c94a20is based on approved #35edf703c3bb3949c807e29c119b4f13b39616a85a, on main294aa94c427c2bd9690af172f07374bfc9877a9c.The generic target contribution provides workflow/project/workspace selection and bounded task input. The host owns timing. Each occurrence resolves the saved revision at dispatch; older runs retain their snapshot. Durable redelivery reuses the same start service and run. Bounded, authorized history preserves exact project/run links and separates dispatch from workflow outcome. Read-only users can open history while mutations remain guarded. Prompt schedules remain usable.
Evidence
External provider turns/availability and forge input are replay; authorization, registered services, scheduler receipts, SQL, workspaces, actual Bun checks, compiled client and native/gate state are real. No live provider/forge, second physical device, hardware-touch, scale benchmark, uninterrupted automatic reconnect or positive human-comprehension claim. Reopening exact pages recovers after disconnection; HTTP-scope replay restart is distinct from actual provider-process-loss tests.
Merge Danger
Door: two-way. Contributions/UI can be reverted; already dispatched runs retain their authoritative durable history.
Blast Radius: scheduling. Generic target controls, saved workflow starts and bounded occurrence history. No new workflow engine or timing owner.
Implementation: Claude Opus 5.5 / Claude Code and OpenAI GPT-6.1-Sol / Codex. Current orchestration, integration and primary client verification: GPT-6.1-Sol / Codex in T3 Code. Independent current review: GPT-6-Astra / Codex with Gilfoyle, R2 APPROVED
5e21740b47a2b9dc4e82043751699e9f68c94a20.