2 Commits
Author SHA1 Message Date
Dolon (Agent)andClaude Fable 5.1 1bec7c784c DNS + ingress: the confirmed names, split-horizon alias, providers on https
Rick confirmed forgeway.<site>.falkvinge.net and the local-first alias
forgeway.services.falkvinge.net. README documents the alias as the front
door, the per-site names as explicit handles, and exactly how the Serenity
override keeps the alias LOCAL (host-record + local= on both Serenity
Pi-holes; the local= line closes the dual-stack AAAA bypass).

OpenClaw providers now point at the https alias with a placeholder apiKey:
OpenClaw exempts plain-IP http base URLs from needing a key but not https
hostnames. scripts/technitium.py ships the Technitium API helper used for
the records (zones / records / add / resync / logtail).

REPORT.md addendum carries the verification table from real clients at both
sites and the findings made on the way.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-18 14:56:12 +00:00
Dolon (Agent)andClaude Opus 5 3155d4a230 forgeway 0.1.1 — per-cluster OpenAI-compatible LLM router
Two endpoints over forge's Ollama gpt-oss:120b:
  /local-optimistic/v1  forge, else cloud gpt-5.4-mini
  /local-strict/v1      forge, else a clean 503 the caller handles

Discovery, not configuration: each instance probes an ordered candidate list
(stable DNS name, then the Lounge and future Serenity literals) concurrently but
in priority order, so the happy path is one round trip and silicon's move to
Serenity needs no rewrite.

/healthz runs a real 1-token completion — forge can be up with Ollama stopped.
Liveness/readiness are deliberately NOT forge-gated: otherwise k8s would evict
the pods during an outage and callers would get a connection failure instead of
the promised 503, and Kuma could not tell "forge down" from "router gone".

max_tokens/max_completion_tokens are translated per backend: Ollama accepts only
the former, gpt-5.4-mini rejects it outright.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-18 14:30:14 +00:00