Write down the Glama build values, which lived nowhere but in Glama

[peopleworks]

Glama does not build from this repository's Dockerfile. It builds from a form in its own admin panel, and today those fields were overwritten. The only surviving copy of the correct values was a screenshot somebody happened to have taken.

A configuration a third party stores for you is a configuration you do not have.

Docs/glama-build.md records the base image, build steps, CMD, environment schema and placeholder parameters verbatim, plus the three things that are easy to get wrong — each of which has already cost something:

• libicu-dev is the first build step and not optional. debian:trixie-slim ships no ICU and .NET dies at startup without it. The tempting fix is DOTNET_SYSTEM_GLOBALIZATION_INVARIANT, which makes the build pass and silently changes how Spanish text is compared and cased — in the product whose differentiator is treating Spanish as a first language.
• The pinned SHA should be empty. It was set to 020554d, from yesterday, so a rebuild would have republished the report that announces a tidy bibliography as a source contradiction — fixed this morning in The committee's findings, which arrived after #52 was merged #53. A pin is a promise to keep shipping whatever that commit said.
• stdio, so no port and no health endpoint. mcp-proxy in the CMD is Glama's own shim for their checks.

Also worth knowing, found while looking

The public listing is healthy — A/A/A, eight tools, no failure indicator — so nothing needs rescuing there. But it is six days stale: it still shows 0.3.0 from 2026-08-04, and its own build history already carried a failure from 2026-08-05 10:51, before today's. NuGet and the MCP registry are at 0.4.0.

That also explains the tool count: eight is what 0.3.0 exposed.

A successful rebuild against current main brings the listing up to date and picks up this morning's fixes at the same time.

🤖 Generated with Claude Code