Make workflows executable and schedulable

[wmeddie]

Summary

• make manual workflow execution a first-class UI action from both the Automations list and workflow editor
• let New Work choose No workflow for a direct task or an agent-compatible workflow, passing the composer text as goal and opening the generated task
• add declared string, number, boolean, and json inputs with descriptions, defaults, required validation, and typed run forms
• add optional five-field cron triggers with saved inputs, persisted trigger state, atomic duplicate prevention, pause/resume controls, and visible trigger errors
• prevent connector-backed legacy workflows from running through the scheduler and skip paused cron occurrences when re-enabled
• update starter templates, workflow documentation, and the architecture decision record

Why

The workflow engine and run endpoint already existed, but users could not discover or operate them through XpressClaw. Definitions also lacked a caller-facing input contract or an automatic trigger that did not depend on the deferred channels model.

This makes workflows usable now while retaining compatibility with existing free-form workflow payloads. New Work offers workflows whose first executable step uses the selected agent and whose remaining required inputs have defaults; workflows needing a richer input form remain available from Automations. Legacy connector triggers and notification sinks remain readable but cannot be enabled, run manually, or started by the scheduler until channels return.

Validation

• npm run check
• npm run build
• full Playwright suite: 28 passed, including mobile coverage
• ./scripts/rustfmt.sh --check
• cargo test -p xpressclaw-core -p xpressclaw-server: 516 passed
• cargo clippy -p xpressclaw-core -p xpressclaw-server --all-targets -- -D warnings

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d51c038a0b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".