@amsterdamdatalabs/enact-extensions 0.1.55 → 0.1.56

package/README.md

@@ -95,7 +95,7 @@ marker.
 | Codex | `.codex/agents/*.toml`, `.agents/skills/<skill>/`, `.codex/config.toml` MCP tables, and `.codex/hooks.json`. Trust the exact project path and review hooks with `/hooks`. |
 | Cursor | `.cursor/agents/*.md`, `.cursor/skills/<skill>/`, `.cursor/mcp.json`, and `.cursor/hooks.json`. |
 | Kimi Code | `.kimi-code/agents/*.md`, `.kimi-code/skills/<skill>/`, and `.kimi-code/mcp.json`. Kimi hooks remain global-only and are installed by `enact-vps`, never by this repo-local command. |
-| OpenCode | A hook-free bundle writes `.opencode/agents/*.md`, `.opencode/skills/<skill>/`, and root `opencode.json` MCP entries. `enact-repo` declares hooks, so its repo-local OpenCode install is refused before any write; install its explicit global OpenCode plugin through `enact-vps`. |
+| OpenCode | `.opencode/agents/*.md`, `.opencode/skills/<skill>/`, and root `opencode.json` MCP entries. The repo-local installer owns these files and removes its lock-owned legacy plugin root unconditionally. |
 
 Skills are installed at each host's native project discovery path: `.agents/skills/` for
 Codex and `.claude/skills/`, `.cursor/skills/`, `.kimi-code/skills/`, or

package/extensions/enact-repo/.agents/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "enact-repo",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "Baseline agent setup for any repository: the full Enact skill catalog plus guard, briefing, and code-review-graph hooks and MCP tooling, installed at repo scope.",
   "author": {
     "name": "amsterdamdatalabs"

package/extensions/enact-repo/README.md

@@ -72,13 +72,13 @@ host, with no `--host` appended.
 Install into a repository with `enact-extensions install enact-repo --repo <repo-root>` (see the
 top-level README, "Repo-local install"). The command writes direct native project files only:
 `.claude/agents` and `.claude/skills`; `.codex/agents` and `.agents/skills`;
-`.cursor/agents` and `.cursor/skills`; `.kimi-code/agents` and `.kimi-code/skills`; and,
-for hook-free bundles, `.opencode/agents` and `.opencode/skills`. It also writes each host's
+`.cursor/agents` and `.cursor/skills`; `.kimi-code/agents` and `.kimi-code/skills`; and
+`.opencode/agents` and `.opencode/skills`. It also writes each host's
 native MCP and hook configuration where supported. It never writes a plugin root, marketplace,
 or plugin registration.
-Kimi hooks are global-only and are installed by `enact-vps`, not by this bundle. OpenCode has no
-repo-local hook carrier: an OpenCode install of a hook-bearing bundle fails before writing anything
-and requires the explicit global OpenCode plugin through `enact-vps`. The installer also marks the
+Kimi hooks are global-only and are installed by `enact-vps`, not by this bundle. OpenCode's
+process-level hook carrier is separate from this repo-local installer; OpenCode bundles always
+install their native local files and remove lock-owned legacy plugin roots. The installer also marks the
 repo as managed through root `enact-config.toml` (the file `enact-hook` checks): it creates the
 file with `version = 1` when missing, manages the `[extensions]` declaration for this bundle by
 text-level surgery only, removes the legacy marker-only `[skills]` block, and never writes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@amsterdamdatalabs/enact-extensions",
-  "version": "0.1.55",
+  "version": "0.1.56",
   "description": "Create and validate Enact multi-platform plugin manifests",
   "license": "UNLICENSED",
   "type": "module",

package/scripts/lib/run-repo-install.mjs

@@ -17,8 +17,8 @@
  *   kimi     — `.kimi-code/agents`, `.kimi-code/skills`, and `.kimi-code/mcp.json`.
  *              Kimi hooks remain global-only and are not owned here.
  *   opencode — `.opencode/agents`, `.opencode/skills`, and `opencode.json` MCP.
- *              OpenCode has no native project hook surface, so a hook-bearing
- *              bundle fails before writes and names enact-vps' global plugin path.
+ *              Its process-level hook carrier is global, while this installer
+ *              owns every repo-local artifact and legacy-root migration.
  *
  * Repo installation never writes a plugin root, marketplace, or plugin
  * registration. Those belong exclusively to explicit global installation.
@@ -507,11 +507,6 @@ const HOST_ADAPTERS = {
   },
 
   opencode(plan, bundle, pluginRoot) {
-    if (bundle.hooks) {
-      throw new Error(
-        "OpenCode repo-local installation cannot install hooks: install the explicit global OpenCode plugin through enact-vps first",
-      );
-    }
     addNativeAgents(plan, pluginRoot, "opencode");
     addNativeSkills(plan, bundle, "opencode");
     const mcp = jsonMerge(plan, "opencode.json");