Skip to content

feat: pure zero-LLM workflows can set a content status#140

Open
lufen wants to merge 1 commit into
superdesigndev:mainfrom
lufen:feat/workflow-status
Open

feat: pure zero-LLM workflows can set a content status#140
lufen wants to merge 1 commit into
superdesigndev:mainfrom
lufen:feat/workflow-status

Conversation

@lufen

@lufen lufen commented Jul 15, 2026

Copy link
Copy Markdown

feat: pure zero-LLM workflows can set a content status

Adds an optional status field (new|resolved|nothing-new — the same
vocabulary an agent sets via loopany report --status) that a pure
workflow return value can set directly, since only a workflow calls
the final report itself with no agent in the loop.

  • daemon: WorkflowResult.status + validation in runWorkflow(); passed
    through ReportBody in the pure-workflow reportRun() call
  • server: RUN_STATUSES whitelist; report()'s body type gains status?;
    both the normal finalize path AND the reconcile/late-wake-report
    path persist a claimed status (the reconcile branch was previously
    missed, which could let a stale nothing-new workflow re-trigger a
    notification via shouldNotify on a late wake-report)

This lets the dashboard's timeline render green for a healthy
workflow-only run (previously only an agent's report --status or
finishLoop() could ever set status, so pure workflows could never turn
a box green).

Adds an optional status field (new|resolved|nothing-new — the same
vocabulary an agent sets via `loopany report --status`) that a pure
workflow return value can set directly, since only a workflow calls
the final report itself with no agent in the loop.

- daemon: WorkflowResult.status + validation in runWorkflow(); passed
  through ReportBody in the pure-workflow reportRun() call
- server: RUN_STATUSES whitelist; report()'s body type gains status?;
  both the normal finalize path AND the reconcile/late-wake-report
  path persist a claimed status (the reconcile branch was previously
  missed, which could let a stale nothing-new workflow re-trigger a
  notification via shouldNotify on a late wake-report)

This lets the dashboard's timeline render green for a healthy
workflow-only run (previously only an agent's report --status or
finishLoop() could ever set status, so pure workflows could never turn
a box green).
@lufen lufen force-pushed the feat/workflow-status branch from 205c218 to c0fc65c Compare July 15, 2026 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant