Automation recon: portal endpoints, ACP control servers, live status

Records verified findings from a credentialed read-only recon of the
iTelescope portal (2026-07-18) in state/NOTES.md: the WebForms login flow,
the /DataService.svc JSON endpoints (GetAccountStatus, GetMyAvailablePlans,
ApplyPromoCode), the per-telescope ACP web servers behind HTTP auth
(tNN.itelescope.online / tNN.itelescope.net:80NN, confirmed on T33), the
Planner redirect to lookup.itelescope.online, and the per-site weather URLs.
Credentials themselves stay outside the repo.

state/TODO.md gains the next automation steps (map ACP endpoints, explore
the new planner, enumerate more DataService methods) and a campaign-impact
note: most Chile scopes plus several others are currently offline, including
recommended T71 and T73, so near-term work should target T33/T8/T32/T59 at
Siding Spring and status must be re-checked before any booking.

state/TODO.md

@@ -19,6 +19,15 @@
 
 ## Pending
 
+- Automation: map the ACP web endpoints on a per-scope server (start with free
+  T33) for plan submission and status; explore lookup.itelescope.online (the new
+  planner); enumerate more /DataService.svc methods. Recon notes in NOTES.md.
+- Campaign impact (status seen 2026-07-18): T71 and T73 are offline
+  (development/mount testing), as are T2, T17, T18, T20, T25, T30, T72, T74,
+  T75, T80. T8, T33, T32, T59 at Siding Spring are operational. Re-plan the
+  July-August campaign around T33 free time and Siding Spring scopes until the
+  Chile rebuild finishes; re-check status before any booking.
+
 - Fill in T74 when iTelescope publishes its specs.
 - Reconcile the retired scopes (T9, T19, T31, T69): the support article still lists
   them but the maintained sheet does not; confirm status and note it.