harness-alchemist 0.1.4 → 0.1.5

package/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "harness-alchemist",
   "displayName": "Harness Alchemist",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Scaffold, validate, and publish portable coding-agent plugins across Claude Code, Codex, OpenCode, Antigravity, and DeepSeek Harness.",
   "author": {
     "name": "Haochuan Zhang"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "harness-alchemist",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Scaffold, validate, and publish portable coding-agent plugins across Claude Code, Codex, OpenCode, Antigravity, and DeepSeek Harness.",
   "author": {
     "name": "Haochuan Zhang",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "harness-alchemist",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Scaffold, validate, and publish portable coding-agent plugins across Claude Code, Codex, OpenCode, Antigravity, and DeepSeek Harness.",
   "type": "module",
   "bin": {

package/skills/harness-alchemist/references/codex.md

@@ -27,9 +27,13 @@ The rich `interface` object is recommended for public presentation but is not re
 
 ```bash
 codex plugin marketplace add owner/repo
+codex plugin add <plugin-name>@<marketplace-name>
+codex plugin list
 ```
 
-Open `/plugins` to install from a configured marketplace, then start a new session. Codex npm marketplace sources download packages without running lifecycle scripts, so published packages must already contain built runtime files.
+The `@marketplace` suffix is required for `codex plugin add`; a bare plugin
+name is rejected. Headless install works without opening `/plugins`, then
+start a new session. Codex npm marketplace sources download packages without running lifecycle scripts, so published packages must already contain built runtime files.
 
 Official references:
 

package/skills/harness-alchemist/references/deepseek-harness.md

@@ -49,6 +49,12 @@ dsh plugin --profile demo add @scope/my-plugin
 dsh --profile demo --dump-config
 ```
 
+`dsh plugin add` forwards to pnpm in the profile directory, so an unpublished checkout can be installed by absolute path and stays linked to the working tree:
+
+```bash
+dsh plugin --profile demo add /absolute/path/to/my-plugin
+```
+
 Bundle membership changes require a profile restart. Profile patch edits may hot-reload.
 
 Shared Agent Skills are discovered from project `.agents/skills` and other configured filesystem roots. Package-relative skill assets are not automatically activated by a bundle; install repository skills separately when needed.

package/skills/harness-alchemist/references/opencode.md

@@ -33,12 +33,16 @@ OpenCode accepts npm package names in `opencode.json`:
 
 OpenCode installs npm plugins with Bun at startup. For local development, register an absolute `file://` URL to compiled JavaScript or a direct TypeScript file with all of its dependencies available.
 
-Skills are separate from the npm plugin. Install them from the Git repository:
+Skills are discovered from `~/.agents/skills/` (and project `.agents/skills/`), not from the OpenCode config directory, and symlinked skill directories are skipped. Install them from the Git repository or a checkout:
 
 ```bash
 npx skills add owner/repo --agent opencode
+# or, from a local clone:
+cp -R skills/<name> ~/.agents/skills/
 ```
 
+Verify discovery with `opencode debug skill`.
+
 ## Extension Rules
 
 - Return `{}` when no hooks are registered.

package/templates/v0.1.0/universal-typescript/README.md.tpl

@@ -19,7 +19,7 @@ cordis.patch.yml             DeepSeek Harness bundle layer
 plugin.json                  Antigravity plugin manifest
 ```
 
-The initial runtime entrypoints are intentionally inert. Add only the hooks, tools, or services the plugin actually needs.
+The runtime entrypoints are thin adapters that delegate to skill scripts; see `skills/{{NAME}}/references/tool-contract.md` before extending them.
 
 ## Skill Boundaries
 
@@ -54,13 +54,13 @@ npm pack --dry-run
 
 ## GitHub Release Publishing
 
-`.github/workflows/npm-publish.yml` publishes when a GitHub release is
-published. Tag the release as `vX.Y.Z` (or a semver prerelease such as
-`vX.Y.Z-rc.1`); the workflow applies that version, synchronizes manifests,
+`.github/workflows/npm-publish.yml` publishes when a `vX.Y.Z` tag is pushed
+(or a GitHub release with a semver tag such as `vX.Y.Z-rc.1` is published);
+the workflow applies that version, synchronizes manifests,
 verifies the package, and publishes with npm provenance.
 
 Configure the repository `NPM_TOKEN` secret with an npm publish token before
-creating a release.
+pushing the tag.
 
 ## Claude Code
 
@@ -80,9 +80,11 @@ claude plugin validate . --strict
 
 ```bash
 codex plugin marketplace add {{REPOSITORY_SOURCE}}
+codex plugin add {{NAME}}@{{MARKETPLACE}}
+codex plugin list
 ```
 
-Open `/plugins`, install **{{DISPLAY_NAME}}**, and start a new session.
+The `@{{MARKETPLACE}}` suffix is required; a bare plugin name is rejected.
 
 ## OpenCode
 
@@ -95,12 +97,24 @@ After publishing `{{PACKAGE_NAME}}`, add it to `opencode.json`:
 }
 ```
 
-Install the shared skill separately:
+For an unpublished checkout, point the entry at the built adapter instead:
+
+```json
+{
+  "plugin": ["file:///absolute/path/to/{{NAME}}/dist/opencode.js"]
+}
+```
+
+Skills are discovered from `~/.agents/skills/`, not from the OpenCode config
+directory, and symlinked directories are skipped. Copy each shared skill you
+need:
 
 ```bash
-npx skills add {{REPOSITORY_SOURCE}} --agent opencode
+cp -R skills/{{NAME}} ~/.agents/skills/
 ```
 
+Verify with `opencode debug skill`.
+
 ## Google Antigravity
 
 Clone the repository and install its root as a plugin:
@@ -120,12 +134,18 @@ dsh plugin --profile demo add {{PACKAGE_NAME}}
 dsh --profile demo --dump-config
 ```
 
-The bundle loads `{{PACKAGE_NAME}}/deepseek`. Install the shared Agent Skill separately when the workflow needs it:
+For an unpublished checkout, `dsh plugin add` forwards to pnpm, so a local
+path works and stays linked to your working tree:
 
 ```bash
-npx skills add {{REPOSITORY_SOURCE}}
+dsh plugin --profile demo add /absolute/path/to/{{NAME}}
 ```
 
+The bundle loads `{{PACKAGE_NAME}}/deepseek` through `package.json`'s
+`dsh.bundle.patch` entry. Verify composition with
+`dsh --profile demo --dump-config`, which should list an insert for
+`{{NAME}}`.
+
 ## License
 
 {{LICENSE}}