Developer Manual
Versioning
Use the current package set and identify the limits of compatibility evidence.
Current package set: Core rc.1, Runtime preview.5 and Actions preview.8. Try HTTP reference preview.4 or Retell adapter preview.3 with equipment example preview.4.
Version history and scope
Retell preview.1 declarations describe the older Runtime preview.1 / Actions preview.2 line. Retell preview.2 uses a mock facade; HTTP preview.1 simulates bookkeeping. The older private HTTP source uses Runtime preview.3 / Actions preview.4. These are separate from the current runnable examples.
Examples use local test systems. They do not validate live providers, arbitrary crashes or distributed durability. Approved participants can use protected downloads.
Tested boundary
The current package set is Core 1.0.0-rc.1, Runtime 0.2.0-preview.5 and Actions 0.2.0-preview.8. Retell adapter preview.3 and equipment example preview.4 use that set. Core supports Node 20+ and CommonJS; use Node 22+ and ESM for the combined examples. Retell preview.1 declarations remain historical. Try the HTTP example.
What is and is not guaranteed
Use package-root imports and the current package set together. Broader compatibility matrices, migration guarantees, deprecation schedules, schema migration commands, and rollback procedures are not established by the current authority. Do not mix provisional versions or treat readable documentation as package installation access. Revalidate an external consumer when the selected package versions or declaration authority changes.
The package pages in the API Reference provide exact declarations; this chapter provides the current boundary rather than an unapproved migration policy.