Initialize repository snapshot

MERIDIAN_V1_CONFORMANCE_TEST_SUITE/README.md

@@ -0,0 +1,58 @@
+# MERIDIAN v1 Conformance Test Suite (Offline / Deterministic / Build‑Blocking)
+
+This suite turns MERIDIAN v1 into an **executable compliance gate**.
+
+What it tests (normative):
+- MERIDIAN v1 is **Sentinel‑governed**; verification is defined by the Sentinel offline verifier in `--strict` mode.
+- No proprietary verifier codes: expected failures are **Sentinel v1 failure codes** only.
+
+Normative references:
+- `2025-12-18-07h58m04s-attachments/MERIDIAN_V1_SPEC.md`
+- `2025-12-18-07h58m04s-attachments/MERIDIAN_V1_EVENT_CONTRACT_MATRIX.md`
+- `vaultmesh-orgine-mobile/spec/SENTINEL_FAILURE_CODE_SEMANTICS.md`
+- `vaultmesh-orgine-mobile/tools/vm_verify_sentinel_bundle.py`
+
+---
+
+## Run (one command)
+
+From `vaultmesh-orgine-mobile/`:
+
+```bash
+bash MERIDIAN_V1_CONFORMANCE_TEST_SUITE/run.sh
+```
+
+What `run.sh` does:
+1. Verifies Sentinel contract parity (code ↔ docs) via `tools/check_sentinel_contract_parity.py`.
+2. Runs each testvector in `manifest.yaml` through `tools/vm_verify_sentinel_bundle.py --strict`.
+3. Produces an auditor‑readable report (JSON + text) under `out/`.
+
+---
+
+## Output
+
+`out/` contains:
+- `out/meridian_v1_conformance_report.json` (suite summary + per-test results)
+- `out/meridian_v1_conformance_report.txt` (human summary)
+- `out/sentinel_reports/<TEST_ID>.verification_report.json` (verifier output per test)
+- `out/sentinel_stdio/<TEST_ID>.stderr.txt` (verifier stderr per test)
+
+---
+
+## Interpreting results
+
+- Suite PASS means the fixtures and verifier behave as the MERIDIAN v1 spec requires.
+- A deployment MAY claim “MERIDIAN v1 compliant” for a specific bundle **iff**:
+
+`python3 tools/vm_verify_sentinel_bundle.py --bundle <BUNDLE_DIR> --strict` returns `PASS`
+
+---
+
+## Notes on “killer tests” terminology
+
+MERIDIAN v1 does not introduce new verifier failure codes.
+
+Examples:
+- “silent denial” ⇒ Sentinel strict-mode failure `E_CHAIN_DISCONTINUITY`
+- “unbounded automation” (v1 boundary) ⇒ modeled as “execution without intent” ⇒ `E_CHAIN_DISCONTINUITY`
+