I built a zero-dependency Node engine for autonomous coding agents with wave execution and hash gates. Here is the architecture

Most coding agent frameworks rely on heavy Python stacks, complex graph libraries, or cloud orchestrators. I wanted something that runs purely in local POSIX environments, works across multiple CLIs (Claude Code, Codex, OpenCode, Gemini CLI), and has zero external npm dependencies (node_modules = 0). Here is how the modular architecture works under the hood: Key Architectural Problems Solved: Gate-2 Content-Hash Check: LLM coding processes frequently exit cleanly with code 0 while silently refusing or making 0 edits. The engine snapshots repo hashes before and after execution to immediately catch fake passes and prevent ghost completions. Wave-based DAG (wave_parser.js, wave.js): Tasks are defined in markdown tables on disk. The parser extracts dependencies and schedules independent tasks into parallel execution waves (Wave A, Wave B). Two-Tier Validation (Task-level vs Project-level): Task level: /wbValid and /wbReview use an independent model to test and score individual task diffs. Project level: /wbAudit performs vertical audits across the entire codebase or package, evaluating broad architectural integrity. Dynamic Model Routing & Custom Chains: Configure fallback chains per role (e.g. WORKER=qwen,gpt-5 and VALIDATOR=claude,gemini). It routes mechanical boilerplate to cheap/fast models while reserving heavy reasoning models for planning and adversarial review. A Loop With Real Stopping Conditions (--loop): Instead of unbounded autonomous loops that burn tokens in a circle, the loop exits deterministically when a stopping condition is reached: all tasks marked valid, a dependency blocks, or a vertical check like /wbAudit reaches target score (e.g. >= 8/10). Verbs Over Personas: Instead of asking an agent to "act like a security engineer", workflows run explicit, deterministic commands: /wbStandup, /wbSecure, /wbContext, /wbRelease, and /wbPublish. The entire core runs on plain Node.js. (Dropping the full architecture flowchart and GitHub repo link in the first comment below!) Happy to answer questions about wave scheduling, stopping conditions, or model chains!