sync: monorepo @ validator 0.1.5 / validation-types 0.1.1

records-bot · records-bot · commit b5f0b95fc22c · 2026-05-09T10:25:47.000+02:00
Snapshot of medvertical/records monorepo state, exported via
oss:export-validator. Tracks the npm publication of:

  @records-fhir/validator@0.1.5
  @records-fhir/validation-types@0.1.1

Run npm i @records-fhir/validator@0.1.5 for the matching
distribution. The conformance evidence in conformance-results/
matches the published tarball.
diff --git a/README.md b/README.md
@@ -90,9 +90,9 @@ Current HL7 `FHIR/fhir-test-cases` status in the source Records repository:
   non-resource formats, disabled upstream cases, unsupported modules, logical
   models, or cases without a Java baseline.
 - Candidate JSON comparison set: 531.
-- Runtime skipped from the headline lane: 38.
-- Executed and compared against Java `OperationOutcome`: 493.
-- 493 passed.
+- Runtime skipped from the headline lane: 35.
+- Executed and compared against Java `OperationOutcome`: 496.
+- 496 passed.
 - Failed/errors: 0.
 - Headline JSON resource parity: 100.0%.
 - Launch-discovery lane: 547/547 comparisons passed, 0 skipped, 0 failed.
@@ -104,7 +104,7 @@ versions, unsupported modules (SHC, CDA, CDS Hooks, JSON5, XVer, DSIG, HL7 v2),
 disabled upstream tests, logical models, or entries without a declared Java
 baseline.
 
-The 38 headline runtime skips are measured by the explicit
+The 35 headline runtime skips are measured by the explicit
 `--include-baseline-backlog` discovery lane. That lane now executes 547
 launch-discovery comparisons, including discovery-only FML/NDJSON, JSON5,
 DSIG JSON, and hidden-Java-outcome fixtures, with 0 skips.
@@ -134,7 +134,7 @@ product scope with actual JSON resource validation correctness.
 
 For that reason, the headline number should be read as:
 
-> Records matches the Java validator on 493/493 currently executable FHIR JSON
+> Records matches the Java validator on 496/496 currently executable FHIR JSON
 > resource validation comparisons.
 
 It should not be read as:
diff --git a/docs/conformance-scope-roadmap.md b/docs/conformance-scope-roadmap.md
@@ -1,6 +1,6 @@
 # FHIR Conformance Scope Roadmap
 
-**Status:** 2026-05-03
+**Status:** 2026-05-09
 **Scope owner:** validator engine / HL7 `FHIR/fhir-test-cases` lane
 **Repository boundary:** public `medvertical/records-fhir-validator` package scope
 **Current headline:** 100.0% on executable JSON resource comparison cases
@@ -28,19 +28,19 @@ standard represented in `FHIR/fhir-test-cases`.
 | Upstream manifest entries | 969 | All entries in `FHIR/fhir-test-cases/validator/manifest.json` at commit `e543043a`. |
 | Pre-filtered out | 438 | Not executable by the current JSON resource comparison harness. |
 | Candidate comparison set | 531 | R4/R5 or unversioned entries with a declared Java baseline. |
-| Runtime skipped | 38 | Candidate entries kept outside the headline JSON score; all are measured in the explicit discovery lane. |
-| Executed and compared | 493 | Records output was normalized to `OperationOutcome` and diffed against Java. |
-| Passed | 493 | All executable comparisons passed. |
+| Runtime skipped | 35 | Candidate entries kept outside the headline JSON score; all are measured in the explicit discovery lane. |
+| Executed and compared | 496 | Records output was normalized to `OperationOutcome` and diffed against Java. |
+| Passed | 496 | All executable comparisons passed. |
 
 The explicit launch-discovery lane is broader than the headline JSON claim:
 it admits the former runtime backlog plus discovery-only JSON5, DSIG JSON,
 parser-baseline, and hidden-Java-outcome fixtures. That lane now executes
 547/547 comparisons with 0 skips and 0 failures.
 
-The 100.0% score applies only to the 493 executed comparison cases. It should
+The 100.0% score applies only to the 496 executed comparison cases. It should
 be described as:
 
-> Records matches the Java validator on 493/493 currently executable FHIR JSON
+> Records matches the Java validator on 496/496 currently executable FHIR JSON
 > resource validation comparisons.
 
 It should not be described as support for every item in the upstream manifest.
@@ -60,12 +60,11 @@ These are excluded because they do not test the current package contract:
 validate a parsed FHIR JSON resource and compare the result with a Java
 `OperationOutcome` baseline.
 
-## Why 38 Candidate Entries Are Runtime Skipped In The Headline Lane
+## Why 35 Candidate Entries Are Runtime Skipped In The Headline Lane
 
 | Reason | Count | Decision |
 |---|---:|---|
 | Java baseline/parity backlog | 35 | Highest-priority expansion path because these are mostly normal JSON validation cases once their Java baseline path or semantic disagreement is resolved. |
-| Non-JSON payload that passed filtering (`.fml`, `.ndjson`) | 3 | Measured in the explicit discovery lane against Java parser baselines, not silently inside the headline JSON score. |
 
 ### Missing Java Baselines By Module
 
@@ -117,7 +116,7 @@ Measured result on 2026-05-03:
 
 | Lane | Executed | Passed | Failed | Skipped | Score |
 |---|---:|---:|---:|---:|---:|
-| Headline JSON resource parity | 493 | 493 | 0 | 38 | 100.0% |
+| Headline JSON resource parity | 496 | 496 | 0 | 35 | 100.0% |
 | Baseline-backlog discovery | 547 | 547 | 0 | 0 | 100.0% pass rate (`similarityScore`: 99.7%) |
 
 Accepted Java-baseline compatibility fixtures in discovery:
diff --git a/packages/validator/CONTRIBUTING.md b/packages/validator/CONTRIBUTING.md
@@ -68,7 +68,7 @@ AI-assisted work; otherwise a topic-style branch (`fix-slicing-edge-case`,
   in `conformance-results/` with the measured delta.
 - Changelog entry under the `[Unreleased]` section in `CHANGELOG.md`.
 - Description that includes the conformance-run delta if the PR touches a
-  validator path. Format: `JSON parity: 493/493 → 494/494` or
+  validator path. Format: `JSON parity: 496/496 → 497/497` or
   `discovery lane executed comparisons: 546/547 → 547/547`.
 
 **What CI runs:**
@@ -86,7 +86,7 @@ disable them — fix the underlying issue.
 
 ## Conformance discipline
 
-The headline conformance number (493/493 JSON resource parity against the
+The headline conformance number (496/496 JSON resource parity against the
 Java validator) is the package's externally-visible quality claim.
 Treat it like a public API:
 
diff --git a/packages/validator/src/README.md b/packages/validator/src/README.md
@@ -61,9 +61,9 @@ Current HL7 `FHIR/fhir-test-cases` status:
 - Upstream manifest entries: 969.
 - Pre-filtered out before validation: 438 because this harness measures JSON FHIR resource validation against Java `OperationOutcome` baselines, not XML, non-resource formats, disabled upstream cases, unsupported modules, logical models, or cases without a Java baseline.
 - Candidate JSON comparison set: 531.
-- Runtime skipped: 38.
-- Executed and compared against Java `OperationOutcome`: 493.
-- Passed: 493.
+- Runtime skipped: 35.
+- Executed and compared against Java `OperationOutcome`: 496.
+- Passed: 496.
 - Failed/errors: 0.
 - Executable comparison score: 100.0%.
 - Baseline-backlog discovery: 547/547 executed comparisons (100.0% pass
@@ -76,7 +76,7 @@ versions, unsupported modules (SHC, CDA, CDS Hooks, JSON5, XVer, DSIG, HL7 v2),
 disabled upstream tests, logical models, or entries without a declared Java
 baseline.
 
-The 38 headline runtime skips are measured by the explicit
+The 35 headline runtime skips are measured by the explicit
 `--include-baseline-backlog` discovery lane. That lane now executes 547
 launch-discovery comparisons, including discovery-only FML/NDJSON,
 JSON5, DSIG JSON, and hidden-Java-outcome fixtures, with 0 skips.
