# TODO

## First usable release

- [x] Create an independent OpenCode V2 package and record the accepted plan.
- [x] Import a small set of ECC skills and agent prompts with provenance.
- [x] Implement the V2 plugin entry and read-only project-status tool.
- [x] Add a project installer with collision and local-edit protection.
- [x] Add uninstall behavior that preserves modified managed files.
- [x] Add unit and installer regression tests and coverage threshold.
- [x] Install the generated tarball in an isolated project and validate
  idempotent CLI install/uninstall and native agent discovery.
- [x] 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.
- [x] 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.
- [x] 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.
- [x] Install the package tarball into a clean project outside this repository;
  verify CLI idempotency and native agent discovery.
- [x] Document how to install and verify a release-candidate tarball without
  credentials, including idempotency and conservative uninstall checks.
- [x] Perform and record a pre-release manual security review of installer paths,
  file ownership, configuration edits, and failure limitations.
- [x] Publish the `0.1.0-rc.1` tarball and SHA-256 as a repository pre-release;
  install from its public URL in a clean project and verify the checksum.
- [ ] Add provider-backed verification after confirming credentials and model
  usage budget with the user.
- [ ] Decide whether to publish the package to npm; repository pre-releases do
  not publish it to the npm registry.

## Follow-up

- [ ] Verify plugin-storage persistence and session/project isolation in a live
  OpenCode 2.0.24 profile; design opt-in learning proposals as a separate step.
- [ ] Decide whether memory needs a bulk-clear command and background expiry
  cleanup before adding automatic learning.
- [ ] 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`](docs/PROVENANCE.md) after any selective import.