Add VSC v2.9 CI conformance check

Author: DigiEmu

.github/workflows/vsc-conformance.yml

@@ -0,0 +1,44 @@
+name: VSC Conformance
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  conformance:
+    name: VSC Conformance Check
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+
+      - name: Setup Go
+        uses: actions/setup-go@v5
+        with:
+          go-version: "1.22"
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Run fixture comparison
+        run: npm run vsc -- compare:fixtures
+
+      - name: Validate fixture comparison JSON
+        shell: bash
+        run: |
+          npm run vsc -- compare:fixtures --json > comparison-result.json
+          cat comparison-result.json
+          node -e "const fs = require('fs'); const data = JSON.parse(fs.readFileSync('comparison-result.json', 'utf8')); if (data.result !== 'COMPARE_PASS') { console.error(data); process.exit(1); } console.log('COMPARE_JSON_PASS');"
+
+      - name: Run full VSC verification
+        run: npm run vsc -- verify-all

README.md

@@ -30,6 +30,28 @@ The VSC v2.7 Conformance Fixture Package is available in [`conformance/v2.7/`](c
 
 The VSC v2.8 Node/Go Result Comparison Draft is available in [`conformance/v2.8/`](conformance/v2.8/). It defines how verifier implementations should compare result classes across the v2.7 conformance fixtures. The v2.8.2 comparison runner supports human-readable and machine-readable output: `npm run vsc -- compare:fixtures` (human-readable table) or `npm run vsc -- compare:fixtures --json` (JSON, intended for automation and future CI).
 
+## CI Conformance Check
+
+VSC includes a GitHub Actions workflow for automated conformance validation.
+
+The workflow runs on every push and pull request targeting `main` and checks:
+
+```powershell
+npm run vsc -- compare:fixtures
+npm run vsc -- compare:fixtures --json
+npm run vsc -- verify-all
+```
+
+The JSON comparison output must be valid JSON and must report:
+
+```json
+{
+  "result": "COMPARE_PASS"
+}
+```
+
+This CI check validates fixture-level comparison behavior and full repository verification status. It does not change VSC verification semantics.
+
 ---
 
 ## Core Concept

docs/releases/v2.9-ci-conformance-check.md

@@ -0,0 +1,75 @@
+# VSC v2.9 — CI Conformance Check
+
+Release: v2.9  
+Project: DigiEmu VSC / VSC Core
+
+## Summary
+
+VSC v2.9 adds a GitHub Actions conformance workflow for automated repository validation.
+
+This release uses the machine-readable JSON output introduced in v2.8.2 to make fixture comparison suitable for CI.
+
+## Added
+
+New GitHub Actions workflow:
+
+```text
+.github/workflows/vsc-conformance.yml
+```
+
+The workflow runs on:
+
+```text
+push to main
+pull_request targeting main
+```
+
+## CI validation steps
+
+The workflow performs the following checks:
+
+```powershell
+npm run vsc -- compare:fixtures
+npm run vsc -- compare:fixtures --json
+npm run vsc -- verify-all
+```
+
+The JSON comparison output is saved to:
+
+```text
+comparison-result.json
+```
+
+Then parsed with Node.js.
+
+CI fails if:
+
+```json
+{
+  "result": "COMPARE_PASS"
+}
+```
+
+is not reported.
+
+## Unchanged
+
+v2.9 does not change:
+
+- Go verifier semantics
+- Node runner comparison semantics
+- Conformance fixture expected results
+- PASS / FAIL / ERROR meaning
+- Evidence bundle verification logic
+
+## Release meaning
+
+v2.9 moves VSC from local conformance checking to automated repository-level conformance validation.
+
+This strengthens VSC as a portable evidence layer by making verification behavior continuously checkable on every relevant repository update.
+
+## Next possible step
+
+```text
+v2.10 — CI Artifact Upload / Published Conformance Report
+```