[davidnmbond]

Patch for the MS Ticket Contract assessment, found by a pilot on real Jira tickets (MS-27629).

• A Verification Evidence table headed Criterion | Evidence (not only Criterion | Test) is recognised as a criteria mapping table, so the evidence heading no longer trips the criteria-duplication cap.
• Bold sub-headings inside a Verification Evidence section (for example *Automated coverage of the MUST criteria*) are not counted as criteria headings.
• An acceptance criterion struck through in full (-text-, optionally followed by a note or "moved to KEY") is no longer counted: it was moved by a person and belongs to another ticket. Partial strikes and leading-minus items still count.

993 tests pass; OPS and parity scores are unchanged. Re-scoring the real pre-edit tickets (MS-26584, MS-27609, MS-26174) gives a passing Ticket Contract with no caps.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 18 complexity · 0 duplication

Metric	Results
Complexity	18
Duplication	0

View in Codacy

🟢 Coverage 100.00% diff coverage · +0.00% coverage variation

Metric	Results
Coverage variation	✅ +0.00% coverage variation (-1.00%)
Diff coverage	✅ 100.00% diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (fded1cd)	2057	2055	99.90%
Head commit (9b24a9d)	2064 (+7)	2062 (+7)	99.90% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#8)	9	9	100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}