Use BudgetHours instead of EstimatedHours for project budget analysis

[Copilot]

ConnectWise EstimatedHours reflects task-level time estimates that change with scope. BudgetHours is the approved resource allocation used for financial tracking. Reports were comparing actuals against estimates instead of budget.

Changes

API Models

• Added BudgetHours field to CWProject, CWPhase, CWTicket (kept EstimatedHours for API compatibility)

DTOs

• BudgetAnalysis.EstimatedHours → BudgetAnalysis.BudgetHours
• PhaseDetail.EstimatedHours → PhaseDetail.BudgetHours
• TicketSummary.EstimatedHours → TicketSummary.BudgetHours

Service Layer

// Before
var estimatedHours = project.EstimatedHours ?? 0;
var hoursVariance = actualHours - estimatedHours;

// After
var budgetHours = project.BudgetHours ?? 0;
var hoursVariance = actualHours - budgetHours;

UI/Reports

• PDF: "Budget Hours" labels, "Hours budget/actual" format
• Web UI: "Budget Hrs" column headers
• AI prompts: "Budget: X hours" terminology

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Project Report Using Estimated Instead of Budget</issue_title>
<issue_description>Estimated time in CW projects refers to the set start and end dates of the project/phase/task
Instead, budget hours is the more appropriate comparison for the report.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Project Report Using Estimated Instead of Budget #40

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.