codex-genesis-harness 0.1.4 → 0.1.5

package/.codebase/CURRENT_STATE.md

@@ -1,8 +1,5 @@
-# Current State
-
-Current objective: evolve `codex-genesis-harness` into a reusable Genesis skill set for test-first, contract-first, memory-aware Codex workflows.
-
-**Current Status**: 100% Complete & Verified! All 24 skills are implemented, structural and smoke tests pass (`verify.sh`), and package integration & regression e2e checks pass cleanly (`run-evals.sh`). Ready for release.
-
-Start every task by reading this file, `MODULE_INDEX.md`, and `TEST_MATRIX.md`, then inspect only relevant files.
+# Current State: COMPLETED
+Last updated: Sun May 31 12:53:47 +07 2026
 
+## Reason
+testing complete transition

package/.codebase/state.json

@@ -0,0 +1,37 @@
+{
+  "current_state": "COMPLETED",
+  "history": [
+    {
+      "from": "INIT",
+      "to": "REQUIREMENTS_GATHERING",
+      "reason": "Started Gathering",
+      "timestamp": "2026-05-31T05:39:53.706Z"
+    },
+    {
+      "from": "REQUIREMENTS_GATHERING",
+      "to": "PLANNING",
+      "reason": "p",
+      "timestamp": "2026-05-31T05:51:07.765Z"
+    },
+    {
+      "from": "PLANNING",
+      "to": "IMPLEMENTATION",
+      "reason": "i",
+      "timestamp": "2026-05-31T05:51:07.883Z"
+    },
+    {
+      "from": "IMPLEMENTATION",
+      "to": "VERIFICATION",
+      "reason": "v",
+      "timestamp": "2026-05-31T05:51:08.001Z"
+    },
+    {
+      "from": "VERIFICATION",
+      "to": "COMPLETED",
+      "reason": "testing complete transition",
+      "timestamp": "2026-05-31T05:53:47.517Z"
+    }
+  ],
+  "context": {},
+  "pending_tasks": []
+}

package/.codex/skills/genesis-harness/SKILL.md

@@ -19,7 +19,7 @@ Use for project initialization, planning, feature work, bug fixes, audits, revie
 Do not use for simple read-only answers that do not require repository workflow or durable artifacts.
 
 ## Inputs required
-Read `.codebase/CURRENT_STATE.md`, `.codebase/MODULE_INDEX.md`, and `.codebase/TEST_MATRIX.md` when present, then inspect only relevant files.
+Read `.codebase/state.json` (MANDATORY on boot), `.codebase/CURRENT_STATE.md`, `.codebase/MODULE_INDEX.md`, and `.codebase/TEST_MATRIX.md` when present, then inspect only relevant files.
 
 ## Outputs required
 Plan or implementation artifact, tests, fixtures, verification evidence, docs sync, and codebase memory updates.
@@ -46,7 +46,7 @@ Work is complete only when tests pass, contracts and docs are current, and verif
 Implementing before tests, skipping fixtures, overloading `AGENTS.md`, and duplicating long context across skills.
 
 ## Recovery workflow
-If blocked or interrupted, reread current state, rerun verification, identify the first failing phase, and resume from that point.
+If blocked or interrupted, read `.codebase/state.json` to identify your exact FSM state. Rerun verification, identify the first failing phase, and resume from that point based on the strict state rules.
 
 ## Core Principle
 
@@ -178,6 +178,7 @@ Bundled scripts live under `scripts/`. Prefer copying or adapting these into `.p
 - `create-bug.sh`: scaffolds `.planning/bugs/NNN-bug-slug/`.
 - `create-adr.sh`: scaffolds `.planning/decisions/ADR-NNN-slug.md`.
 - `update-state.sh`: updates common fields in `.planning/STATE.md`.
+- **NEW**: `transition_state.sh`: Strict FSM transition script. You MUST use this script to move between `INIT`, `REQUIREMENTS_GATHERING`, `PLANNING`, `IMPLEMENTATION`, `VERIFICATION`, and `COMPLETED` states.
 - `offload-log.sh`: captures and trims large command outputs to protect the context window.
 - `compact-context.sh`: intelligent context compaction summarizing state to disk.
 - `run-verify-loop.sh`: state-tracked Ralph Loop verify-fix loop executor.
@@ -371,6 +372,14 @@ Feature, bug, phase, audit, and architecture work is ready to implement only whe
 
 If any item is false, do not implement. Update tracking to `[!]` or ask the user.
 
+## Validation Gates
+
+Before moving to the `COMPLETED` state, the agent MUST pass the validation gates:
+- Run `bash scripts/validation_gates.sh`
+- Ensure no leftover `TODO`, `FIXME`, `console.log`, or `print` statements remain in production code.
+- Ensure all tests and `verify.sh` checks pass.
+- If the validation gates fail, the agent is forced to remain in `VERIFICATION` or return to `IMPLEMENTATION` to fix the issues.
+
 ## Definition Of Done
 
 Work is done only when:

package/.codex/skills/genesis-state-machine/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: genesis-state-machine
+description: Formal Finite State Machine for memory, context persistence, and validation gates.
+---
+
+# Genesis State Machine (FSM)
+
+This skill dictates how the Agent tracks, persists, and transitions its internal state to survive session interruptions and enforce strict execution gates.
+
+## Core States
+
+The Genesis Harness operates in the following strict states:
+
+1. `INIT`: The agent has just booted. Needs to gather user intent or resume a previous task.
+2. `REQUIREMENTS_GATHERING`: Clarifying the user's request, doing empirical research.
+3. `PLANNING`: Creating `implementation_plan.md` and writing tests.
+4. `IMPLEMENTATION`: Writing code to satisfy tests and plan.
+5. `VERIFICATION`: Running test scripts (`verify.sh`) and validating constraints.
+6. `COMPLETED`: All tests pass, docs are updated, ready for the next task.
+
+## Rules of State Transition
+
+- **NEVER** skip a state directly (e.g., from `REQUIREMENTS_GATHERING` to `IMPLEMENTATION` without `PLANNING`).
+- **ALWAYS** use the strict transition script to change states: `bash scripts/transition_state.sh <NEW_STATE> "Reason for transition"`
+- **ALWAYS** read `.codebase/state.json` when you start a new conversation or wake up, to know exactly where you left off.
+
+## Handling Interruptions
+If the user's connection drops or you are restarted:
+1. Read `.codebase/state.json`
+2. If `current_state` is `IMPLEMENTATION`, resume coding based on the `task.md`.
+3. If `current_state` is `VERIFICATION`, resume running test scripts.
+
+## The State File
+The state is persisted in `.codebase/state.json`. **Do not edit this file manually.** Always use the `transition_state.sh` script to ensure validation gates are respected.

package/.codex-plugin/plugin.json

@@ -1,12 +1,12 @@
-{
+{
   "name": "genesis-skill-set",
-  "version": "0.1.0",
+  "version": "0.1.5",
   "description": "Genesis harness skill system for Codex test-first, contract-first, memory-aware autonomous workflows.",
-  "author": {
+  "author": {
     "name": "Genesis Skill Set"
-  },
-  "license": "MIT",
-  "keywords": [
+  },
+  "license": "MIT",
+  "keywords": [
     "codex",
     "skill",
     "planning",

package/README.EN.md

@@ -6,7 +6,7 @@
 
 ## 📌 What is Genesis Codex Harness?
 
-**Genesis Codex Harness** is an enterprise-grade, **Codex-exclusive** development framework for building production-quality software with Codex (Claude 3 Opus) as your AI engineer.
+**Genesis Codex Harness** is an enterprise-grade, **Codex-exclusive** development framework for building production-quality software with Codex as your AI engineer.
 
 ### Core Capabilities
 
@@ -546,14 +546,14 @@ Genesis:
 
 ---
 
-## 📚 All 24 Skills
+## 📚 24 Skills (All Available)
 
-Each skill follows standardized naming under the `.codex/skills/` directory:
+Each skill follows the standard naming convention in `.codex/skills/`:
 
 | Skill Directory | Purpose | When to Use |
 |---|---|---|
-| **genesis-harness** | Main orchestration engine and CLI entry point | `/genesis-init`, `/new-feature`, `/fix-bug` |
-| **genesis-research-first** | Autonomous empirical research before design & planning | Triggers automatically on new tasks |
+| **genesis-harness** | Main entry point of the system | `/genesis-init`, `/new-feature`, `/fix-bug` |
+| **genesis-research-first** | Autonomous empirical research before planning | Triggers automatically on new tasks |
 | **genesis-api-contract** | Design robust API contracts (schema, request, response) | Before implementing endpoints |
 | **genesis-api-sync** | Automate bi-directional contract & codebase synchronization | When endpoints are updated |
 | **genesis-spec-propagation** | Automatically cascade design specification updates downstream | When specs change |
@@ -599,7 +599,7 @@ Each skill follows standardized naming under the `.codex/skills/` directory:
 A: No! Genesis handles most Codex interactions. You mainly use simple commands like `/genesis-init`, `/new-feature`, etc.
 
 **Q: Is Genesis Codex-exclusive or can I use it with other models?**  
-A: **Codex-exclusive only**. Genesis is specifically designed for Claude 3 Opus strengths. Using other models will break the workflow.
+A: **Codex-exclusive only**. Genesis is specifically designed for Codex strengths. Using other models will break the workflow.
 
 **Q: How much can I actually save on tokens?**  
 A: Typically **40-60% per project**. Average project: 150k tokens (normal) → 60-90k tokens (with Genesis caching).
@@ -620,7 +620,7 @@ A: Main limits are technical: max 5 phases per project (performance), token budg
 ### Requirements
 - Node.js 16+
 - npm 8+
-- Codex (Claude 3 Opus) via VS Code Copilot
+- Codex via VS Code Copilot
 
 ### Install Methods
 
@@ -632,7 +632,7 @@ genesis-harness verify
 
 **Method 2: From Git**
 ```bash
-git clone https://github.com/your-org/codex-genesis-harness.git
+git clone https://github.com/tuanpham09/codex-genesis-harness.git
 cd codex-genesis-harness
 ./scripts/install.sh
 ./scripts/verify.sh
@@ -684,9 +684,20 @@ npm run pack:check      # Check npm package
 
 ---
 
+## 💖 Support the Project (Donate)
+
+This project is open-source and developed with passion. If you find **Genesis Codex Harness** helpful and it saves you time, consider buying me a coffee to keep the momentum going:
+
+- **Momo (Vietnam)**: `0865814259`
+- **PayPal**: *(Will be updated later)*
+
+Thank you so much for supporting the development of this project! ❤️
+
+---
+
 ## 🔗 Resources
 
-- **GitHub**: [codex-genesis-harness](https://github.com/your-org/codex-genesis-harness)
+- **GitHub**: [codex-genesis-harness](https://github.com/tuanpham09/codex-genesis-harness)
 - **Documentation**: See [.codex/](./codex/) folder
 - **Issues**: GitHub Issues
 - **Discussions**: GitHub Discussions

package/README.VI.md

@@ -6,7 +6,7 @@
 
 ## 📌 Genesis Codex Harness Là Gì?
 
-**Genesis Codex Harness** là một bộ framework phát triển phần mềm cấp enterprise, **chỉ dành cho Codex** (Claude 3 Opus), giúp bạn xây dựng phần mềm chất lượng cao một cách có quy trình và hiệu quả.
+**Genesis Codex Harness** là một bộ framework phát triển phần mềm cấp enterprise, **chỉ dành cho Codex**, giúp bạn xây dựng phần mềm chất lượng cao một cách có quy trình và hiệu quả.
 
 ### Các Khả Năng Chính
 
@@ -598,7 +598,7 @@ Mỗi skill tuân theo naming quy chuẩn trong thư mục `.codex/skills/`:
 A: Không! Genesis xử lý hầu hết. Bạn chỉ dùng commands đơn giản như `/genesis-init`, `/new-feature`.
 
 **Q: Genesis có dành cho mô hình AI khác không?**  
-A: **Chỉ dành cho Codex (Claude 3 Opus)**. Genesis được thiết kế riêng cho Codex.
+A: **Chỉ dành cho Codex**. Genesis được thiết kế riêng cho Codex.
 
 **Q: Tiết kiệm token bao nhiêu thực tế?**  
 A: **40-60% per project**. Dự án bình thường: 150k tokens → 60-90k tokens (với Genesis).
@@ -619,7 +619,7 @@ A: Main limits: max 5 giai đoạn/project, token budget enforcement.
 ### Yêu Cầu
 - Node.js 16+
 - npm 8+
-- Codex (Claude 3 Opus) qua VS Code Copilot
+- Codex qua VS Code Copilot
 
 ### Cách Cài
 
@@ -631,7 +631,7 @@ genesis-harness verify
 
 **Cách 2: Từ Git**
 ```bash
-git clone https://github.com/your-org/codex-genesis-harness.git
+git clone https://github.com/tuanpham09/codex-genesis-harness.git
 cd codex-genesis-harness
 ./scripts/install.sh
 ./scripts/verify.sh
@@ -677,9 +677,20 @@ npm run eval            # Chạy evaluation
 
 ---
 
+## 💖 Ủng Hộ Dự Án (Donate)
+
+Dự án này là mã nguồn mở và được phát triển hoàn toàn vì đam mê. Nếu bạn thấy **Genesis Codex Harness** hữu ích và giúp bạn tiết kiệm thời gian, bạn có thể mời tôi một ly cafe để tiếp thêm động lực phát triển nhé:
+
+- **Momo**: `0865814259`
+- **PayPal**: *(Sẽ cập nhật sau)*
+
+Cảm ơn bạn rất nhiều vì đã đồng hành cùng sự phát triển của dự án! ❤️
+
+---
+
 ## 🔗 Tài Nguyên
 
-- **GitHub**: [codex-genesis-harness](https://github.com/your-org/codex-genesis-harness)
+- **GitHub**: [codex-genesis-harness](https://github.com/tuanpham09/codex-genesis-harness)
 - **Tài Liệu**: Xem thư mục [.codex/](./codex/)
 - **Issues**: GitHub Issues
 - **Thảo Luận**: GitHub Discussions

package/README.md

@@ -1,23 +1,28 @@
-# Genesis Codex Harness | 开发高效软件的完整工具集
+# 🚀 Genesis Codex Harness | The Ultimate Enterprise SDLC Harness for Codex
 
-🌍 **Choose Your Language**:
-- **[📘 English Documentation](README.EN.md)** - Full comprehensive guide with real-world examples
-- **[📗 Tiếng Việt](README.VI.md)** - Hướng dẫn chi tiết bằng tiếng Việt
+[![npm version](https://img.shields.io/npm/v/codex-genesis-harness.svg?style=flat-square&color=blue)](https://www.npmjs.com/package/codex-genesis-harness)
+[![license](https://img.shields.io/npm/l/codex-genesis-harness.svg?style=flat-square&color=green)](LICENSE)
+[![Harness Verification](https://img.shields.io/badge/harness--verification-passed-brightgreen?style=flat-square)](#)
+[![Token Savings](https://img.shields.io/badge/token--savings-40%20to%2060%25-blueviolet?style=flat-square)](#)
+[![Target Model](https://img.shields.io/badge/model-Codex-orange?style=flat-square)](#)
+
+**Genesis Codex Harness** is an enterprise-grade, Codex-exclusive software development lifecycle (SDLC) framework. It converts Codex from a simple autocomplete assistant into a rigorous, autonomous AI Software Engineer that enforces strict test-first development, contract-first design, and persistent codebase memory.
+
+> [!NOTE]
+> Engineered to eliminate the #1 frustration of AI-assisted development—**context decay, token exhaustion, and silent regression**—while slashing API token overhead by **40% to 60%** per project.
 
 ---
 
-## ⚡ Quick Summary
+## ⚡ Core Pillars at a Glance
 
-**Genesis Codex Harness** is an enterprise-grade, Codex-exclusive development framework for building production-quality software with:
+*   🛑 **The Death of Context Rot:** Automatically offloads massive terminal outputs (`offload-log.sh`) and dynamically compacts codebase state (`compact-context.sh`). Your prompt stays clean and sharp even after 100+ continuous development turns.
+*   🔥 **Autonomous Self-Healing (Ralph Loops):** Caught a test failure or compiler crash? The harness executes closed-loop **Verify-Fix cycles** (`run-verify-loop.sh`) up to 5 times autonomously, reading errors and refactoring source code until the tests turn green.
+*   🧠 **Empirical, Research-First Engineering:** Enforces evidence-based solutions. Genesis runs automated scans of your local codebase patterns and official package repositories *before* writing a single line of plans or implementation code.
+*   🔄 **Cascading Spec Propagation:** Change a single schema field or API contract and watch the harness automatically cascade modifications (`/propagate-spec`) across all downstream phases, test fixtures, and integration assertions.
 
-- ✅ **Test-first development** (RED → GREEN → IMPROVE)
-- ✅ **Contract-first API design** (before coding)
-- ✅ **Persistent project memory** (no re-explaining needed)
-- ✅ **40-60% token savings** (via smart caching)
-- ✅ **Automatic spec propagation** (changes cascade through phases)
-- ✅ **Multi-phase orchestration** (5 phases per project)
+---
 
-### 🎯 Perfect For
+## 🎯 Perfect For
 - Enterprise teams building complex software with Codex
 - Projects requiring reliable, repeatable workflows
 - Organizations wanting to reduce token costs
@@ -188,7 +193,7 @@ Learn more: [FILE_NAMING_CLARIFICATION.md](.codebase/FILE_NAMING_CLARIFICATION.m
 ### Requirements
 - Node.js 16+
 - npm 8+
-- Codex (Claude 3 Opus)
+- Codex
 
 ### Quick Install
 ```bash

package/VERSION

@@ -1,2 +1,2 @@
-0.1.3
+0.1.5
 

package/package.json

@@ -1,43 +1,62 @@
-{
-  "name": "codex-genesis-harness",
-  "version": "0.1.4",
-  "description": "Install and manage the Project Genesis Harness Codex skill.",
-  "license": "MIT",
-  "bin": {
-    "genesis-harness": "bin/genesis-harness.js"
-  },
-  "scripts": {
-    "postinstall": "node bin/genesis-harness.js postinstall",
-    "verify": "bash scripts/verify.sh",
-    "eval": "bash scripts/run-evals.sh",
-    "pack:check": "npm pack --dry-run"
-  },
-  "files": [
-    ".codex-plugin",
-    ".codex/skills",
-    ".codebase",
-    "contracts",
-    "fixtures",
-    "tests",
-    "playwright",
-    "observability",
-    "bin",
-    "scripts",
-    "README.md",
-    "LICENSE",
-    "VERSION"
-  ],
-  "keywords": [
-    "codex",
-    "codex-skill",
-    "planning",
-    "project-management",
-    "engineering-harness"
-  ],
-  "engines": {
-    "node": ">=18"
-  },
-  "publishConfig": {
-    "access": "public"
-  }
-}
+{
+  "name": "codex-genesis-harness",
+  "version": "0.1.5",
+  "description": "Hệ thống quản trị (Harness) dành cho AI Agent (Codex) với cơ chế FSM State Persistence, Validation Gates và Test-First Workflow. Đảm bảo agent không bị trôi context.",
+  "license": "MIT",
+  "bin": {
+    "genesis-harness": "bin/genesis-harness.js"
+  },
+  "scripts": {
+    "postinstall": "node bin/genesis-harness.js postinstall",
+    "verify": "bash scripts/verify.sh",
+    "eval": "bash scripts/run-evals.sh",
+    "pack:check": "npm pack --dry-run"
+  },
+  "files": [
+    ".codex-plugin",
+    ".codex/skills",
+    ".codebase",
+    "contracts",
+    "fixtures",
+    "tests",
+    "playwright",
+    "observability",
+    "bin",
+    "scripts",
+    "README.md",
+    "LICENSE",
+    "VERSION"
+  ],
+  "keywords": [
+    "codex",
+    "ai-agent",
+    "autonomous-agent",
+    "harness-engineering",
+    "llm-workflow",
+    "project-management",
+    "state-machine",
+    "fsm",
+    "codex-plugin",
+    "developer-tools",
+    "validation-gates"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "author": "Genesis Codex Team",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/tuanpham09/codex-genesis-harness.git"
+  },
+  "bugs": {
+    "url": "https://github.com/tuanpham09/codex-genesis-harness/issues"
+  },
+  "homepage": "https://github.com/tuanpham09/codex-genesis-harness#readme",
+  "funding": {
+    "type": "momo",
+    "url": "tel:0865814259"
+  }
+}

package/scripts/transition_state.sh

@@ -0,0 +1,67 @@
+#!/bin/bash
+
+if [ -z "$1" ]; then
+  echo "Usage: bash scripts/transition_state.sh <NEW_STATE> [Reason]"
+  exit 1
+fi
+
+NEW_STATE=$1
+REASON=${2:-"State transition"}
+STATE_FILE=".codebase/state.json"
+CURRENT_STATE_MD=".codebase/CURRENT_STATE.md"
+
+if [ ! -f "$STATE_FILE" ]; then
+  echo "Error: $STATE_FILE not found."
+  exit 1
+fi
+
+if [ "$NEW_STATE" == "COMPLETED" ]; then
+  if [ -f "scripts/validation_gates.sh" ]; then
+    echo "Running Validation Gates before transitioning to COMPLETED..."
+    if ! bash scripts/validation_gates.sh; then
+      echo "Transition blocked by Validation Gates."
+      exit 1
+    fi
+  fi
+fi
+
+node -e "
+const fs = require('fs');
+const file = '$STATE_FILE';
+const newState = '$NEW_STATE';
+const reason = '$REASON';
+
+const allowed = {
+  'INIT': ['REQUIREMENTS_GATHERING', 'PLANNING'],
+  'REQUIREMENTS_GATHERING': ['PLANNING'],
+  'PLANNING': ['IMPLEMENTATION'],
+  'IMPLEMENTATION': ['VERIFICATION', 'PLANNING'],
+  'VERIFICATION': ['COMPLETED', 'IMPLEMENTATION'],
+  'COMPLETED': ['INIT', 'REQUIREMENTS_GATHERING']
+};
+
+let data = JSON.parse(fs.readFileSync(file, 'utf8'));
+const current = data.current_state || 'INIT';
+
+if (allowed[current] && allowed[current].includes(newState)) {
+  data.history = data.history || [];
+  data.history.push({ from: current, to: newState, reason: reason, timestamp: new Date().toISOString() });
+  data.current_state = newState;
+  fs.writeFileSync(file, JSON.stringify(data, null, 2));
+  console.log('Transition successful: ' + current + ' -> ' + newState);
+} else {
+  console.error('Invalid transition from ' + current + ' to ' + newState);
+  process.exit(1);
+}
+"
+
+if [ $? -eq 0 ]; then
+  echo "# Current State: $NEW_STATE" > "$CURRENT_STATE_MD"
+  echo "Last updated: $(date)" >> "$CURRENT_STATE_MD"
+  echo "" >> "$CURRENT_STATE_MD"
+  echo "## Reason" >> "$CURRENT_STATE_MD"
+  echo "$REASON" >> "$CURRENT_STATE_MD"
+  exit 0
+else
+  exit 1
+fi

package/scripts/validation_gates.sh

@@ -0,0 +1,46 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+echo "====================================="
+echo "   RUNNING VALIDATION GATES          "
+echo "====================================="
+
+repo_root="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+FAILURES=0
+
+fail() {
+  echo "❌ VALIDATION FAILED: $*" >&2
+  FAILURES=$((FAILURES + 1))
+}
+
+echo "1. Checking for leftover debug logs and TODOs..."
+# Exclude node_modules, .git, .codex, scripts, .codebase, bin, and md files
+EXCLUDES="--exclude-dir=node_modules --exclude-dir=.git --exclude-dir=.codex --exclude-dir=scripts --exclude-dir=.codebase --exclude-dir=bin --exclude=*.md"
+
+# We check for TODO, FIXME, console.log, print( (python)
+# Using grep recursively
+if grep -rn $EXCLUDES -E 'TODO|FIXME|console\.log|print\(' "$repo_root" | grep -v 'validation_gates.sh'; then
+  fail "Found unresolved TODOs or leftover debug logs in codebase!"
+else
+  echo "✅ Codebase cleanliness gate passed."
+fi
+
+echo "2. Verifying Harness Integrity..."
+if [ -f "$repo_root/scripts/verify.sh" ]; then
+  if bash "$repo_root/scripts/verify.sh" > /dev/null 2>&1; then
+    echo "✅ Harness Integrity gate passed."
+  else
+    fail "verify.sh failed. Core files or templates are missing."
+  fi
+else
+  fail "scripts/verify.sh is missing."
+fi
+
+echo "====================================="
+if [ $FAILURES -gt 0 ]; then
+  echo "❌ $FAILURES Validation Gate(s) failed."
+  exit 1
+else
+  echo "✅ All Validation Gates passed! Output is ready for production."
+  exit 0
+fi