Repository navigation
Agent ETA v0.9.2 — Isolate SDK example tracking failures
Pre-release
Agent ETA v0.9.2 repairs the runnable JavaScript SDK example so a tracking failure does not abort the operation it is observing. Previously, a failed timer-driven heartbeat could escape as an uncaught exception, and a failed terminal write could replace the operation's original error.
- The copyable example preserves the operation's exact return value or original thrown value.
- A heartbeat failure emits an incomplete-tracking notice and stops that timer; a final write remains best effort. Failed final writes are never reported as saved completion.
- Tracking startup failures still allow the operation to execute. Status/warning callback exceptions and rejected promises are contained, and the timer and constructed tracker are cleaned up when the operation settles.
- Document the boundaries: this is example code, not a new package SDK export. Lower-level SDK methods, the CLI wrapper, default estimator and retention are unchanged. CPU-blocking work, human waiting, cancellation and remote work need an appropriate explicit lifecycle or process boundary.
Validation: 294 local tests, including isolated SQLite write failures and error-preservation regressions. Clean-package checks cover the runnable installed example, actual heartbeat/final-write failure, CLI/SDK/wrapper/HTTP behavior, and identical forecasts/evaluation reports against v0.9.1. Public Linux/Windows × Node 22/24 CI passed on the release commit.
This is an integration-reliability fix backed by synthetic fault-injection checks. Independent real-user adoption and future prediction accuracy remain pending. No private databases, raw conversations or provider logs are published.