Jason Woltje
a86d304f07
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Implement rejection handling for tasks that fail quality gates after all continuation attempts are exhausted. Schema: - Add TaskRejection model for tracking rejections - Store failures, attempts, escalation state Service: - handleRejection: Main entry point for rejection handling - logRejection: Database logging - determineEscalation: Rule-based escalation determination - executeEscalation: Execute escalation actions - sendNotification: Notification dispatch - markForManualReview: Flag tasks for human review - getRejectionHistory: Query rejection history - generateRejectionReport: Markdown report generation Escalation rules: - max-attempts: Trigger after 3+ attempts - time-exceeded: Trigger after 2+ hours - critical-failure: Trigger on security/critical issues Actions: notify, block, reassign, cancel Tests: 16 passing with 80% statement coverage Fixes #139 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
26 lines
531 B
TypeScript
26 lines
531 B
TypeScript
export interface RejectionContext {
|
|
taskId: string;
|
|
workspaceId: string;
|
|
agentId: string;
|
|
attemptCount: number;
|
|
failures: FailureSummary[];
|
|
originalTask: string;
|
|
startedAt: Date;
|
|
rejectedAt: Date;
|
|
}
|
|
|
|
export interface FailureSummary {
|
|
gateName: string;
|
|
failureType: string;
|
|
message: string;
|
|
attempts: number;
|
|
}
|
|
|
|
export interface RejectionResult {
|
|
handled: boolean;
|
|
escalated: boolean;
|
|
notificationsSent: string[];
|
|
taskState: "blocked" | "reassigned" | "cancelled";
|
|
manualReviewRequired: boolean;
|
|
}
|