Extension 0.9.1: publisher note at the top of the README, extension changelog

GUIDE.md

@@ -592,7 +592,7 @@ Three ways to get it:
 
 1. VSCodium: open the Extensions tab, search "DSSL" and install. It is on Open VSX:
    https://open-vsx.org/extension/ehs-studio/dssl-vscode
-2. VS Code: download `dssl-vscode/dssl-vscode-0.9.0.vsix` from the repo files, then
+2. VS Code: download `dssl-vscode/dssl-vscode-0.9.1.vsix` from the repo files, then
    Extensions panel, `...`, Install from VSIX. (The Microsoft Marketplace listing is not published yet.)
 3. Build it yourself: `cd dssl-vscode && npx @vscode/vsce package --no-dependencies`.
 

README.md

@@ -68,7 +68,7 @@ Both drop a `dssl-engine/` folder next to you: the engine, a starter token set,
 
 Prefer to click: [dssl-engine.zip](https://dssl-sable.vercel.app/dssl-engine.zip) or [dssl-engine.tar.gz](https://dssl-sable.vercel.app/dssl-engine.tar.gz). Same package, straight from the browser.
 
-Writing your own .dssl? The official editor extension (`ehs-studio.dssl-vscode`) puts the real compiler in your editor: the squiggles are the same errors the browser console prints, completions come from your own token registry, and hovers explain the semantic vocabulary. One package for VS Code and VSCodium (same extension API). In VSCodium, search "DSSL" in the Extensions tab (it is on Open VSX: https://open-vsx.org/extension/ehs-studio/dssl-vscode). In VS Code, download `dssl-vscode/dssl-vscode-0.9.0.vsix` from the repo files, then Extensions panel -> ... -> Install from VSIX. See `dssl-vscode/PUBLISHING.md` for publishing.
+Writing your own .dssl? The official editor extension (`ehs-studio.dssl-vscode`) puts the real compiler in your editor: the squiggles are the same errors the browser console prints, completions come from your own token registry, and hovers explain the semantic vocabulary. One package for VS Code and VSCodium (same extension API). In VSCodium, search "DSSL" in the Extensions tab (it is on Open VSX: https://open-vsx.org/extension/ehs-studio/dssl-vscode). In VS Code, download `dssl-vscode/dssl-vscode-0.9.1.vsix` from the repo files, then Extensions panel -> ... -> Install from VSIX. See `dssl-vscode/PUBLISHING.md` for publishing.
 
 AI agents and machine reviewers: this repo ships `llms.txt` (dense, structured facts), `AGENTS.md` (how to work on the codebase) and `PARITY.md` (the honest feature matrix against CSS). The site serves the same `llms.txt` at https://dssl-sable.vercel.app/llms.txt
 

dssl-vscode/CHANGELOG.md

@@ -0,0 +1,36 @@
+# Changelog
+
+## 0.9.1
+
+- README: a note at the top explaining the publisher name (`ehs-studio` is the same person as
+  [wasselnl77-hash on GitHub](https://github.com/wasselnl77-hash)), since the install
+  warning can look alarming.
+- This changelog.
+- Docs now say the extension is on Open VSX and can be installed from VSCodium's Extensions tab.
+
+## 0.9.0
+
+- **Designers.** Three live panels that read and write DSSL: aura, texture and slider.
+  Open them from the command palette (*DSSL: Open the designer*, *DSSL: Design an aura*,
+  *DSSL: Design a texture*, *DSSL: Design a range slider*). Previews are drawn by the same
+  renderer the engine uses, and the generated code is checked by the real compiler as you edit.
+  *Insert at cursor* and *Copy* put it in your file; *Load from selection* reads an existing
+  declaration back into the controls.
+- **Convert CSS.** *DSSL: Convert a CSS file to DSSL* turns a CSS file or selection into DSSL.
+- **New language features understood.** Completions and hover docs for `texture`, `aura`,
+  `aura-glow`, `aura-particle(s)`, `glow-particle(s)`, `aura-glow-particle(s)` and `slider`,
+  scoped to the property you are typing in.
+- **Lint warnings.** Low text contrast, removed focus outlines with no replacement, and tap
+  targets under 24px show up as warnings.
+- Bundled engine updated to 0.9.0.
+
+## 0.8.x
+
+- Bundled engine updated: one cascade across all stylesheets, `fluid` on longhand
+  properties, and the compiler fixes shipped with those releases.
+
+## 0.7.1
+
+- First release: diagnostics from the real DSSL parser and resolver (did-you-mean included),
+  completions from the workspace token registry, hover docs for the semantic vocabulary,
+  syntax highlighting.

dssl-vscode/README.md

@@ -1,5 +1,13 @@
 # DSSL Language Support (VS Code + VSCodium)
 
+> **About the publisher name.** You may see a warning when you install this, because the
+> publisher `ehs-studio` is new on Open VSX. It is me: **EHS-Studio is the same person as
+> [wasselnl77-hash on GitHub](https://github.com/wasselnl77-hash)**, and the project is
+> open source (MIT). The source is in the
+> [Hugging Face repo](https://huggingface.co/EHS-Studio/dssl), and you can read every file in
+> this extension before you install it. It does not make network requests and does not
+> collect anything.
+
 The DSSL style language in your editor. Not a re-implementation: this extension bundles
 the **real parser and resolver** that ship in the engine, so the diagnostics you see are
 the same errors the browser console prints, did-you-mean included.

dssl-vscode/package.json

@@ -2,7 +2,7 @@
   "name": "dssl-vscode",
   "displayName": "DSSL Language Support",
   "description": "The DSSL style language in your editor: syntax highlighting, real-compiler diagnostics (the same errors the browser console shows), completions from the live token registry and for textures, auras and sliders, hover docs, an interactive designer with sliders and live previews for aura, texture and range sliders, and a CSS to DSSL converter. Works in VS Code and VSCodium.",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "publisher": "ehs-studio",
   "icon": "icon.png",
   "license": "MIT",

llms.txt

@@ -70,4 +70,4 @@ Wait for the `dssl-ready` event on `window` before measuring layout: the engine
 
 ## Editor support
 
-The official extension (VS Code and VSCodium, same .vsix) bundles the real parser and resolver: diagnostics identical to the browser console, completions from the workspace token registry, hover docs for the semantic vocabulary. In VSCodium, search "DSSL" in the Extensions tab (it is on Open VSX: https://open-vsx.org/extension/ehs-studio/dssl-vscode). In VS Code, download `dssl-vscode/dssl-vscode-0.9.0.vsix` from the repo files, then Extensions panel -> ... -> Install from VSIX. Source lives in `dssl-vscode/` in the repo.
+The official extension (VS Code and VSCodium, same .vsix) bundles the real parser and resolver: diagnostics identical to the browser console, completions from the workspace token registry, hover docs for the semantic vocabulary. In VSCodium, search "DSSL" in the Extensions tab (it is on Open VSX: https://open-vsx.org/extension/ehs-studio/dssl-vscode). In VS Code, download `dssl-vscode/dssl-vscode-0.9.1.vsix` from the repo files, then Extensions panel -> ... -> Install from VSIX. Source lives in `dssl-vscode/` in the repo.

public/llms.txt

@@ -70,4 +70,4 @@ Wait for the `dssl-ready` event on `window` before measuring layout: the engine
 
 ## Editor support
 
-The official extension (VS Code and VSCodium, same .vsix) bundles the real parser and resolver: diagnostics identical to the browser console, completions from the workspace token registry, hover docs for the semantic vocabulary. In VSCodium, search "DSSL" in the Extensions tab (it is on Open VSX: https://open-vsx.org/extension/ehs-studio/dssl-vscode). In VS Code, download `dssl-vscode/dssl-vscode-0.9.0.vsix` from the repo files, then Extensions panel -> ... -> Install from VSIX. Source lives in `dssl-vscode/` in the repo.
+The official extension (VS Code and VSCodium, same .vsix) bundles the real parser and resolver: diagnostics identical to the browser console, completions from the workspace token registry, hover docs for the semantic vocabulary. In VSCodium, search "DSSL" in the Extensions tab (it is on Open VSX: https://open-vsx.org/extension/ehs-studio/dssl-vscode). In VS Code, download `dssl-vscode/dssl-vscode-0.9.1.vsix` from the repo files, then Extensions panel -> ... -> Install from VSIX. Source lives in `dssl-vscode/` in the repo.

scripts/test-designer-host.mjs

@@ -20,7 +20,8 @@ const EXT = join(ROOT, 'dssl-vscode');
 const pkg = JSON.parse(readFileSync(join(EXT, 'package.json'), 'utf8'));
 
 section('the package manifest');
-ok('the version matches the engine it bundles', pkg.version === VERSION, `${pkg.version} vs ${VERSION}`);
+const mm = (v) => v.split('.').slice(0, 2).join('.');
+ok('the version line (major.minor) matches the engine it bundles; patch may differ for extension-only releases', mm(pkg.version) === mm(VERSION), `${pkg.version} vs ${VERSION}`);
 ok('main points at a file that exists', existsSync(join(EXT, pkg.main)));
 ok('the icon exists', existsSync(join(EXT, pkg.icon)));
 const declared = pkg.contributes.commands.map((c) => c.command);