- VSCode does not provide any API to reuse its syntax highlighting engine so far
- Falling back to shiki, it seems there is a community consensus on this one
- Asynchronous implementation is mandatory
- Vue template updated to use raw html
- Uses language grammar from `elpi-lang` (to be removed when merging there)
- VSCode does not provide access to its token style sheets (mtkX)
- These *could* be retrieved from the DOM when:
  - Loading the view, TODO later on
  - Monitoring color theme changes, TODO later on
- As a fallback, FTM, token colors are defined in the extension style sheet arbitrarily
- Overall beautifying (includes light theme compliance, css galore)
- Style sheet to be factorised later on, in a DRYness manner, it is cascading by design afterall
- TODO: highlight *_text, whenever possible

This gets us rid of the status field on the left hand side card
rendering, that is, in the card feed.

It is still possible to turn this field into a more successful attempts
one as it used to be somehow, should we really want that.

In case of an empty panel (e.g. Failed attempts of an inference rule
with no entries), add a tiny footer that honors the corner radius of the
overall element and makes otherwise visually clear it is empty.

... forked from the very same step.

Some file locations were not rendered consistently.

- Inspection tools load & reference it correctly
- To be confirmed
- Will start an iconography and disseminate meaningful glyphs up to my intuition for a start

this.exec("eval $(opam env) && cd " +
vscode.workspace.workspaceFolders[0].uri.path + " && dune exec elpi -- "
+ this._options + " -no-tc -trace-on json /tmp/foo.json -trace-at run 0
999 -trace-only user " + current_file);

To discuss and change at will.

- Better rendering of trace infroamtion
- Towards elpi command line options exposed

- Added a file system watcher
- corresponding start command
- corresponding stop command
- reads and displays the trace on change file system events
- try with e.g. an equivalent of the following command:

cp /home/jwintz/Development/elpi/tests/sources/trace_findall.elab.json /tmp/traced.json

- either when the watch is running
- either when the watch has stopped

- Needs visual hints

Visuals:

- make message feed scrollable
- try and animate vertical scrolling to reflect navigation (can be better)
- towards a header
- display file name and date time for elaboration (consider using current locale)

As discussed.

goal's card color status.

Fix the algorithm to retrieve linked goals to stick with the one of
minimal step id in the current runtime.

... to the card W/ corresponding goal text displayed (elided if needed)
- See https://github.com/LPCIC/elpi/issues/148. This may require to rely
on another identifiers than goal ids.

- stop propagating mouse clicks to parent when toggling subcards
- actually display store after panel for CHR rules

next to the badge (these are step ids in the same runtime).

- Findall subcards
- CHR condition cards

- The sub trace is to be parsed

- Handling of goal ids for navigation
- Rendering of RESUME & SUSPEND step kind

Raised the question of the handling of step kinds with no such id:
- CUT
- RESUME

- CUT kind formatting
- RESUME kind formatting
- SUSPEND kind formatting

NOT recursive so far.

- Added stack
- About to parse sub cards