semconv: registry v2 -- collections and features

The registry spoke MapGenie's ontology: a zone, a category, a
location, three entities for what the unified format knows as two.
v2 collapses them into collection and feature -- every named set of
things on a map is a collection, everything in one is a feature --
and moves each key to the entity it always described. Icon, render
and stroke keys attach to the collection; coordinates and watershed
membership attach to the feature; the world keys do not move. Two
keys arrive for the unified wire to speak later: atlas.geometry.kind,
stable, declaring point, path or area once per collection; and
atlas.label.policy, experimental, letting an area collection choose
quiet names over always-on ones. One key is renamed with its entity:
atlas.category.key becomes atlas.collection.key, which is the sole
payload byte change and touches only Cyberpunk 2077, the one game
with curated category equivalents -- no reader looks the old key up.

The wire itself has not moved, so two allowances bridge to flag day.
A v2 zone still spells its path collection's stroke width on itself,
and the validators let the zone answer for its collection's one
attribute until the write moves where the registry points. And the
manifest keeps declaring conventions 1: the number names the
vocabulary the payloads actually speak, and stamping the registry's
own version would have drifted every bundle's identity over words no
payload says yet. A rebuilt Westminster bundle lands under the same
stamp, byte for byte.

REGISTRY.md is rewritten as the v2 document, and the parity test
holds it to the new entity names.

commit

b8595f20a1749ae8b0c7c87ca55c4a158b320478

parent

37327fa0fa66c5c50b789baac693355d8715dd0f

author

Dami <dami.etoile@gmail.com>

kind

feat risk score 2.1 of 3, Jev's estimate