Downstream reproduction: hyperpolymath/stateful-artefacts#69, governance job https://github.com/hyperpolymath/stateful-artefacts/actions/runs/37126259604/job/111212024402.
check-uuid-v7.sh at standards a9a3281d620bdd195369c9a6f0bc1d661910965a rejects .machine_readable/6a2/CLADE.a2ml identity UUID dbc2ef6f-015c-525d-bed8-ed0d04788cf1 (v5, existing since instantiation). The file declares membership in gv-clade-index. The checker says to “type external/legacy IDs explicitly”, but apart from hardcoded Julia dependency handling it scans every literal regardless of field/metadata annotation. There is no supported typed-legacy mechanism here.
Please define and validate an explicit legacy/external field or reviewed identity-migration mapping, with tests rejecting untyped new non-v7 IDs while preserving previously issued external identities. A downstream agent should not silently assign a different registry identity to make a metadata-description PR green, nor obfuscate the old literal to evade the gate.
Requested maintainer decision for this consumer: confirm whether the existing UUID is registered; if migrating to v7, specify how the registry and downstream references retain a mapping. The downstream PR is not force-merged.
Downstream reproduction: hyperpolymath/stateful-artefacts#69, governance job https://github.com/hyperpolymath/stateful-artefacts/actions/runs/37126259604/job/111212024402.
check-uuid-v7.shat standardsa9a3281d620bdd195369c9a6f0bc1d661910965arejects.machine_readable/6a2/CLADE.a2mlidentity UUIDdbc2ef6f-015c-525d-bed8-ed0d04788cf1(v5, existing since instantiation). The file declares membership in gv-clade-index. The checker says to “type external/legacy IDs explicitly”, but apart from hardcoded Julia dependency handling it scans every literal regardless of field/metadata annotation. There is no supported typed-legacy mechanism here.Please define and validate an explicit legacy/external field or reviewed identity-migration mapping, with tests rejecting untyped new non-v7 IDs while preserving previously issued external identities. A downstream agent should not silently assign a different registry identity to make a metadata-description PR green, nor obfuscate the old literal to evade the gate.
Requested maintainer decision for this consumer: confirm whether the existing UUID is registered; if migrating to v7, specify how the registry and downstream references retain a mapping. The downstream PR is not force-merged.