Make the merged repository coherent: README, state, and internal links

The mechanical merge preserved both histories but left two repositories
sitting side by side rather than one repository. This is the part that
makes it whole.

A top-level README explains the three strands - the telescope network
and campaign, the processing code, and in-person observing plans - and
says plainly that image data does not live here, because that is the
first question anyone will have when they find a pipeline with no
pixels.

state/PROJECT.md was still describing a markdown-only reference project
whose scope explicitly EXCLUDED automating bookings and image
processing. Both of those are now most of what the project does, so the
objective, scope and key facts are rewritten to match reality.

state/DECISIONS.md records why the merge happened - the two repos were
split by chronology rather than design, and the seam was already
leaking, with the campaign's TODO citing results held in the other repo
and the pipeline's README explaining a campaign it did not contain. It
also records that the image data deliberately stays out of the
repository.

state/TODO.md gains the pipeline and observing work that previously had
nowhere to live, including the measurement that changes the pipeline
plan: per-frame processing is 2.9 seconds and the whole 24-frame session
is 1.1 minutes single-threaded, so a scheduler earns nothing on stacking
and should be pointed at the Monte Carlo stages instead.

Internal links fixed for the new paths: pipeline/README.md referred to
session-scripts/ throughout, and itelescope/README.md pointed at a
state/ directory that is now one level up.

The .gitignore conflict between the two repositories is resolved by
combining them, with image formats ignored globally except under docs/,
where documentation figures are committed deliberately.

state/TODO.md

@@ -76,7 +76,32 @@
   10 Aug cancellation sweep. Update the CAMPAIGN.md ledger after every session
   from account/history.aspx.
 
-## Pending
+## Pending - pipeline
+
+- Productionise the processing code: a staged CLI
+  (ingest -> calibrate -> measure -> register -> stack -> solve -> compose ->
+  analyse), each stage resumable, packaged as an Apptainer image. Slurm array
+  jobs afterwards and ONLY for the expensive stages: measured on the NGC 5128
+  session, per-frame work is 2.9 s and all 24 frames take 1.1 min
+  single-threaded, so a scheduler buys nothing there. It pays for the Monte
+  Carlo work (completeness and injection-recovery tests, difference imaging,
+  shift-and-stack), which is where compute actually bit.
+- Must handle beyond mono LRGB: narrowband palettes, one-shot colour with
+  debayering, other observatories' header conventions, and full calibration
+  from bias/dark/flat for sources that do not pre-calibrate.
+- Three findings from the first session are requirements, not options: vet
+  moving objects in DETECTOR coordinates; carry r50/psf into any catalogue
+  cross-match; never fit a sky background to a field the target fills.
+
+## Pending - observing
+
+- Total solar eclipse, 12 Aug 2026, Menorca (`observing/eclipse-2026-menorca/`).
+  Totality 1m12s at Ciutadella with the Sun at 2 degrees, azimuth 288.
+  **Order the certified solar filter - it is the only item with no substitute
+  and there are three weeks left.** Then practise on a low sunset to calibrate
+  exposures for the extreme atmospheric extinction.
+
+## Pending - iTelescope
 
 - 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