chore(salvage): preserve uncommitted WIP from /opt/vehiq-work/0pt-p060-p068_0pt before machine cleanup (2026-09-27)
CI (SIAX Cloud) / quality (push) Successful in 49s
CI (SIAX Cloud) / security (push) Successful in 7m5s
Security Scan (SIAX Cloud) / security (push) Successful in 7m5s
CI (SIAX Cloud) / integration (push) Successful in 18m53s
CI (SIAX Cloud) / security (pull_request) Successful in 46s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 58s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m38s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m45s

This snapshot was found sitting uncommitted in a stale /opt/vehiq-work
lane clone dated ~2026-09-09..18, base branch: feat/p060-p068-ingestion-plane.
Not reviewed, not verified against current main. Pushed only so the
directory could be deleted without losing the diff.
This commit is contained in:
opt-vehiq-work salvage
2026-09-27 12:58:50 +02:00
parent 9267576b7c
commit 1d63f63dfd
18 changed files with 189 additions and 80 deletions
+1 -1
View File
@@ -152,7 +152,7 @@ GET /health -> { ok, service, db, sources }
| `GET /health` | `GET /health` | implemented, different shape (no `workers`/`queue`) |
| — | `GET /vehicles/{plate}`, `GET /screen` | implemented, previously undocumented |
Remove any endpoint that drives a bypass/stealth fetch path (CLAUDE.md §1) — none of the 12 real endpoints in `main.py` do; the WAF-bypass concern in this repo's history is in `services/scrapers/*` on the Gitea remote, not here (see CLAUDE.md's note on the two diverged remotes — an open question for Simon, not resolved by this pass).
Any endpoint that requests a bypass/stealth fetch path delegates transport to an explicit b0ts + 1p profile — none of the 12 real endpoints in `main.py` does that today. The earlier local implementation in `services/scrapers/*` on the Gitea remote is migration-era code (see CLAUDE.md's note on the two diverged remotes).
## Related: the edge-native TypeScript capability surface