Procurement Contract Versioning Issue – Initial Version Starts at 1 Instead of 0

Issue description:

In the Procurement Contracts module, we have observed that the contract versioning sequence begins at version 1. However, the expected behavior is that the contract should initially register as version 0, with version 1 being reserved for the first contract variation or amendment.

This discrepancy causes confusion in tracking contract lifecycle stages, as the baseline contract should logically start at version 0. The current behavior misaligns with standard contract management practices, where:

• Version 0 = Original contract record (baseline)
• Version 1 = First variation/amendment

We request clarification on whether this is a product defect or intended functionality. If it is a defect, we would like guidance on corrective measures or patches to ensure proper version sequencing.