Epic: Mainframe runtime interactions -- queues, async, data access and lineage as fact channels #3445

The engine now matches fully cross-verified answer keys on three pinned COBOL corpora (zopeneditor, CBSA, CardDemo; #3210, #3415, #3421, #3429) for structure, dependencies, record layouts and I/O boundaries. It maps what programs are. It does not yet carry most of how they interact at runtime: queues, asynchronous work, data access and data flow. This epic makes each of those a fact channel with its own ground truth.

Children, in priority order

• Mainframe fact channel: SQL table usage (DML): which programs read and write which tables #3446 SQL table usage (DML): which programs read and write which tables
• Mainframe fact channel: MQ messaging: queues, put/get direction, producer/consumer graph #3447 MQ messaging: queues, put/get direction, producer/consumer graph
• Mainframe fact channel: online→batch bridge: a CICS transaction submitting a job via the internal reader #3448 online→batch bridge: a CICS transaction submitting a job via the internal reader
• Mainframe fact channel: async CICS: RUN/START TRANSID children, FETCH joins, RETRIEVE #3449 async CICS: RUN/START TRANSID children, FETCH joins, RETRIEVE
• Mainframe fact channel: IMS DL/I database access (CBLTDLI / EXEC DLI) #3450 IMS DL/I database access (CBLTDLI / EXEC DLI)
• Mainframe fact channel: JCL job flow: step order, COND/IF, GDG and dataset producer/consumer across jobs #3451 JCL job flow: step order, COND/IF, GDG and dataset producer/consumer across jobs
• Mainframe fact channel: field-level data lineage (MOVE / COMPUTE / STRING) #3452 field-level data lineage (MOVE / COMPUTE / STRING)
• Mainframe fact channel: unit of work and error handling: SYNCPOINT/COMMIT points, HANDLE CONDITION handlers #3453 unit of work and error handling: SYNCPOINT/COMMIT points, HANDLE CONDITION handlers
• Mainframe fact channel: batch CALL USING parameter contracts #3454 batch CALL USING parameter contracts
• Mainframe fact channel: VSAM file definitions: ORGANIZATION, ACCESS MODE, RECORD KEY #3455 VSAM file definitions: ORGANIZATION, ACCESS MODE, RECORD KEY

Every child ships with its own answer-key section, a blind census and a ledger field, so each new capability arrives with a measured accuracy.

Not recoverable from a repository

Scheduler dependencies (CA-7, TWS, Control-M), MQ trigger definitions, and runtime values (a call target computed at run time, a flag's actual value). Channels should say so in galaxy_ir SCOPE rather than guess.

Complements #3122 (CICS platform modernization), which consumes these channels in the refraction pipeline.

🤖 Generated with Claude Code