Repository navigation
Add service survey and human selection before procurement payments - #6
Merged
Merged
Conversation
Contributor
Author
|
Deployed merged commit
The current production catalog has two services marked |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The workspace now pauses after an agent service survey so an operator can compare candidates, choose one service, and explicitly submit procurement before payment begins. New requests capture invoice and Mello Registry certification requirements, filter the survey accordingly, and display each service’s invoice/certification availability. The login page shows the requested demo access code.
Selection is persisted and dispatched atomically; duplicate submissions do not create duplicate payment jobs. A changed price or certification returns the task to selection. Existing automated API clients retain their previous behavior when they omit survey requirements.
Validation: 394 API unit tests, 9 frontend tests, and 31 focused database integration tests passed locally, along with API type checking, lint, and the Next.js build. Browser checks covered all four requirement combinations, selection gating, a budget edge case, reload persistence, and desktop/mobile layouts. CI now includes the survey, controls, and queue integration suites.
Deployment: apply
20260906000000_procurement_survey_selectionbefore starting the new API, then deploy Web. The migration addsWAITING_SELECTIONand two nullable JSONB columns; it does not rewrite existing purchases. This branch also preserves the seller-wallet rotation guard and historical-payee fix already deployed in production, plus their committed release evidence.