The agent satisfied the task by retrieving core information about MapLibre's mission, projects, and open-source model from the site itself, then filling critical gaps (license type, historical relationship to Mapbox, why it exists) using web search results. The site is poorly navigable for this task: it avoids naming licenses, funding models, and comparisons to alternatives, forcing the agent to infer audience and value proposition from project descriptions alone.

• ›The site calls MapLibre 'open source' and 'free' repeatedly but never states a license name on any fetched page (steps [1–3]); the agent discovered BSD-3-Clause only via external search (step [4]).
• ›MapLibre.com redirects to maplibre.org (step [0]), creating a discovery friction that the agent had to manually route around by typing the correct domain from memory.
• ›The homepage and About page contain no positioning relative to alternatives, no audience persona, and no explanation of when to use MapLibre; the site links to migration guides for Mapbox, Leaflet, and OpenLayers but does not explain the differences (step [1]).
• ›The agent had to use external search (step [4]) to learn that MapLibre GL JS is a fork of Mapbox's last OSS release (v1.31.1) following Mapbox's 2020 license change—this context is absent from the site entirely, yet is critical to understanding MapLibre's existence and value.
• ›The site does not disclose funding model, maintainers, or governance structure; the About page only links to external documents (Charter on GitHub, Strategy 2023, Sponsors page) without explaining their relevance (step [2]).