fix(tools): formatter bracket rules, LSP compiler diagnostics, vocabulary sync

- ludic-fmt: `rows[i]`, `new []int`, `s[a..b]`, `emit(`, `~x`, list-literal
  and query-tag braces stay tight; member calls hug their paren
  (`Date.new(`, `Prefab.spawn(`); `<< >> & | ^ ~` are operators and
  `&& ||` are not — mirrored in ludic_syntax.h, LudicLexer.kt and the
  TextMate grammar. 149 of 274 tracked sources failed --check before.
- ludic-lsp: `initializationOptions.compilerDiagnostics` / `compilerPath`
  are honoured — on save the document's compilation unit is compiled and
  `file:line: error: msg` is published as a "ludicc" diagnostic (the
  option had been documented but never implemented); the workspace scan
  file is per process; bracket codes spelled as char literals
- Overlay added to LUDIC_PHASES, LudicTokens.kt, ludic-mode.el and the
  grammar (the game uses it; check-vocabulary flagged the drift)
- editors: VS Code snippets/package.json/extension.js (`${workspaceFolder}`
  and `~` expansion, PATH lookup, Apache-2.0, real repo URL), Neovim root
  markers, Helix/Zed/Sublime bin/ paths, Emacs vocabulary, JetBrains
  comments; tools/editors/README.md no longer describes C tooling
- .forgejo workflows clone `${{ github.server_url }}/${{ github.repository }}`
  so a fork or mirror tests itself; the docs publish pushes the same way

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

tools/editors/README.md

@@ -1,20 +1,18 @@
 # Ludic in your editor
 
-Everything here is built on one idea: **write the language knowledge once, in C,
-and let every editor talk to it.** There is one lexer, one vocabulary, one
+Everything here is built on one idea: **write the language knowledge once, in
+Ludic, and let every editor talk to it.** There is one vocabulary, one
 formatter and one language server. VS Code and JetBrains get first-class plugins
 because those are the two that were asked for; every other editor gets the same
 capabilities by pointing at the same binary.
 
 ```
-tools/ludic-tools/            the actual language knowledge, in C, no dependencies
-  ludic_syntax.h              lexer + the vocabulary — the source of truth
-  ludic_fmt.h                 comment-preserving formatter
-  ludic_index.h               error-tolerant reader: declarations, bindings, scopes
-  ludic_workspace.h           multi-file model: imports, compilation units, Markdown
-  ludic_json.h                just enough JSON for LSP
-  ludic_fmt_main.c            -> bin/ludic-fmt
-  ludic_lsp.c                 -> bin/ludic-lsp
+tools/ludic-tools/            the actual language knowledge, in Ludic
+  ludic_syntax.h              the vocabulary tables (keywords, operators, builtins)
+                              that the formatter, the server and the vocabulary
+                              check all read — the source of truth
+  fmt.ludic                   -> bin/ludic-fmt   token-based, comment-preserving formatter
+  lsp.ludic                   -> bin/ludic-lsp   the language server (LSP 3.17)
 
 tools/editors/
   shared/                     TextMate grammar + Markdown injection + language config