Repository navigation
COPAUA0C: DL/I fault scenarios, line-700 infeasible outcomes, re-proved record (Part of #5278) - #6108
Merged
Merged
Conversation
squid-protocol
added
the
shepherd:merge
Owner
Author
|
No description provided. |
squid-protocol
marked this pull request as ready for review
October 23, 2026 01:03
Owner
Author
|
No description provided. |
squid-protocol
enabled auto-merge (squash)
October 23, 2026 01:08
squid-protocol
added
shepherd:merge
Owner
Author
|
No description provided. |
Owner
Author
|
No description provided. |
5 tasks done
Owner
Author
|
No description provided. |
This was referenced Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #5278.
Checklist: partial [c:0c25aa7e] -- COPAUA0C is at 60/69 branches (4 still run no input: SCHD status other than TC at 308, the 501st message at 339, MQGET other than 2033 at 416, MQCLOSE failure at 963; the last two need MQ fault injection the harness lacks); the 5 line-700 outcomes are proposed infeasible and need owner review.
What changed
The case, port and record for COPAUA0C already exist (#5842, #5982). This slice:
carddemo-copaua0c:gu-summary-bad-status(GU of the summary answers AC: WHEN OTHER of 5500, I002) andrepl-summary-fails(REPL answers AC: 8400, I003). Branches 58 -> 60 of 69, runs 18 -> 20, fault runs 4 -> 6.infeasible_outcomes.json(6000-MAKE-DECISION line 700, the CARD-NOT-ACTIVE / ACCOUNT-CLOSED / CARD-FRAUD / MERCHANT-FRAUD arms and WHEN OTHER), each with the COBOL reason. Owner review needed. The 4 WHENs: nothing writes those flag values. OTHER: every decline already satisfies an earlier arm.evidence.py prove: proven, unapproved) and refreshes the det-sweep coverage ledger.Evidence ladder
Executed-equivalent: 20 scenarios, 6 fault runs, 41/41 paragraphs, 60/69 branches (58/64 net of the 5 proposed infeasible, if accepted); oracle GnuCOBOL + our stub, not z/OS. Residual: the 4 outcomes above.
Gates
pr_gates --fast7/7,--ratchets9/9,test_evidence.py, tree-wide guards,infeasible_outcomes.py check: pass. No golden change (no engine code touched).Sibling gaps
COPAUS0C (80/93 branches) and CARDDEMO COPAUS1C have the same coverage shape; out of scope in the issue.
Lessons for agents
The harness has
dli_faults(GU/REPL/ISRT statuses) but no MQ fault injection, so MQGET/MQCLOSE failure paths cannot be covered by a case alone.🤖 Generated with Claude Code