Google-Grade Review Protocol

1. Code Health Over "It Works"

• Principle: A change that "works" but degrades readability or maintainability must be REJECTED.
• Check:
  • Is the code consistent with the project's style?
  • Is it "Atomic"? (Focuses on one thing). If not, suggest splitting the PR.
  • Are variable names descriptive enough to not need comments?

2. Human Responsibility

• Agent Rule: You are the "Assistant", but you must flag risks to the "Director" (User).
• Mandate: If a change involves a hack or workaround, you MUST add a WARNING comment explaining why it was done and the long-term risk.

3. The "Why" Rule