fix: inline definePlugin to remove runtime dependency on repterm-api

When repterm is installed via symlink/link outside its monorepo,
bun resolves imports from the symlink target path rather than the
node_modules location. This causes 'Cannot find package repterm-api'
errors because repterm-api isn't in the symlink target's resolution
path.

Fix by inlining the trivial definePlugin function and changing all
repterm-api imports to type-only (erased at compile time). The
repterm-api package remains in dependencies for TypeScript type
resolution but is no longer needed at runtime.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: cnbailian

packages/repterm/src/plugin/index.ts

@@ -7,16 +7,33 @@
 
 import type { TestContext } from '../runner/models.js';
 import type { DollarFunction } from '../terminal/dollar.js';
-import {
-  definePlugin as definePluginFromApi,
-  type BasePluginContext as BasePluginContextGeneric,
-  type PluginHooks,
-  type PluginDefinition,
-  type AnyPlugin,
+import type {
+  BasePluginContext as BasePluginContextGeneric,
+  PluginHooks,
+  PluginDefinition,
+  AnyPlugin,
 } from 'repterm-api';
 
-// Re-export plugin-api for consumers (repterm re-exports these from index)
-export { definePluginFromApi as definePlugin };
+// Inline definePlugin to avoid runtime dependency on repterm-api.
+// This prevents "Cannot find package 'repterm-api'" errors when repterm
+// is installed via symlink/link outside its monorepo.
+function definePlugin<
+  TName extends string,
+  TContextIn extends object,
+  TContextOut extends object,
+  TMethods extends object,
+>(
+  name: TName,
+  setup: (ctx: TContextIn) => {
+    methods: TMethods;
+    context?: TContextOut;
+    hooks?: PluginHooks<any>;
+  },
+): PluginDefinition<TName, TContextIn, TContextOut, TMethods> {
+  return { name, setup };
+}
+
+export { definePlugin };
 export type { PluginDefinition, AnyPlugin, PluginHooks };
 export type BasePluginContext = BasePluginContextGeneric<TestContext>;