Package migration

Use @soterias/core for the TypeScript library and @soterias/mcp-server for the local MCP server. Python stays soterias. These names describe what each package provides; you do not need to install the platform packages yourself.

The live installation page lists the versions verified through public registry installs. Publishing a new scope does not move or rename an existing package.

For a new Node project, install the matching pilot versions:

npm install @soterias/core@0.1.0-rc.4
npm install @soterias/mcp-server@0.1.0-rc.4

Run the complete first program from this checkout:

node examples/tasks/58-easy-sdk/start.mjs

It imports Soterias from @soterias/core, returns a total of 1500, and records one call in a new private native metrics store. The adjacent example guide explains the code, qualified learning, optional LangChain middleware, and protected accounting tools. Ordinary observation grants no access restrictions or permissions.

Update existing imports, install the new packages, and regenerate your lockfile with your normal package manager. Keep your application configuration and review keys in their existing trusted locations. The native package names are @soterias/core-win32-x64-gnu and @soterias/core-linux-x64-gnu; npm selects the matching one automatically. The MCP command remains soterias-mcp.

The earlier @soterias/sdk and @soterias/mcp names were unpublished candidates, not required compatibility dependencies. Published @kimo267 releases remain available during migration. Removing an organization can unpublish its eligible packages, so deleting the old organization is a separate npm account recovery step. npm does not support changing an existing username directly.

This release changes package names and documentation. It does not close Task16, add platform support, or establish full production/security acceptance.