ops: verify the command-line and tarball install path on a clean profile #5

New issue

Open

opened 2026-10-22 19:06:33 +00:00 by dsh · 2 comments

dsh commented

2026-10-22 19:06:33 +00:00

Owner

Context

The plugin was installed in the web profile through plugin_manager (application: applied). The documented dsh plugin --profile <name> add <path|tarball> path has not yet been exercised on a clean profile.

Acceptance criteria

npm pack produces a tarball whose contents match the documented list.
Create or reuse a non-production profile and install from the tarball with dsh plugin.
Confirm the bundle is selected, the row mounts, and resend_status / mcp__resend__list-domains work.
Confirm a local-path (link:) install works after npm run dev:link.
Record exact commands and outcomes in README/AGENTS.

Notes

Do not disturb the live web profile beyond what is necessary.
If a Host restart is required, document that explicitly.

## Context The plugin was installed in the `web` profile through `plugin_manager` (application: applied). The documented `dsh plugin --profile <name> add <path|tarball>` path has not yet been exercised on a clean profile. ## Acceptance criteria - [ ] `npm pack` produces a tarball whose contents match the documented list. - [ ] Create or reuse a non-production profile and install from the tarball with `dsh plugin`. - [ ] Confirm the bundle is selected, the row mounts, and `resend_status` / `mcp__resend__list-domains` work. - [ ] Confirm a local-path (`link:`) install works after `npm run dev:link`. - [ ] Record exact commands and outcomes in README/AGENTS. ## Notes - Do not disturb the live `web` profile beyond what is necessary. - If a Host restart is required, document that explicitly.

dsh referenced this issue

2026-10-23 00:57:35 +00:00

release: publish dsh-resend-mcp to npm and a public mirror #2

dsh commented

2026-10-23 10:24:43 +00:00

Author

Owner

Install-path verification from the public registry:

export PATH="/opt/node-v24.22.0-linux-x64/bin:$PATH"
DSH_HOME=$(mktemp -d) dsh plugin --profile clean add dsh-resend-mcp@0.1.0

Result: a real 0.1.0 directory (not a link) in the throwaway profile. Peer warnings are expected there because no DSH runtime is installed; in the live profile DSH's resolver supplies schemastery 3.18.5, dsh-tools/dsh-mcp-client 0.2.0-rc.2, and @modelcontextprotocol/client 2.0.0 from the installation scope, and createRuntimeResolution reports no skipped bundles.

Remaining check: restart the Host once so the web profile loads the npmjs-installed 0.1.0, then confirm resend_status and the tools. Keeping this open until that restart.

Install-path verification from the public registry: ```bash export PATH="/opt/node-v24.22.0-linux-x64/bin:$PATH" DSH_HOME=$(mktemp -d) dsh plugin --profile clean add dsh-resend-mcp@0.1.0 ``` Result: a real `0.1.0` directory (not a link) in the throwaway profile. Peer warnings are expected there because no DSH runtime is installed; in the live profile DSH's resolver supplies `schemastery` 3.18.5, `dsh-tools`/`dsh-mcp-client` 0.2.0-rc.2, and `@modelcontextprotocol/client` 2.0.0 from the installation scope, and `createRuntimeResolution` reports no skipped bundles. Remaining check: restart the Host once so the `web` profile loads the npmjs-installed 0.1.0, then confirm `resend_status` and the tools. Keeping this open until that restart.

dsh commented

2026-10-23 13:37:30 +00:00

Author

Owner

Update: the live web profile is now on the npmjs-installed 0.1.2 (Plugin Manager reports restart-required). The resolver peer check still holds. Only the Host restart remains before this can close.

Update: the live `web` profile is now on the npmjs-installed `0.1.2` (Plugin Manager reports `restart-required`). The resolver peer check still holds. Only the Host restart remains before this can close.

dsh added the

labels

2026-10-23 17:26:21 +00:00