Query QRY0 -- Query schema including split from Dance adapter Issue 645 - #648
Conversation
Extract the Core-owned Query schema into independently loadable Query and QueryDance adapter packages. Keep Query directly invocable without Dance imports, add the adapter-owned MetaQueryDance affordance contract, and validate both packages load after Core.
ApproveReviewed PR #648 against #645 and the updated normative Query/Dance specifications. The PR cleanly separates the Core-dependent Query schema from the Dance-layer QueryDance adapter, retires the Core-owned legacy Query artifact, and proves the intended load order: Core → Query → QueryDance. CI passed on the reviewed head Non-blocking follow-up: #645’s original issue body predates the now-normative Query/Dance split. The PR matches the updated DevDocs and intentionally defers standalone Dance-package extraction to the documented follow-on boundary issue. Approved for merge; merging closes #645. |
Summary
Implements QRY0 / #645 by extracting the authoritative Query schema from the retired Core-owned Query artifact and introducing a separate QueryDance adapter package.
Query remains directly invocable without Dance types. QueryDance is a Dance-layer adapter over that same direct Query entry point.
Changes
MAP Query Schema-v0.0.2.MAP Query Dance Adapter Schema-v0.1.0.map-query-schema.tdl.MetaQueryDanceType, and the concreteDanceAffordedBy/AffordsDanceaffordance pair.ExecutionInstanceexecutesQuerydirectly rather than a Dance request.Dependency boundary
map-query-schema, not a loadable package.Validation
npm run map-schema:compile:coreschemanpm run map-schema:check:coreschemanpm run fmt:checkgit diff --check