Fetch and split support tickets with HTTP Request in the support queue

## 5 · Finish and fair play 1. Copy both computed counts into the Challenge 06 website form. Its optional Check both answers sends one paired POST /check with both totals and your workflow. It returns overall correctness only. There are no separate Q1/Q2 check HTTP nodes. 2. Submit both answers, your sanitized workflow JSON and your own explanation of 40 to 2,000 characters and at least eight words, with both rule acknowledgements. 3. A supported correct final enters the leaderboard automatically. The server validates native calculations and the tickets contributing to each Count. The first accepted evidence and finish stay locked. No pending replay or human approval is part of ordinary season-time acceptance. Clock: first successful personal fetch to first accepted final. Practice is untimed. Weekly rank points follow 15 / 12 / 12 / 11, with exact ties sharing rank and points. Reward review happens at season end. No AI assistance of any kind. No Code, Function, AI, Agent, MCP or Tool nodes, hardcoded totals or executable code hidden in expressions. Before export: blank Settings.key and remove all credential references and pinned data. Keep Settings.username for your account binding. Never export participant keys. Open Challenge 06 submission · Leaderboard · Rules Data and submission are available only during Challenge 06's participation window.