Assign echo-types a clade in the gv-clade-index registry #197

What

echo-types currently has no clade assignment. The governance scaffold added in #195 deliberately left the clade fields as TODO rather than fabricating registry data:

• .machine_readable/anchors/ANCHOR.a2ml → [clade] uuid / primary / assigned = TODO: assign via gv-clade-index registry
• .machine_readable/svc/k9/examples/project-metadata.k9.ncl → clade = "TODO: assign via gv-clade-index registry"
• 0-AI-MANIFEST.a2ml carries a clade-assignment-needed escalation
• .machine_readable/contractiles/trust/Trustfile.a2ml carries an anchor-no-fabricated-clade check that asserts the clade stays TODO until a real assignment lands (so this is enforced, not silently forgotten)

Action needed (maintainer / registry, not automatable from a scoped agent session)

1. Assign echo-types a clade + UUID in hyperpolymath/gv-clade-index (the registry repo is out of scope for the agent that filed this).
2. Create .machine_readable/CLADE.a2ml with the assigned uuid / primary clade / assigned date (cf. the shape in other estate repos' CLADE.a2ml).
3. Fill the [clade] fields in ANCHOR.a2ml + the k9 example from that assignment.
4. The anchor-no-fabricated-clade Trust check then flips from "must be TODO" to "must match CLADE.a2ml".

For reference, wokelang's clade is nl (nextgen-languages family); echo-types is a constructive-Agda type-theory repo, so it may warrant a different clade — that's the registry maintainer's call.

Filed during the estate-wide machine-readable checkpoint sweep (#195).