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
+12 -2
View File
@@ -3,8 +3,8 @@ title: Camoufox vs Chrome
type: comparison
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: medium
tags: [comparison, browser]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -46,6 +46,16 @@ Compare the two browser-automation options for Hermes's browser tool.
- Runs headed under Xvfb rather than a true headless mode, per [[systems/headless-server]] — fluxbox provides the window manager, x11vnc/noVNC expose it for human viewing.
- `cua-driver` bridges Hermes's computer-use tool calls to the browser.
> **Re-verified 2026-11-20 (stocktake).** Live config unchanged: `cloud_provider: camofox`,
> `camera_provider: camofox`, `engine: auto`, `headed: true`, `inactivity_timeout: 450`,
> `use_gateway: false`, `cdp_url: ""`, `camofox.managed_persistence: true`, `user_id: anthony`.
> `cua-driver` still **v0.28.2**; `cua-driver serve` + `camoufox-ws-server.mjs` + a `camoufox-bin`
> tree all running on CT460 (under Xvfb `:99` 1600×1200 + fluxbox).
> **Correction:** ~~Camofox's REST port 9377 is not listening on CT460 — the service runs on CT450~~ —
> `:9377` **is listening on CT460** (`node`, `/health` → `ok`, engine `camoufox`); the service is the
> local `systemd --user` unit `camofox-browser.service` (active), per [[systems/browser-backend]]'s
> 2026-10-13 correction. The CT450 attribution is dead. The ws-server also listens on `:9222` (CDP).
> No Chrome/Chromium process found in this probe either.
### Chrome (not found in use)
- No `google-chrome`, `chromium`, or CDP-only launch flags found in the sanitized config or running process list during this audit.
- Included in the comparison because the page existed as a placeholder — if Chrome/CDP was evaluated and rejected, that reasoning isn't captured anywhere; worth a [[decisions/index]] entry if anyone remembers why Camoufox was chosen over stock Chrome.
+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]]