fix(ingest): normalize OVERPASS_URL so a bare origin also resolves

overpassUrl() returned the env value verbatim, so a self-hoster setting
OVERPASS_URL=http://overpass (a bare origin, no /api/interpreter) would POST
to the wrong path and get no data — while the openmapx side, which normalizes,
would accept it. Add OC's own normalizeOverpassUrl (append /api/interpreter
when absent, strip a trailing slash) so both a bare origin and a full endpoint
resolve identically, matching openmapx's behavior without OC depending on
@openmapx/core.

Author: Medformatik

services/ingest/src/__tests__/osm-import.test.ts

@@ -236,4 +236,16 @@ describe("overpassUrl", () => {
       "http://overpass/api/interpreter"
     );
   });
+
+  it("normalizes a bare-origin OVERPASS_URL to the interpreter path", () => {
+    expect(overpassUrl({ OVERPASS_URL: "http://overpass" })).toBe(
+      "http://overpass/api/interpreter"
+    );
+  });
+
+  it("normalizes a trailing-slash OVERPASS_URL", () => {
+    expect(overpassUrl({ OVERPASS_URL: "http://overpass/" })).toBe(
+      "http://overpass/api/interpreter"
+    );
+  });
 });

services/ingest/src/pipeline/osm-import.ts

@@ -96,16 +96,30 @@ export interface OsmWaySource {
 // different fetcher, behind the OsmWaySource interface above.
 const DEFAULT_OVERPASS_URL = "https://overpass-api.de/api/interpreter";
 
+/**
+ * Normalizes an Overpass endpoint to the `…/api/interpreter` path so a bare
+ * origin (`http://overpass`) and a full endpoint (`http://overpass/api/interpreter`)
+ * resolve identically. Mirrors the openmapx-side client (which also accepts
+ * either form) so a shared `OVERPASS_URL` behaves the same for both — without OC
+ * taking a dependency on openmapx's `@openmapx/core`.
+ */
+function normalizeOverpassUrl(url: string): string {
+  const trimmed = url.replace(/\/$/, "");
+  return trimmed.endsWith("/api/interpreter") ? trimmed : `${trimmed}/api/interpreter`;
+}
+
 /**
  * Resolves the Overpass endpoint from `OVERPASS_URL`, falling back to the
  * public instance when unset or empty (Compose's `${VAR:-}` unset-injection).
  * A self-hoster running their own Overpass (e.g. a planet instance already on
  * the stack) can point large per-region pulls at it to avoid the public
- * server's fair-use budget and client-timeout risk on heavy bboxes.
+ * server's fair-use budget and client-timeout risk on heavy bboxes. The value
+ * may be a bare origin or a full `…/api/interpreter` endpoint — both normalize
+ * to the same interpreter URL.
  */
 export function overpassUrl(env: NodeJS.ProcessEnv = process.env): string {
   const raw = env["OVERPASS_URL"];
-  return raw != null && raw !== "" ? raw : DEFAULT_OVERPASS_URL;
+  return raw != null && raw !== "" ? normalizeOverpassUrl(raw) : DEFAULT_OVERPASS_URL;
 }
 
 const HIGHWAY_FILTER =