stocktake 2026-11-20: re-verify 9-page 2026-10-29 stale cohort live; correct nanobot docker/cron drift, camofox host/port claims, dead-pin residual; freshness 0 stale/136 fresh

This commit is contained in:
Tony0410
2026-11-20 03:11:58 +08:00
parent 8bf0a37022
commit f603c29d17
11 changed files with 137 additions and 44 deletions
+6 -2
View File
@@ -3,8 +3,8 @@ title: Browser Automation
type: concept
status: active
created: 2026-07-22
updated: 2026-10-29
verified_on: 2026-10-29
updated: 2026-11-20
verified_on: 2026-11-20
confidence: high
tags: [concept, browser, camofox, steel]
sources: [live-probe, session-history]
@@ -33,6 +33,10 @@ Steel Browser (Chromium 140 on CT201) was briefly the primary backend. It offere
**Lesson:** A local browser backend (same host, no network hop) has fewer failure modes than a remote Docker container. The `browser-steel` plugin **was deleted on 2026-10-29** and the Steel deployments on CT201 and CT333 were torn down, so there is no Steel fallback left to fall back to — Camofox is the only backend. See [[comparisons/steel-vs-camoufox]] and [[decisions/rollback-steel-to-camofox]].
> **Re-verified 2026-11-20 (stocktake).** Camofox service active on CT460 (`systemctl --user`),
> `:9377/health` → `ok`; Xvfb `:99` at 1600×1200×24 with fluxbox, websockify on 127.0.0.1:6080.
> Config `cloud_provider: camofox` / `camera_provider: camofox` confirmed. No Steel anywhere
> (CT201/CT333 containers, images, routes, plugin all re-probed absent).
## Related
- [[systems/browser-backend]]
- [[comparisons/steel-vs-camoufox]]