Files
opencode-toolkit/TODO.md
T

2.2 KiB

TODO

First usable release

  • Create an independent OpenCode V2 package and record the accepted plan.
  • Import a small set of ECC skills and agent prompts with provenance.
  • Implement the V2 plugin entry and read-only project-status tool.
  • Add a project installer with collision and local-edit protection.
  • Add uninstall behavior that preserves modified managed files.
  • Add unit and installer regression tests and coverage threshold.
  • Install the generated tarball in an isolated project and validate idempotent CLI install/uninstall and native agent discovery.
  • Validate the tarball in a project with pre-existing JSONC settings, unrelated plugins, and a user-owned skill; verify repeat install and conservative uninstall after a managed-file edit.
  • Diagnose and fix plugin loading: register the installed local plugin directory, and expose its namespaced tool through Code Mode. Verify activation and execution in OpenCode 2.0.24 against a local mock provider.
  • Detect and refuse ambiguous projects with both project config locations.
  • Evaluate support for multi-layer project config only after verifying V2 array merge and precedence behavior.
  • Install the package tarball into a clean project outside this repository; verify CLI idempotency and native agent discovery.
  • Document how to install and verify a release-candidate tarball without credentials, including idempotency and conservative uninstall checks.
  • Perform and record a pre-release manual security review of installer paths, file ownership, configuration edits, and failure limitations.
  • Add provider-backed verification after confirming credentials and model usage budget with the user.
  • Confirm repository/package names and decide whether to publish.

Follow-up

  • Add a diagnostic command for installation state and supported versions.
  • Evaluate global/XDG installation only if project-local usage proves insufficient.
  • Revisit memory and continuous-learning features as a separate design.
  • Review selected ECC content against a newer upstream SHA and update docs/PROVENANCE.md after any selective import.