traigent 0.18.1.dev10__tar.gz → 0.19.1__tar.gz

{traigent-0.18.1.dev10 → traigent-0.19.1}/CHANGELOG.md

@@ -6,6 +6,86 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.19.1] - 2026-07-03
+
+No-silent-legacy hardening release: five classes of silent failure now either
+work correctly or fail loudly.
+
+### Fixed
+- `ObjectiveSchema` weights now govern `best_config` selection for grid/random
+  runs via observed-range (min-max, orientation-aware) weighted scoring;
+  per-trial `metrics["score"]` is populated and post-hoc
+  `calculate_weighted_scores` uses the same scorer. Flipping weights
+  0.9/0.1 ↔ 0.1/0.9 on an accuracy/cost tradeoff now flips the winner. (#1682)
+- `warm_start_transfer` returned in the session-create response now reaches
+  `result.metadata` (previously dropped; runs reported `no_seed_configs` from
+  valid cloud-tracked priors). An explicit `warm_start_from` that applies 0
+  seeds emits a warning naming the refusal reason. (#1683)
+- Dataset file-not-found errors name the resolution rule
+  (`TRAIGENT_DATASET_ROOT` vs cwd), the registry-resolved path, and the exact
+  candidate tried — the doubled-path case is self-diagnosing. (#1684)
+
+### Changed (fail loud instead of silent)
+- Smart algorithms (`bayesian`, `tpe`, `cmaes`, `nsga2`, `optuna*`) raise an
+  actionable error when the managed cloud path cannot execute them, instead of
+  returning a silent 0-trial COMPLETED result with `best_config=None`. Runtime
+  `optimize(algorithm=...)` smart overrides re-resolve to cloud-required
+  policy (no silent local fallback). (#1681)
+- `.optimize()` rejects decorator-only arguments at call time with a
+  move-it-to-the-decorator `TypeError` — `warm_start_from` and 39 sibling
+  options were previously swallowed silently. (#1683)
+- Deprecated `execution_mode` selectors (notably `"edge_analytics"`) raise
+  `ConfigurationError` with `algorithm=` + `offline=` migration guidance on
+  every entry path (decorator, `initialize`, `TraigentConfig`, client) —
+  previously a silent 0-trial run. On the wire, `metadata["mode"]` now carries
+  the canonical `local`/`hybrid`/`hybrid_api` vocabulary. (#1684, #1393)
+- Nonpositive cost limits raise at configuration time; a budget-gate block
+  logs "budget gate blocked N planned trials (estimated $X > limit $Y)"
+  instead of silently completing with 0 trials. (#1684)
+- Flagship multi-objective examples and docs migrated off removed/deprecated
+  parameters (`execution_mode`, `budget_limit`). (#1684)
+
+## [0.19.0] - 2026-07-03
+
+### Added
+- `SemanticSaturationStopCondition` rebuilt from the shipped schema plan
+  (FR-SDK-SEMANTIC-SATURATION-V1).
+- Surrogate (pre-screen) evaluator: a cheap second scorer over captured
+  outputs, with an e2e co-evolution demo in mock mode.
+- Smart-pruning producer wired end-to-end: per-example pruning is reachable
+  from the SDK, with real per-example accuracy threaded into pruning progress
+  and live-e2e-confirmed correctness/durability fixes.
+- `list_sessions()` with typed `SessionSummary`; `delete_session` defaults to
+  non-destructive and `cascade=True` now calls the backend DELETE.
+- Experiment group analytics client.
+
+### Changed
+- Deprecation warnings for the legacy session contract and the
+  `edge_analytics` wire value (now `local`).
+- Self-describing default experiment names.
+- Real streaming token-cost accounting with a plausibility clamp on
+  self-reported costs; `budget.max_cost_usd` is sent on typed session create
+  so the backend cost cap arms.
+
+### Fixed
+- Abort on systematic provider failures instead of reporting fake
+  convergence; fail fast when the optimizer is unavailable instead of
+  hanging.
+- Offline-sync finalization is status-aware and skips terminal non-COMPLETED
+  experiments; sync CLI surfaces terminal-skip warnings.
+- Trial-results table no longer double-scales 0-100 metrics; cost capture
+  works when the config has no `model` key.
+- `FunctionDescriptor` identity, metric batching, and audit-alert
+  ratchet-surfaced bugs.
+
+### Security
+- `RestrictedUnpickler` pinned to a precise (module, name) allowlist,
+  closing a pickle deserialization RCE vector.
+- CLI login rate limiting enforced; file-read containment for CWE-23.
+- Sensitive tuned config values are redacted on the privacy-mode submission
+  path; safety-sensitive-key blocking is non-bypassable on best-config
+  drift; CI-approval token expiry compared in UTC.
+
 ## [0.18.0] - 2026-06-27
 
 ### Added
@@ -26,6 +106,29 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
   var (`OPTUNA_ROLLOUT`, renamed during the managed-routing migration).
 - Smart algorithms (`bayesian` and the Optuna family) now route to the Traigent
   cloud; the local SDK supports `grid` and `random` only.
+- Removed 7 production-dead internal modules (`config_builder`,
+  `llm_processor`, `refactoring_utils`, `service_registry`, `event_manager`,
+  `langchain/discovery`, empty `telemetry` package) and their tests.
+
+### Fixed
+- Per-config `cost` metric is now wired to the authoritative `total_cost`, so
+  the `minimize cost` objective is no longer inert and the portal no longer
+  shows `$0` per config on a real paid run; a model unpriced at runtime is
+  surfaced on the result (and fails closed under
+  `TRAIGENT_STRICT_COST_ACCOUNTING`).
+- `traigent sync` / `traigent local sync` no longer fail every completed
+  session with `409 EXPERIMENT_HAS_NO_RUNS`; sync now creates the experiment
+  `PENDING`, uploads runs, finalizes to `COMPLETED`, resumes idempotently, and
+  returns a non-zero exit on failure.
+- Runtime `optimize(algorithm="grid"|"random")` with a portal key now stays
+  local and exhaustive instead of routing to the cloud sampler.
+- `traigent quickstart` runs on a bare install (uses base `litellm`, not the
+  `integrations` LangChain extra) and fails closed when no trial succeeds.
+- `ObjectiveDefinition` fails closed on unimplemented normalization strategies
+  (`z_score`/`robust`) instead of silently behaving like `min_max`.
+
+### Dependencies
+- Bumped `langsmith` 0.8.3 → 0.8.18 and `pydantic-settings` 2.14.1 → 2.14.2.
 
 ## [0.14.1] - 2026-06-19
 
@@ -123,6 +226,13 @@ Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - **`langgraph-checkpoint` 3.x → 4.x:** the 4.0 release drops default deserialization of payloads serialized with the legacy `"json"` serde mode. Users running `langgraph` with a persistent checkpoint saver (SQLite, Postgres, Redis, etc.) whose stored state contains JSON-format blobs will see deserialization failures unless they configure `serde` with an explicit `allowed_json_modules` list. Traigent does not bind `langgraph-checkpoint` directly — it arrives transitively through the `langgraph` dependency — so this only affects projects that also use `langgraph` checkpointers in their own code. See [CVE-2026-27794](https://github.com/langchain-ai/langgraph/security/advisories) for the underlying RCE that motivated removing the default.
 
 ### Changed
+- **CI approval gate:** running `optimize()` in local/offline mode within a CI
+  environment now requires explicit approval via `TRAIGENT_RUN_APPROVED=1`.
+  `TRAIGENT_MOCK_LLM` no longer bypasses this gate — mock and offline runs in
+  CI are intentionally included (a purpose-built approval signal replaces an
+  env-var bypass of a security control). Cloud-mode runs are unaffected.
+  Migration: set `TRAIGENT_RUN_APPROVED=1` in CI for legitimately-approved
+  runs.
 - **Strict evidence modes now fail closed in promotion** (#1103,
   FR-SDK-FAIL-CLOSED-PROMOTION-V1). When a TVL promotion policy declares a strict
   evidence mode — `require_calibration.enabled: true` or `chance_constraints` —

{traigent-0.18.1.dev10/traigent.egg-info → traigent-0.19.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: traigent
-Version: 0.18.1.dev10
+Version: 0.19.1
 Summary: Enterprise-grade LLM optimization platform with advanced analytics and AI-powered insights
 Author-email: Traigent Team <opensource@traigent.ai>
 License-Expression: AGPL-3.0-only OR LicenseRef-Traigent-Commercial
@@ -92,7 +92,7 @@ Requires-Dist: mcp>=1.27.0; extra == "hybrid"
 Provides-Extra: mcp
 Requires-Dist: mcp>=1.27.0; extra == "mcp"
 Provides-Extra: internal-schema
-Requires-Dist: traigent-schema==4.1.0; extra == "internal-schema"
+Requires-Dist: traigent-schema==4.7.1; extra == "internal-schema"
 Provides-Extra: test
 Requires-Dist: pytest>=9.0.3; extra == "test"
 Requires-Dist: pytest-asyncio>=0.21.0; extra == "test"

{traigent-0.18.1.dev10 → traigent-0.19.1}/docs/api-reference/complete-function-specification.md

@@ -247,6 +247,7 @@ async def optimize(
 | `metric_limit` / `metric_name` / `metric_include_pruned` | Configure soft cumulative-metric early stopping. |
 | `budget_limit` / `budget_metric` / `budget_include_pruned` | Deprecated aliases for metric-limit controls. Use `cost_limit` for hard USD spend control. |
 | `plateau_window` / `plateau_epsilon` | Configure plateau detection stop conditions. |
+| `semantic_saturation` | Configure opt-in semantic saturation. Uses per-example metric-vector churn plus continuous objective improvement and emits sanitized diagnostics in `OptimizationResult.metadata["semantic_saturation"]`. |
 | `parameter_order` | Grid search only: mapping of parameter names to numeric priorities. Lower values vary slowest; higher values vary fastest. |
 | `order` | Alias for `parameter_order` (grid search only). |
 

{traigent-0.18.1.dev10 → traigent-0.19.1}/docs/api-reference/decorator-reference.md

@@ -596,8 +596,9 @@ approve.
 )
 ```
 
-`budget_limit` / `budget_metric` / `budget_include_pruned` are deprecated aliases
-for compatibility. Use `cost_limit` for hard USD spend control.
+`budget_limit` / `budget_metric` / `budget_include_pruned` were removed in
+0.13.0 and now raise `TypeError`. Use `cost_limit` for hard USD spend control,
+or `metric_limit` / `metric_name` for other cumulative metrics.
 
 **Stop Conditions**:
 

{traigent-0.18.1.dev10 → traigent-0.19.1}/docs/api-reference/telemetry.md

@@ -16,7 +16,11 @@ During optimization runs, Traigent collects:
 - Trial suggested/intermediate/completed timestamps
 - Trial status (completed, failed, pruned)
 - Trial duration
-- Trial configuration (parameter values being tested, with internal keys stripped)
+- Trial configuration. On the default portal-backed path, this includes tuned
+  config-space key/value pairs being tested, with internal keys stripped. If you
+  tune prompt variants or other free-text strings as configuration values, those
+  tuned values are sent on the default path so the portal can display winning
+  configs.
 - Trial metrics (accuracy, cost, latency, etc.)
 
 **Optimization Run Metadata**:
@@ -26,7 +30,7 @@ During optimization runs, Traigent collects:
 - Total optimization duration
 - Result source (`cloud_brain`, `local_fallback`, `explicit_local`, or `offline`)
 - Stop conditions triggered
-- Content-free tuned-variable observations can include knob names, enum/scalar values, numeric metrics, and aggregate effectuation events for backend optimization. Set `TRAIGENT_TVAR_OBSERVATION=off` to disable them, or use `TRAIGENT_TVAR_OBSERVATION=hashed` (default) to hash free-form string values. Only `off` and `hashed` are supported; unsupported values fall back to `hashed`.
+- Content-free tuned-variable observations can include knob names, enum/scalar values, numeric metrics, and aggregate effectuation events for backend optimization. Set `TRAIGENT_TVAR_OBSERVATION=off` to disable the `tvar_observation_v1` metadata sub-field, or use `TRAIGENT_TVAR_OBSERVATION=hashed` (default) to hash free-form string values in that sub-field. Only `off` and `hashed` are supported; unsupported values fall back to `hashed`. This setting does not control the trial `config` field.
 
 **Performance Metrics**:
 - LLM API response times
@@ -36,7 +40,8 @@ During optimization runs, Traigent collects:
 
 ### What is NOT Collected
 
-Traigent does **not** collect:
+Outside tuned configuration values explicitly sent on the default portal-backed
+path, Traigent does **not** collect:
 
 - **User prompts or inputs**
 - **LLM responses or outputs**
@@ -47,10 +52,25 @@ Traigent does **not** collect:
 
 ### Data Boundary and No-Egress Runs
 
-The default portal-backed path sends configuration identifiers and numeric metrics. It
-does not send dataset example inputs, expected outputs, prompts, responses, or
-example metadata. Use `offline=True` when your policy requires no Traigent
-backend egress at all:
+The default portal-backed path sends tuned config-space values and numeric
+metrics. This is deliberate: the portal uses those values to display and compare
+winning configs. If a prompt variant, persona instruction, model name, or other
+string is part of the tuned configuration space, the default path sends that
+string value. It does not send dataset example inputs, expected outputs, model
+responses, or example metadata unless you put that content into the tuned
+configuration itself.
+
+Use privacy-mode redaction when you need backend coordination without sending
+tuned string values. Privacy submissions preserve which keys were tuned, but
+redact sensitive-key values and all string/free-text config values. Numeric,
+boolean, and `None` config values still pass through. This redaction is gated by
+the run's effective `TraigentConfig.privacy_enabled` setting, including
+configuration loaded from `TRAIGENT_PRIVACY_MODE=true` for compatibility. Do not
+use `@traigent.optimize(..., privacy_enabled=True)` for new code; that decorator
+keyword is deprecated and emits a warning. Use `offline=True` instead when the
+requirement is no Traigent backend egress.
+
+Use `offline=True` when your policy requires no Traigent backend egress at all:
 
 ```python
 @traigent.optimize(
@@ -63,8 +83,10 @@ backend egress at all:
 No-egress runs keep Traigent optimization metadata local while still allowing your
 own function to call LLM providers or other services.
 
-Use `TRAIGENT_DISABLE_TELEMETRY=true` for telemetry opt-out and `offline=True`
-for zero Traigent backend egress.
+Use `TRAIGENT_DISABLE_TELEMETRY=true` for SDK telemetry opt-out, effective
+`TraigentConfig.privacy_enabled` privacy mode to redact tuned string config
+values on privacy-mode submissions, and `offline=True` for zero Traigent backend
+egress.
 
 ### OpenTelemetry Tracing
 
@@ -128,7 +150,7 @@ Telemetry data is used for:
 - No data is sent to the Traigent backend
 
 **Portal-backed runs**:
-- Configuration IDs/schema and numeric metrics can be sent to Traigent backend for optimization coordination
+- Tuned config-space values, configuration IDs/schema, and numeric metrics can be sent to Traigent backend for optimization coordination
 - Retention policies depend on your managed-service agreement
 - You can request data deletion at any time
 
@@ -249,7 +271,10 @@ control and CI artifact collection in sensitive projects.
 ### Data Sanitization
 
 Configuration data is sanitized before telemetry. Private/internal keys
-(starting with `_`) are automatically removed.
+(starting with `_`) are automatically removed. On default portal-backed
+submissions, tuned config values are otherwise sent unchanged so the portal can
+display winning configs. On privacy-mode submissions, sensitive-key values and
+all string/free-text config values are redacted while preserving the tuned keys.
 
 ### Error Handling
 
@@ -305,9 +330,10 @@ For HIPAA compliance or handling sensitive data:
 
 ### Q: Is telemetry enabled by default?
 
-**A**: Yes, for local optimization metadata. The default portal-backed path sends
-configuration IDs/schema and numeric metrics only; use `offline=True` for zero
-Traigent backend egress.
+**A**: Yes, for local optimization metadata. The default portal-backed path can
+send tuned config-space values, configuration IDs/schema, and numeric metrics;
+use privacy-mode redaction when backend coordination is needed without tuned
+string values, or `offline=True` for zero Traigent backend egress.
 
 ### Q: How do I verify telemetry is disabled?
 

{traigent-0.18.1.dev10 → traigent-0.19.1}/docs/architecture/stop_conditions.md

@@ -29,9 +29,12 @@ Built-in implementations:
 | `MetricLimitStopCondition` | Soft stop when the cumulative value of a named completed-trial metric reaches a limit. | `metric_limit`, `metric_name`, `metric_include_pruned`. |
 | `CostLimitStopCondition` | Hard money-spend guard backed by `CostEnforcer` permits before execution starts. Parallel-safe. | `cost_limit`, `cost_approved`. |
 | `HypervolumeConvergenceStopCondition` | Stops when hypervolume improvement remains below a threshold across a sliding window. | `convergence_metric="hypervolume_improvement"`, `convergence_window`, `convergence_threshold`. |
+| `SemanticSaturationStopCondition` | Stops when per-example quality vectors are stable and monitored continuous objectives are no longer improving. | `semantic_saturation={...}`. |
 
-`budget_limit` remains as a deprecated alias for `metric_limit` for compatibility.
-New code should not use it.
+`budget_limit`/`budget_metric`/`budget_include_pruned` were removed in 0.13.0.
+Passing any of them to `@traigent.optimize` or `.optimize(...)` now raises
+`TypeError`. Use `cost_limit` for money-spend control, or `metric_limit`/
+`metric_name` for other cumulative metrics.
 
 ## Cost limit vs metric limit
 
@@ -58,10 +61,12 @@ def chat(question: str) -> str:
     ...
 ```
 
-Legacy migration:
+Removed legacy API:
 
 ```python
-# Deprecated compatibility path. Emits a DeprecationWarning.
+# Raises TypeError: budget_limit/budget_metric/budget_include_pruned were
+# removed in 0.13.0. Use cost_limit=<value> and/or metric_limit=<value> with
+# metric_name=<name> instead.
 @traigent.optimize(
     eval_dataset="qa.jsonl",
     configuration_space={"temperature": [0.0, 0.5, 0.9]},
@@ -72,15 +77,53 @@ def chat(question: str) -> str:
     ...
 ```
 
-If a legacy `budget_limit` call omits the metric name, Traigent defaults to
-`total_cost` for compatibility and warns that money spend control should use
-`cost_limit` instead.
+Migrate to:
+
+```python
+@traigent.optimize(
+    eval_dataset="qa.jsonl",
+    configuration_space={"temperature": [0.0, 0.5, 0.9]},
+    metric_limit=50_000,
+    metric_name="total_tokens",
+)
+def chat(question: str) -> str:
+    ...
+```
 
 The orchestrator instantiates the conditions during construction via
 `_configure_stop_conditions()` and calls `reset()` for every run so state never leaks
 between optimizations. `_should_stop()` evaluates all configured conditions before
 fallback logic (timeout or optimizer-provided stop signals).
 
+## Semantic saturation
+
+`semantic_saturation` is an opt-in stop condition for runs where aggregate
+accuracy alone is not enough to decide convergence. It only reads `example_id`
+and numeric or boolean values from each example's `metrics` map. It never reads
+or emits inputs, expected outputs, actual outputs, model text, or document
+content.
+
+The condition selects the latest completed trials with distinct configuration
+signatures, warms up until `max(window, min_trials)` distinct configs are
+available, then evaluates the latest `window` configs:
+
+* Quality metrics come from `example_score_metrics`/`accuracy_metrics` or from
+  accuracy-like and binary per-example metrics.
+* Quality saturation is measured as churn across common example IDs, gated by
+  `min_overlap`, `score_tolerance`, and `churn_threshold`.
+* Continuous objectives come from `continuous_objectives`/`objectives`, the
+  `ObjectiveSchema`, or cost/latency/token-like aggregate metrics.
+* Continuous objectives use direction-aware best improvement over the window,
+  compared to `relative_improvement_epsilon` and
+  `absolute_improvement_epsilon`.
+
+The run stops only when every quality metric and every continuous objective is
+saturated. When it fires, `OptimizationResult.stop_reason` is
+`"semantic_saturation"`. The latest sanitized decision payload is emitted under
+`OptimizationResult.metadata["semantic_saturation"]` and follows TraigentSchema
+`optimization/semantic_saturation_schema.json`; example ID lists are capped by
+`max_example_ids`.
+
 ## Vendor-error pause semantics
 
 When every trial in a parallel batch fails with a vendor-classifiable error
@@ -175,6 +218,8 @@ All three examples share the same stop-condition machinery with no additional
 plumbing.
 
 Built-in convergence stops report `OptimizationResult.stop_reason = "convergence"`.
+Semantic saturation reports
+`OptimizationResult.stop_reason = "semantic_saturation"`.
 Custom stop-condition instances still report the generic `"condition"` reason
 unless they are explicitly mapped into the public `StopReason` contract.
 
@@ -186,6 +231,11 @@ Unit coverage lives under:
   - Max-trial threshold (including invalid inputs).
   - Plateau detection, weight handling, reset semantics, and parameter validation.
   - Metric-limit enforcement, compatibility fallback, and pruned-trial filtering.
+  - Stop-condition exports include semantic saturation.
+* `tests/unit/core/test_semantic_saturation_stop_condition.py` – verifies:
+  - Stable vectors, boolean scores, aggregate-flat no-stop behavior, repeated
+    config warmup, cost-improving continuation, schema-valid result metadata,
+    and the privacy boundary.
 * `tests/unit/core/test_orchestrator.py` – integration tests for plateau and metric limit
   within the orchestrator, ensuring early termination and reasonable counts in
   sequential runs.

{traigent-0.18.1.dev10 → traigent-0.19.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "traigent"
-version = "0.18.1.dev10"
+version = "0.19.1"
 authors = [
     {name = "Traigent Team", email = "opensource@traigent.ai"},
 ]
@@ -137,7 +137,7 @@ mcp = [
 
 # Internal schema validation support for DTO strict-validation paths.
 internal_schema = [
-    "traigent-schema==4.1.0",
+    "traigent-schema==4.7.1",
 ]
 
 # Testing dependencies
@@ -199,7 +199,9 @@ ml = [
     "scipy>=1.7.0",
 ]
 
-# DeepEval integration (LLM evaluation metrics as optimization objectives)
+# DeepEval integration (LLM evaluation metrics as optimization objectives).
+# Explicit opt-in only while Aikido/deepeval#2497 telemetry exfiltration remains
+# unfixed upstream; Traigent applies telemetry and TracerProvider guards at import.
 deepeval = [
     "deepeval>=1.0.0",
 ]

{traigent-0.18.1.dev10 → traigent-0.19.1}/traigent/adapters/execution_adapter.py

@@ -153,12 +153,12 @@ class LocalExecutionAdapter(ExecutionAdapter):
             }
 
         except Exception as e:
-            logger.error(f"Edge Analytics execution failed: {str(e)}")
+            logger.error(f"Local execution failed: {str(e)}")
             raise
 
     async def get_execution_mode(self) -> str:
         """Get execution mode."""
-        return ExecutionMode.EDGE_ANALYTICS.value
+        return ExecutionMode.LOCAL.value
 
     def _evaluate_output(
         self,

{traigent-0.18.1.dev10 → traigent-0.19.1}/traigent/analytics/predictive.py

@@ -760,18 +760,6 @@ class PerformanceForecaster:
         else:
             avg_score = 0.5
 
-        # Check for missing metrics and add warnings
-        warnings = {}
-        if (
-            isinstance(config_or_config_history, dict)
-            and "metrics" in config_or_config_history
-        ):
-            metrics = config_or_config_history["metrics"]
-            expected_metrics = ["accuracy", "cost", "latency"]
-            missing = [m for m in expected_metrics if m not in metrics]
-            if missing:
-                warnings["missing_metrics"] = missing
-
         result = {
             "expected_improvement": 0.05,
             "confidence": 0.7,
@@ -780,9 +768,6 @@ class PerformanceForecaster:
             "predicted_score": avg_score,
         }
 
-        if warnings:
-            result["warnings"] = warnings
-
         return result
 
 

{traigent-0.18.1.dev10 → traigent-0.19.1}/traigent/analytics/render.py

@@ -19,6 +19,7 @@ optional dependency (``pip install 'traigent[analytics]'`` or
 
 from __future__ import annotations
 
+import math
 from pathlib import Path
 from typing import Any, Literal
 
@@ -92,7 +93,7 @@ def _as_float(value: Any) -> float | None:
     else:
         return None
     # Reject NaN/inf so matplotlib never plots a meaningless point.
-    if result != result or result in (float("inf"), float("-inf")):
+    if not math.isfinite(result):
         return None
     return result
 

{traigent-0.18.1.dev10 → traigent-0.19.1}/traigent/api/config_builder.py

@@ -163,14 +163,6 @@ class ConfigurationBuilder:
         """Clear global configuration."""
         self.global_config.clear()
 
-    @staticmethod
-    def _normalize_execution_mode(execution_mode: str) -> str:
-        """Normalize execution mode labels (deprecated)."""
-        return resolve_execution_policy(
-            execution_mode=execution_mode,
-            source_hint="config_builder.normalize_execution_mode",
-        ).legacy_execution_mode.value
-
 
 # Module-level functions for backward compatibility
 def build_optimize_configuration(