The EOI dialog now lists "Documenso Standard EOI" (default) plus any seeded in-app EOI templates and routes the submit to the dual-path generate-and-sign endpoint with the correct pathway: - "documenso-template" sentinel id → pathway: documenso-template - any other template id → pathway: inapp Signers are derived server-side from EoiContext for both pathways when the template type is EOI (interest's client + hardcoded developer + approver), so the dialog doesn't collect them. Non-EOI templates still require explicit signers. Drops the legacy `client.yachtLengthFt` prerequisite check (yacht is now a first-class entity) and replaces it with hasYacht based on interest.yachtId. Tests updated; 646/646 green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
13 KiB
13 KiB