Strengthen Anti-Slop / Quality Pre-Commit Gate in Agent Operational Mandates

Problem

Currently, the operational rules prioritize the "Ticket-before-Commit" gate as an absolute hard stop. The "Anchor & Echo" Knowledge Base strategy is technically also a gate but doesn't share the same critical warning footprint, leading to instances where AI agents might write code fast (and get the ticket right) but commit it without documentation—potentially exposing the codebase to "AI slop".

Goal

We must harden the Agent Pre-Flight checks so that the code quality standard (specifically 100% semantic JSDoc & the Anchor/Echo strategy) is treated organically as the second half of a single, non-negotiable Pre-Commit Hard Gate.

Execution

1. Target AGENTS.md and upgrade the "Ticket-Before-Commit" section into "The Pre-Commit Hard Gates (Tickets & Anti-Slop)".
2. Define Gate 1 (Tickets) and Gate 2 (Anti-Slop) directly next to each other.
3. Target AGENTS_STARTUP.md and boldly establish the Knowledge Base Enhancement section as a "Mandatory Anti-Slop Gate", making it strictly forbidden to commit undocumented logic.