1.2.0

Added

• The extension runs in the browser: github.dev, vscode.dev and any other
  virtual workspace. It ships a second bundle built for a web extension host,
  and capabilities.virtualWorkspaces no longer warns about limited support.

Changed

• Paths to template files are built as URIs from the workspace folder rather
  than as strings through node:path and Uri.file. The scheme is inherited,
  so @FILE completion, Go to Definition and block names from {extends} will
  work in a virtual workspace, where files live under vscode-vfs: and there is
  no disk to address.
• Descriptions come from the editor's own vscode.l10n instead of a bundle the
  extension read from disk itself. One step towards running in a virtual
  workspace, where there is no disk to read: node:fs ran at module load, so
  the extension could not even start in a browser host.
• Fenom re-indents while a tag is typed again. The grammar package declares
  indentation rules once more, and they now cover every block tag Fenom closes:
  {var}, {set} and {add} in their block form but not when they carry an
  assignment, the {case} and {default} branch markers, and a tag that opens
  and closes on one line no longer shifts the line under it.

Fixed

• A tag that opens and closes on one line no longer moves everything after it.
  srcset="{$a}{if $b}, {$c} 2x{/if}" changes no nesting, but the {if} was
  counted as an open block that nothing ever closed, so the next closing
  construct took its level — in a real template {/block} ended up two levels
  deep where there was no nesting left at all.
• Formatting no longer walks a template left. An HTML tag written over several
  lines — normal with Tailwind — matched none of the per-line patterns, so the
  nesting never grew on it while the closing tag still shrank it: every such tag
  cost one level, and by the end of the file {/block} sat four tabs deep.
  Attribute lines are now indented as a continuation, and a closing > on a
  line of its own comes back to the level of the tag it opened.
• Suggestions typed between two tags on the same line behave as they do outside
  a tag: a system setting completes to [[++name]] instead of a bare name, and
  a chunk is offered at all. Where a construct ends was decided by a regular
  expression that searched the current line and did not stop at ]], so
  [[a]] … [[b]] read as one tag with the cursor inside it.
• The Marketplace badges in the readme render again. shields.io retired its
  Visual Studio Marketplace badges, and all three showed as "retired badge" on
  the Marketplace page itself.

Full changelog: v1.1.0...v1.2.0