[BE-26] Implement maintenance records CRUD — POST, GET, PATCH /assets/:id/maintenance

[yusuftomilola]

Overview

The "Maintenance" tab on the asset detail page shows service history and lets users log new maintenance events. Maintenance records track what was done, by whom, at what cost, and the outcome.

Context

• Frontend API: frontend/lib/api/assets.ts — createMaintenanceRecord(assetId, data), getMaintenanceRecords(assetId), update status via PATCH /assets/:id/maintenance/:maintId
• Frontend types in frontend/lib/query/types/asset.ts: MaintenanceRecord with type (PREVENTIVE, CORRECTIVE, SCHEDULED), status (SCHEDULED, IN_PROGRESS, COMPLETED, CANCELLED), scheduledDate, completedDate, cost, notes, technician
• Status changes set asset status to MAINTENANCE when IN_PROGRESS, and back to ACTIVE when COMPLETED

Acceptance Criteria

• Create MaintenanceRecord entity: id, assetId, type (MaintenanceType enum), status (MaintenanceStatus enum), title, description, scheduledDate, completedDate, cost (decimal), technicianName, providerId (nullable FK to Vendor), notes, createdBy, createdAt, updatedAt
• POST /assets/:id/maintenance — creates record, if status: IN_PROGRESS sets asset status to MAINTENANCE, logs MAINTENANCE history entry
• GET /assets/:id/maintenance — paginated list of maintenance records, most recent first, with total cost sum
• PATCH /assets/:id/maintenance/:maintId — update status, completedDate, cost, notes. If status becomes COMPLETED, set asset status back to ACTIVE
• Return 404 if maintenance record does not belong to the specified asset

[temiport25]

@temiport25 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

can i work on this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @temiport25 to this issue.

[drips-wave]

Congratulations, @temiport25! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @temiport25: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @temiport25 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @temiport25: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.