self-healing

Fresh

Source: BIBLE.md (Phase 12 Phase 4, self-healing 4 routes), ROADMAP.md (Phase 4.1)

Detects WHY an account failed and auto-applies the right fix. Not just error recovery, an immune system that keeps accounts alive without human intervention.

7 failure patterns

Pattern	Auto-fix
cookie-expired	Refresh via cookie-refresh plugin
captcha	Vision solve (Ender Eyes)
rate-limited	Wait + retry with exponential backoff
proxy-dead	Rotate from proxy pool
account-blocked	Quarantine + alert
fingerprint-detected	Regenerate fingerprint, reset cookies
timeout	Retry with fresh browser instance

Decision flow

flowchart TD
  F[Failure detected] --> C[Classify pattern]
  C -- cookie-expired --> R1[Refresh cookies]
  C -- captcha --> R2[Vision-solve captcha]
  C -- rate-limited --> R3[Backoff and retry]
  C -- proxy-dead --> R4[Pull fresh proxy]
  C -- account-blocked --> R5[Quarantine plus notify]
  C -- fingerprint-detected --> R6[Regenerate FP]
  C -- timeout --> R7[Fresh browser]
  R1 --> V[Verify fix worked]
  R2 --> V
  R3 --> V
  R4 --> V
  R6 --> V
  R7 --> V
  V -- ok --> D[Resume]
  V -- still failing --> ES[Escalate to error-recovery]

Routes (4)

Method	Route	What
POST	/self-healing/classify	Classify a failure log
POST	/self-healing/fix	Apply the fix for a classified failure
GET	/self-healing/patterns	List patterns and recent fixes
GET	/self-healing/stats	Success rate per pattern

How it fits with other plugins

• Triggered by error-recovery when a failure threshold is hit
• Calls cookie-refresh, proxy-manager, fingerprint-manager, vision-fallback
• Updates account-store health/status
• Logs via notifications for critical patterns

Related

• error-recovery
• canary-system: early detection of when patterns shift