MDAPI package for deploying Docusign Composite Envelope Builder

Contents:
- `classes/` — Apex classes and test classes
- `flows/` — Flow file for DocuSign Envelope Templates (V4)
- `package.xml` — package manifest

Usage (Salesforce CLI, Metadata API format):

1. Ensure you have the Salesforce CLI installed and authenticated to the target org.

2. Deploy the package directory (from repository root):

```bash
# convert source if needed, or deploy mdapi directly
sfdx force:mdapi:deploy -d deploy/mdapi -u <prod-org-alias> -w 10
```

3. If you prefer ANT, zip the `deploy/mdapi` directory and use the Metadata API/ANT deployment procedure.

Notes:
- The `flows` file included is the V4 flow file (`Docusign_Envelope_Templates_V4.flow-meta.xml`). The Flow API name is `DocuSign_Envelope_Templates` — ensure the Flow member name in `package.xml` matches the flow's API name.
- The implementation depends on the managed-package `dfsle` (Docusign for Salesforce) toolkit and its `dfsle__EnvelopeConfiguration__c` records. Ensure the managed package and its configuration/data exist in Production before invoking the Flow.
- This package intentionally excludes `Docusign_Configuration__c` (legacy metadata) — include it only if you intentionally want to keep that object in Production.