Known issues and validation gaps

The installer deliberately refuses projects with both opencode.json and .opencode/opencode.json. Decide whether safe support for multi-layer config is worth implementing after studying V2 merge behavior.
The installer previously registered the unpublished npm package name, which made OpenCode attempt a registry download and fail with 404. It now registers the local package directory. The package root provides index.js because configured local plugin paths must be directories with an entrypoint.
The namespaced tool now opts into Code Mode. OpenCode 2.0.24 loaded the installed tarball and executed toolkit_project_status through a local mock OpenAI-compatible endpoint without external model usage.
Provider-backed workflows (agent delegation and actual skill invocation) have not been tested; they require configured credentials and explicit approval of any model usage.
Optional memory has deterministic tests but has not been checked for persistence and isolation across restarts in a live OpenCode 2.0.24 profile. Provider-backed learning proposals are not implemented.
Global/XDG installation is not implemented; project-level update and uninstall are supported, while global installation remains out of scope.
The package name and GitHub URL are provisional and must be confirmed before publishing.
The uninstaller currently removes files incrementally. If an I/O failure occurs mid-uninstall, inspect the install manifest and rerun after resolving the filesystem issue.