docs(dataset): sync documentation from dataset@v1.4.0

Author: github-actions[bot]

docs/changelog-dataset.md

@@ -4,6 +4,12 @@ All notable changes to this project will be documented in this file.
 
 This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and [Conventional Commits](https://www.conventionalcommits.org/).
 
+## 1.4.0 (2025-12-28)
+
+* feat: add full data validation script and a guide for contributing vehicle data ([47503d8](https://github.com/open-ev-data/open-ev-data-dataset/commit/47503d8))
+* chore: add documentation sync workflow for GitHub Pages ([52d5932](https://github.com/open-ev-data/open-ev-data-dataset/commit/52d5932))
+* chore: update OpenEV Data logo in README ([c68f49c](https://github.com/open-ev-data/open-ev-data-dataset/commit/c68f49c))
+
 ## 1.3.0 (2025-12-27)
 
 * fix(dockerignore): exclude SQL dump from Docker context ([4a0e590](https://github.com/open-ev-data/open-ev-data-dataset/commit/4a0e590))

docs/dataset/CONTRIBUTING_VEHICLES.md

@@ -247,6 +247,8 @@ Variants are for configurations with material differences (battery size, chargin
 
 ## Step 5: Validate Your Changes
 
+The validation system has three levels:
+
 ### Quick Syntax Check
 
 Validates JSON syntax only:
@@ -255,29 +257,75 @@ Validates JSON syntax only:
 npm run validate
 ```
 
+### Schema Validation
+
+Validates directory structure and JSON schema (no Docker required):
+
+```bash
+npm run validate:schema
+```
+
+This validates:
+
+**Structure Rules**:
+- Each model directory must contain `base.json`
+- Each year directory must contain `{model}.json`
+- Variant files must be named `{model}_{variant}.json`
+- No other files allowed in model directory
+
+**Schema Rules**:
+- All required fields present after merge
+- No extra fields (only fields defined in schema.json allowed)
+- Field values match expected types and constraints
+
 ### Full Validation
 
-Validates the complete merge pipeline and all required fields:
+Validates everything including the Rust ETL pipeline:
 
 ```bash
 npm run validate:full
 ```
 
-This command:
-1. Loads all vehicle files from `src/`
-2. Merges layers (base.json + year + variant)
-3. Validates each canonical vehicle
-4. Reports errors with affected vehicle count
+This runs schema validation first, then the ev-etl Docker binary for complete compilation testing.
 
 **Expected output for valid data**:
 
 ```
-Loaded 27 vehicle files
-Merged into 13 vehicles
-Validation complete: 13 valid, 0 invalid
+=== OpenEV Data Validation ===
+
+Step 1: Validating directory structure...
+Structure validation passed.
+
+Step 2: Validating merged vehicles against schema.json...
+Found 13 vehicles to validate.
+All 13 vehicles passed schema validation.
+
+=== Validation Complete ===
 ```
 
-**If validation fails**, the output will indicate which vehicles have errors.
+**Example error output** (missing required field):
+
+```
+SCHEMA ERRORS: 1 vehicle(s) have errors.
+
+File: src/byd/dolphin/2024/dolphin.json
+Type: year_base
+Errors:
+  - /: must have required property 'sources'
+```
+
+**Example error output** (invalid file name):
+
+```
+STRUCTURE ERRORS: 1 issue(s) found.
+
+  src/byd/dolphin/2024/wrong_name.json
+    Invalid file name. Variants must be named dolphin_<variant>.json
+```
+
+### IDE Real-Time Validation
+
+VS Code, Cursor, and compatible editors show validation errors while you edit. Look for red squiggly lines under fields with issues.
 
 ---