GeezerVison

Closes #115. Uses liquidjava-fsm 0.2.1 (liquid-java/liquidjava-fsm#13).

Why

A class with several @StateSets, like ImageWriteParam with its tiling and compression states, was drawn as one diagram of the first state set. Every compression method ended up on the tiling diagram, and a compression error was marked on a tiling state: setCompressionQuality() in startCompression showed startTiling as rejected.

What

• Server: liquidjava/fsm and StateRefinementErrorDTO now return one StateMachineDTO per state set (stateMachines, with a stateSet index), using StateMachineParser.parseAll from fsm 0.2.1.
  • The error context goes only on the diagrams whose transitions include the called method, and each one uses its own state set's part of the verifier's states.
  • A state is marked rejected only if no accepted state includes it, so a call that is rejected because of another state set doesn't blame this one. With one state set this gives the same marks as before.
• View: the diagrams are stacked, each titled with its states. The diagram with the error comes first, and Focus on error dims the others. The summary combines the state sets the call involves. Copy Mermaid Source copies every diagram.
• A class with one state set looks exactly as before.
• The walkthrough mentions the per-state-set diagrams.

Arrows between state sets are left for later. A method that needs a state of the other state set keeps it as a condition, e.g. [compressionSet(this)].

Screenshots

Expert ImageWriteParam spec, in headless VS Code.

Tiling error: the tiling diagram comes first.

Focus on error: the compression diagram below it is dimmed.

Compression error, before and after: before, it was drawn on the tiling diagram with startTiling marked rejected. Now it is on the compression diagram.

Before	After

Show all:

Tests

• Server: StateMachineDTOTest (new) and StateErrorContextDTOTest cover per-state-set marking and not blaming another state set. 34 tests pass.
• Client: new specs for stacking, dimming, ordering and copying several diagrams, and for an error that cannot be marked (Keep the stepper and View error when a state error cannot be marked, and put State Machine next to Verification #161) on a class with several state sets. 105 unit tests pass, typecheck and lint are clean.
• Integration (vscode-test): all 10 tests pass.

Rebased on main after #165. The screenshots are from the build after #161.

🤖 Generated with Claude Code