Release and contract status
Availability, generated references and reproducible documentation updates.
Current service
The production REST API, OAuth MCP connection and dashboard are live. Chemistry checks use an explicitly versioned validator; corpus responses expose semantic provenance rather than claiming every observation was expert reviewed.
SDK distributions
As checked on2026-10-28, the cyberrxn package is not published on npm or PyPI. Installation uses verified first-party distribution files, with content-addressed URLs and SHA-256 metadata. A local build label is not a registry publication.
The public download manifest identifies exact package files. The OpenAPI snapshot and contract manifest identify the documented API and SDK interface snapshots.
Updating this site
Maintain human guides in RU/EN Markdown. Sync the checked-in source contracts, regenerate API references, test links and code examples, then build a static release. A docs change does not require users to upload a local skill; the runtime MCP guide remains hosted by the service.
API schemas and guides should change together. Automated checks detect snapshot drift when sibling repositories are present; independent CI can build from the committed snapshots. Runtime chemistry/source validation remains separate from documentation tests.