pullfrog 0.1.14 → 0.1.16

package/dist/utils/packageManager.d.ts

@@ -0,0 +1,49 @@
+export type SupportedPackageManager = "npm" | "pnpm" | "yarn" | "bun";
+export interface PackageManagerSpec {
+    name: SupportedPackageManager;
+    /**
+     * either a concrete semver (e.g. "11.1.1") or a range (e.g. "^11.0.0").
+     * `concrete` distinguishes — corepack only accepts concrete versions.
+     */
+    version: string;
+    concrete: boolean;
+    /** which package.json field this came from */
+    source: "devEngines" | "packageManager";
+}
+/**
+ * resolve the project's intended package manager from package.json. precedence
+ * matches pnpm 11+: `devEngines.packageManager` wins over `packageManager`.
+ * when both are present, a concrete `packageManager` that satisfies a
+ * `devEngines` range is preferred (we can pin it via corepack); otherwise
+ * we warn on disagreement and stick with `devEngines`.
+ */
+export declare function resolvePackageManagerSpec(cwd: string): Promise<PackageManagerSpec | null>;
+/** the per-run directory the corepack shim is installed into. deliberately
+ * NOT the node bin dir: that's npm's `-g` target, and a corepack shim sitting
+ * there makes a customer setup script's `npm i -g pnpm` abort with EEXIST
+ * (npm refuses to clobber a binary it doesn't own). lives under the run
+ * tmpdir so it's cleaned up with everything else. */
+export declare function packageManagerBinDir(tmpdir: string): string;
+export interface EnsurePackageManagerParams {
+    spec: PackageManagerSpec;
+    /** directory to install the corepack shim into (see `packageManagerBinDir`).
+     * prepended to PATH so the pinned binary resolves by name. */
+    binDir: string;
+}
+/**
+ * ensure the requested package manager is on PATH at the declared version,
+ * provisioning via corepack when applicable. returns true if PATH now
+ * resolves to that version, false if we couldn't pin it (in which case
+ * the caller should treat PATH as untrusted and may fall back to its
+ * legacy install path).
+ *
+ * the corepack shim is installed into `params.binDir` (prepended to PATH),
+ * not the node bin dir, so a later `npm i -g pnpm` in a setup hook can't
+ * collide with it. our dir wins the PATH lookup, so the pinned version is
+ * also what resolves even if that `npm i -g` succeeds into the node bin dir.
+ *
+ * never throws: network failure, missing corepack, range-only versions —
+ * all degrade to "log warning, return false". the existing PATH binary
+ * still works; we just don't get our version guarantee.
+ */
+export declare function ensurePackageManager(params: EnsurePackageManagerParams): Promise<boolean>;

package/dist/utils/run.d.ts

@@ -1,9 +1,9 @@
 import type { AgentResult } from "../agents/shared.ts";
 import type { MainResult } from "../main.ts";
-import type { ToolState } from "../toolState.ts";
+import type { ToolContext } from "../mcp/server.ts";
 export interface HandleAgentResultParams {
     result: AgentResult;
-    toolState: ToolState;
+    toolContext: ToolContext;
     silent: boolean | undefined;
 }
 export declare function handleAgentResult(ctx: HandleAgentResultParams): Promise<MainResult>;

package/dist/utils/runErrorRenderer.d.ts

@@ -33,8 +33,10 @@
  *      `toolState.agentDiagnostic`; `formatAgentHangBody` renders that as
  *      a markdown block.
  *
- *   6. Default — a generic `❌ Pullfrog failed` block with the raw error
- *      message in a fenced code block. Same body for both surfaces.
+ *   6. Default — a plain-English lead sentence explaining the run failed,
+ *      followed by the raw error message in a fenced code block (so the user
+ *      never sees a bare internal string). The job summary adds the
+ *      `### ❌ Pullfrog failed` banner on top of the same body.
  *
  * The hang body and the API-key body diverge between the two surfaces only
  * in that the job summary wraps them in the `### ❌ Pullfrog failed` H3

package/dist/utils/runLifecycle.d.ts

@@ -46,11 +46,12 @@ export declare function persistRunArtifacts(toolContext: ToolContext): Promise<v
  *      prepended below in step 4) — same classifier as the catch path so
  *      the user sees it instead of a deleted-comment void / empty summary
  *      tab
- *   3. when the run succeeded and the progress comment was never finalized
- *      via `report_progress`, delete it (three sub-cases — orphan
- *      "Leaping into action" comment, abandoned checklist, agent wrote
- *      a substantive artifact via another MCP write tool but skipped
- *      report_progress)
+ *   3. when the run succeeded, some write landed (`wasUpdated`), but the
+ *      progress comment was never finalized via `report_progress`, delete
+ *      the stranded comment (abandoned checklist, or a substantive artifact
+ *      written via another MCP write tool that skipped report_progress). a
+ *      run where NO write landed keeps its comment for handleAgentResult to
+ *      salvage into — see the `wasUpdated` guard below and #868
  *   4. write the GitHub Actions step summary (best-effort — a write
  *      failure must not throw past this point because we'd hit the outer
  *      catch and clobber any progress comment we just wrote)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pullfrog",
-  "version": "0.1.14",
+  "version": "0.1.16",
   "type": "module",
   "bin": {
     "pullfrog": "dist/cli.mjs",
@@ -26,11 +26,12 @@
   },
   "devDependencies": {
     "@actions/core": "^1.11.1",
-    "@anthropic-ai/claude-code": "2.1.112",
+    "@anthropic-ai/claude-code": "2.1.150",
     "@ark/fs": "0.56.0",
     "@ark/util": "0.56.0",
     "@clack/prompts": "^1.2.0",
     "@modelcontextprotocol/sdk": "^1.26.0",
+    "@opencode-ai/sdk": "1.2.27",
     "@octokit/plugin-throttling": "^11.0.3",
     "@octokit/rest": "^22.0.0",
     "@octokit/webhooks-types": "^7.6.1",
@@ -50,7 +51,7 @@
     "fastmcp": "^3.34.0",
     "file-type": "^21.3.0",
     "husky": "^9.0.0",
-    "opencode-ai": "1.15.1",
+    "opencode-ai": "1.15.13",
     "package-manager-detector": "^1.6.0",
     "picocolors": "^1.1.1",
     "semver": "^7.7.3",
@@ -58,6 +59,7 @@
     "table": "^6.9.0",
     "turndown": "^7.2.0",
     "typescript": "^5.9.3",
+    "undici": "^7.22.0",
     "vitest": "^4.0.17",
     "yaml": "^2.8.2"
   },