[CatarinaGamboa]

For the error-message study (liquidjava-study-env). Two settings, both off by default so nothing changes for other users.

What changes

• liquidjava.hover.showHints (default true). Off: the editor hover leaves the hints out and ends with Hints: in the LiquidJava view (Hints, under the error). The view already renders the hints closed (<details>), so with the setting off a participant sees a hint only by opening it. Decided with the PM on 2026-11-12: keep the hints, start them closed, let the person open them.

• liquidjava.usageLog (default empty): the path of a JSON Lines file to which the extension appends what is used in the view, one line per use with the time:

  event	when	fields
  tab	a tab is switched	tab: diagnostics, fsm, context
  hints	the Hints section is opened or closed	open, error (the diagnostic's key)
  found-step	a Found step arrow	direction, error
  location	a location in the view is clicked	file, line, character
  state-machine	Show in state machine, in the view or the code lens	from: view or code-lens
  show-view	the error's title code lens	file, line
  state-error-step, reveal, context, context-section, scope, diagram, copy	the other controls	as named

  The webview posts a usage message for each; services/usage-log.ts writes it. A write failure goes to the LiquidJava output channel only. utils/usage-log.ts is the pure part, with its own spec.

Tests

npm run test:unit: 149 tests pass, three new (the hover without hints; the tab and hints usage messages; the log lines). The exact-messages assertion of the tab test now lists the usage messages too. Lint and webpack clean.

Screenshots

Headless VS Code (openvscode 1.109), the study's practice file, liquidjava.hover.showHints off. The hover ends with the pointer to the view; in the view the Hint is closed until clicked.

Study side

liquidjava-study-env sets both in the redesign instance's workspace settings (liquidjava.hover.showHints: false, liquidjava.usageLog: logs/<P>/<X>/liquidjava-usage.jsonl) and its export counts the uses per task. The baseline branch ignores both settings.

🤖 Generated with Claude Code

[CatarinaGamboa]

Codex review (read-only, on the diff against main), three findings, all applied in 4bb0d41:

1. A render of an open <details> fires toggle too, so an opened hint drawn again after a save would have counted as opened again. Now a toggle counts only right after the summary was clicked or keyed (hintToggleByUser), with a test that a bare toggle logs nothing and a clicked one does.
2. zoom was listed in the event doc but not instrumented. Removed from the list; context-section added, which is.
3. Synchronous writes on the extension host. The writes are now chained promises (fs.promises.appendFile), asynchronous and in order.

Also in 8ee51bd: a tab click that lands on the badge inside the tab (the error count) now switches the tab; before, it did nothing, which the study's walk showed as a Verification tab click that never registered.

🤖 Generated with Claude Code