editor 0.5.0 — spec/ktav 0.5.0 sync, highlighting parity, icon, build-only release pipeline

Sync vscode/lsp/intellij to spec 0.5.0 and ktav 0.5.0.

Highlighting parity (VS Code + IntelliJ):
- inline bracket matching, whole-string selection, `##` line comments
- IntelliJ native lexer rewrite (## comments, inline tokenization, COMMA);
  fresh lexer per getHighlightingLexer() call (a shared mutable lexer made
  colours flicker)
- bare array-item line is one scalar to EOL — `a, b` is one string (commas
  separate items only inline) and `hello{world` / IPs like `127.0.0.1` keep
  one string highlight; key-vs-item decided by `:` only
- a line beginning with `{`/`[` is an inline-compound array item, tokenised
  structurally (was mis-read as `key: value`)
- numbers require a well-formed form (≤1 dot / ≤1 exponent) so `127.0.0.1`
  and versions are strings, not floats
- distinct value-type palette across all IDEs: strings #1FB0FF, numbers
  #2563EB, booleans #C26A12, null #B11A1A, keys #333333. LSP gains a dedicated
  `null` semantic-token type (was lumped with booleans as keyword); IntelliJ
  ships matching Default/Darcula colour schemes; VS Code grammar splits
  boolean/null scopes
- plugin icon

Dual-license MIT OR Apache-2.0 across the repo (LICENSE-MIT + LICENSE-APACHE,
README en/ru/zh, CONTRIBUTING en/ru/zh, manifest SPDX).

LSP test suite brought to spec 0.5.0: drop typed-scalar / inline-forbidden
fixtures, re-pin error wording, point the conformance corpus at
spec/versions/0.5. cargo fmt applied.

release.yml: a tag push BUILDS ONLY (cross-platform artifacts → GH Release,
no registry publish). Registry publishes (crates.io / VS Code Marketplace /
Open VSX / JetBrains) run ONLY on a manual workflow_dispatch with publish=true,
so the same tag can be re-run unchanged once tokens are configured. Each
publish is gated on its token and marked continue-on-error.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: PHPCraftdream

.github/workflows/release.yml

@@ -6,9 +6,22 @@ name: Release
 # notes from CHANGELOG.md). Each subproject's publish step is gated
 # on its own verify step.
 #
-# Required secrets (set per subproject's environment):
+# Build vs. publish: the build/package steps always run and produce
+# universal artifacts — a fat VSIX bundling all 6 platform LSP binaries
+# and a single IntelliJ plugin zip that loads on every JetBrains IDE on
+# every OS. Publishing is OFF for tag pushes — a `git push origin v*`
+# only builds artifacts and attaches them to the GH Release. Registry
+# publishes run ONLY on a manual `workflow_dispatch` with `publish: true`
+# (re-run the same tag once tokens are configured, version unchanged).
+# Even then each publish is BEST-EFFORT: skipped when its token is unset
+# and marked `continue-on-error`, so a missing token, an Open VSX read-
+# only window, or a pending JetBrains first-upload moderation never
+# blocks the run or the artifact upload.
+#
+# Optional secrets (set per subproject's environment). Absent → that
+# registry publish is skipped, artifacts still ship to the GH Release:
 #   • crates-io  → CARGO_REGISTRY_TOKEN
-#   • npm-vscode → VSCE_PAT, OVSX_PAT
+#   • npm-vscode → VSCE_PAT (VS Code Marketplace), OVSX_PAT (Open VSX)
 #   • intellij   → INTELLIJ_PUBLISH_TOKEN
 
 on:
@@ -18,8 +31,12 @@ on:
   workflow_dispatch:
     inputs:
       tag:
-        description: "Tag to publish (e.g. v0.1.0). Must already exist."
+        description: "Tag to build/publish (e.g. v0.1.0). Must already exist."
         required: true
+      publish:
+        description: "Publish to registries (crates.io / Marketplace / Open VSX / JetBrains). Tag pushes NEVER publish — they only build artifacts."
+        type: boolean
+        default: true
 
 permissions:
   contents: read
@@ -75,6 +92,10 @@ jobs:
     needs: [verify-versions, lsp-binaries]
     runs-on: ubuntu-latest
     environment: crates-io
+    env:
+      # Job-level so the publish step's `if:` can detect whether the token
+      # is configured (secrets are only visible to `if:` via the env context).
+      CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
     defaults:
       run:
         working-directory: lsp
@@ -90,8 +111,12 @@ jobs:
       - run: cargo clippy --release --all-targets -- -D warnings
       - run: cargo test --release
       - name: cargo publish
-        env:
-          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
+        # Publishes only on a manual dispatch with publish=true; tag pushes
+        # build only. Best-effort: skip without a token, and don't fail the
+        # run if this version was already published. fmt/clippy/test above
+        # still gate the build, so a genuinely broken crate blocks the run.
+        if: ${{ github.event_name == 'workflow_dispatch' && inputs.publish && env.CARGO_REGISTRY_TOKEN != '' }}
+        continue-on-error: true
         run: cargo publish
 
   # ------------------------------------------------------------------
@@ -183,6 +208,11 @@ jobs:
     needs: [verify-versions, lsp-binaries]
     runs-on: ubuntu-latest
     environment: npm-vscode
+    env:
+      # Job-level so each publish step's `if:` can detect whether the token
+      # is configured (secrets reach `if:` only through the env context).
+      VSCE_PAT: ${{ secrets.VSCE_PAT }}
+      OVSX_PAT: ${{ secrets.OVSX_PAT }}
     defaults:
       run:
         working-directory: vscode
@@ -202,14 +232,25 @@ jobs:
       - name: Organize binaries
         shell: bash
         run: |
-          mkdir -p ../vscode/bin/{linux-x64,linux-arm64,darwin-x64,darwin-arm64,win32-x64,win32-arm64}
-          [ -d "binaries/ktav-lsp-linux-amd64" ] && cp binaries/ktav-lsp-linux-amd64/ktav-lsp ../vscode/bin/linux-x64/
-          [ -d "binaries/ktav-lsp-linux-arm64" ] && cp binaries/ktav-lsp-linux-arm64/ktav-lsp ../vscode/bin/linux-arm64/
-          [ -d "binaries/ktav-lsp-darwin-amd64" ] && cp binaries/ktav-lsp-darwin-amd64/ktav-lsp ../vscode/bin/darwin-x64/
-          [ -d "binaries/ktav-lsp-darwin-arm64" ] && cp binaries/ktav-lsp-darwin-arm64/ktav-lsp ../vscode/bin/darwin-arm64/
-          [ -d "binaries/ktav-lsp-windows-amd64.exe" ] && cp binaries/ktav-lsp-windows-amd64.exe/ktav-lsp.exe ../vscode/bin/win32-x64/
-          [ -d "binaries/ktav-lsp-windows-arm64.exe" ] && cp binaries/ktav-lsp-windows-arm64.exe/ktav-lsp.exe ../vscode/bin/win32-arm64/
-          ls -lhR ../vscode/bin/
+          # `download-artifact` placed the artifacts at $GITHUB_WORKSPACE/binaries
+          # (workspace-root relative — NOT relative to this step's vscode
+          # working-directory). Each artifact dir holds ONE file named after the
+          # asset (lsp-binaries stages it as `$asset`, not `ktav-lsp`). Copy each
+          # into the platform dir the extension probes, renamed to `ktav-lsp[.exe]`.
+          # Absolute $GITHUB_WORKSPACE paths avoid any cwd ambiguity; no `[ -d ]`
+          # guards so a missing binary fails the release loudly instead of
+          # silently shipping a partial (Windows-only) VSIX.
+          B="$GITHUB_WORKSPACE/binaries"
+          D="$GITHUB_WORKSPACE/vscode/bin"
+          mkdir -p "$D"/{linux-x64,linux-arm64,darwin-x64,darwin-arm64,win32-x64,win32-arm64}
+          cp "$B/ktav-lsp-linux-amd64/ktav-lsp-linux-amd64"           "$D/linux-x64/ktav-lsp"
+          cp "$B/ktav-lsp-linux-arm64/ktav-lsp-linux-arm64"           "$D/linux-arm64/ktav-lsp"
+          cp "$B/ktav-lsp-darwin-amd64/ktav-lsp-darwin-amd64"         "$D/darwin-x64/ktav-lsp"
+          cp "$B/ktav-lsp-darwin-arm64/ktav-lsp-darwin-arm64"         "$D/darwin-arm64/ktav-lsp"
+          cp "$B/ktav-lsp-windows-amd64.exe/ktav-lsp-windows-amd64.exe" "$D/win32-x64/ktav-lsp.exe"
+          cp "$B/ktav-lsp-windows-arm64.exe/ktav-lsp-windows-arm64.exe" "$D/win32-arm64/ktav-lsp.exe"
+          chmod +x "$D/linux-x64/ktav-lsp" "$D/linux-arm64/ktav-lsp" "$D/darwin-x64/ktav-lsp" "$D/darwin-arm64/ktav-lsp"
+          ls -lhR "$D"
 
       - uses: actions/setup-node@v6
         with:
@@ -227,13 +268,25 @@ jobs:
       - name: Package .vsix
         run: npx vsce package --no-dependencies
       - name: Publish to VS Code Marketplace
-        env:
-          VSCE_PAT: ${{ secrets.VSCE_PAT }}
+        # Publishes only on a manual dispatch with publish=true; tag pushes
+        # build only. The Marketplace PAT requires an Azure DevOps org (behind
+        # an Azure subscription wall) — when VSCE_PAT is unset the step skips
+        # and the fat VSIX still ships as a GH Release artifact for manual
+        # upload. continue-on-error keeps a failed publish from blocking the run.
+        if: ${{ github.event_name == 'workflow_dispatch' && inputs.publish && env.VSCE_PAT != '' }}
+        continue-on-error: true
         run: npx vsce publish --no-dependencies --pat "$VSCE_PAT"
       - name: Publish to Open VSX
-        env:
-          OVSX_PAT: ${{ secrets.OVSX_PAT }}
+        # Publishes only on a manual dispatch with publish=true; tag pushes
+        # build only. Skipped when OVSX_PAT is unset. continue-on-error so an
+        # Open VSX read-only maintenance window, or a namespace not yet
+        # created, doesn't fail the run — re-run later with
+        # `ovsx publish ktav-<ver>.vsix --pat <token>` (no rebuild needed).
+        if: ${{ github.event_name == 'workflow_dispatch' && inputs.publish && env.OVSX_PAT != '' }}
+        continue-on-error: true
         run: npx ovsx publish --pat "$OVSX_PAT" *.vsix
+      # The universal VSIX always ships, regardless of whether either publish
+      # ran — this is the artifact for manual Marketplace / Open VSX upload.
       - uses: actions/upload-artifact@v5
         with:
           name: vscode-vsix
@@ -248,6 +301,10 @@ jobs:
     needs: [verify-versions, lsp-binaries]
     runs-on: ubuntu-latest
     environment: intellij
+    env:
+      # Job-level so the publish step's `if:` can detect whether the token
+      # is configured (secrets reach `if:` only through the env context).
+      INTELLIJ_PUBLISH_TOKEN: ${{ secrets.INTELLIJ_PUBLISH_TOKEN }}
     defaults:
       run:
         working-directory: intellij
@@ -267,14 +324,21 @@ jobs:
       - name: Organize binaries
         shell: bash
         run: |
-          mkdir -p ../intellij/bin/{linux-x64,linux-arm64,darwin-x64,darwin-arm64,win32-x64,win32-arm64}
-          [ -d "binaries/ktav-lsp-linux-amd64" ] && cp binaries/ktav-lsp-linux-amd64/ktav-lsp ../intellij/bin/linux-x64/
-          [ -d "binaries/ktav-lsp-linux-arm64" ] && cp binaries/ktav-lsp-linux-arm64/ktav-lsp ../intellij/bin/linux-arm64/
-          [ -d "binaries/ktav-lsp-darwin-amd64" ] && cp binaries/ktav-lsp-darwin-amd64/ktav-lsp ../intellij/bin/darwin-x64/
-          [ -d "binaries/ktav-lsp-darwin-arm64" ] && cp binaries/ktav-lsp-darwin-arm64/ktav-lsp ../intellij/bin/darwin-arm64/
-          [ -d "binaries/ktav-lsp-windows-amd64.exe" ] && cp binaries/ktav-lsp-windows-amd64.exe/ktav-lsp.exe ../intellij/bin/win32-x64/
-          [ -d "binaries/ktav-lsp-windows-arm64.exe" ] && cp binaries/ktav-lsp-windows-arm64.exe/ktav-lsp.exe ../intellij/bin/win32-arm64/
-          ls -lhR ../intellij/bin/
+          # Same as vscode-publish: artifacts live at $GITHUB_WORKSPACE/binaries
+          # (workspace-root relative), each dir holding one file named after the
+          # asset. Copy into the per-platform dir as `ktav-lsp[.exe]`. Absolute
+          # paths avoid cwd ambiguity; fail loudly on any missing binary.
+          B="$GITHUB_WORKSPACE/binaries"
+          D="$GITHUB_WORKSPACE/intellij/bin"
+          mkdir -p "$D"/{linux-x64,linux-arm64,darwin-x64,darwin-arm64,win32-x64,win32-arm64}
+          cp "$B/ktav-lsp-linux-amd64/ktav-lsp-linux-amd64"           "$D/linux-x64/ktav-lsp"
+          cp "$B/ktav-lsp-linux-arm64/ktav-lsp-linux-arm64"           "$D/linux-arm64/ktav-lsp"
+          cp "$B/ktav-lsp-darwin-amd64/ktav-lsp-darwin-amd64"         "$D/darwin-x64/ktav-lsp"
+          cp "$B/ktav-lsp-darwin-arm64/ktav-lsp-darwin-arm64"         "$D/darwin-arm64/ktav-lsp"
+          cp "$B/ktav-lsp-windows-amd64.exe/ktav-lsp-windows-amd64.exe" "$D/win32-x64/ktav-lsp.exe"
+          cp "$B/ktav-lsp-windows-arm64.exe/ktav-lsp-windows-arm64.exe" "$D/win32-arm64/ktav-lsp.exe"
+          chmod +x "$D/linux-x64/ktav-lsp" "$D/linux-arm64/ktav-lsp" "$D/darwin-x64/ktav-lsp" "$D/darwin-arm64/ktav-lsp"
+          ls -lhR "$D"
 
       - uses: actions/setup-java@v5
         with:
@@ -283,9 +347,18 @@ jobs:
       - uses: gradle/actions/setup-gradle@v4
       - run: ./gradlew test verifyPlugin buildPlugin --no-daemon
       - name: Publish to JetBrains Marketplace
-        env:
-          INTELLIJ_PUBLISH_TOKEN: ${{ secrets.INTELLIJ_PUBLISH_TOKEN }}
+        # Publishes only on a manual dispatch with publish=true; tag pushes
+        # build only. The FIRST version must be uploaded manually via
+        # https://plugins.jetbrains.com/plugin/add and pass moderation before
+        # token publishing works. Skipped when the token is unset, and
+        # continue-on-error so a rejected/blocked publishPlugin doesn't fail
+        # the run — the universal plugin zip ships as a GH Release artifact
+        # for that manual first upload.
+        if: ${{ github.event_name == 'workflow_dispatch' && inputs.publish && env.INTELLIJ_PUBLISH_TOKEN != '' }}
+        continue-on-error: true
         run: ./gradlew publishPlugin --no-daemon
+      # The universal plugin zip (loads on all JetBrains IDEs / all OSes,
+      # bundling every platform LSP binary) always ships.
       - uses: actions/upload-artifact@v5
         with:
           name: intellij-zip

CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# Contributing to ktav-lang/editor
+
+**Languages:** **English** · [Русский](CONTRIBUTING.ru.md) · [简体中文](CONTRIBUTING.zh.md)
+
+## Core rules
+
+### 1. Every bug fix ships with a regression test
+
+When you find a bug, **before fixing it**, write a test that reproduces
+it — the test **must fail on `main`** and pass after the fix. Include
+both in the same PR.
+
+### 2. Don't reinvent the format in the editor layer
+
+Editor extensions and the LSP are thin consumers of the `ktav` parser
+crate. Format behaviour belongs in the Rust crate
+([`ktav-lang/rust`](https://github.com/ktav-lang/rust)) — changing it
+there updates every consumer at once. Only **editor-specific
+ergonomics** (TextMate scopes, LSP feature wiring, IDE-specific
+integrations) belong in this repo.
+
+If your change requires a format change, start a discussion in
+[`ktav-lang/spec`](https://github.com/ktav-lang/spec) first.
+
+### 3. One concept per commit
+
+Commits should be atomic: a bug fix and its test together, a feature
+and its tests together, a rename on its own, a refactor on its own.
+`git log --oneline` should read like a changelog. Don't prefix commit
+messages with `feat:` / `fix:` — no conventional commits here.
+
+## Dev setup
+
+Each subproject has its own toolchain. See the README in each:
+
+- `grammars/` — pure JSON; no build
+- `vscode/` — Node + `vsce`
+- `intellij/` — JDK 17 + Gradle
+- `lsp/` — Rust 1.70+
+
+## Language policy
+
+This repo participates in the org-wide three-language policy (EN / RU /
+ZH). Every prose file lives in three parallel versions — see
+[`ktav-lang/.github/AGENTS.md`](https://github.com/ktav-lang/.github/blob/main/AGENTS.md)
+for the naming convention and the "update all three in one commit"
+rule.
+
+### License of contributions
+
+Unless you explicitly state otherwise, any contribution intentionally
+submitted for inclusion in this project by you, as defined in the
+Apache-2.0 license, shall be dual-licensed as **MIT OR Apache-2.0**,
+without any additional terms or conditions.

CONTRIBUTING.ru.md

@@ -0,0 +1,52 @@
+# Вклад в ktav-lang/editor
+
+**Языки:** [English](CONTRIBUTING.md) · **Русский** · [简体中文](CONTRIBUTING.zh.md)
+
+## Основные правила
+
+### 1. Каждый багфикс сопровождается регрессионным тестом
+
+Когда вы нашли баг, **до исправления** напишите тест, который его
+воспроизводит — он **должен падать на `main`** и проходить после
+фикса. Оба — в одном PR.
+
+### 2. Не изобретайте формат на уровне редактора
+
+Расширения редакторов и LSP — тонкие потребители крейта-парсера `ktav`.
+Поведение формата принадлежит Rust-крейту
+([`ktav-lang/rust`](https://github.com/ktav-lang/rust)) — правки там
+обновляют всех потребителей одновременно. В этот репозиторий идёт только
+**эргономика, специфичная для редакторов** (TextMate-скоупы, обвязка
+LSP-фич, интеграции с конкретными IDE).
+
+Если ваше изменение требует правки формата — начните с обсуждения в
+[`ktav-lang/spec`](https://github.com/ktav-lang/spec).
+
+### 3. Один концепт — один коммит
+
+Коммиты атомарны: фикс вместе с тестом, фича вместе с тестами,
+переименование — отдельно, рефакторинг — отдельно. `git log --oneline`
+должен читаться как changelog. Без `feat:` / `fix:` префиксов.
+
+## Dev-окружение
+
+Каждый подпроект — свой toolchain. См. README в каждом:
+
+- `grammars/` — чистый JSON; без build'а
+- `vscode/` — Node + `vsce`
+- `intellij/` — JDK 17 + Gradle
+- `lsp/` — Rust 1.70+
+
+## Языковая политика
+
+Репо участвует в трёхъязычной политике организации (EN / RU / ZH).
+Каждый prose-файл живёт в трёх параллельных версиях — см.
+[`ktav-lang/.github/AGENTS.md`](https://github.com/ktav-lang/.github/blob/main/AGENTS.md)
+про naming convention и правило "обновлять все три в одном коммите".
+
+### Лицензия вкладов
+
+Если вы явно не заявите иное, любой вклад, намеренно отправленный
+для включения в этот проект, в соответствии с определением лицензии
+Apache-2.0, будет лицензирован на условиях **MIT OR Apache-2.0** без
+каких-либо дополнительных условий или ограничений.

CONTRIBUTING.zh.md

@@ -0,0 +1,48 @@
+# 为 ktav-lang/editor 做贡献
+
+**语言:** [English](CONTRIBUTING.md) · [Русский](CONTRIBUTING.ru.md) · **简体中文**
+
+## 核心规则
+
+### 1. 每个 bug 修复都伴随一个回归测试
+
+发现 bug 时,**在修复之前** 先写一个复现它的测试 —— 测试在
+`main` 分支上 **必须失败**,修复之后才通过。两者放在同一个 PR。
+
+### 2. 不要在编辑器层重新发明格式
+
+编辑器扩展和 LSP 是 `ktav` 解析器 crate 的薄消费者。格式行为属于
+Rust crate
+([`ktav-lang/rust`](https://github.com/ktav-lang/rust)) —— 改那里
+等于同步更新所有消费者。这里仅收 **编辑器特定的人体工学**
+(TextMate scope、LSP 功能接线、IDE 特定集成)。
+
+如果改动需要格式变更,先去
+[`ktav-lang/spec`](https://github.com/ktav-lang/spec) 讨论。
+
+### 3. 一个概念一次提交
+
+提交要保持原子:bug 修复与其测试一起、新功能与其测试一起、
+重命名单独、重构单独。`git log --oneline` 应当读起来像 changelog。
+不要使用 `feat:` / `fix:` 前缀。
+
+## 开发环境
+
+每个子项目都有自己的工具链。详见各子项目下的 `README.md`:
+
+- `grammars/` —— 纯 JSON,无需构建
+- `vscode/` —— Node + `vsce`
+- `intellij/` —— JDK 17 + Gradle
+- `lsp/` —— Rust 1.70+
+
+## 语言政策
+
+本仓库参与组织级三语政策(EN / RU / ZH)。每份 prose 文档都有三种
+并行版本 —— 命名约定和"三份一并更新"规则见
+[`ktav-lang/.github/AGENTS.md`](https://github.com/ktav-lang/.github/blob/main/AGENTS.md)。
+
+### 贡献的许可
+
+除非您另有明确声明,否则您有意提交以纳入本项目的任何贡献(按
+Apache-2.0 许可证中的定义),均按 **MIT OR Apache-2.0** 双重许可,
+不附加任何额外条款或条件。