feat: decompose V1 CRUD routes into pipeline primitives (#86)

[intel352]

Summary

Replace the last 2 V1 admin CRUD routes (deploy and stop) that still delegated to admin-v1-mgmt (V1APIHandler) with declarative pipeline definitions using admin-db.

Routes Decomposed

All 6 routes from Phase B now use pipeline primitives:

Route	Status
POST /api/v1/admin/organizations/{id}/projects	✅ Already decomposed
POST /api/v1/admin/projects/{id}/workflows	✅ Already decomposed
POST /api/v1/admin/workflows	✅ Already decomposed
PUT /api/v1/admin/workflows/{id}	✅ Already decomposed
POST /api/v1/admin/workflows/{id}/deploy	🆕 Decomposed in this PR
POST /api/v1/admin/workflows/{id}/stop	🆕 Decomposed in this PR

Pipeline Pattern (deploy/stop)

request_parse → set(now) → db_exec(UPDATE status) → db_query(get workflow) → json_response(200)

Each route now uses pipeline steps (request_parse, set, db_exec, db_query, json_response) instead of Go delegates, consistent with the other decomposed routes.

Verification

• go build ✅
• go test ./... ✅
• go vet ./... ✅
• golangci-lint run ✅

Closes #86

[Copilot]

Pull request overview

This PR completes Phase B of the admin config decomposition by replacing the remaining V1 admin workflow deploy and stop CRUD routes that previously delegated to admin-v1-mgmt with fully declarative pipeline definitions backed by admin-db.

Changes:

• Replaced /api/v1/admin/workflows/{id}/deploy delegate step with a pipeline that updates status to active and returns the workflow record.
• Replaced /api/v1/admin/workflows/{id}/stop delegate step with a pipeline that updates status to stopped and returns the workflow record.

[Copilot]

The stop pipeline responds 200 with steps.get-workflow.row even when the workflow isn't found. Because step.db_query (mode: single) returns found: false + empty row, this endpoint will return {} with 200 rather than a 404.

Add a conditional step on steps.get-workflow.found (or check affected_rows from the UPDATE) and return a 404 json_response when the workflow does not exist.

Suggested change

	- name: respond
	type: step.json_response
	config:
	status: 200
	body_from: "steps.get-workflow.row"
	- name: respond-if-found
	type: step.condition
	config:
	condition: "{{index .steps \"get-workflow\" \"found\"}}"
	true_steps:
	- name: respond
	type: step.json_response
	config:
	status: 200
	body_from: "steps.get-workflow.row"
	false_steps:
	- name: respond-not-found
	type: step.json_response
	config:
	status: 404
	body:
	error: "workflow not found"

[Copilot]

The deploy pipeline always responds 200 with steps.get-workflow.row even when the workflow ID doesn't exist. step.db_query in mode: single returns found: false and an empty row, so this endpoint will return {} with 200 instead of a 404 (unlike the GET/PUT/DELETE workflow routes above).

Add a conditional step on steps.get-workflow.found and a not-found json_response (404) route, or otherwise fail the pipeline when no row is found.

Suggested change

	mode: single
	- name: respond
	type: step.json_response
	mode: single
	- name: not-found
	type: step.json_response
	condition: "{{ not .steps.get-workflow.found }}"
	config:
	status: 404
	body:
	error: "workflow not found"
	- name: respond
	type: step.json_response
	condition: "{{ .steps.get-workflow.found }}"

[intel352]

@copilot open a new pull request to apply changes based on the comments in this thread

[Copilot]

@intel352 I've opened a new pull request, #137, to work on those changes. Once the pull request is ready, I'll request review from you.