v0.5.0 – Environment Isolation, dldb 1.1 Compatibility, and Operational Tooling

Highlights

• Added profile-aware environment-config isolation: test uses env_config_test, while production and prod use evaluation_env_config; explicit table overrides remain supported.
• Upgraded the dldb dependency to dldb-v1.1.0, enabling correct unpartitioned SimpleTable reopening and exact logical-table resolution without SDK-side wrapper pinning.
• Updated ETL checkpoint handling to use current dldb session APIs and removed dependencies on deleted table-opening APIs.
• Added reusable environment-config operations for table initialization, querying, cleanup, index maintenance, fragment inspection, and index-coverage reporting.
• Improved operational query performance with partition pruning, optimized counting and cleanup paths, distinct-value inspection, and HASH partition health diagnostics.
• Added controlled landing archive workflows for full-table rotation and online cold-data migration.
• Expanded serving delivery tooling with verified batch export and dataset-level counting.
• Enhanced ETL with trainability processing, FreeCoT enrichment, search-text generation, improved incremental execution, and broader integration coverage.

Upgrade Notes

• Downstream applications should update their SDK dependency to v0.5.0.
• WT_SDK_PROFILE now also selects the default environment-config table. Omitting the profile continues to default safely to test.
• Existing applications that explicitly pass an environment-config table name retain their current behavior.
• Existing environments should force-reinstall dldb because the dldb-v1.1.0 source tag may still report distribution version 1.0.0, which can cause pip to reuse an older installation.