dow-prod-tracker/prisma
DJP 1de8985507 Outcome-branch routing: only one path fires per approval decision
Adds PipelineBranchKind (NONE/APPROVED/DECLINED) on stage definitions
so producers can tag the two routes downstream of a FORMAL-approval
stage. The engine then picks exactly one branch per decision:

  • Approve → APPROVED-branch children auto-open, DECLINED-branch
    siblings auto-SKIPPED (grayed out, unreachable)
  • Request Changes → DECLINED-branch children auto-stamped APPROVED
    (passive record of the decline), APPROVED-branch siblings auto-
    SKIPPED, then the existing rework edge fires as before

Also fixes a quiet bug in pipeline-template-service.addStage where
approvalType was being dropped from new stages (whitelist didn't
include it).

UI: dropdown on the stage edit sheet + branch-kind badges on the
deliverable detail page. SKIPPED rendering already grays things out.

Smoke test extended: 65/65 passing including the user's split-on-
decision case, N-way split, regression assertion that untagged
pipelines still open all children, and an idempotency check.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-15 21:16:22 -04:00
..
migrations Outcome-branch routing: only one path fires per approval decision 2026-05-15 21:16:22 -04:00
schema.prisma Outcome-branch routing: only one path fires per approval decision 2026-05-15 21:16:22 -04:00
seed-dow.ts Board drag-and-drop with forward/rework pipeline rules 2026-04-21 12:45:17 -04:00
seed-tracker-data.ts feat: enhance UI components and add assignment feature to deliverables 2026-03-02 13:46:55 -06:00
seed.ts Database cleanup pre rollout 2026-04-06 14:35:56 -05:00