sync: monorepo @ validator 0.1.12 / validation-types 0.1.4

Snapshot of medvertical/records monorepo state, exported via
oss:export-validator. Tracks the npm publication of:

  @records-fhir/validator@0.1.12
  @records-fhir/validation-types@0.1.4

Run npm i @records-fhir/validator@0.1.12 for the matching
distribution. The conformance evidence in conformance-results/
matches the published tarball.

Author: records-bot

README.md

@@ -45,7 +45,7 @@ jobs:
 For production CI, pin an immutable patch tag:
 
 ```yaml
-- uses: medvertical/records-fhir-validator@v0.1.11
+- uses: medvertical/records-fhir-validator@v0.1.12
   with:
     paths: resources/**/*.json
     profile-url: http://hl7.org/fhir/StructureDefinition/Patient
@@ -58,7 +58,7 @@ Action pinning:
 | Goal | Pin in `uses:` | Notes |
 |---|---|---|
 | Latest stable in current major | `medvertical/records-fhir-validator@v0` | Floating tag, force-moved on stable releases only |
-| Exact released version | `medvertical/records-fhir-validator@v0.1.11` | Immutable consumer tag |
+| Exact released version | `medvertical/records-fhir-validator@v0.1.12` | Immutable consumer tag |
 | Bit-exact reproducibility | `medvertical/records-fhir-validator@<commit-sha>` | Best for audit and forensics |
 
 The `validator-v<semver>` tag is the npm mirror/release-page tag. Use
@@ -67,7 +67,7 @@ The `validator-v<semver>` tag is the npm mirror/release-page tag. Use
 ### npm Package
 
 ```sh
-npm install @records-fhir/validator@0.1.11 @records-fhir/validation-types@0.1.4
+npm install @records-fhir/validator@0.1.12 @records-fhir/validation-types@0.1.4
 ```
 
 Validate a resource from Node.js:
@@ -88,7 +88,7 @@ artifacts until their upstream licenses and notices have been reviewed.
 
 ## What Is Included
 
-- `@records-fhir/validator` 0.1.11 - Apache-2.0 validation engine.
+- `@records-fhir/validator` 0.1.12 - Apache-2.0 validation engine.
 - `@records-fhir/validation-types` 0.1.4 - Apache-2.0 validation-domain types.
 - Composite GitHub Action at repository root.
 - Standalone examples under `packages/validator/examples/`.
@@ -134,9 +134,9 @@ Current HL7 `FHIR/fhir-test-cases` JSON resource validation status:
 
 Evidence artifacts:
 
-- [`conformance-results/report-2026-05-09.json`](./conformance-results/report-2026-05-09.json)
+- [`conformance-results/hl7-validator-testkit-2026-05-20.json`](./conformance-results/hl7-validator-testkit-2026-05-20.json)
 - [`conformance-results/baseline-backlog-discovery-2026-05-03.json`](./conformance-results/baseline-backlog-discovery-2026-05-03.json)
-- [`conformance-results/mii-triangulation-2026-05-09.json`](./conformance-results/mii-triangulation-2026-05-09.json)
+- [`conformance-results/mii-triangulation-alpha7-2026-05-19.json`](./conformance-results/mii-triangulation-alpha7-2026-05-19.json)
 
 The 438 pre-filtered entries are not counted as failures because they do not
 exercise the thing this harness measures: JSON FHIR resource validation with a

conformance-results/hl7-validator-testkit-2026-05-20.json

@@ -0,0 +1,10 @@
+{
+  "generatedAt": "2026-05-20T05:11:06.211Z",
+  "lane": "hl7-fhir-validator-testkit",
+  "repoUrl": "https://github.com/nicola-coventry/fhir-validator-testkit.git",
+  "checkout": "HEAD",
+  "workDir": ".external/hl7-validator-testkit",
+  "status": "unavailable",
+  "error": "Command failed: git ls-remote https://github.com/nicola-coventry/fhir-validator-testkit.git HEAD\nremote: Repository not found.\nfatal: repository 'https://github.com/nicola-coventry/fhir-validator-testkit.git/' not found\n",
+  "nextAction": "Confirm the authoritative HL7 validator test-kit repository URL or replace --repo-url with a reachable source."
+}