Skip to content

chore(dsh): move the npm package to the @everos-ai scope - #20

Merged
gloryfromca merged 1 commit into
mainfrom
chore/dsh-npm-scope-everos-ai
Sep 10, 2026
Merged

gloryfromca merged 1 commit into
mainfrom
chore/dsh-npm-scope-everos-ai

Conversation

@gloryfromca

Copy link
Copy Markdown
Member

Renames the package from @evermind-ai/dsh-plugin to @everos-ai/dsh-plugin,
matching #19. The name was never published to npm, so there is no deprecation
step and nothing for existing users to migrate.

cordis.patch.yml moves with it

Its name is the module DSH resolves when mounting the plugin into a
composition, so it has to equal the published package name or the host cannot
load what it just installed. The composition-local id: everos-memory is a DSH
concept, unrelated to the npm name, and stays.

 - insert:
     - id: everos-memory
-      name: '@evermind-ai/dsh-plugin'
+      name: '@everos-ai/dsh-plugin'

One test added

Nothing in the suite pinned that pair. A future rename could miss the patch and
ship a package pointing at a name that no longer exists, and the suite would
stay green. test/package-identity.test.ts asserts the patch's name equals
package.json's name.

It was verified to have teeth, not just to be green: reverting the patch to the
old name turns the run red (20 tests, 19 pass, 1 fail), restoring it turns it
green again.

Verification

npm run ci green: lint, typecheck, tests, build.

Tests 20 run / 20 pass / 0 skipped
npm pack --dry-run everos-ai-dsh-plugin-0.1.0.tgz, 22 files, ships cordis.patch.yml
Old scope left in the tree none

Local runs emit EBADENGINE because this machine has Node 23.10.0 and the
package requires ^22.19.0 || >=24.0.0. CI runs Node 22.19.0 and is
unaffected.

Renames the package from @evermind-ai/dsh-plugin to @everos-ai/dsh-plugin,
matching the openclaw plugin. The name was never published, so there is no
deprecation and nothing for existing users to migrate.

cordis.patch.yml has to move with it. Its `name` is the module DSH resolves
when it mounts the plugin into a composition, so it must equal the published
package name or the host cannot load what it installed. The composition-local
`id: everos-memory` is a DSH concept and stays.

Nothing in the suite pinned that pair, so a rename could silently ship a
patch pointing at a package that no longer exists. Adds one test asserting
the patch's `name` equals package.json's `name`. Verified by reverting the
patch to the old name and watching the test fail, then restoring it.

npm run ci is green: 20 tests, 0 skipped. npm pack ships cordis.patch.yml as
everos-ai-dsh-plugin-0.1.0.tgz.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@gloryfromca
gloryfromca merged commit f46b3db into main Sep 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant