v1.7.10

Re-cut of v1.7.9 with release-gate test fixes — the server changes are identical to v1.7.9 (which never reached production; its release pipeline was blocked by two stale test expectations that release unmasked). See the v1.7.9 notes for the full changelog of what this release delivers, headlined by the sender-identity recovery work (#908/#911, migration 105) and the self-hosting fail-closed defaults (#918).

Added since v1.7.9

• Release-gate test fixes (#923): the TS/Python SDK live suites now accept both contract-valid sending_teardown receipt states (a configured provider legitimately starts at pending), and the e2e-prod domain-lifecycle suite mints fixture domains inside the staging SES IAM fence's namespace so delete-time deprovision can prove absence. Both expectations dated from before staging ran the sender-identity subsystem for real; no server behavior changed.
• SDK hardening (#909): the TS and Python SDKs now reject dot-segment path parameters that would collapse a request path onto a broader resource (e.g. a crafted id retargeting a DELETE). Client-side validation only; ships to npm/PyPI with the next client release.

Note for self-hosters (carried from v1.7.9): if you run the MCP HTTP server, set E2A_API_URL (or E2A_URL/E2A_BASE_URL) and MCP_ALLOWED_HOSTS (or MCP_PUBLIC_URL) explicitly — it now exits with a config error instead of silently using the hosted service's endpoints.

SDK/CLI package versions are unchanged (TS SDK 5.7.0, Python 5.7.0, CLI 2.4.0 remain current); the client-side changes from #918 and #909 ship in the next client release.

---

What's Changed

• fix(sdk): reject dot-segment path params that collapse a DELETE onto a bigger resource by @AmirF194 in #909
• fix(test): align live domain suites with staging sender-identity parity by @jiashuoz in #923

Full Changelog: v1.7.9...v1.7.10