GLEN umbrella rebrand: rename the family to glen-* (tracking)

[cboettig]

Tracking issue for the GLEN rebrand. Consolidates #284, #285, #286 and rescopes #132. The earlier framing ("rename this repo to GLEN") is superseded by an umbrella model.

The model: GLEN is the umbrella, not a repo

GLEN ("Geospatial LLM-Enabled Navigator" — pending final confirmation) is the product family / brand. No single repo is GLEN; each repo is a glen-* component named by its role.

This inverts today's README.md, which opens # GLEN: Map + AI Data Analyst and thereby asserts this repo = GLEN. Under the umbrella model this repo is one component (glen-web), and the brand + acronym live at the umbrella level (org profile or a glen landing repo), not in this repo's README.

Naming + org map

Today	→	Org	Notes
geo-agent (this repo)	glen-web	schmidtdse	glen-js rejected (inconsistent naming axis); glen-map rejected (too generic)
mcp-data-server	glen-mcp	schmidtdse	live service endpoint — rename last (widest ripple)
data-workflows	glen-stac	schmidtdse	builds the STAC catalog
geo-agent-ops	glen-ops	stays in boettiger-lab	ops over mostly boettiger-lab apps
(new)	glen-ops	schmidtdse	fresh repo for schmidtdse apps (ca-wolves, cacao, …)

Three core components (web / mcp / stac) move to schmidtdse under the glen-* prefix. Ops is deliberately split across both orgs.

What this subsumes / rescopes

• Rename to GLEN? #284 ("Rename to GLEN?") — answered by the umbrella model.
• Spell out "GLEN" in README #286 ("Spell out GLEN in README") — the acronym belongs at the umbrella level, not this repo's README; this repo's README becomes "glen-web, the map + agent front-end of GLEN."
• Docs on ReadTheDocs? #285 ("Docs on ReadTheDocs?") — folds into the "where the umbrella + docs live" open decision below.
• Rebrand to GLEN + move repo to schmidtdse/glen #132 ("Move to schmidtdse/glen") — rescoped to the geo-agent → glen-web slice of this tracking issue (target name glen-web, not glen).

Sequenced rename (safe order, once names are locked)

1. Stand up the umbrella (landing/acronym — see open decision Fix pmtiles source-layer: read vector:layers[0] from STAC asset #2) before any component claims the name.
2. Lowest blast radius first: data-workflows → glen-stac, geo-agent-ops → glen-ops.
3. geo-agent → glen-web + repoint every downstream jsDelivr pin (migrate — do not lean on GitHub's repo redirect), coordinated through glen-ops.
4. Last: mcp-data-server → glen-mcp — it's a live service endpoint referenced from glen-web config/guidance and k8s, so it has the widest ripple.

Open decisions (blocking a clean start)

1. Peripheral repos — geo-agent-template, geo-agent-benchmark, jupyter-geoagent: rename now (glen-template / glen-benchmark / glen-jupyter) and which org? Default: rename for consistency; template → schmidtdse alongside the core three; benchmark + jupyter follow later.
2. Where the umbrella + docs live — a schmidtdse/glen meta/landing repo, or the schmidtdse org-profile README? This is where the acronym, the family map, and the docs question from Docs on ReadTheDocs? #285 land.
3. Acronym text — confirm "Geospatial LLM-Enabled Navigator" is final before it goes anywhere canonical.

Coordination

Cross-repo execution (pin bumps, deploy re-serving) runs through the ops repos per the usual pinned/unpinned validation order. GitHub redirects the old repo paths, but pins/URLs are migrated, not left to redirect.