Document page/wire linking -- folio reports -- in the user's own words
Wires continuing across pages had no page anywhere: element_linking
covers master/slave cross-references, not next_report/previous_report.
Written with "page" and "wire" in the prose and a glossary mapping them
to folio and conductor, since that is how people ask about it.
The central fact, taken from LinkElementCommand::isLinkable(): QET checks
exactly two things when linking two reports -- matching inverse type, and
both being free. It does not check that they are on different pages, that
either has a wire attached, that the two wires share a potential, or that
the arrows point sensibly. A link is an assertion the user makes and QET
renders without verifying, so --export-links is the only real audit.
Also documents what was written down nowhere: a report's dynamic text is
restricted to five variables (folioReportInfoKeys), the label describes
the partner's position rather than its own, report terminals are
deliberately excluded from wire-number counts because they are not real
terminals, linking replaces rather than adds, and a report is only
clickable in an exported PDF when its text actually shows %{label}.
EN/FR/DE.
ispyisail