chore(deps): require data designer 0.9

[lipikaramaswamy]

Summary

• require Data Designer 0.9.x and drop support for 0.7/0.8
• update the lockfile from Data Designer 0.8.0 to 0.9.1

Motivation and user impact

Data Designer 0.8 validates NEMO_DEPLOYMENT_TYPE at import time and rejects Anonymizer's existing cli value. Consequently, fresh installations can fail before any CLI command starts.

Data Designer 0.9 safely coerces unknown deployment values to undefined rather than raising during import. Requiring 0.9.x fixes CLI startup without changing Anonymizer's current telemetry environment-variable behavior. This PR intentionally removes compatibility with Data Designer 0.7 and 0.8.

This is an alternative release-unblocking approach to #247.

Validation

• make check
• uv pip check: all 221 installed packages compatible
• full unit suite: 1,191 passed
• real CLI startup:
  • anonymizer --help
  • anonymizer --version
  • anonymizer validate --source docs/data/NVIDIA_synthetic_biographies.csv --text-column biography --replace redact
• live model-backed smoke test with OpenAI-compatible Brev endpoints and one synthetic record:
  • Substitute: 6 entities detected, 1 record processed, 0 failures
  • Rewrite with repair disabled: 1 record processed, 0 failures, leakage mass 0.0

Contributor checklist

• No plan required: focused dependency compatibility update
• No linked GitHub issue required: maintainer-owned release fix for QA bug NVIDIA 6557542
• Public API impact: supported Data Designer range changes from >=0.7,<0.9 to >=0.9,<0.10; no Anonymizer symbols, signatures, or bundled skill templates changed
• Documentation: package dependency metadata is the owning source for the supported range
• PII fixtures: none added
• Secrets or credentials: none added

[binaryaaron]

we should probably look into more fine-grained pinning at some point but this works.

[greptile-apps]

Greptile Summary

The PR raises the supported Data Designer range to 0.9.x to avoid the import-time deployment-type failure and refreshes the lockfile accordingly.

• Requires data-designer>=0.9,<0.10.
• Resolves Data Designer, Data Designer Config, and Data Designer Engine to 0.9.1.
• Updates the associated transitive dependency graph, including MCP and Pydantic extras.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete blocking or independently actionable issue identified.

The declared dependency range and lockfile agree, relevant Data Designer integration seams are covered by repository tests, and the changed dependency graph does not establish a reachable regression or new security consequence.

Important Files Changed

Filename	Overview
pyproject.toml	Updates the Data Designer requirement to the intended 0.9.x compatibility range, consistently reflected in locked project metadata.
uv.lock	Resolves Data Designer 0.9.1 and its transitive dependency changes without an established changed-code failure.

_{Reviews (1): Last reviewed commit: "chore(deps): require data designer 0.9" | Re-trigger Greptile}