Ricardo's baseline branch restored the old text inside an August 2026 verifier.
The study needs the baseline and the redesign to run the same verifier, so this
branch keeps the released verifier 0.0.38 untouched and writes its errors the
way the verifier of July 2025 wrote them (ErrorHandler) in the language server:
the code, the expected type, the refinement found as the whole verification
condition, the instance translation table and the location, in one block that
is the diagnostic's message. State errors are written as state predicates
again (not the state-set notation), generated values as #fresh_N, and a value
created by a whole block shows the block's first line in the table.

The extension stays plain (diagnostics only), with the LiquidJava: Verify
command and the status bar that the study environment and its tour use.
BaselineLauncher prints the messages from the command line.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

The server tells the client when a run starts, so the status bar spins on
open and on save as well as on the Verify command, as the study tour says.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

The July 2025 verifier had no named state sets, so there is no old way of
writing a state of one; the spec files use the set notation, and both
conditions should show the same. PM's decision.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

activate() returns onStatus (loading, passed, failed, crashed, stopped) and getStatus(). The
study extension listens for passed, failed and crashed, which the server sends after it has
published the diagnostics, to know when a verification has ended: the diagnostics changes
alone cannot tell the emptying before a run from a pass.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>