GitLab MCP Server 2.7.3 letöltés

Follow-through release on the mcp.jmrp.io directory audit: every cross-reference the surface emits now resolves, in every text layer — not only the See-also clauses v2.7.2 fixed.
The 13 invisible clauses (#307)
The follow-up audit found 32 unprojected See-also references across 13 entries on the deployed 2.7.2. Root cause was format, not names: the integrations family's clauses ended without a trailing period and discovery's clause carried parenthetical annotations, so the canonical clause pattern never matched — no per-surface rewrite, no tier-aware drop, and no guard extraction. All 13 canonicalized, and the guard gained a format-lint leg (with its rules pinned by a table-driven test): any See also: occurrence outside the canonical shape now fails CI naming the entry. Live after the fix: 2,052 references, 0 orphans.
The whole text surface, swept
Tool-name references live in more places than See-also clauses. A full sweep of runtime error hints, markdown next-step hints, workflow guides, schema descriptions, and aliases corrected ~40 stale references across 27 files — pre-rename names (gitlab_user_gpg_keys_list → gitlab_list_gpg_keys), wrong dispatchers (gitlab_commit → gitlab_repository), the pipeline guide's gitlab_job_log → gitlab_job_trace, a ghost alias, and two hints that named actions that do not exist (a db-migrations list, a topic merge), both reworded honestly. Polymorphic resource-event hints now name both their issue and MR variants. A permanent guard validates every gitlab_* token in the catalog's text fields against the catalog itself.
Honest wording
- project.archive and group.archive said "(read-only)" — describing the archived object, but reading as a safety claim on a mutating action. Now: "making it read-only in GitLab". (Neither action's actual read-only classification was ever wrong.)
- The typed required_params omission semantics are documented: an entry without type means the schema states no single plain type (admin.feature_set's value, the only case in 851 entries) — read it as "any" and consult gitlab://tools/{id}.
Full detail in #307.