@@ -92,12 +92,23 @@ heuristics to module constants so they are sweepable: single-line guard
9292` 1.5 * avg_fs ` , spanning-promote ` 0.7 * page_width ` , bottom-merge
9393` 0.65 * page_height ` .
9494
95- ### C. Corrector-side banner fallback (cheap safety net, may fix isporeu2023 alone )
95+ ### C. Corrector-side banner fallback (DONE, commit 0fd5166 — does not fix the 3 )
9696Independent of xy_cut: when ` _banner_region ` from the lead author does not yield a
97- parseable legend, also try building the banner from the top-of-text region (first
98- N lines) or search the whole pre-first-body-section span for the numbered legend.
99- Lower risk than editing xy_cut and may recover isporeu2023 without touching
100- reading order. Consider doing this first as a quick win, then A for gasimova.
97+ parseable legend, parse the legend from the top-of-document band and search each
98+ author marker across the full text. Implemented, tested (+2 unit tests), safe (no
99+ regressions, single-affiliation posters still no-op).
100+
101+ ** Outcome: recovers none of the 3 ORDER-GAP posters.** They do not match the
102+ "legend separated from an intact byline" pattern C targets; their bylines are
103+ scrambled or lost in extraction:
104+ - gasimova: 6 of 7 authors have adjacent markers, but the lead author's name is
105+ split from her marker ("...Gasimova Bhavesh / Aydan", her ` 1 ` detached to the
106+ line start), so the all-authors-resolve gate bails.
107+ - isporeu2023: the byline markers are absent from the extracted text entirely;
108+ only the ORCID-list author names survive ("ORCID iDs: Ivanyi P, https://...").
109+ - 8228476: RTL, the affiliation numbers are detached from the institutions.
110+ C remains as a real robustness net for the wider corpus; the three corpus cases
111+ require A (and D for the RTL one).
101112
102113### D. Bidi/RTL handling for 8228476 (separate sub-track)
103114The Hebrew poster needs the affiliation markers preserved through bidi
0 commit comments