Tri-comparison: baseline the new csd language (gated on a crucible corpus) #3252

csd was added as a registered language in PR #3251 (#3211-followup), but it has no tree-sitter grammar, so it is invisible to the tri-comparison chart until hand-added to _GG_ONLY_LANGS — the same gap #3191 fixed for the other mainframe languages. all_languages() is NODE_MAPS ∪ _GG_ONLY_LANGS (tests/tools/tri_comparison_chart.py), and csd is in neither.

Blocked on

• language-crucible must ship a data/csd/ corpus first (Add a csd (CICS CSD/RDO) corpus dir (data/csd) language-crucible#30), then cut a release and this repo bumps LANGUAGE_CRUCIBLE_REF. Adding csd to _GG_ONLY_LANGS before the pinned corpus contains it would make the tri-comparison CI job fail closed (test_tri_comparison_ci_fails_closed_when_a_baselined_language_has_no_data).

What to do (after the crucible pin includes csd)

1. _GG_ONLY_LANGS += "csd" in tests/tools/tri_comparison_chart.py.
2. ARGS_GRANULARITY["csd"] = "none" — a CSD resource definition has no parameter-list concept (same category as jcl/dockerfile/yaml).
3. Regenerate the tri-comparison chart data (the docs: auto-update tri-comparison data job).
4. Re-bless the golden-master crucible snapshots (tests/golden_master_audit.json, tests/golden_master_zero_dep_audit.json) for the new corpus, both dependency modes — see docs/self_scan/BUMPING_THE_CRUCIBLE_PIN.md.

Also (keyword-rosetta, separate)

Adding csd to keyword-rosetta is tracked in squid-protocol/keyword-rosetta#139 (bms precedent).

Reference

• Engine handler + transaction map: PR feat(mainframe): capture the CICS transaction map (#3211-followup, PR1 of 2) #3251
• _GG_ONLY_LANGS: tests/tools/tri_comparison_chart.py:190