312ebf1a88
The user asked us to confirm we copied the Documenso template's auto-fill schema verbatim from the legacy system. Confirmed and documented in the canonical mapping file: - Every legacy formValues key (Name, Email, Address, Yacht Name, Length, Width, Draft, Berth Number, Lease_10, Purchase) is still emitted with identical names and types — single-berth EOIs are byte-for-byte compatible with template id 8. - Phase 5 added one new field: `Berth Range` (compact range string for multi-berth EOIs from the is_in_eoi_bundle junction rows). Documenso silently drops unknown formValues, so the live template will simply not render the range until someone adds the field. The doc now flags this explicitly. - Verified buildDocumensoPayload() populates all 11 fields from the resolved EoiContext; tests at tests/unit/services/documenso-payload cover every field. The "rest is handled inside Documenso" (signature, date, terms) - those fields live on the template itself and don't appear in our formValues map. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>