06-core-verify-project-gate-integrity-before-writing-any-codelisted

# Gate Integrity Verification Manual These gates exist to **replace manual testing and test files**. The goal is bulletproof vibe-coding: code that just works on direct-deploy, with zero test files (they burn tokens and rot when requirements change). Every gate either **prevents a runtime/deploy failure** or **prevents an unmaintainable mega-file**. They are designed to hold the line even for non-intelligent agents that trip constantly — the gate is the hard floor, the AGENTS.md rules are the prevention layer above it. If you are about to write or edit any code, you MUST run **Tier 1** first and fix every failure before writing a single line of implementation code. --- ## The four tiers | Tier | Script | When | Speed | What it guarantees | |------|--------|------|-------|--------------------| | **1 — Static** | `verify-gates.mjs` | Before writing ANY code, and first in the build chain | Instant (no build) | Config + source can't bypass type/lint safety, can't leak secrets, can't crash on missing env, can't ship a mega-file, can't break on Linux/container deploy. | | **2 — Ship** | `verify-ship.mjs` | Right before the direct-image deploy | Slow (after build) | Docker image is small enough to deploy and the Dockerfile won't bloat it. | | **3 — Boot** | `verify-boot.mjs` | End of a session / before deploy | Medium (boots app once) | The app actually boots and key routes respond without 5xx — catches what static analysis physically can't (wrong handler, undefined-env crash,