dssl-vscode 0.7.1 registry-ready: lowercase publisher, icon, PUBLISHING.md, vsix in repo files; editor chapter updated

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 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): grab `dssl-vscode/dssl-vscode-0.7.1.vsix` from the repo source, or build it with `npx @vscode/vsce package` inside `dssl-vscode/`, then Extensions panel -> ... -> Install from VSIX.
+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): download `dssl-vscode/dssl-vscode-0.7.1.vsix` from the repo files, then Extensions panel -> ... -> Install from VSIX. An Open VSX listing (so it appears in VSCodium's Extensions tab, searchable) is staged and publishes with one Open VSX token; see `dssl-vscode/PUBLISHING.md`.
 
 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/PUBLISHING.md

@@ -0,0 +1,61 @@
+# Publishing DSSL Language Support
+
+The extension is a normal, registry-ready package: publisher `ehs-studio`, id
+`ehs-studio.dssl-vscode`, repository field, icon, LICENSE, README all set. What
+follows is exactly what it takes to put it in each registry.
+
+## Open VSX (this is the one for VSCodium)
+
+VSCodium's Extensions tab searches **open-vsx.org** by default. Once published
+there, "DSSL" shows up in the tab, searchable, one-click install, updates included.
+
+One-time, on your side (about 2 minutes):
+
+1. Go to https://open-vsx.org and sign in with your GitHub account.
+2. Top right: your avatar → **Settings** → **Access Tokens** → **Generate token**.
+3. Give it any name, copy the value, and paste it in chat. It gets stored the
+   same way as the HF and Vercel tokens (chmod 600, outside every tracked file,
+   mirrored into `.git/backups/`).
+
+Then it is one command on my side:
+
+```sh
+bash scripts/publish-openvsx.sh
+```
+
+The script reads the token, creates the `ehs-studio` namespace (tolerates "already
+exists"), and publishes the newest `.vsix`. After that:
+
+- VSCodium: Extensions tab → search "DSSL" → Install.
+- Future updates: bump `version` in `dssl-vscode/package.json`, repackage with
+  `npx @vscode/vsce package --no-dependencies`, rerun the script.
+
+## Microsoft Marketplace (for VS Code proper, optional, more hoops)
+
+VS Code proper searches the Microsoft Marketplace. Same package, different
+gatekeeper: it requires an Azure DevOps organization and a personal access token.
+
+1. Create an organization at https://dev.azure.com (free).
+2. Go to https://marketplace.visualstudio.com/manage and create a publisher.
+   Suggested ID: `ehs-studio`.
+3. In Azure DevOps: User settings → **Personal access tokens** → New token with
+   scope **Marketplace → Manage**.
+4. Hand over the token like the others, then it is:
+
+```sh
+cd dssl-vscode && npx @vscode/vsce publish --pat <token>
+```
+
+This can happen at any time; Open VSX first does not block it.
+
+## Local install (works today, no accounts, no waiting)
+
+- VSCodium / VS Code: Extensions panel → **⋯** → *Install from VSIX* → pick the
+  `.vsix`. Dragging the `.vsix` onto the Extensions panel works too.
+- The latest build always lives in `download/` and in the HF repo tree.
+
+## Before every publish
+
+- `node scripts/sync-extension-engine.mjs` after ANY engine change, so the
+  bundled compiler matches the browser compiler.
+- Run the extension lib tests (36 assertions) before packaging.

dssl-vscode/README.md

@@ -7,6 +7,11 @@ the same errors the browser console prints, did-you-mean included.
 Works in **VS Code** and **VSCodium** (same extension API; install the `.vsix` in either
 via Extensions panel → ⋯ → *Install from VSIX*).
 
+Extension id: **`ehs-studio.dssl-vscode`**. An Open VSX listing (the registry VSCodium's
+Extensions tab searches) is staged: one Open VSX token from the user and
+`scripts/publish-openvsx.sh` puts it in the tab, searchable. See PUBLISHING.md for both
+that flow and the Microsoft Marketplace flow.
+
 ## Features
 
 - **Real-compiler diagnostics.** Errors AND warnings (the v0.7 warnings channel included:

dssl-vscode/package.json

@@ -3,7 +3,8 @@
   "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, hover docs. Works in VS Code and VSCodium.",
   "version": "0.7.1",
-  "publisher": "EHS-Studio",
+  "publisher": "ehs-studio",
+  "icon": "icon.png",
   "license": "MIT",
   "engines": {
     "vscode": "^1.82.0"

scripts/make-extension-icon.py

@@ -0,0 +1,37 @@
+#!/usr/bin/env python3
+"""Generates the DSSL extension marketplace icon (128x128 PNG).
+
+Design ties into the site's classic re-skin: ink background, parchment
+section-mark glyph (the site's logo mark is a literal section sign), brass accent.
+"""
+from PIL import Image, ImageDraw, ImageFont
+
+SIZE = 128
+INK = (24, 19, 16, 255)          # candlelit walnut, the site's dark bg
+PARCHMENT = (245, 240, 228, 255)  # site parchment
+BRASS = (201, 164, 92, 255)       # brass accent
+
+img = Image.new("RGBA", (SIZE, SIZE), (0, 0, 0, 0))
+d = ImageDraw.Draw(img)
+d.rounded_rectangle([2, 2, SIZE - 2, SIZE - 2], radius=24, fill=INK)
+
+font_path = "/usr/share/fonts/truetype/dejavu/DejaVuSerif-Bold.ttf"
+try:
+    font = ImageFont.truetype(font_path, 78)
+except OSError:
+    font = ImageFont.truetype("/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf", 78)
+
+glyph = "\u00a7"  # section sign, the site's logo mark
+bbox = d.textbbox((0, 0), glyph, font=font)
+w = bbox[2] - bbox[0]
+h = bbox[3] - bbox[1]
+x = (SIZE - w) / 2 - bbox[0]
+y = (SIZE - h) / 2 - bbox[1] - 6
+d.text((x, y), glyph, font=font, fill=PARCHMENT)
+
+# brass baseline accent under the glyph
+d.rounded_rectangle([36, SIZE - 26, SIZE - 36, SIZE - 20], radius=3, fill=BRASS)
+
+out = "/home/z/my-project/dssl-vscode/icon.png"
+img.save(out, "PNG")
+print("wrote", out, img.size)

scripts/publish-openvsx.sh

@@ -0,0 +1,51 @@
+#!/usr/bin/env bash
+# Publishes the DSSL extension to Open VSX (the registry VSCodium searches).
+#
+# Token resolution order: $1 | $OPENVSX_TOKEN | /home/z/.openvsx_token
+# The token is never echoed and never lands in a tracked file.
+set -uo pipefail
+
+DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)/dssl-vscode"
+
+TOKEN="${OPENVSX_TOKEN:-}"
+if [ -z "$TOKEN" ] && [ -f /home/z/.openvsx_token ]; then
+  TOKEN="$(tr -d '[:space:]' < /home/z/.openvsx_token)"
+fi
+if [ $# -ge 1 ] && [ -n "$1" ]; then
+  TOKEN="$(printf '%s' "$1" | tr -d '[:space:]')"
+fi
+if [ -z "$TOKEN" ]; then
+  echo "error: no Open VSX token (pass as arg 1, set OPENVSX_TOKEN, or write /home/z/.openvsx_token)" >&2
+  exit 1
+fi
+if [ ${#TOKEN} -lt 16 ]; then
+  echo "error: token looks too short to be real" >&2
+  exit 1
+fi
+
+VSIX="$(ls -t "$DIR"/dssl-vscode-*.vsix 2>/dev/null | head -1)"
+if [ -z "$VSIX" ]; then
+  echo "error: no .vsix found in $DIR (run: cd dssl-vscode && npx @vscode/vsce package --no-dependencies)" >&2
+  exit 1
+fi
+
+echo "publishing $(basename "$VSIX") to Open VSX (namespace ehs-studio)..."
+cd "$DIR"
+
+# create-namespace fails if it already exists; that is fine, keep going
+npx --yes ovsx create-namespace ehs-studio --pat "$TOKEN" \
+  || echo "(namespace create reported an error, continuing: it probably already exists)"
+
+npx --yes ovsx publish "$(basename "$VSIX")" --pat "$TOKEN"
+rc=$?
+
+if [ $rc -eq 0 ]; then
+  name="$(python3 -c "import json;print(json.load(open('package.json'))['name'])")"
+  ver="$(python3 -c "import json;print(json.load(open('package.json'))['version'])")"
+  echo ""
+  echo "LIVE: https://open-vsx.org/extension/ehs-studio/$name/$ver"
+  echo "VSCodium: Extensions tab -> search DSSL -> Install"
+fi
+
+unset TOKEN
+exit $rc