[FEAT] Build Repair Job Lifecycle API (Request, Quote, Milestone Payments)

[Rampop01]

Issue #55

[FEAT] Build Repair Job Lifecycle API (Request, Quote, Milestone Payments)

🟡 Priority: High
Difficulty: Hard
Estimated Effort: 4-5 days
Relevant Files: src/controllers/repair.controller.ts, src/services/repair.service.ts, src/routes/repair.routes.ts
Labels: api, repair, priority:high

Requirements

1. Repair Lifecycle Endpoints

   • Implement POST /repair/request for users to submit a repair request to a specific technician.
   • Implement POST /repair/:id/quote for a technician to respond with a price and milestone breakdown.
   • Implement PATCH /repair/:id/accept-quote for the user to accept and fund the repair escrow on-chain.
   • Implement PATCH /repair/:id/milestone/:n/complete for the technician to mark a milestone as done and trigger the partial payout.

2. Security & Access Control

   • Strict ownership checks on all PATCH endpoints: only the involved technician or user can mutate the repair record.
   • Validate that a milestone cannot be marked complete if the previous milestone is not yet approved by the user.

3. Testing Requirements

   • Integration test: Walk through the full lifecycle (Request -> Quote -> Accept -> Milestone 1 complete -> Milestone 2 complete -> Final release).
   • Test that an unauthorized user attempting to accept a quote receives a 403 Forbidden.

---

[MissBlue00]

Hi! I’d like to work on Issue #55. I can implement the full repair lifecycle API, including request/quote/accept/milestone endpoints, enforce strict technician/user authorization and milestone ordering, integrate escrow funding and payouts, and add end-to-end integration tests plus unauthorized-access coverage.

[Wilfred007]

Hi! I’d like to work on this repair job lifecycle API. I can implement the complete request → quote → escrow → milestone payment flow while keeping authorization and state transitions strict.

My approach would include:

• Implementing the request, quote, quote acceptance, and milestone completion endpoints.
• Adding strict ownership and role-based access checks for users and technicians.
• Validating milestone sequencing so payouts cannot occur before the required user approvals.
• Integrating the quote acceptance flow with on-chain repair escrow funding.
• Triggering milestone-based partial payouts and the final release.
• Adding integration tests covering the complete lifecycle and unauthorized access scenarios, including the required 403 Forbidden case.

I’ll keep the implementation consistent with the existing controller, service, and routing architecture and make the lifecycle state transitions predictable and secure.

[grantfox-oss]

🦊 GrantFox — @Wilfred007 has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #25)
2. Your PR will be reviewed by the Veloxous maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@Wilfred007's PR #29 was approved and merged by @Rampop01.

🏆 @Wilfred007: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (990 total points). Track your full progress on GrantFox.

👏 Great work, @Wilfred007! Keep contributing to Veloxous.