Feat: Fabric Network Orchestrator Agent

[manu-equinix]

Checklist

• I have read the CONTRIBUTING.md
• I certify that my MD file is onboarded to the OnEvent.json or OnSchedule.json (not README or catalog.json)
• I certify that my preview and released lists for OnEvent.json/OnSchedule.json are correct
• I certify that all OnEvent/OnSchedule in released are properly tested and ready for production

Summary:

• Creates the network + connections: builds a Fabric Network of a supported type (EVPLAN, EPLAN, EVPTREE, EPTREE, or IPWAN), waits for it to become ACTIVE, then creates one connection per caller-supplied access point — Ports for Layer2 types, existing Cloud Routers for IPWAN.
• Provisions and attaches to observability: waits for each connection to reach PROVISIONED, then attaches the provisioned connections to an observability stream (creating one if none is supplied).
• Independent, fully-reported: processes each access point on its own so one failure never blocks the others, and sends a single completion report covering every item's outcome.

[github-actions]

🧪 Template Spec Check (static — not execution-tested)

Grades the template text only: structure + an LLM judge on spec quality. No agent was run and no tools were executed — a pass does not mean the agent works.

⚠️ LLM judge could not reach the Groq API (network error, timeout, or bad response). Deterministic checks ran; judge scores are skipped. Templates passed on deterministic checks alone — spec quality was NOT graded.

✅ All templates passed  ·  1/1 passed  ·  threshold: 0.6

Template	Result	Judge Min	Issues
network-connection-orchestrator.md	✅ PASS	⚠️ skipped	—