[777genius]

Why

OpenCode project plugins need an explicit project configuration context, with exact ownership and data receipts, so installation and recovery cannot affect the user profile or another repository.

Changes

• Configure .opencode/skills and the selected root opencode.json / opencode.jsonc through the existing transactional transition and recovery engine.
• Keep user config semantics and foreign members intact; enforce exact scoped package, skill, native member and persisted data authority.
• Refuse stale active MCP projections whose embedded data root differs from the selected receipt, without rewriting immutable packages.

Verification

Two independent final implementation reviews are GO at production checkpoint 90fcc0af; both reports are committed.

The public CLI E2E uses real TLS Git acquisition through saved A/B install, byte-stable sync, old-pin repair after the remote ref moves, native and managed artifact repair, repeated recovery, update, status and repeated removal. It preserves user/B byte, mode and state inventories plus retained application data. The stdio preparation fixture is inert; it is not a native OpenCode runtime qualification.

Focused client/provider and composed lifecycle tests pass; changed-line lint reports zero issues. Actual native discovery, MCP initialization and model behavior remain separately unqualified.

Stack

Client-specific draft for #472, temporarily based on the reviewed integration checkpoint branch. Retarget and merge only into the project feature branch after applicable CI, not into main.

Delivered in #499

Delivered by #499, merged into main as 3b93148c. The integrated source 3386c72a91e7e9b3574f12ce0613b399227a1ada passed all 74 check runs and 24 PR workflows; the actual merge tree is identical to that validated source.

This PR's reviewed head 3d4e900a6251095a9dcb1cd94cdf1718c09118b1 is preserved by ancestry in the integrated source and the main merge. Closing as incorporated; no separate merge into the earlier stacked base is needed.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}