pullfrog 0.1.0 → 0.1.2

package/dist/internal.js

@@ -463,9 +463,6 @@ Rules:
 - Do NOT include a changelog section \u2014 the key changes list serves this purpose
 - Focus on *intent*, not *what* \u2014 the diff already shows what changed
 - Get the file count and commit count from the checkout_pr metadata, not by counting manually`;
-function learningsStep(t, n) {
-  return `${n}. **learnings** (only if high confidence): if you discovered something about repo setup, test commands, conventions, or patterns that you are confident is correct and would reliably help future runs, call \`${t("update_learnings")}\` to persist it. skip this step if you are unsure or the finding is speculative/one-off. format as a flat bullet list (\`- \` per line, one fact per bullet). merge with existing learnings from the prompt \u2014 pass the FULL merged list. deduplicate, and drop bullets that are clearly wrong or no longer relevant to the current codebase.`;
-}
 function computeModes(agentId) {
   const t = (toolName) => formatMcpToolRef(agentId, toolName);
   return [
@@ -521,8 +518,6 @@ function computeModes(agentId) {
    - create a PR via \`${t("create_pull_request")}\`
    - call \`${t("report_progress")}\` with the PR link or the exact error if push/PR failed
 
-${learningsStep(t, 6)}
-
 ### Notes
 
 For simple, well-defined tasks, skip the plan phase and go straight to build.`
@@ -550,9 +545,7 @@ For simple, well-defined tasks, skip the plan phase and go straight to build.`
    - confirm a clean working tree, then push via \`${t("push_branch")}\` (same push/prepush guidance as Build mode in *SYSTEM*)
    - reply to each comment using \`${t("reply_to_review_comment")}\`
    - resolve addressed threads via \`${t("resolve_review_thread")}\`
-   - call \`${t("report_progress")}\` with a brief summary (or the exact push error if push failed)
-
-${learningsStep(t, 6)}`
+   - call \`${t("report_progress")}\` with a brief summary (or the exact push error if push failed)`
     },
     // Review and IncrementalReview use the multi-lens orchestrator pattern
     // (canonical source: .claude/commands/anneal.md). The orchestrator does
@@ -723,9 +716,7 @@ ${PR_SUMMARY_FORMAT}`
 
 2. Produce a structured, actionable plan with clear milestones.
 
-3. Call \`${t("report_progress")}\` with the plan.
-
-${learningsStep(t, 4)}`
+3. Call \`${t("report_progress")}\` with the plan.`
     },
     {
       name: "Fix",
@@ -747,9 +738,7 @@ ${learningsStep(t, 4)}`
 
 5. Finalize:
    - confirm a clean working tree, then push via \`${t("push_branch")}\` (same push/prepush guidance as Build mode in *SYSTEM*)
-   - call \`${t("report_progress")}\` with the diagnosis and fix summary (or the exact push error if push failed)
-
-${learningsStep(t, 6)}`
+   - call \`${t("report_progress")}\` with the diagnosis and fix summary (or the exact push error if push failed)`
     },
     {
       name: "ResolveConflicts",
@@ -793,9 +782,7 @@ ${learningsStep(t, 6)}`
 3. Finalize:
    - if code changes were made, push to a pull request (new or existing) using \`${t("push_branch")}\` and \`${t("create_pull_request")}\` as needed. \`git status\` must be clean before you finish (see *SYSTEM* Git rules if push fails).
    - call \`${t("report_progress")}\` once with results \u2014 include exact tool errors if push or PR creation failed
-   - if the task involved labeling, commenting, or other GitHub operations, perform those directly
-
-${learningsStep(t, 4)}`
+   - if the task involved labeling, commenting, or other GitHub operations, perform those directly`
     }
   ];
 }

package/dist/mcp/server.d.ts

@@ -60,6 +60,9 @@ export interface ToolState {
     summaryFilePath?: string;
     summarySeed?: string;
     summaryPersistAttempted?: boolean;
+    learningsFilePath?: string;
+    learningsSeed?: string;
+    learningsPersistAttempted?: boolean;
     output?: string;
     usageEntries: AgentUsage[];
     model?: string | undefined;

package/dist/utils/apiUrl.d.ts

@@ -7,3 +7,11 @@
  * enforces https:// for non-local URLs to prevent cleartext credential transmission.
  */
 export declare function getApiUrl(): string;
+/**
+ * true when the action is configured to talk to a localhost API server (i.e.
+ * `pnpm dev` running on the developer's box). signals we can use dev-only
+ * affordances like the `x-dev-repo` proxy-token bypass — the corresponding
+ * server-side dev gates (`NODE_ENV === "development"`) ensure these paths
+ * never activate against prod regardless of what the action does.
+ */
+export declare function isLocalApiUrl(): boolean;

package/dist/utils/instructions.d.ts

@@ -8,7 +8,10 @@ interface InstructionsContext {
     modes: Mode[];
     agentId: AgentId;
     outputSchema?: Record<string, unknown> | undefined;
-    learnings: string | null;
+    /** absolute path to the seeded learnings tmpfile, or null when the file
+     * couldn't be seeded for some reason. main.ts always seeds, so in
+     * practice this is always set; the null case keeps the type honest. */
+    learningsFilePath: string | null;
 }
 export interface ResolvedInstructions {
     full: string;

package/dist/utils/learnings.d.ts

@@ -0,0 +1,31 @@
+/**
+ * Repo-level learnings — operational facts about a repo (setup steps, test
+ * commands, conventions, gotchas) that accumulate across agent runs and feed
+ * back into future runs as durable context. Modeled on the PR-summary tmpfile
+ * pattern (see action/utils/prSummary.ts):
+ *
+ *   1. server seeds `pullfrog-learnings.md` from `Repo.learnings` (or empty
+ *      when the repo has none yet)
+ *   2. the agent reads the file at startup as part of its context, and may
+ *      edit it in place at end-of-run when prompted by the reflection turn
+ *   3. main.ts reads the file back at end-of-run and PATCHes
+ *      `/api/repo/[owner]/[repo]/learnings` if it changed (byte-trim equality
+ *      against the seed determines change detection)
+ *
+ * Edit-in-place avoids stuffing the entire learnings list into both the
+ * prompt context and an `update_learnings` MCP tool call (which previously
+ * required passing the FULL merged list as a string parameter — an
+ * output-token tax that grew linearly with the learnings size).
+ */
+export declare const LEARNINGS_FILE_NAME = "pullfrog-learnings.md";
+export declare function learningsFilePath(tmpdir: string): string;
+/** seed the learnings file with the repo's current learnings, or an empty
+ * file when the repo has none yet. returns the absolute path. */
+export declare function seedLearningsFile(params: {
+    tmpdir: string;
+    current: string | null;
+}): Promise<string>;
+/** read the agent-edited learnings file. returns null when the file is
+ * missing or unreadable (treated as "no change"). caps content at the
+ * server's max length to avoid a 400 round-trip. */
+export declare function readLearningsFile(path: string): Promise<string | null>;

package/dist/utils/subprocess.d.ts

@@ -26,6 +26,7 @@ export interface SpawnOptions {
     stdio?: ("pipe" | "ignore" | "inherit")[];
     onStdout?: (chunk: string) => void;
     onStderr?: (chunk: string) => void;
+    killGroup?: boolean;
 }
 export interface SpawnResult {
     stdout: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pullfrog",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "type": "module",
   "bin": {
     "pullfrog": "dist/cli.mjs",

package/dist/mcp/learnings.d.ts

@@ -1,6 +0,0 @@
-import type { ToolContext } from "./server.ts";
-export declare function UpdateLearningsTool(ctx: ToolContext): import("fastmcp").Tool<any, import("@standard-schema/spec").StandardSchemaV1<{
-    learnings: string;
-}, {
-    learnings: string;
-}>>;