1.0.4 — ship the README fix npm never got

[jeremiahsay]

Documentation-only release. No runtime file changed since 1.0.3 — the diff
across those five commits is README.md, .github/workflows/image.yml and
glama.json.

Why a one-line version bump matters here

PR #9 corrected "exact source cell" → "exact source reference" in the README
on 13 Sep, because #1575 on the site retired that phrase: not every factor
carries a cell-level reference, so the claim was untrue.

But 1.0.3 was published on 10 Sep, three days earlier. npm still serves the
old README — and npm is what the MCP directories scrape.

Measured this morning, the retired claim is live on:

Directory	instances
lobehub.com	7 (across two listings)
glama.ai	4
libraries.io	1

The sentence rendered on LobeHub is byte-identical to the npm packument
README, which is how we know npm is the single upstream rather than each
directory having written its own. Publishing 1.0.4 corrects all of them at once.

Why it isn't cosmetic

A 125-answer search-enabled run on 14 Sep found Gemini grounding on
greencalculus.com 0 times in 70 calls while still answering about
GreenCalculus in all of them — sourced from lobehub.com, mcpservers.org,
github.com, kaggle.com and libraries.io. For at least one model family,
what these directories say is the brand copy. Leaving a retired, untrue
claim there means models repeat it.

release.yml is self-healing and publishes on a version change to main, so
merging this ships npm and refreshes the registry entry. server.json still
reads 1.0.3 in the repo; the workflow rewrites it from package.json.

Known and NOT fixed by this

LobeHub separately states "The server is remote and requires an API key",
which is false — search_factors and explain_absence answer keyless, and the
registry entry sets isRequired: false deliberately. That text is not in the
npm README, so LobeHub is inferring it. Needs a separate approach.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LeaxFttn3GPPVq1yj3Jjuk