[Agent OS] Scaffold 'ticket-intake' Progressive Disclosure Skill

🎯 Objective

Create a new Progressive Disclosure skill (ticket-intake) to explicitly govern how agents ingest and validate existing GitHub tickets before beginning execution.

🧠 Architectural Rationale

Our PR generation pipeline is now secured against tactical loops, but our intake pipeline remains vulnerable to "Blind Execution". Since Neo.mjs evolves at an extreme pace, historical or externally submitted tickets easily go stale, duplicate existing efforts, or contradict modern architectural paradigms.

If an autonomous swarm agent blindly accepts a ticket's premise, it will write regressions. We need a mandatory Pre-Execution Reflection Gate.

📋 Scope

1. Scaffold .agent/skills/ticket-intake/SKILL.md (triggered whenever a new ticket is assigned or selected).
2. Author the reference payload to mandate:
   • Relevance Validation: Query the Memory Core and Knowledge Base to ensure the requested feature/fix is still architecturally valid.
   • Duplication Check: Traverse the active Native Edge Graph to identify colliding active tickets.
   • Rejection Protocol: Empower the agent to aggressively reject the ticket. Document the exact workflow to formally reject the premise, post an Architectural explanation comment, and automatically close the issue rather than coding a regression.
3. Update AGENTS.md (Section 6: Request Triage) to point to this lazy-loaded skill, enforcing it for Frontier Models.