Reconcile stateful-artefacts identity and registry metadata before UUID v7 cutover #98

Cross-repository identity reconciliation discovered while repairing hyperpolymath/stateful-artefacts#66 in PR hyperpolymath/stateful-artefacts#69. Related conformance policy: hyperpolymath/standards#1140.

At gv-clade-index commit 7f875de3c39931775213a98a5c2e4e0a3c3fd8a0:

• verisim/seed/repos.a2ml registers stateful-artefacts with primary rm.
• worker/data/repos.json publishes UUID ae44803d-a1e9-5d05-b7cf-ab8d9776ad9b, prefix rm-stateful-artefacts.
• That UUID equals URL-namespace UUIDv5 of github.com/hyperpolymath/stateful-artefacts, matching sync/deploy-clade-a2ml.sh.

The repository's existing .machine_readable/descriptiles/CLADE.a2ml (previously .machine_readable/6a2/CLADE.a2ml) instead has UUID dbc2ef6f-015c-525d-bed8-ed0d04788cf1, primary gv and explicitly provisional prefix. It has been preserved pending reconciliation, not silently replaced to satisfy CI.

Please coordinate an inventory of consumers of BOTH IDs, reviewed UUIDv7 migration/alias mapping consistent with standards policy, updates to the registry's UUIDv5 generator and generated data, referential checks, and rollback before cutover. A matching literal was not found elsewhere in indexed GitHub code for the local UUID; that is not proof no external consumer exists. No claim is made about live VeriSimDB/Worker deployment state.

Separately, both seed and Worker data have an empty description. The approved README-derived description is:

State-carrying artefact layer of the Reposystem/OPSM stack: schemas and tooling for artefacts that carry machine-readable state (identity, provenance, lifecycle, verification) across the git forges and estates.

This source metadata can be populated without changing either identity. Please do not close the identity issue merely because repository-local CI becomes green.