wiki: publish pending edits (2026-10-20)

This commit is contained in:
Tony0410
2026-10-20 18:38:11 +08:00
parent 667ab7f41d
commit fbd4f297eb
46 changed files with 1012 additions and 197 deletions
+11 -2
View File
@@ -3,8 +3,8 @@ title: Decisions
type: collection
status: active
created: 2026-07-22
updated: 2026-07-22
verified_on: 2026-07-22
updated: 2026-10-20
verified_on: 2026-10-20
confidence: high
tags: [decisions]
---
@@ -19,6 +19,15 @@ Stable strategic and config decisions, with evidence and status.
- [[decisions/persistent-shell-enabled]]
- [[decisions/rollback-steel-to-camofox]]
> **Status sweep 2026-10-20:** all three listed decisions are still `status: active`, but two now
> carry a review note:
> - [[decisions/keep-openrouter-as-fallback]] — its 30-day revisit trigger is **met**; OpenRouter is
> reachable only through the OmniRoute catalog, not as a standalone provider.
> - [[decisions/persistent-shell-enabled]] — still `true`; its `review_after: 0001-01-01` zero-date
> bug is now corrected to a real date.
> - [[decisions/rollback-steel-to-camofox]] — the *engine* is Camoufox as decided, but
> `cloud_provider: steel` remains in the config while the Steel service itself is unreachable.
## History
- **Verified:** Decision pages initialized during wiki setup on 2026-07-22
- **Inferred:** Config version 33 and multiple named backups imply iterative changes in vision, browser, and model routing
+24 -2
View File
@@ -3,8 +3,9 @@ title: Keep OpenRouter as fallback
type: decision
status: active
created: 2026-07-22
updated: 2026-07-22
review_after: 2026-08-22 # was 0001-01-01 (bug), fixed during 2026-07-22 audit; real trigger is conditional, see Revisit when
updated: 2026-10-20
review_after: 2026-10-20 # was 0001-01-01 (bug), fixed during 2026-07-22 audit; real trigger is conditional, see Revisit when
verified_on: 2026-10-20
confidence: high
tags: [routing, provider, decision]
sources: []
@@ -28,6 +29,27 @@ OpenRouter must remain available as a fallback provider, even if a self-hosted r
## Revisit when
A self-hosted router has operated reliably for at least 30 days.
> **Revisit trigger MET (verified 2026-10-20).** OmniRoute has been the primary router for well over
> 30 days — `custom:omni-101` is the pin on effectively every model-calling cron job, and
> `Omniroute:20128` is a second live OmniRoute endpoint. The estate has **no standalone OpenRouter
> provider**: `custom_providers` in `~/.hermes/config.yaml` holds only `litellm`, `guacano`,
> `Omniroute:20128`, `command-code` and `omni-101` (see [[systems/openrouter]]).
>
> **But the fallback is now provided *through* OmniRoute rather than alongside it** — OpenRouter-style
> slugs (`openrouter/auto`, `freeapi/openrouterfree`, `or-openrouter-fusion`, …) are present in the
> OmniRoute catalog, so OpenRouter capacity remains reachable without a separate Hermes provider.
>
> **Status: decision still `active`, but the mechanism it protects has changed.** The intent
> (OpenRouter capacity must remain reachable as a fallback) is satisfied via the OmniRoute catalog.
> The literal reading — a standalone OpenRouter provider in `custom_providers` — is **not** satisfied
> and has not been since at least 2026-07-22. This needs a re-affirmation or a rewrite of the
> decision text; it should not simply be left to drift on a 30-day timer.
>
> Related context: OmniRoute has also been the source of repeated fleet-wide failures —
> the 2026-10-14 connection-refused storm, the 2026-10-16/17 and 2026-10-19 resource-pressure 503
> bursts, and the 2026-10-18 degenerate-stream delivery. A single-node fallback posture carries
> that concentration risk with it.
## Related
- [[model-routing]]
- [[systems/omniroute]]
+12 -2
View File
@@ -3,8 +3,9 @@ title: Persistent shell enabled
type: decision
status: active
created: 2026-07-22
updated: 2026-07-22
review_after: 0001-01-01
updated: 2026-10-20
review_after: 2026-10-20
verified_on: 2026-10-20
confidence: high
tags: [automation, shell, decision]
sources: []
@@ -24,5 +25,14 @@ Enable persistent shells for Hermes.
## Revisit when
Use case becomes critical again.
> **Re-verified 2026-10-20 — decision still `active` and the setting is still `true`.**
> `terminal.persistent_shell: true` in `~/.hermes/config.yaml`, `backend: local`,
> `timeout: 180`, `home_mode: auto`, `container_cpu: 1`, `lifetime_seconds: 300`.
> The `review_after: 0001-01-01` value was a zero-date bug (same class as
> [[decisions/keep-openrouter-as-fallback]]); it is now a real date.
> One caveat worth carrying into the review: `lifetime_seconds: 300` means a persistent shell
> is torn down after 5 minutes idle, so "state persists across turns" is true within a burst of
> work but not indefinitely. See [[concepts/persistent-shells]].
## Related
- [[persistent-shells]]
+17 -2
View File
@@ -3,8 +3,8 @@ title: Rollback Steel to Camoufox
type: decision
status: active
created: 2026-08-02
updated: 2026-08-02
verified_on: 2026-08-02
updated: 2026-10-20
verified_on: 2026-10-20
confidence: high
tags: [decision, browser, steel, camofox, rollback]
sources: [session-history, live-config]
@@ -28,6 +28,21 @@ Steel Browser was deployed on CT201 on 2026-07-29 as the primary browser automat
## Decision
**Revert to Camoufox as primary.** Steel plugin disabled but left running on CT201.
> **Status check 2026-10-20 — the decision is *partially* undone in configuration.**
> The live `browser:` block in `~/.hermes/config.yaml` reads
> `cloud_provider: steel` with `engine: camofox`. The **engine** is Camoufox (decision honoured),
> but the **cloud_provider** key still says `steel`, and `camera_provider: camofox`.
> This is the same split seen in [[comparisons/camoufox-vs-chrome]].
>
> Meanwhile the Steel service itself is **not reachable**: `http://steel.martinwa.org` returns
> **000** (connection failed) on 2026-10-20. Combined with the degraded CT201 stack recorded in
> [[systems/homepage-dashboard]] (main container removed, asset proxy 502), it looks like the
> "left running on CT201" part of this decision is no longer true.
>
> **Recommendation, not actioned here:** the `cloud_provider: steel` value appears to be residue
> from the reverted deployment. Confirm against the live Steel service and either restore it or
> set `cloud_provider: camofox` so the config matches the decision this page records.
## 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.
2. **Auth persistence:** Camoufox's persistent profile `anthony` is already authenticated into key services (Uber Eats, LinkedIn). Steel required cookie re-exports.