Spaces: the inside of the world, and a sun that is actually where it should be

Ten agents wrote this in parallel against CONTRACT.md, which exists because the
five design agents before them collided on fifteen blocking points — four files
specified twice with incompatible contents, three separate backends for one box,
and `Environment` exported twice meaning different things.

What landed: a Stage owning only the renderer and the loop, with the city and an
office as two scenes over it. They cannot share one — San Francisco is ~94 m per
scene unit with 3.6x vertical exaggeration and an office is 1 unit = 1 m — and
the city is paused rather than disposed on the way in, because rebuilding its
336,864-point heightfield costs about a second on the way back out.

Offices are data. `src/offices/lumbridge-hq.ts` is fifteen rooms and seventy-six
seats, and it is the file a self-hoster copies. Walls are a segment list with
1-D openings, so doors and windows are holes punched in a wall rather than
placed objects, and the pass that splits a wall around its openings hands the
walk-mode collider its segments for free.

The sun is real. `solar.ts` is a NOAA/Meeus implementation with no imports at
all — not even three.js — so time of day keeps working on a laptop in a field.
Verified against known values: 75.45 degrees at the June solstice in SF, 28.79
at December, sunset at 03:15Z. The first screenshot after wiring it was a black
rectangle, which turned out to be correct: it was midnight in San Francisco.

Presence binds to a seat id and never to a coordinate. The pack knows where
`eng-04` is; who is sitting in it is private data behind an API. Same shape as
the marker rule, one level in.

Two corrections to ARCHITECTURE.md are in here. Containment does not discharge
ODbL — publishing OSM-derived coordinates is Public Use of a Derivative Database
wherever the rows live, so the rule is about the geocoder (US Census, public
domain) and not the storage. And a person at a desk is not a Marker; markers are
geographic.

One contract gap surfaced only in a screenshot: two agents read `height` on a
viewpoint differently, so the establishing shot aimed at empty air fourteen
metres above the roof. It now means what the same field means for a city.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

server/src/http.ts

@@ -0,0 +1,43 @@
+/**
+ * The one place this service talks to somebody else's server.
+ *
+ * Every outbound call is bounded and every failure is a returned `null` rather
+ * than a thrown exception, because the callers are all route handlers whose
+ * contract is that they answer. An upstream that has gone away must degrade the
+ * body, never the response.
+ */
+
+const DEFAULT_TIMEOUT_MS = 6000;
+
+export interface GetJsonOptions {
+  headers?: Record<string, string>;
+  timeoutMs?: number;
+}
+
+/**
+ * `null` on any failure at all — transport, status, or unparseable body. The
+ * caller decides what a missing answer means; nothing here does.
+ */
+export async function getJson<T>(url: string, opts: GetJsonOptions = {}): Promise<T | null> {
+  try {
+    const res = await fetch(url, {
+      headers: { accept: "application/json", ...opts.headers },
+      signal: AbortSignal.timeout(opts.timeoutMs ?? DEFAULT_TIMEOUT_MS),
+    });
+    if (!res.ok) return null;
+    return (await res.json()) as T;
+  } catch {
+    return null;
+  }
+}
+
+/**
+ * A User-Agent that identifies this software and the operator running it.
+ *
+ * NWS and MET Norway both ask for a contact and are entitled to block a caller
+ * who sends a generic agent. This is also why an empty contact demotes the
+ * source in `config.ts` rather than being papered over here with a fake address.
+ */
+export function userAgent(contact: string): string {
+  return `tera-api (+https://github.com/lumbridge-public/tera; ${contact})`;
+}