fix(plugin): load local toolkit and expose status tool

This commit is contained in:
sargatxet committed 2026-10-08 13:35:44 +02:00
1 parent aac5627e98
commit 2fcfe2fbf7
14 files changed
+145 -34

No files matched your search

+9 -7
View File
@@ -80,15 +80,16 @@ unverified behavior.
**Acceptance:** OpenCode discovers installed skills and agents; resources are
present; imported files have provenance and license attribution.
### Phase 2 — Prove V2 runtime (unit contract complete; real-runtime smoke open)
### Phase 2 — Prove V2 runtime (complete)
- Use `Plugin.define({ id, setup(ctx) })`, V2 transforms and documented VCS APIs.
- Avoid the V1 plugin callback, V1 event names, and module-global session state.
- Verify namespaced tool registration and output through contract tests.
- Test loading and unloading under an actual OpenCode 2.0.24 runtime.
- Test loading and tool execution under an actual OpenCode 2.0.24 runtime.
**Acceptance:** installed package appears as one active plugin and the tool runs
in a real OpenCode session without a provider call to exercise the tool itself.
**Acceptance:** installed package loads and the tool runs in a real OpenCode
session. Verified using a local mock OpenAI-compatible endpoint; no external
provider call was made.
### Phase 3 — Implement project installer (initial behavior complete)
@@ -117,9 +118,10 @@ uninstall preserves locally modified content.
- Verify behavior in a project with pre-existing config and skills.
**Progress:** package tarball installs outside the checkout; the CLI is
idempotent and OpenCode discovers the three packaged agents. OpenCode 2.0.24's
standalone plugin API reports an empty active-plugin list, so the custom tool's
runtime activation still needs diagnosis.
idempotent and OpenCode discovers the three packaged agents. Runtime testing
showed that the old npm-name entry caused a registry 404 and that the namespaced
tool needed Code Mode enabled. Both were corrected and the packaged plugin and
tool were verified in a local mock-provider session.
**Acceptance:** no checkout symlink or development dependency is needed at
runtime; config collisions are handled or reported before writes; the V2 plugin