COBOL import rule misses single-line EXEC SQL INCLUDE <member> END-EXEC #3416

Found by the mainframe ground-truth ledger on CardDemo (answer key added in the CardDemo key PR). Cause: engine_sql_include_same_line.

Problem

The COBOL import rule (gitgalaxy/standards/language_standards/languages/cobol.py, around line 550) is anchored at the start of the line:

^(?:[0-9a-zA-Z \t]{6}[ \-]?)?[ \t]*(?:COPY|INCLUDE)\b

INCLUDE is only seen when it begins its own line, as in the two-line EXEC SQL / INCLUDE X form. That's why CBSA scores exact: its includes use that form. The one-line form EXEC SQL INCLUDE X END-EXEC never matches, so the COPY edge is lost.

6 missed copybook edges on CardDemo, all verified against the source:

Acceptance

• These 6 engine | copybook paths | … | fn ledger entries stop reproducing, and are ratcheted out with ground_truth_ledger.py update.
• A registry fixture for EXEC SQL INCLUDE X END-EXEC on one line, with and without a sequence area.
• The golden-master / rosetta re-bless this implies, as usual for a registry change.

🤖 Generated with Claude Code