feat: adapt pullfrog for gitea + ollama

toolState.ts

@@ -1,6 +1,3 @@
-import type { AgentUsage } from "./agents/shared.ts";
-import type { PrepResult } from "./prep/types.ts";
-import type { AgentDiagnostic } from "./utils/agentHangReport.ts";
 import { log } from "./utils/cli.ts";
 import type { DiffCoverageState } from "./utils/diffCoverage.ts";
 import {
@@ -24,87 +21,19 @@ export type StoredPushDest = {
   localBranch: string;
 };
 
-/**
- * Valid inline-comment anchor lines per side at a particular checkout SHA.
- * Lives here (not in `mcp/review.ts`) so `ToolState` — which caches
- * `Map<path, CommentableLines>` per checkout — does not pull the MCP server
- * graph into every consumer of run state (the action's main loop, agent
- * harnesses, cf-worker indexing).
- */
 export type CommentableLines = { RIGHT: Set<number>; LEFT: Set<number> };
 
-/**
- * mutable per-run record of facts that occurred during execution. shared
- * between the action process and the MCP server (one process — toolState is
- * just a JS object passed by reference into both surfaces).
- *
- * design rule: ToolState is LITERAL. each field records a thing that
- * happened — `review` is set when `create_pull_request_review` succeeded,
- * `finalSummaryWritten` flips when `report_progress` wrote a non-plan body,
- * `selectedMode` is set when `select_mode` was called. fields should never
- * encode the absence of an event ("unsubmittedReview", "missingArtifact"),
- * speculative state, or values derived from other fields.
- *
- * any predicate the rest of the code needs ("the agent picked review mode but
- * never produced a review or progress write") is computed inline at the call
- * site, not stored. derived state in this struct invariably drifts from the
- * literal fields under refactors and is the wrong layer for the check.
- *
- * write narrowly: prefer adding state inside the tool that mutates it (e.g.
- * `create_pull_request_review` populates `toolState.review`) and reading
- * narrowly elsewhere. don't introduce flags from main.ts that mirror what an
- * MCP tool already records.
- */
 export interface ToolState {
-  // where we're allowed to push - base repo initially, fork URL for fork PRs
-  // set by setupGit, updated by checkout_pr. always set before push validation.
   pushUrl?: string;
-  // push destination set by checkout_pr - used as primary source in push_branch
-  // because git config reads can fail in certain environments
   pushDest?: StoredPushDest;
-  // HEAD identity captured by setupGit at run start. load-bearing for the
-  // checkout_pr initial-branch invariant: the only sanctioned HEAD positions
-  // when calling checkout_pr are the run-entry HEAD or the target `pr-N`.
-  // blocks the zed-style cross-PR clobber where a subagent left HEAD on
-  // someone else's `pr-X` and the orchestrator's next checkout_pr inherited
-  // that position.
-  //
-  // discriminated by `kind` because `git rev-parse --abbrev-ref HEAD` returns
-  // the literal sentinel string `"HEAD"` on detached entry, which is the
-  // default state from `actions/checkout` on `pull_request` events (it
-  // checks out the merge commit as a detached SHA). without the kind tag,
-  // detached-entry runs would trivially accept any future detached state.
   initialHead?: { kind: "branch"; name: string } | { kind: "detached"; sha: string };
-  // issue or PR number (same number space in GitHub)
   issueNumber?: number;
-  // PR HEAD sha at checkout time — used to detect new commits pushed during a review
   checkoutSha?: string;
-  // commentable lines per file at checkoutSha — captured during checkout_pr so
-  // review-time inline-comment validation matches the diff GitHub will anchor
-  // to (commit_id=checkoutSha). without this, a PR update between checkout and
-  // review would make listFiles (latest HEAD) disagree with the anchor,
-  // silently dropping valid comments or letting invalid ones through.
-  //
-  // commentableLinesPullNumber records WHICH PR this snapshot belongs to. if
-  // the agent checks out PR B and then reviews PR A in the same session, the
-  // cached snapshot for B would silently mis-validate A's comments — keying
-  // by PR number forces a re-fetch when the target changes.
-  //
-  // commentableLinesCheckoutSha pins the snapshot to the SHA it was built
-  // against. if a second checkout_pr for the SAME PR bumps checkoutSha but
-  // fails before repopulating the cache (e.g., listFiles rate-limits), the
-  // stale snapshot would silently mis-validate comments against the new SHA.
-  // comparing both fields forces a re-fetch when either moves.
   commentableLinesByFile?: Map<string, CommentableLines>;
   commentableLinesPullNumber?: number;
   commentableLinesCheckoutSha?: string | undefined;
-  // SHA to diff incrementally against — set from event payload on first checkout,
-  // then from checkoutSha when review.ts detects new commits mid-review
   beforeSha?: string;
   selectedMode?: string;
-  // number of prepush hook failures this run. push_branch runs the hook
-  // while this is 0 and skips it once non-zero; never decremented within
-  // a run.
   prepushFailureCount: number;
   backgroundProcesses: Map<string, BackgroundProcess>;
   browserDaemon?: BrowserDaemon | undefined;
@@ -113,80 +42,26 @@ export interface ToolState {
     nodeId: string;
     reviewedSha: string | undefined;
   };
-  // dedupe key: parent review comment_id → most-recent reply written this
-  // session by reply_to_review_comment. used by duplicateReplyDecision to
-  // skip identical-body re-emissions of the same call (PR #610 root cause).
-  // body-keyed (not just id-keyed) so legitimate follow-up replies with
-  // different content still go through.
   reviewReplies?: Map<
     number,
     { commentId: number; url: string | undefined; bodyWithFooter: string }
   >;
   dependencyInstallation?: {
     status: "not_started" | "in_progress" | "completed" | "failed";
-    promise: Promise<PrepResult[]> | undefined;
-    results: PrepResult[] | undefined;
+    promise: Promise<unknown[]> | undefined;
+    results: unknown[] | undefined;
   };
-  // undefined = no comment yet, object = active comment, null = deliberately deleted
   progressComment: ProgressComment | null | undefined;
-  // immutable snapshot: true if a progress comment was pre-created at init time.
-  // survives deleteProgressComment so handleAgentResult can still detect "expected but never reported".
   hadProgressComment: boolean;
   lastProgressBody?: string;
   wasUpdated?: boolean;
-  // set after a non-plan report_progress successfully writes the final summary.
-  // decoupled from todoTracker.enabled so cleanup detection survives API failures.
   finalSummaryWritten?: boolean;
-  // set by select_mode when Plan + issue_number and plan-comment API returns existing plan (for report_progress target_plan_comment)
   existingPlanCommentId?: number;
   previousPlanBody?: string;
-  // absolute path to the PR summary markdown file the agent edits in place.
-  // seeded by main.ts before the agent starts when payload.generateSummary is set;
-  // read back at end-of-run to persist to DB.
-  summaryFilePath?: string;
-  // exact bytes of the seeded snapshot file at run start. compared against
-  // the file content at end-of-run to detect "agent never touched it" — in
-  // that case persistSummary skips the DB write (saving the seed verbatim
-  // would either re-write what the DB already has, on incremental runs, or
-  // serialize the placeholder scaffold, on first runs).
-  summarySeed?: string;
-  // set to true after persistSummary completes once. prevents the error-path
-  // call (which exists so a successful agent edit before a crash still gets
-  // persisted) from redundantly re-running the DB PATCH on the
-  // success-then-late-throw path.
-  summaryPersistAttempted?: boolean;
-  // absolute path to the rolling repo-level learnings markdown file the
-  // agent reads at startup and may edit at end-of-run. seeded by main.ts
-  // for every run from `Repo.learnings` (empty file when no learnings
-  // exist yet); read back at end-of-run to persist any edits.
-  learningsFilePath?: string;
-  // exact bytes of the seeded learnings file at run start. compared
-  // against the file content at end-of-run to detect "agent never touched
-  // it" — in that case persistLearnings skips the DB PATCH (saving the
-  // identical content would be a no-op write that wastes a LearningsRevision
-  // row and the API round-trip).
-  learningsSeed?: string;
-  // mirror of `summaryPersistAttempted` for the learnings tmpfile — guards
-  // the error-path / exit-signal callers from a redundant second PATCH
-  // after the success path already persisted.
-  learningsPersistAttempted?: boolean;
   output?: string | undefined;
-  usageEntries: AgentUsage[];
   model?: string | undefined;
-  // set by main.ts when the BYOK fallback engaged (configured model needed
-  // a provider key the runner didn't have). carried into PR-comment footers
-  // so users can see "Using <free model> (credentials for <configured> not
-  // configured)" rather than just being silently downgraded. literal record
-  // of an event that happened — matches the ToolState design rule.
-  modelFallback?: { from: string } | undefined;
   todoTracker?: TodoTracker | undefined;
   diffCoverage?: DiffCoverageState | undefined;
-  // mutable handle the agent harness writes to as a run progresses (recent
-  // stderr ring buffer reference, last provider-error label, event count).
-  // read by main.ts's outer catch so a watchdog-fired activity timeout still
-  // surfaces the same agent-side context the harness's own catch path returns
-  // via `result.error`. see `utils/agentHangReport.ts`.
-  agentDiagnostic?: AgentDiagnostic | undefined;
 }
 
 interface InitToolStateParams {
@@ -205,6 +80,5 @@ export function initToolState(params: InitToolStateParams): ToolState {
     hadProgressComment: !!resolved,
     prepushFailureCount: 0,
     backgroundProcesses: new Map(),
-    usageEntries: [],
   };
 }