chore(release): @hasna/emails 1.3.11

[andrei-hasna]

Summary

• bump @hasna/emails from 1.3.10 to 1.3.11
• release the merged client-env diagnostic redaction from fix: redact structured client env diagnostics #210
• metadata only: no runtime-code or lockfile changes

Todos: 45424a68-3c8a-494d-ae88-ed0fc8a81c62
References: #210

Validation

• focused output-safety/client-env/mode tests: 50 pass, 0 fail
• shared suite: 4326 pass, 156 skip, 0 fail
• hermetic suite: exit 0 across 289 test files
• build, generated SDK, deployment policy, no-cloud source/package, and static self-hosting contract: pass
• staged and commit-range secret scans: no leaks found

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[andrei-hasna]

[REVIEW] GO — #211 @ cd73bff — lens: correctness+security+gates, reviewer Trebius (1 of 1)

Scope read:

• Verified HEAD cd73bff5059c0fa43294b31a59d7b9c80136b32d and exact fetched base 3482cc0aab4a673c33db402b05eb98d696903cb4.
• Ran git log --oneline origin/main..HEAD and git diff origin/main...HEAD --stat, then read the full diff and complete surrounding package.json plus the lockfile manifest context.
• The only candidate change is @hasna/emails version 1.3.10 -> 1.3.11; there are no runtime-code, dependency, script, lockfile, data, session, authorization, or trust-boundary changes.
• Read the PR metadata and current release context. Registry state remains 1.3.10; 1.3.11 is unused (npm view @hasna/emails@1.3.11 version --json exited 1 with expected E404; informational, not a gate).

Commands and gates:

• bun install — exit 0; setup only, not a test gate; pass/fail counts: N/A.
• bun run test — exit 0; 4326 pass, 156 skip, 0 fail; 21058 expect() calls; 4482 tests across 289 files.
• git diff --exit-code after setup/tests — exit 0; candidate remained clean.
• This repository declares no typecheck script, so no typecheck command was invented.

Blocking P0/P1 findings: none.

Security/correctness conclusion: the metadata-only version bump exposes no new input, sink, authorization path, secret-bearing path, mutation path, migration, or session behavior. The declared gate is green and the intended version is available for publication.

Non-blocking follow-ups: none.