feat(array): add endpoint for kicking off a task, remove workflow triggers from other endpoints

[joshsny]

Problem

We now support local and cloud workflows - we don't want to trigger the cloud workflow on changes anymore, but we need an endpoint to kick off the cloud workflow.

Changes

• Remove workflow triggers from existing endpoints
• Add a run endpoint that triggers the temporal workflow, leaves it to the SDK to decide how to work on the task and to update it's status

[greptile-apps]

_{2 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

style: task created with current_stage from a workflow but without setting workflow field - creates inconsistent state

the test creates a stage that belongs to workflow, then assigns that stage to the task without setting the task's workflow field. while this tests the effective_workflow logic, it creates an inconsistent state that may not represent real usage.

consider either:

1. not setting current_stage at all (truly no workflow)
2. or clarify in a comment that this tests the edge case of inconsistent state

Suggested change

	def test_run_endpoint_without_workflow_fails(self):
	workflow = self.create_workflow()
	stage = workflow.stages.first()
	task = Task.objects.create(
	team=self.team,
	title="Task without workflow",
	description="Test",
	origin_product=Task.OriginProduct.USER_CREATED,
	current_stage=stage,
	position=0,
	)
	def test_run_endpoint_without_workflow_fails(self):
	# Create task without workflow or stage to test the effective_workflow fallback
	task = Task.objects.create(
	team=self.team,
	title="Task without workflow",
	description="Test",
	origin_product=Task.OriginProduct.USER_CREATED,
	current_stage=None,
	position=0,
	)

Prompt To Fix With AI

This is a comment left during a code review.
Path: products/tasks/backend/tests/test_api.py
Line: 440:451

Comment:
**style:** task created with `current_stage` from a workflow but without setting `workflow` field - creates inconsistent state

the test creates a stage that belongs to `workflow`, then assigns that stage to the task without setting the task's `workflow` field. while this tests the `effective_workflow` logic, it creates an inconsistent state that may not represent real usage.

consider either:
1. not setting `current_stage` at all (truly no workflow)
2. or clarify in a comment that this tests the edge case of inconsistent state

```suggestion
    def test_run_endpoint_without_workflow_fails(self):
        # Create task without workflow or stage to test the effective_workflow fallback
        task = Task.objects.create(
            team=self.team,
            title="Task without workflow",
            description="Test",
            origin_product=Task.OriginProduct.USER_CREATED,
            current_stage=None,
            position=0,
        )
```

How can I resolve this? If you propose a fix, please make it concise.

[github-actions]

Size Change: +70 B (0%)

Total Size: 3.05 MB

ℹ️ View Unchanged

Filename	Size	Change
frontend/dist/toolbar.js	3.05 MB	+70 B (0%)

_{compressed-size-action}