clezcoding 5296ff152d docs(#2533): list gsd-cursor EoS integration (#2581) ...

* docs: add gsd-cursor to the EoS registry

Appends the gsd-cursor EoS entry to docs/registries/eos.json and regenerates
docs/registries/eos-registry.md. Discussion: open-gsd/gsd-core#2578.

* docs(#2533): regenerate eos-registry.md (id-sorted) + add changeset

Addresses review on #2581: the generator sorts entries by id, so gsd-cursor
(< gsd-omp) must appear first in both the table and the detail sections.
Also adds the required .changeset Added fragment (mirrors precedent #2448).

* docs(#2533): regenerate eos-registry.md via gen-registry.cjs (markdown escaping)

The hand-written markdown left ( ) and _ unescaped; scripts/gen-registry.cjs
escapes them (\(...\), model\_profile\_overrides), so gen-registry.cjs --check
(part of lint:ci / the lint-tests job) failed. This is the generator's exact
output; node scripts/gen-registry.cjs --check now passes.

* docs(#2533): regenerate eos-registry.md for corrected compat floor

Regenerated via scripts/gen-registry.cjs after the enginesGsd fix.
node scripts/gen-registry.cjs --check passes (exit 0).

* docs(#2533): correct gsd-cursor enginesGsd floor to >=1.8.0 (real release)

The >=1.39.0 floor referenced a legacy-lineage version number that no
current @opengsd/gsd-core release has ever reached (latest is 1.8.0).
Per trek-e's review, corrected to >=1.8.0 — the current release, which
ships the model_profile_overrides.<runtime> config key gsd-cursor uses.

* docs(#2533): regenerate eos-registry.md (enginesGsd >=1.0.0, install v1.0.1)

* docs(#2533): mirror gsd-cursor enginesGsd >=1.0.0 + repoint install to v1.0.1

Per review: enginesGsd must mirror what the package declares. Corrected
engines.gsd upstream in gsd-cursor to >=1.0.0 and cut v1.0.1; this mirrors
that range and pins install at the new tag.

2026-07-28 18:33:32 -04:00

2.6 KiB

Raw Blame History

View Raw