[waleedlatif1]

Summary

• Extract the editor Run button's entry check (no runnable trigger, more than one API trigger, selected trigger with no outgoing edge) from use-workflow-execution into one pure resolveManualRunEntry in lib/workflows/triggers/manual-run.ts. The hook calls it with the same messages, order, and execution teardown, so the Run button behaves the same
• Workflow lint reports that result as lint.manualRunIssue (reason, message, trigger block ref, or null). It is advisory like every lint finding and never blocks a write or deploy. A webhook or schedule workflow that is wired correctly gets no finding, because a manual run accepts it with a mock payload. A workflow only a chat trigger can start is exempt, and an empty graph keeps its existing note
• hasWorkflowLintIssues / formatWorkflowLintMessage include the new finding. That means sim workflows lint and deploy lint see it too
• POST /api/v2/workflows/{id}/operations (committed and dry run) now adds the formatWorkflowLintMessage summary to warnings[] whenever lint has findings. An agent that projects the response down to warnings no longer loses the findings
• Lower the two selectBestTrigger grouping logs from info to debug, since lint now runs them on graph writes

Consumers of the apply result

• Only the v2 operations route uses applyWorkflowOperations; its presenter passes warnings through as before. The CLI prints the response as it comes. No UI reads this result
• Duplication: the summary is one string, built only from lint, and it never matches the normalization warnings already in the array. The result never carries it twice
• Size: one line per finding, built from the same findings lint already returns. Growth is bounded by the graph and scales with the existing lint payload
• PUT /state and deploy still return findings only under lint (their warnings keep their current meaning)

Type of Change

• Improvement

Testing

• lint-report.test.ts: new manual-run cases. Reported: unconnected trigger, no trigger, disabled trigger, two API triggers. Not reported: connected start/webhook/schedule, legacy starter, chat-only, empty graph. All failed with the fix reverted. Separately, removing only the chat exemption turns the chat-only case red
• apply-workflow-operations.test.ts: the lint summary appears in warnings on commit and on dry run, and nothing is added when lint is clean. Red with the fix reverted
• Ran the targeted suites (editing, triggers, application, v2 contracts and routes, agent-cli lint), bun run lint, check:openapi, check:cli-api, check:mcp-operations, check:boundaries, check:client-boundary, check:utils, check:comment-hygiene, check:test-patterns, check:explicit-any, check:file-names, check:source-conventions, check:import-specifiers, check:api-validation. CI is the gate for the rest

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Nov 3, 2026 9:54pm UTC

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Shares the editor’s manual-run entry check with workflow lint and adds lint summaries to apply warnings.

• Workflow lint reports when the editor’s Run button would refuse to start.
• Workflow operation responses include lint findings in their warnings.
• Trigger grouping and selection messages now appear at debug level.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  Editor[Editor Run button] --> Entry[resolveManualRunEntry]
  Lint[Workflow lint] --> Entry
  Entry --> Result[Selected trigger or entry issue]
  Result --> Report[Lint report]
  Report --> API[API lint response]
  Report --> Summary[Apply warnings summary]

Loading

_{Reviews (3) · Last reviewed commit: "docs(workflows): make the apply-operatio..." · Reviewed by Greptile}

[cubic-dev-ai]

All reported issues were addressed across 19 files

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 19 files

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 19 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}