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:
@@ -3,8 +3,8 @@ title: Rollback Steel to Camoufox
|
||||
type: decision
|
||||
status: active
|
||||
created: 2026-08-02
|
||||
updated: 2026-10-29
|
||||
verified_on: 2026-10-29
|
||||
updated: 2026-11-20
|
||||
verified_on: 2026-11-20
|
||||
confidence: high
|
||||
tags: [decision, browser, steel, camofox, rollback]
|
||||
sources: [session-history, live-config]
|
||||
@@ -50,7 +50,7 @@ Steel Browser was deployed on CT201 on 2026-07-29 as the primary browser automat
|
||||
> restoration was needed or wanted.
|
||||
|
||||
## Rationale
|
||||
1. **Reliability:** Camoufox runs on the same host as Hermes (CT450) — no Docker networking, no CDP URL normalization patches, no container-to-host routing issues.
|
||||
1. **Reliability:** Camoufox runs on the same host as Hermes (~~CT450~~ **CT460** — host attribution corrected 2026-11-20; the service is the local `camofox-browser.service` on the production Hermes host) — no Docker networking, no CDP URL normalization patches, no container-to-host routing issues.
|
||||
2. **Auth persistence:** Camoufox's persistent profile `anthony` is already authenticated into key services (Uber Eats, LinkedIn). Steel required cookie re-exports.
|
||||
3. **Failure mode:** The `opencode-go/deepseek-v4-flash` empty-stream errors were hitting all providers, but Steel added an extra failure surface (CDP connection, plugin layer) on top of the same problem.
|
||||
4. **DeepSeek 0731 compatibility:** The new model's stricter tool name validation (`^[a-zA-Z0-9_-]+$`) affected all providers — not a Steel-specific issue, but another reason to minimise the toolchain.
|
||||
@@ -103,6 +103,14 @@ removed**, so the `plugin_steel` toolset is no longer selectable.
|
||||
The decision itself is unchanged — Camofox is the backend — but the "Steel is still there if you need it"
|
||||
assumption is dead. Detail: [[systems/browser-backend]], [[comparisons/steel-vs-camoufox]].
|
||||
|
||||
> **Re-verified 2026-11-20 (stocktake).** Every removal claim in the 2026-10-29 update re-probed:
|
||||
> config `cloud_provider/camera_provider: camofox`, `engine: auto`; plugin dir absent; CT201 steel
|
||||
> containers/images/network/project dir gone, Serve only `/`→8085 + `/mgr`→8084 on :443/:8443,
|
||||
> nothing on 3000/5173/9223; CT333 steel gone, :3000 closed; `/root/_archived-steel/` archive intact
|
||||
> (compose, Dockerfile.api, cache tgz). Camofox `:9377/health` → `ok` (idle). **Note:** the Rationale's
|
||||
> "Camoufox runs on the same host as Hermes (CT450)" reflects the July-era attribution — the service
|
||||
> runs on **CT460** (the production Hermes host), corrected in [[systems/browser-backend]] 2026-10-13.
|
||||
> The decision and its consequences are unchanged.
|
||||
## Related
|
||||
- [[comparisons/steel-vs-camoufox]]
|
||||
- [[systems/browser-backend]]
|
||||
|
||||
Reference in New Issue
Block a user