SUG 9.2: inconsistencies with index.json common_name(s) field

I have been reading through the SUG to understand the structure of sky culture data, especially the common_name/common_names field. I have noticed some inconsistencies that I think should be addressed:

SUG 9.2.4: Constellation -> common_name

• missing field translators_comments (9.2.7 has it), generate-pot.py uses it
• index.json (ex. arabic_arabian_peninsula) uses references but this is neither documented nor read by Constellations.cpp
• Constellations.cpp and generate-pot.py use context but this is not documented

SUG 9.2.5: Asterisms -> common_name

• missing field translators_comments (9.2.7 has it), generate-pot.py uses it
• Bug: SUG mentions references in common_name, but Asterisms.cpp tries to read data["references"] instead of data["common_name"]["references"] (GZ EDIT: fixed)
• unlike Constellations, Asterisms.cpp does not use context, but generate-pot.py does, but the field is not documented in the SUG

SUG 9.2.7: Sky Culture -> common_names (Names of Stars, Planets and Nonstellar Objects)

• SUG says translator_comments, index.jsons use translators_comments (with an extra "s")
• the function process_names in generate-pot.py uses context in common_names, but this is not documented in the SUG

These are just examples of what I have found so far. I will edit this issue if I find more. I suppose a solution would be to introduce a single section in the SUG that defines the structure of common_name/common_names, including all the fields and thus serving as a "single source of truth" so its easier to update and maintain.