docs: stop the README reading as if the banned scraper stack were already gone
An independent review of this unification branch flagged that the tree asserts the bypass/stealth/proxy-rotation paths are 'excluded by design' while services/scrapers/ still contains all 64 files implementing exactly that -- curl_cffi TLS impersonation, cloudscraper, Tor rotation, WAFBypass, ProxyRotator, plus committed .pyc bytecode. Both statements were true in their own frame: CLAUDE.md §1 is the policy, and the code is the state. The README stated the policy in the present tense, which reads as a description of the tree. This adds the state next to the policy and points at PR #1, which exists to delete the directory and has been open since 2026-07-19. docs/06-data-engine.md already documented the arrival honestly; this brings the README in line with it. Deliberately NOT deleting services/scrapers/ here. That is PR #1's job, and folding a policy deletion into a history-unification merge would make both harder to review. Recording the truth is what this merge owes; removing the code is a separate, reviewable change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
bcf285f057
commit
96f19aab05
@@ -16,6 +16,16 @@ confidence; nothing is guessed.
|
||||
Never on Vercel (long jobs). Bypass/stealth/proxy-rotation/fake-account paths are excluded
|
||||
by design (CLAUDE.md §1).
|
||||
|
||||
> ⚠️ **The exclusion above is the POLICY, not the current state of this tree.**
|
||||
> `services/scrapers/` still contains 64 files implementing exactly what CLAUDE.md §1
|
||||
> prohibits — curl_cffi TLS impersonation, cloudscraper, Tor rotation, `WAFBypass`,
|
||||
> `ProxyRotator` — plus committed `__pycache__/*.pyc`. They arrived on the Gitea line on
|
||||
> 2026-07-13 and are documented in [docs/06-data-engine.md](docs/06-data-engine.md).
|
||||
> [PR #1](https://git.siax.io/sax3l/0pt/pulls/1) exists to delete them and has been open
|
||||
> since 2026-07-19. Nothing in the TypeScript tree imports them and they are not copied
|
||||
> into the runner stage, so they do not execute — but they are present, and this README
|
||||
> previously read as if they were not.
|
||||
|
||||
## Routes
|
||||
|
||||
| Area | Routes |
|
||||
|
||||
Reference in New Issue
Block a user