Source location in output for local builds

[PaulMartinsen]

📑 Description

This PR adds an extra batch file (.ci\asciidoc-converter\build_standard_debug.bat) for debugging document build locally with trace that includes reasonably accurate source locations. For example, should one forget the required transaction-id when registering a transaction such as:

// This an example of an error. Here the required `transaction-id` is missing
[role=transaction]
=== Retrieve BICEPS Content [{var_transaction_id}]

The build trace will report the error with the filename and approximate line number (actually the error is on line 9, not 16):

   ⁝
2026-08-06 21:02:14 INFO  - Processing actors for transaction DEV-29.
2026-08-06 21:02:14 ERROR - volume2/dev-30/tf2-dev-30.adoc: line 16 -> Missing transaction-id on section with role of transaction
2026-08-06 21:02:14 ERROR - asciidoctor: FAILED: D:/Projects/BLS/SDPi/DEV.SDPi/asciidoc/sdpi-standard.adoc: Failed to load AsciiDoc document

This may aid in tracking down the offending issue. The document and artefacts will be generated in sdpi-documents/sdpi-standard-debug/, though it may not be particularly useful because…

The downside is that some of the document processing does not occur in debug mode, viz:

• IssuesSectionPreprocessor: which populates the document with github issues (though this generally doesn't happen locally anway),
• DisableSectNumsProcessor: which removes any occurrences of :sectnums: from the document to prevent the AscidoctorJ parser from rendering additional section numbers.
• ReferenceSanitizerPreprocessor, ReferenceSanitizerPostprocessor: which re-writes links to conform to IHE guidelines.

Note

During normal builds, source information is incomprehensible by mortals. The example error above, for example. reports
an error in sdpi-standard.adoc: line -13633.

☑ Mandatory Tasks

The following aspects have been respected by the pull request assignee and at least one reviewer:

• Changelog update… though not sure if it is appropriate since this one is about tooling?
• Pull Request Assignee
• Reviewer

[ToddCooper]

@PaulMartinsen -- So is this PR ready for review & merge as part of our next SDPi Friday call on 7 August 2026?

[PaulMartinsen]

yep. Review, merge and be merry. Hopefully. I'll plan to address any review issues over the weekend.

[ToddCooper]

All changes reviewed and approved