SDK regeneration

[fern-api]

Automated SDK generation by Fern

---

Action required: 3 files with unresolved customization conflicts

The new generation changed code you previously customized. Non-conflicting customizations have been applied automatically. The following files need manual resolution:

File	Your customization	Why it conflicted
Cargo.lock	chore: restore .fernignore, defer windows npm package	The new generation changed the same lines you edited
.github/workflows/ci.yml	chore: publish packageIdentity metadata to npm, restore .fernignore	This customization was from a previous generation
Cargo.lock	chore: publish packageIdentity metadata to npm, restore .fernignore	The new generation changed the same lines you edited

How to resolve

1. Check out this branch:

   git fetch origin && git checkout -b fern-bot/2026-09-14_19-53-56_673 origin/fern-bot/2026-09-14_19-53-56_673

   Or if you don't have the repo cloned:

   git clone https://github.com/agentmail-to/agentmail-cli.git && cd agentmail-cli && git checkout -b fern-bot/2026-09-14_19-53-56_673 origin/fern-bot/2026-09-14_19-53-56_673

2. Run: fern replay resolve
3. Open the conflicting files in your editor — you'll see standard merge conflict markers
4. Resolve using your editor's merge tools (VS Code, IntelliJ, etc.)
5. Run: fern replay resolve again to finalize
6. Push your changes

Your resolved customizations will be remembered on future SDK generations.
If you merge this PR without resolving, your unresolved customizations will conflict again on the next generation.

[duharry0915]

Superseded: regenerating 1.4.0 after agentmail-to/agentmail-docs#243, which restores the api-keys create flags this generation dropped.