build-execution · supabase_json

FLOW Intake Route

build-execution artifact · for Bezel Workflow · phase W0-S3 · status complete

Planning Surface

Use this to decide what happens next.

Status

complete

Phase

W0-S3

Next Action

W0-S4: connect apps/workflow shell to a real FLOW fixture and POST /flows flow submission path, or add workflow run timeline product view backed by existing workflow run/task/event APIs.

verification

npx vitest run apps/api/test/flow-intake-route.test.ts: 3/3 passed
npx vitest run apps/api/test/http-server.test.ts: /flows route covered and passed
npx vitest run apps/api/test/openapi-contract.test.ts: passed after adding /flows to public path list
npm test: 44 files / 166 tests passed
npm run typecheck: passed
npm run build: passed

next action

W0-S4: connect apps/workflow shell to a real FLOW fixture and POST /flows flow submission path, or add workflow run timeline product view backed by existing workflow run/task/event APIs.

Agent Handoff

Start Here

W0-S4: connect apps/workflow shell to a real FLOW fixture and POST /flows flow submission path, or add workflow run timeline product view backed by existing workflow run/task/event APIs.

Completion Evidence

npx vitest run apps/api/test/flow-intake-route.test.ts: 3/3 passed
npx vitest run apps/api/test/http-server.test.ts: /flows route covered and passed
npx vitest run apps/api/test/openapi-contract.test.ts: passed after adding /flows to public path list
npm test: 44 files / 166 tests passed
npm run typecheck: passed
npm run build: passed

Next Action

W0-S4: connect apps/workflow shell to a real FLOW fixture and POST /flows flow submission path, or add workflow run timeline product view backed by existing workflow run/task/event APIs.

Structured Payload

Machine-readable source fields

kind

build-execution

repo

/Users/justinking/Vaults/Projects/bezel-api

title

FLOW Intake Route

status

complete

changes

Added apps/api/src/flow-intake-route.ts.
Added POST /flows to compile human-product FLOW.json into existing PlanIntake-compatible runtime plans.
POST /flows supports raw FLOW.json or wrapper body { flow, role_id_by_name } for product role to runtime role mapping.
POST /flows rejects invalid FLOW.json and missing compiled runtime queues before materialization.
Wired /flows through apps/api/src/http-server.ts using existing principal resolution, role queue resolution, and materializePlan runtime path.
Documented /flows in README, apps/api/README.md, OpenAPI paths, and Flow schemas.

project

Bezel Workflow

phase id

W0-S3

next action

W0-S4: connect apps/workflow shell to a real FLOW fixture and POST /flows flow submission path, or add workflow run timeline product view backed by existing workflow run/task/event APIs.

completed at

2026-05-09T17:06:35.906Z

verification

npx vitest run apps/api/test/flow-intake-route.test.ts: 3/3 passed
npx vitest run apps/api/test/http-server.test.ts: /flows route covered and passed
npx vitest run apps/api/test/openapi-contract.test.ts: passed after adding /flows to public path list
npm test: 44 files / 166 tests passed
npm run typecheck: passed
npm run build: passed