[CatarinaGamboa]

The State Machine view described a state error in its own words: "x.m() is rejected when x is in state A · allowed in state B", with a legend of Call rejected, Call allowed and Allowed, but not reachable here for the possible and accepted states. It now uses the terms of a compiler error, as the Verification tab does (Expected / Found):

• Summary: Invalid method call x.m() · expected state B or C · actual state A
  • expected lists every state that accepts the call (before, only the possible ones were listed, or all accepted ones when the state is unknown); actual lists the states the receiver may be in, or unknown.
  • with several state sets, one group per set, joined with and: expected state tilingSet and compressionExplicit · actual state startTiling and compressionExplicit.
  • when the error cannot be marked: Invalid method call x.m(), or Invalid method call at line N.
• Legend: ✕ Actual state, not expected, ✓ Actual state, expected, Expected state (the dashed outline). The marks on the diagram are unchanged.

Before	After

Second error of the same file, param.setCompressionQuality():

The summary drops the receiver, which is already in the call.

Testing

• npm run test:unit (107 passed), tsc -p tsconfig.test.json, webpack build.
• Checked in a headless VS Code on the ImageWriteParam study exercise (screenshots above).

Independent of #167 (shows the conditions by default); both touch the State Machine view but not the same lines.

🤖 Generated with Claude Code