BinlogServer

Run automated loop checks for three-level documentation compliance after code changes. Use when verifying changed files for required L3 file-header declarations and required L2 module README.md synchronization before commit or CI merge.

Define and enforce a strict three-level documentation protocol for every code change. Use when developing, reviewing, or refactoring any project that requires L1 root README architecture map, L2 module README files, and mandatory L3 file-header input/output/pos declarations with post-change loop checks.

Repository-level guardrails for task delivery quality, verification, and completion artifacts