v0.7.0 context missing top-level `type` keyword alias

The 0.7.0 UNTP context does not declare "type": "@type" at its top level. When the context is used standalone (without the W3C VCDM v2 context), i.e. when constructing a conformity scheme, every type property in a document is treated as an ordinary unknown property rather than as a type assertion, so type-scoped contexts never activate and any property defined only inside those scopes (e.g. conformsTo under ConformityScheme) silently fails to expand.

Steps to reproduce

Expand a minimal ConformityScheme document against the 0.7.0 context with jsonld.expand(doc, { safe: true }):

{
  "@context": ["https://.../0.7.0-untp-context.jsonld"],
  "type": ["ConformityScheme"],
  "id": "https://example.com/scheme",
  "name": "Example",
  "conformsTo": { "type": ["Link"], "linkURL": "..." }
}

Observed

jsonld.ValidationError: Safe mode validation error.
code: "invalid property"
message: "Dropping property that did not expand into an absolute IRI or keyword."
details: { property: "conformsTo", expandedProperty: "conformsTo" }

Same warning fires on every nested type in the document.

Expected

Document expands cleanly. Works whether the context is used standalone or prepended with https://www.w3.org/ns/credentials/v2.

Proposed fix

Add one entry to the top level of the context:

"type": "@type"