pullfrog 0.1.13 → 0.1.15

package/dist/agents/opencodePlugin.d.ts

@@ -1,60 +0,0 @@
-/**
- * Source for the opencode plugin we drop into the per-run tmpdir at
- * `<XDG_CONFIG_HOME>/opencode/plugin/pullfrog-events.ts`. The harness already
- * redirects `XDG_CONFIG_HOME` to `ctx.tmpdir/.config` (see `opencode.ts`
- * `homeEnv`), so opencode's auto-discovery scans the tmpdir, never the user's
- * working tree. opencode's `Global.Path.config` resolves to
- * `path.join(xdgConfig, "opencode")` and the config layer auto-discovers
- * plugins from every directory in its scan list — including
- * `Global.Path.config` — by globbing `{plugin,plugins}/*.{ts,js}` via
- * `ConfigPlugin.load(dir)`.
- *
- * We MUST NOT write into the user's repo working tree. The repo is a checkout
- * the agent operates on; only the agent's own tools (gated by
- * `OPENCODE_PERMISSION`) may modify it. The whole reason we redirect HOME and
- * XDG_CONFIG_HOME is so harness-side files (config, plugins, scratch state)
- * land in the tmpdir.
- *
- * Why this plugin exists: opencode's `task` tool runs subagents in-process and
- * the CLI's `cli/cmd/run.ts` event loop filters `part.sessionID !== sessionID`,
- * so subagent-internal `message.part.updated` events are silently discarded
- * before reaching our parent NDJSON stream. plugins, by contrast, receive
- * EVERY bus event via `bus.subscribeAll()` regardless of session.
- *
- * The plugin re-emits every relevant bus event onto opencode's stdout as a
- * single JSON line wrapped in a sentinel envelope. our `runOpenCode` parser
- * recognises the envelope, unpacks it, and routes the inner part through the
- * existing handlers with a per-session label from `SessionLabeler` so each
- * subagent's tool calls / text appear inline alongside the orchestrator's.
- *
- * Dumb plugin / smart parent split: the plugin emits every part for every
- * session. the parent dedupes against the orchestrator's own session id (which
- * it already knows from the `init` event). this keeps the plugin trivial and
- * keeps the per-session attribution logic on the parent side where the
- * SessionLabeler already lives.
- *
- * Event-name prefixing: the wrapped event-type sentinel is
- * `pullfrog_bus_event` — picked to be unmistakably ours so a future opencode
- * release that introduces a coincidentally-named event type won't collide.
- */
-export declare const PULLFROG_BUS_EVENT_TYPE: "pullfrog_bus_event";
-export declare const PULLFROG_OPENCODE_PLUGIN_FILENAME: "pullfrog-events.ts";
-/**
- * Source written verbatim to `<XDG_CONFIG_HOME>/opencode/plugin/pullfrog-events.ts`.
- *
- * - Structural typing only (no runtime import of `@opencode-ai/plugin`):
- *   opencode installs that dep into the directory containing the plugin
- *   alongside discovery, but a) the dep isn't required for the structural
- *   shape we use, and b) keeping zero imports avoids any module-resolution
- *   coupling to opencode's plugin-loader internals across versions.
- * - default export is the plugin factory (opencode's plugin loader accepts
- *   default exports as the server entrypoint).
- * - we only forward `message.part.updated`. that's where the user-visible
- *   subagent activity (tool calls, text, step transitions) lives. add more
- *   event types here if the parent needs them.
- * - JSON.stringify+single write keeps the line atomic up to PIPE_BUF (4KB on
- *   Linux). longer parts may interleave with concurrent stdout writers; the
- *   parser tolerates non-JSON lines (logs them at debug) so a torn line is a
- *   missed event, not a crash.
- */
-export declare const PULLFROG_OPENCODE_PLUGIN_SOURCE: string;