Skip to content

PM-5067: Set task copilot payments to owed#187

Merged
jmgasper merged 1 commit into
devfrom
PM-5067
May 26, 2026
Merged

PM-5067: Set task copilot payments to owed#187
jmgasper merged 1 commit into
devfrom
PM-5067

Conversation

@jmgasper

Copy link
Copy Markdown
Collaborator

What was broken
Task copilot payments for regular, TAAS, and Topgear challenges were generated in On Hold (Admin) status instead of Owed.

Root cause
Task payment status resolution only treated TAAS winner payments as Owed. Copilot payments use the COPILOT_PAYMENT category, so the generic non-TAAS task fallback forced them to On Hold (Admin).

What was changed
Task payment status resolution now treats copilot payment categories as Owed while preserving the existing On Hold (Admin) default for other non-TAAS task payments.

Latest-dev type and test expectations that blocked lint/test validation were also aligned without changing runtime payment behavior.

Any added/updated tests
Added challenge-service coverage for regular, TAAS, and Topgear task copilot payments resolving to Owed.

Updated existing latest-dev specs/type assertions so lint and the full Jest suite pass on the branch.

Validation

  • pnpm lint
  • pnpm build
  • pnpm test

What was broken
Task copilot payments for regular, TAAS, and Topgear challenges were generated in On Hold (Admin) status instead of Owed.

Root cause
Task payment status resolution only treated TAAS winner payments as Owed. Copilot payments use the COPILOT_PAYMENT category, so the generic non-TAAS task fallback forced them to On Hold (Admin).

What was changed
Task payment status resolution now treats copilot payment categories as Owed while preserving the existing On Hold (Admin) default for other non-TAAS task payments. Latest-dev type and test expectations that blocked lint/test validation were also aligned without changing runtime payment behavior.

Any added/updated tests
Added challenge-service coverage for regular, TAAS, and Topgear task copilot payments resolving to Owed. Updated existing latest-dev specs/type assertions so lint and the full Jest suite pass on the branch.
@jmgasper jmgasper merged commit 7488b19 into dev May 26, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant