High-performance browser automation bridge and multi-instance orchestrator with advanced stealth injection and real-time dashboard.
docs: drop the three references the solver deletion left behind, including a package doc justifying itself by a duplication that no longer exists (PIN-147)
Luigi Agosti580ac85b3aa2
diff --git a/docs/architecture/autosolver.md b/docs/architecture/autosolver.mdindex 10143a70..c2afb634 100644--- a/docs/architecture/autosolver.md+++ b/docs/architecture/autosolver.md@@ -73,10 +73,9 @@ internal/autosolver/│ ├── llm.go # LLM provider skeleton with structured prompts│ └── trim.go # HTML trimming for token efficiency└── solvers/- ├── cloudflare.go # Cloudflare Turnstile (new interface, no chromedp)+ ├── cloudflare.go # Cloudflare Turnstile solver├── jschallenge.go # Generic JavaScript challenge/interstitial solver- ├── jschallenge_test.go- └── legacy.go # Compatibility shim for existing solver.Solver+ └── jschallenge_test.go```## Core Interfacesdiff --git a/internal/autosolver/solvers/cloudflare.go b/internal/autosolver/solvers/cloudflare.goindex 6ceacc55..571ea34a 100644--- a/internal/autosolver/solvers/cloudflare.go+++ b/internal/autosolver/solvers/cloudflare.go@@ -15,9 +15,7 @@ import ()// Cloudflare implements autosolver.Solver for Cloudflare Turnstile-// and interstitial challenges. Unlike bridge/cloudflare.go, this-// implementation uses the Page/ActionExecutor abstraction and has-// zero dependency on chromedp.+// and interstitial challenges.type Cloudflare struct{}func (s *Cloudflare) Name() string { return autosolver.CloudflareSolverName }diff --git a/internal/cfchallenge/cfchallenge.go b/internal/cfchallenge/cfchallenge.goindex f53cded3..5320e4c6 100644--- a/internal/cfchallenge/cfchallenge.go+++ b/internal/cfchallenge/cfchallenge.go@@ -1,11 +1,8 @@-// Package cfchallenge holds the substrate-free Cloudflare challenge data-// (title indicators, challenge-type tokens, turnstile selector JS, spinner-// text) shared verbatim by the two Cloudflare solver flows —-// internal/bridge/cloudflare.go and internal/autosolver/solvers/cloudflare.go —-// so the duplicated copies can't drift. It depends on nothing but the stdlib so-// both packages can import it without an import cycle. Control flow (jitter,-// attempt counts, retry, detect/solve) stays in each flow; only the verbatim-// data lives here.+// Package cfchallenge holds the substrate-free Cloudflare challenge data: the+// title indicators, challenge-type tokens, turnstile selector JS and spinner+// text a solver matches against. It depends on nothing but the stdlib, so any+// flow can import it without an import cycle. Control flow (jitter, attempt+// counts, retry, detect/solve) stays with the solver; only the data lives here.package cfchallengeimport "strings"