fix: bundle @omniroute/opencode-plugin inside omniroute + add 'setup opencode' CLI command

[herjarsa]

Problema

El @omniroute/opencode-plugin (issue #3711) nunca se compilaba como parte del pipeline de npm publish, y no existía un comando CLI para instalarlo en OpenCode. El usuario tenía que extraer el tarball y configurarlo manualmente.

Cambios

@omniroute/opencode-plugin/src/index.ts

• Fix baseURL: La cadena de resolución ahora incluye _provider.options.baseURL como tercer eslabón (plugin opts → auth.json → provider config). Esto corrige el caso donde baseURL se setea via opencode.json o config hook y no era detectado, resultando en 0 modelos.
• Diagnóstico: warnings claros cuando no hay baseURL resoluble.

scripts/build/prepublish.ts

• Nuevo Step 8.8: Compila @omniroute/opencode-plugin via tsup durante el publish. El dist/ viaja dentro del tarball npm (el package.json raíz ya incluye "@omniroute/" en files). Falla con error claro si la compilación falla.

bin/cli/commands/setup-open-code.mjs (NUEVO)

• Comando omniroute setup opencode que:
  1. Resuelve el plugin bundled desde el package omniroute instalado
  2. Detecta el directorio de configuración de OpenCode (XDG-aware, multi-plataforma)
  3. Copia el plugin a ~/.config/opencode/plugins/omniroute/
  4. Crea/actualiza opencode.json (idempotente, reemplaza entries legacy)
  5. Opcional: --auth ejecuta opencode auth login
• runSetupOpenCodeCommand() exportada para testabilidad.

bin/cli/commands/setup.mjs

• Importa y registra setup-open-code como subcomando de setup.

bin/cli/locales/en.json

• String setup.opencode.

Verificación

• @omniroute/opencode-plugin build OK + 257 tests pasan
• Syntax check del nuevo comando CLI OK
• Commit hooks (prettier, eslint, any-budget check) pasan
• Branch basada en upstream/main

[gemini-code-assist]

Code Review

This pull request introduces a new CLI command omniroute setup opencode to automate the installation and registration of the bundled @omniroute/opencode-plugin into a local OpenCode installation, along with integration into the build pipeline. The reviewer feedback highlights several critical issues: a lack of unit or integration tests for the new CLI command (violating the repository style guide), a Windows-specific execution bug in spawnSync when running opencode, potential crashes when parsing empty or non-object opencode.json files, robust filtering of legacy auth plugins, and the risk of publishing stale build artifacts by skipping the plugin rebuild during prepublish.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The pull request introduces a new CLI command file under bin/cli/commands/setup-open-code.mjs and modifies bin/cli/commands/setup.mjs, but does not include any unit or integration tests. This violates the repository style guide rule which requires tests when changing production code in bin/.

References

1. Always include tests when changing production code (src/, open-sse/, electron/, bin/). ^(link)

[gemini-code-assist]

On Windows, executing batch files (.cmd, .bat) via spawnSync requires the shell option to be set to true (or isWin). Without it, the OS cannot execute the script directly, resulting in an ENOENT or ERROR_INVALID_FUNCTION error.

Suggested change

	const res = spawnSync(opencodeBin, ["auth", "login", "--provider", providerId], {
	stdio: "inherit",
	shell: false,
	});
	const res = spawnSync(opencodeBin, ["auth", "login", "--provider", providerId], {
	stdio: "inherit",
	shell: isWin,
	});

[gemini-code-assist]

If opencode.json exists but is empty or contains non-object JSON (such as null or []), JSON.parse will succeed but cfg will not be a valid object. This can cause subsequent property accesses like cfg.plugin to throw a TypeError. We should validate that the parsed result is a non-null object.

Suggested change

	let cfg = {};
	if (existsSync(configPath)) {
	try {
	cfg = JSON.parse(readFileSync(configPath, "utf8"));
	} catch (err) {
	throw new Error(
	`Failed to parse existing ${configPath}: ${err.message}\n` +
	`Fix or remove the file manually, then re-run \`omniroute setup opencode\`.`
	);
	}
	}
	let cfg = {};
	if (existsSync(configPath)) {
	try {
	const parsed = JSON.parse(readFileSync(configPath, "utf8"));
	if (parsed && typeof parsed === "object" && !Array.isArray(parsed)) {
	cfg = parsed;
	}
	} catch (err) {
	throw new Error(
	`Failed to parse existing ${configPath}: ${err.message}\n` +
	`Fix or remove the file manually, then re-run \"omniroute setup opencode\".`
	);
	}
	}

[gemini-code-assist]

If a legacy opencode-omniroute-auth entry is registered as an array without options (e.g., ["opencode-omniroute-auth"]), the current filtering logic will skip it because p[1] is undefined. Refactoring the filter to check the first element of the array regardless of options makes the cleanup much more robust.

Suggested change

	const filtered = plugins.filter((p) => {
	if (typeof p === "string") {
	return !p.includes("opencode-omniroute-auth");
	}
	if (Array.isArray(p) && p[1] && typeof p[1] === "object") {
	const pid = p[1].providerId;
	if (pid === providerId) return false;
	// Also drop the legacy auth plugin if it's there.
	if (typeof p[0] === "string" && p[0].includes("opencode-omniroute-auth")) {
	return false;
	}
	}
	return true;
	});
	const filtered = plugins.filter((p) => {
	if (typeof p === "string") {
	return !p.includes("opencode-omniroute-auth");
	}
	if (Array.isArray(p)) {
	const pluginPath = p[0];
	if (typeof pluginPath === "string" && pluginPath.includes("opencode-omniroute-auth")) {
	return false;
	}
	if (p[1] && typeof p[1] === "object") {
	const pid = p[1].providerId;
	if (pid === providerId) return false;
	}
	}
	return true;
	});

[gemini-code-assist]

During a release/publish pipeline, we should always rebuild the plugin to ensure that any recent changes to @omniroute/opencode-plugin/src/index.ts are compiled into the published dist/. Skipping the build just because dist/index.js exists is dangerous because developers often have old build artifacts lying around in their local workspace.

  console.log("\n  🔨 Building @omniroute/opencode-plugin (tsup)...");
  try {
    execFileSync(NPX_BIN, ["tsup"], {
      cwd: opencodePluginSrc,
      stdio: "inherit",
      env: { ...process.env, NODE_ENV: "production" },
    });
    console.log("  ✅ @omniroute/opencode-plugin bundled to @omniroute/opencode-plugin/dist/");
  } catch (err: any) {
    console.error("  ❌ Failed to build @omniroute/opencode-plugin:", err.message);
    console.error("     The published package would be missing the plugin dist.");
    console.error(
      "     Run `cd @omniroute/opencode-plugin && npm install && npm run build` to debug."
    );
    process.exit(1);
  }

[diegosouzapw]

Thanks @herjarsa — this closes the #3711 gap properly: the plugin finally ships inside the omniroute tarball and omniroute setup opencode makes the install one command (XDG-aware, idempotent, legacy-entry cleanup — nicely engineered). 🎯

Pushed a review commit (e4fcf5b4, keeping you as author) with four adjustments:

1. src/index.ts rebuilt on the release base — your diff carried ~1,250 lines of formatting churn; the real change (the provider.options.baseURL third link + clear warning) is now a 28-line diff, preserving blame and the fix(combo): stop premature context compaction — real auto-combo windows + per-target compression limit #3680 context handling.
2. --base-url was silently ignored: Commander camelCases it into opts.baseUrl, but the runner only read opts.baseURL. Fixed with a failing-then-passing test.
3. Step 8.8 hardening: the plugin is standalone (not a workspace), so a fresh CI checkout has no node_modules there — and tsup with dts: true needs the plugin's devDependencies. The step now installs them first (reproduced the failure locally before the fix).
4. Rule fix(ci): add environment for npm token access #18 tests (cli-setup-opencode.test.ts): happy path honouring --base-url, idempotent re-run, legacy opencode-omniroute-auth cleanup, missing-dist error path.

Validation: 4/4 new CLI tests, 257/257 plugin tests, tsup build green. Ships in v3.8.23. 🚀