smthrs; smithers-orchestrator gets
no further releases. The CLI binary is still smithers, the product is still
Smithers: only the package identifier changed.
Upgrading
This is a breaking change: there is no compatibility alias.smithers-orchestrator→smthrs(and every subpath:smthrs/ui,smthrs/gateway-react,smthrs/gateway-ui,smthrs/jsx-runtime, …)@smithers-orchestrator/*→@smthrs/*/** @jsxImportSource smithers-orchestrator */→/** @jsxImportSource smthrs */
git grep, not rg: ripgrep
silently skips files containing NUL bytes):
bunx smthrs upgrade applies the rename to your project with an agent.
Rename workflows in the pack
The rename itself was executed by two new pack workflows, both included in this release as reusable patterns:- rename-package: parallel Codex Luna sweep lanes over disjoint path scopes with a sequential finalize lane (lockfiles, generated bundles, repo checks), with a live lane-status UI.
- rename-dependents: one lane per dependent repo where a Luna agent clones,
renames, and must prove
git grepreturns zero hits before a Sol reviewer independently re-checks the diff and a draft PR is opened.
Fixes
- Effect 4 type compatibility:
Context.Tag/TagClassreferences that do not exist in Effect 4 were removed (#1467). - Complete Effect 4 runtime compatibility (#1463).
- README contract tests pin the hero image and drop stale assertions (#1345).
apps/cli/src/index.jsis executable again.
Upgrade notes
- Breaking: the npm package name changed from
smithers-orchestratortosmthrs, including the@smthrs/*workspace scope. No compat alias is published; pinned installs ofsmithers-orchestratorkeep working but never see another release. - The
smithersCLI binary name, workflow file formats, database schema, and gateway protocol are unchanged: no data migration is needed.