Diagnose and recover Review Runs #20

Open
opened 2026-07-14 22:32:25 -04:00 by caleb-brown · 0 comments
Owner

What to build

Temper Operators can understand every Review Run and take safe recovery actions without reading database state, raw prompts, or repository content.

Acceptance criteria

  • Operators can list and filter Review Runs by repository, pull request, state, trigger, and time.
  • Run detail shows Forgejo backlink, revision, actor, frozen configuration, attempts, coverage, usage, timings, publications, and sanitized failures.
  • Connection, acquisition, provider, validation, stale, cancellation, and publication failures are distinct and actionable.
  • Retry, cancel, or reconcile actions appear only when valid for the current state and are themselves idempotent.
  • Operator actions are audited without storing raw source, prompts, secrets, or unsafe model output.
  • Console scenarios cover healthy, queued, partial, stale, retrying, failed, cancelled, and recovered runs.

Blocked by

  • #18 — Keep feedback correct across retries and revisions
## What to build Temper Operators can understand every Review Run and take safe recovery actions without reading database state, raw prompts, or repository content. ## Acceptance criteria - [ ] Operators can list and filter Review Runs by repository, pull request, state, trigger, and time. - [ ] Run detail shows Forgejo backlink, revision, actor, frozen configuration, attempts, coverage, usage, timings, publications, and sanitized failures. - [ ] Connection, acquisition, provider, validation, stale, cancellation, and publication failures are distinct and actionable. - [ ] Retry, cancel, or reconcile actions appear only when valid for the current state and are themselves idempotent. - [ ] Operator actions are audited without storing raw source, prompts, secrets, or unsafe model output. - [ ] Console scenarios cover healthy, queued, partial, stale, retrying, failed, cancelled, and recovered runs. ## Blocked by - [#18](https://git.caleb-brown.dev/caleb-brown/temper/issues/18) — Keep feedback correct across retries and revisions
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
caleb-brown/temper#20
No description provided.