docs(lamni): mark flomni-to-lamni migration status, only webpage left

FLOMNI_TO_LAMNI_COMPARISON.md was written before any porting work started
and read as a stale plan once the tomo-queue backend and tomo-params GUI
were both done. Add a status pointer at the top so a fresh session can
find what's actually left (the webpage generator) without re-deriving it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

csaxs_bec/bec_ipython_client/plugins/LamNI/AI_docs/TOMO_PARAMS_GUI_PORT.md

@@ -15,7 +15,7 @@ each was a direct port, not a new design.
 
 **Status:** All of the below implemented, tested, and live-verified against
 the running simulated lamni deployment. §1/§2 committed as `bac3fa8`, §3 as
-`f3c90c5`; §4 not yet committed as of this doc.
+`f3c90c5`; §4 as `46cadc8`.
 
 ## 1. GUI: `TomoParamsWidget` generalized to lamni
 

csaxs_bec/bec_ipython_client/plugins/flomni/AI_docs/FLOMNI_TO_LAMNI_COMPARISON.md

@@ -3,7 +3,31 @@
 Comparison of the `flomni` and `LamNI` ipython-client plugins, written to scope
 which flomni features (GUI, status webpage, tomo-parameter widget, angle
 distribution) are worth porting to lamni. This is a comparison only — no
-migration has been implemented yet.
+migration had been implemented yet as of when it was originally written.
+
+**Status update (2026-07-16): items 2–4 of §5's recommended order are now
+done.** Only **item 1, the webpage generator (§4), remains open** — the rest
+of this document (originally a forward-looking comparison/plan) is now a
+historical snapshot of the *starting* gap, not the current state. See:
+
+- `csaxs_bec/bec_ipython_client/plugins/LamNI/AI_docs/TOMO_QUEUE_PORT.md` —
+  tomo-queue/job-list backend ported to lamni via a shared `TomoQueueMixin`
+  (`csaxs_bec/bec_ipython_client/plugins/OMNY_shared/tomo_queue_mixin.py`).
+- `csaxs_bec/bec_ipython_client/plugins/LamNI/AI_docs/TOMO_PARAMS_GUI_PORT.md` —
+  `TomoParamsWidget` generalized to lamni (setup detection, per-setup field
+  lists/order, lamni-only offsets section, "Duplicate selected" queue
+  button), plus several real `lamni.py` bugs found and fixed along the way
+  (two `sub_tomo_scan()` angle bugs, three `tomo_scan()`/`write_pdf_report()`
+  crashes, progress-GUI-auto-show + stale-busy-heartbeat).
+- **Remaining**: `LamNI_webpage_generator.py` is still the stub described in
+  §4 below — `_collect_setup_data()` commented out, `_TEMP_MAP` empty,
+  `HAS_TOMO_QUEUE = False` (now incorrect — a queue backend exists, see
+  above), `TOMO_TYPES` placeholders, and never wired into
+  `lamni.py.__init__`. §4's 5-step plan is otherwise still accurate.
+- Also still explicitly deferred (confirmed with Mirko, separate future
+  tasks): `zero_deg_reference_at_each_subtomo` for lamni (not implemented at
+  all yet), and sharing angle-calculation code between flomni/lamni
+  (currently same *shape* but not literally shared/DRY'd).
 
 ## 1. Scope & method