Debug Loop Verdict

Decide whether a debugging session is CONVERGING, CIRCLING or THRASHING, from the session's own history.

THE PATTERN, IN THE COMMUNITY'S OWN WORDS. "Vibe coding is amazing... until you get stuck in a debugging loop. AI wrote the code in minutes. I spent hours debugging." And from a beginners' forum: "it's easy for two beginners to just prompt-and-pray themselves into a hallucination loop they can't [escape]." Prompt-and-pray is their phrase, not ours.

WHY THIS IS NARROW ON PURPOSE. "Am I making progress" is largely subjective and this package does not pretend otherwise. What IS objective is RECURRENCE: the same error signature reappearing after a change that claimed to fix it is a non-fix, regardless of anyone's judgement. That is the spine of the product, and the scope was cut to it deliberately — an earlier, broader version was rejected during validation for having no truth table.

WHAT IT DECIDES. Given error signatures seen per attempt, files changed, and whether the failing set is shrinking, it returns a status with the evidence for it. It never scores "code quality", never rates the developer, and never guesses at intent.

IT REFUSES RATHER THAN GUESSING. Insufficient history returns an explicit refusal carrying the counts, never a confident default.

VERIFIED: 30 tests, plus evidence/verify-truth-table.mjs which checks all 12 rows of the decision table against the real implementation — 12/12 match.

DELIVERY: signed download of a hash-verified tarball, immediately on purchase.

Interface

What you call, and what comes back. Types and signatures only — the implementation ships with the source.

  export function evaluateDebugSession(history: Attempt[]): SessionVerdict;

  export type Channel = "errorSignatures" | "failingTests";
  export type Severity = "critical" | "warning" | "note";
  export type SessionStatus = "CIRCLING" | "CONVERGING" | "THRASHING" | "UNDECIDABLE";