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
+9 -2
View File
@@ -3,8 +3,8 @@ title: Steel Browser vs Camoufox
type: comparison
status: active
created: 2026-07-29
updated: 2026-10-29
verified_on: 2026-10-29
updated: 2026-11-20
verified_on: 2026-11-20
confidence: high
tags: [comparison, browser, steel, camofox, decision]
sources: [live-probe, session-history]
@@ -77,6 +77,13 @@ the CT201 and CT333 deployments torn down — so returning to Steel means redepl
- **Reversibility:** the compose file and Dockerfile are archived on CT201 under `/root/_archived-steel/`, plus
`/root/_archived-steel/steel-cache-archive-20261029.tgz`; the images remain re-pullable from ghcr.io.
> **Re-verified 2026-11-20 (stocktake).** Steel-removal claims re-probed live: CT201 has **no** steel
> container or image, nothing on :3000/:5173/:9223, Serve routes are only `/` → 8085 and `/mgr` → 8084
> on :443 **and** :8443; `/root/_archived-steel/` holds `docker-compose.yml`, `Dockerfile.api`,
> `steel-cache-archive-20261029.tgz`. CT333 likewise has no steel container/image and nothing on :3000.
> `~/.hermes/plugins/browser-steel/` absent. Camofox healthy on CT460: `:9377/health` → `ok`
> (idle — `browserConnected:false` at probe time, no active session), unit active, config
> `cloud_provider: camofox`. All removal claims **hold**.
## Related
- [[systems/browser-backend]]
- [[concepts/browser-automation]]