fix(test): make the no-annotation control a valid workflow (main is red)

[ako]

main is currently red. TestDescribeWorkflow_NoAnnotationEmitsNoComment fails:

issue1007_annotation_emit_test.go:135: unexpected violations [MDL-WF05] for a plain jump
--- FAIL: TestDescribeWorkflow_NoAnnotationEmitsNoComment
FAIL    github.com/mendixlabs/mxcli/mdl/executor

Both PRs were green

• fix(describe): emit workflow annotations as comments, not statements (mendixlabs/mxcli#1007) #351 added the test. Its fixture is a lone JumpToActivity whose target "Review" does not exist, and it asserted len(violations) == 0.
• fix(workflow): stop naming a jump activity after its target (mendixlabs/mxcli#1005) #350 added MDL-WF05, which reports exactly that: a jump to naming no activity.

Each CI run passed because neither branch contained the other's change. The failure only exists in the merge.

The rule is right; the fixture was not

no violations at all is only a meaningful assertion over input that should have none. Over an invalid fixture it quietly asserts something much weaker — "no rule has been written yet that notices this" — and that expires the moment someone writes one.

The fixture now carries the jump's target as a real activity, so the workflow is valid and the assertion means what it says. No production code changes.

The general lesson, recorded in the symptom table

When a test asserts the absence of diagnostics, make the input something you would be happy to ship. Two green PRs can merge to red and neither PR's CI can detect it — the only protection is a fixture that doesn't depend on which rules exist today.

Found by running make test on an unrelated docs branch cut from the merged main, which is an argument for doing exactly that after a batch of PRs lands.

🤖 Generated with Claude Code