@smile-digital-health/crl 5.1.1 → 5.3.0

package/README.md

@@ -4,38 +4,52 @@ Clinical Reasoning Language (CRL) parser and validator
 
 Clinical Reasoning Language (CRL) provides a structured way to model clinical decision logic, concept derivations, clinical activities, measurements, and summaries — while remaining simple, readable, and guideline-compatible.
 
+## CRL 5.3.0
+
+This release adds the Medical Validation Question–Result view, route question cards,
+a separate Result Questionnaire, and MV-scoped wording proposals for the owning KE.
+CRL/CEL syntax and CQL/FHIR emission semantics are unchanged from 5.2.0. Core APIs
+add selected answer values, presentation field ownership, and execution-model access
+without source correspondence. Policy storage can be discovered from `src/crl` plus
+`src/cel` without provenance; source highlighting still requires correspondence.
+Authoring kit 2.2 documents MV case intent and the wording-patch handoff. Folder-based
+MV/regression emission filtering is not implemented. See the [release notes](https://github.com/alphora/clinical-reasoning-language/releases/tag/v5.3.0)
+and [MV guide](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/docs/mv-component-view.md).
+
 ## Overview
 
-See the [User Guide](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/packages/crl/USER_GUIDE.md) for a comprehensive introduction to the CRL language, syntax, and authoring best practices. For the **CLI and MCP tool reference** (emit, validate, the MCP tools — for both CRL and CEL), see [TOOLING.md](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/packages/crl/TOOLING.md).
+See the [User Guide](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/packages/crl/USER_GUIDE.md) for a comprehensive introduction to the CRL language, syntax, and authoring best practices. For the **CLI and MCP tool reference** (emit, validate, the MCP tools — for both CRL and CEL), see [TOOLING.md](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/packages/crl/TOOLING.md).
 
 CRL is a domain-specific language designed for expressing clinical practice guidelines in a structured and machine-readable format. The language is implemented in TypeScript and provides a comprehensive set of tools for processing CRL documents.
 
 For the authoring reference over MCP, call `authoring_kit({})` to discover guidance,
 or `authoring_kit({view:"full",format:"markdown"})` for the complete audited Markdown.
 The response is the same document as the release's `authoring-kit.md`; the agent can
-read or save it. JSON remains the default. See the [kit guide](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/docs/authoring-kit.md).
+read or save it. JSON remains the default. See the [kit guide](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/docs/authoring-kit.md).
 
 ## Metadata annotations
 
-CRL concepts can carry typed metadata via an `@tag` convention on `meta` lines (e.g. `@description`, `@ke-feedback`, `@kg-concept`) — for descriptions, knowledge-engineer feedback, plain-language logic, external-store hints, and extraction provenance. See the [metadata model](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/packages/crl/spec/metadata-model.md) and the canonical [tag registry](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/packages/crl/spec/metadata-registry.json). *(Draft: the convention parses today; Validator enforcement is forthcoming.)*
+CRL concepts can carry typed metadata via an `@tag` convention on `meta` lines (e.g. `@description`, `@ke-feedback`, `@kg-concept`) — for descriptions, knowledge-engineer feedback, plain-language logic, external-store hints, and extraction provenance. See the [metadata model](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/packages/crl/spec/metadata-model.md) and the canonical [tag registry](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/packages/crl/spec/metadata-registry.json). *(Draft: the convention parses today; Validator enforcement is forthcoming.)*
 
 ## Installation
 
 The package is publicly available from npm; installation does not require an npm account or token.
 
 ```bash
-npm install @smile-digital-health/crl@5.1.1
+npm install @smile-digital-health/crl@5.3.0
 ```
 
-For a dependency that accepts compatible CRL5 updates:
+Pin the version so generated-artifact migrations are adopted deliberately:
 
 ```json
 "dependencies": {
-  "@smile-digital-health/crl": "^5.1.0"
+  "@smile-digital-health/crl": "5.3.0"
 }
 ```
 
-CRL5.1 changes the public authoring-kit npm and MCP APIs. When upgrading from 5.0.0, update kit calls as described in the [5.1.0 release notes](https://github.com/alphora/clinical-reasoning-language/releases/tag/v5.1.0); the CRL/CEL language and emitted CQL/FHIR are unchanged from 5.0.0. A `^5` dependency permits 5.1.0. Content from before the CRL5 language transition may also need language migration using the current authoring kit.
+CRL 5.2 renames generated retrieval libraries from `LocalPrimitives`/`ExternalPrimitives` to `LocalElements`/`ExternalElements`, including CQL includes and FHIR Library identities. Regenerate CQL and FHIR together and replace the previous generated-file inventory, preserving independently authored files. Re-emission does not automatically delete obsolete artifacts. See the [5.2.0 migration notes](https://github.com/alphora/clinical-reasoning-language/releases/tag/v5.2.0). A `^5` or `^5.1.0` dependency can acquire this update automatically; use an exact version pin when upgrades require coordinated artifact replacement.
+
+CRL/CEL syntax is unchanged by 5.2. When upgrading from 5.0.0, also update the authoring-kit npm/MCP calls described in the [5.1.0 release notes](https://github.com/alphora/clinical-reasoning-language/releases/tag/v5.1.0). Content from before the CRL5 language transition may need language migration using the current authoring kit.
 
 ### For Package Maintainers
 
@@ -165,7 +179,7 @@ The FSH-to-CRL transformer converts FHIR Shorthand (FSH) files into Clinical Rea
 - **Deduplication and Suffixing**: Terminology blocks are unique by identifier and body. If a duplicate identifier is encountered with a different body, a numeric suffix (e.g., `_2`) is added to the identifier. If both identifier and body are the same, the block is not duplicated.
 - **Extraction Logic**: For `medicationCodeableConcept`, the transformer uses `system`, `code`, and `identifier` from the FSH object. For `dynamicValue.expression.expression` (where `path = "code.coding"`), the transformer uses `system` and `code` from the CQL code expression string and `identifier` from the corresponding description.
 
-For more details, see the [User Guide](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/packages/crl/USER_GUIDE.md) and the technical mapping documentation.
+For more details, see the [User Guide](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/packages/crl/USER_GUIDE.md) and the technical mapping documentation.
 
 ## CLI Tool Usage
 
@@ -193,7 +207,7 @@ crl-emit --path <root.crl> --out-dir <project-root> --target fhir-def
 
 Output lands at `<project-root>/src/fhir/<ResourceType>/<id>.json`. CQL emit (the existing `--target cql` / default behavior) lands at `<project-root>/src/cql/<library-name>.cql`. Library content references the CQL file via the relative path `../../cql/<library-name>.cql`.
 
-For semantic rules, layout details, deliberate spec deviations, and the MCP `emit_crl` tool, see [`USER_GUIDE.md` §"Emitting FHIR Definition resources"](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/packages/crl/USER_GUIDE.md#emitting-fhir-definition-resources).
+For semantic rules, layout details, deliberate spec deviations, and the MCP `emit_crl` tool, see [`USER_GUIDE.md` §"Emitting FHIR Definition resources"](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/packages/crl/USER_GUIDE.md#emitting-fhir-definition-resources).
 
 ## API Usage & Reference
 
@@ -495,7 +509,7 @@ Note: This project uses a custom AST implementation that uses ANTLR's visitor pa
 >
 > The authoritative release checklist and instructions are maintained in a single location:
 > 
-> **[.github/PULL_REQUEST_TEMPLATE/release.md](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/.github/PULL_REQUEST_TEMPLATE/release.md)**
+> **[.github/PULL_REQUEST_TEMPLATE/release.md](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/.github/PULL_REQUEST_TEMPLATE/release.md)**
 >
 > Always follow the steps in this file when preparing a new release. This ensures consistency and reduces maintenance overhead. If you need to update the release process, update the PR template only.
 
@@ -509,7 +523,7 @@ Note: This project uses a custom AST implementation that uses ANTLR's visitor pa
 - **Generated Files:** Auto-generated files (e.g., ANTLR outputs, grammar-driven types) are ignored by git and should never be edited manually. Always use the provided scripts to regenerate them.
 - **Documentation:** Keep all documentation referencing the release checklist up-to-date by linking to the PR template.
 
-For more details, see the [release PR template](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/.github/PULL_REQUEST_TEMPLATE/release.md) and the automation scripts in `.github/scripts/`.
+For more details, see the [release PR template](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/.github/PULL_REQUEST_TEMPLATE/release.md) and the automation scripts in `.github/scripts/`.
 
 ### Error Handling Strategy
 
@@ -552,7 +566,7 @@ We provide a Visual Studio Code extension for CRL files:
 - Comment support
 - Language basics for a better editing experience
 
-For installation instructions and full details, see [crl-vscode/README.md](https://github.com/alphora/clinical-reasoning-language/blob/v5.1.1/packages/crl-vscode/README.md)
+For installation instructions and full details, see [crl-vscode/README.md](https://github.com/alphora/clinical-reasoning-language/blob/v5.3.0/packages/crl-vscode/README.md)
 
 ## License
 

package/dist/ast/types.d.ts

@@ -218,16 +218,16 @@ export interface ActivityBecause extends ASTNode {
     rationale: string;
     location: Location;
 }
-export type InterfaceSourceLayer = "LocalPrimitives" | "ExternalPrimitives" | "Inferences";
+export type InterfaceSourceLayer = "LocalElements" | "ExternalElements" | "Inferences";
 export interface ValueElement {
     path: string;
     location: Location;
 }
 export type RecordUnionTerm = {
-    kind: "local-primitives";
+    kind: "local-elements";
     define: string;
 } | {
-    kind: "external-primitives";
+    kind: "external-elements";
     define: string;
 } | {
     kind: "constructed";
@@ -284,7 +284,7 @@ export interface Concept extends ASTNode {
     __pureQuestion?: true;
     __pureQuestionRead?: true;
     __reductionLocalUnion?: string;
-    __bothRepFoldInLocalPrimitives?: string;
+    __bothRepFoldInLocalElements?: string;
     __recordUnionTerms?: readonly RecordUnionTerm[];
     __bothRepMerge?: "union" | "recency-value" | "record-union";
     __effectiveDescriptor?: unknown;

package/dist/authoring-kit/audit.json

@@ -1,7 +1,7 @@
 {
-    "auditedRevision": "18799337ec6b91e91a4b1577c0e31a7f1b575714",
-    "auditedSchemaVersion": "2.0",
-    "auditedContentHash": "e9870c0042e7cb2e76a66d10b0edc72056786e0a53ccb73dc417544c8753c8b2",
-    "scope": "Unified kit schema 2.0: canonical content unchanged; Markdown MCP retrieval and JSON compatibility reviewed from 451be38f1fc33723cfe44eec12c1add689c5c52b. Prior 301-file survey and explicit clinical/native evidence limitations retained. Transport owning tests and both real MCP entry points verified; see evidence ledger.",
+    "auditedRevision": "cc1b675ed9431d047bd5fb34305abef1b9af18a8",
+    "auditedSchemaVersion": "2.2",
+    "auditedContentHash": "f31aadf37e8e371f55d83f9632933baa383259bfa8023b5d31bba29d08392e36",
+    "scope": "Kit schema 2.2 maintenance from 34d591eeab7fae22485546add54efe41106d756d through cc1b675ed9431d047bd5fb34305abef1b9af18a8. MV case authoring and wording-patch handoff; corrected provenance-independent flag storage. Complete changed-test/source delta reviewed in 737-739. Core 4,864 pass/32 skipped, actual MCP pass; extension 1,261 pass/3 expected failures. Scoped presentation emit parity and 19-case CRE comparison with installed 5.2.0 passed. Native final review converged; external final review exhausted its budget after prior findings were dispositioned. This stamp does not claim suite-aware MV/regression emission or new clinical/native verification. See evidence ledger.",
     "evidence": "packages/crl/src/authoring-kit/tests/coverage.md"
 }