Backend API for the ProCalc estimating calculator. The calculation engine returns the same results as the current 1.0 calculator.
A short, human-readable summary of the problem.
A human-readable explanation specific to this occurrence of the problem.
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
A URI reference that identifies the problem type
Retrieves a ConstraintViolation resource.
Engine sum after the regional multiplier, before the result formulas.
Result formulas: low / mid / high (normalized from "hight").
PoC (vertical slice B1 + B2 + API): POST /api/v1/calculate/legacy. Takes input in the 1.0 format (docs/15 section 3.1, the B-INT variant), runs the CalculationEngine against a version config loaded from the database and returns { sum, result: { low, mid, high } }. The key is "high", not "hight": the public 2.0 contract does not keep the 1.0 typo (decision D8). Deliberate PoC shortcuts: TODO B4: we calculate from draft_definition, without the draft -> validate -> publish -> compile pipeline and without mapping input to canonical keys. TODO B5: no rate limiting (Symfony RateLimiter, 429). TODO B6: no auth (endpoint open on dev only).
S1 test resource: confirms that API Platform and Swagger UI work. Remove once the first real domain resources exist.
The message associated with the violation