refactor(cli)!: split the contributor tool out of the ludic CLI

`ludic help` ended with a section titled "contributing to the toolchain itself",
listing bootstrap, reseed, docs-gen and release tasks. None of that is available
to someone who installed the language — those tasks need the repository — so the
shipped tool was advertising work its user cannot do, in a namespace they have to
read past to find `new` and `run`.

The tasks move to a second program, dev.ludic -> bin/ludic-dev, built from a
checkout and excluded from every release artifact. `ludic` keeps the project and
package commands and nothing else; `ludic dev …` now explains where the tasks
went instead of failing as an unknown command.

What this shook out: the two programs share prelude/build/project/pkg, so the
helpers each had accreted in whichever file first needed them — cc(),
ensure_ludicc, the string functions, title_case, cmd_version — moved to where
both can see them. The argument-shift indirection added for the `dev` namespace
is gone with the namespace, so commands read argv directly again.

`ludic-dev test` asserts the split rather than trusting it: the staged install
must build a project, and `ludic dev build` there must fail while naming
ludic-dev. install.sh keeps building older tags, whose bootstrap goes through
main.ludic.

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

tools/editors/README.md

@@ -31,11 +31,11 @@ it needs no path configuration.
 From a checkout, build them with:
 
 ```bash
-bin/ludic dev tools
+bin/ludic-dev tools
 ```
 
 Produces `bin/ludic-fmt` and `bin/ludic-lsp`. Add `--install` to symlink both
-into `~/.local/bin`, `--test` to run `bin/ludic dev test-tools` afterwards.
+into `~/.local/bin`, `--test` to run `bin/ludic-dev test-tools` afterwards.
 
 ## What you get, in any editor
 
@@ -118,7 +118,7 @@ ln -sf ../../tools/git-hooks/pre-commit .git/hooks/pre-commit
 
 The hook runs `ludic-fmt --check` over the staged `.ludic` and `.md` files only,
 and does nothing at all when `bin/ludic-fmt` has not been built — so it never
-blocks a commit on a machine that has not run `bin/ludic dev tools`.
+blocks a commit on a machine that has not run `bin/ludic-dev tools`.
 
 ## Why the formatter is not `ludicc --fmt`
 
@@ -140,7 +140,7 @@ both spellings are what the language documents and uses:
   (`const R_DIR:   int = 0    # 0 up`) survive a save;
 - `id=Root` inside a `ui` block and `{Enemy}` inside a query stay tight.
 
-`bin/ludic dev test-tools` checks the property that matters: formatting every file in
+`bin/ludic-dev test-tools` checks the property that matters: formatting every file in
 the tree and re-running the *compiler's* canonical dump produces byte-identical
 output. The formatter cannot change what a program means.
 
@@ -149,8 +149,8 @@ output. The formatter cannot change what a program means.
 The vocabulary is written down in five places that cannot include each other —
 the compiler's two tables, `ludic_syntax.h`, the TextMate grammar (JSON), and the
 JetBrains lexer (Kotlin). Adding a builtin and forgetting the rest is silent
-failure, so `bin/ludic dev check-vocabulary` (written in Ludic) compares all five, and
-`bin/ludic dev test-tools` runs it.
+failure, so `bin/ludic-dev check-vocabulary` (written in Ludic) compares all five, and
+`bin/ludic-dev test-tools` runs it.
 
 When you add a keyword or builtin: put it in `ludic_syntax.h`, then run
-`bin/ludic dev test-tools` and let it tell you which copies still need it.
+`bin/ludic-dev test-tools` and let it tell you which copies still need it.

tools/editors/jetbrains/README.md

@@ -43,7 +43,7 @@ The first build downloads an IntelliJ IDEA Community distribution (over 1 GB),
 so expect it to take a while; later builds take seconds. Once the cache is warm,
 
 ```bash
-LUDIC_TEST_JETBRAINS=1 bin/ludic dev test-tools
+LUDIC_TEST_JETBRAINS=1 bin/ludic-dev test-tools
 ```
 
 includes the plugin build in the toolchain's own test run.
@@ -55,4 +55,4 @@ LSP4IJ is a required dependency; the IDE offers to install it for you.
 
 **Settings -> Languages & Frameworks -> Ludic** — the path to `ludic-lsp` and to
 `ludicc`. Both default to `bin/` under the project root, which is where
-`bin/ludic dev tools` puts them.
+`bin/ludic-dev tools` puts them.

tools/editors/jetbrains/src/main/kotlin/io/ludic/ide/LudicServer.kt

@@ -17,7 +17,7 @@ import java.io.File
 
 /**
  * Where to find the toolchain. Both paths may be left blank, in which case the
- * plugin looks under the project root for what `bin/ludic dev tools` produces —
+ * plugin looks under the project root for what `bin/ludic-dev tools` produces —
  * which is the case for anyone working in the Ludic repository itself.
  */
 @Service(Service.Level.PROJECT)
@@ -121,7 +121,7 @@ class LudicConnectionProvider(private val project: Project) : ProcessStreamConne
             append("  on PATH, and in ~/.ludic/bin.\n")
         }
         append("\nInstall the toolchain (curl -fsSL https://workshopsoft.pages.workshopsoft.io/ludic/install.sh | sh), ")
-        append("build it with `bin/ludic dev tools` from a checkout, ")
+        append("build it with `bin/ludic-dev tools` from a checkout, ")
         append("or set the path in Settings | Languages & Frameworks | Ludic. ")
         append("Syntax highlighting works without it; completion and diagnostics do not.")
     }

tools/editors/jetbrains/src/main/resources/META-INF/plugin.xml

@@ -67,7 +67,7 @@
             name="Ludic"
             factoryClass="io.ludic.ide.LudicLanguageServerFactory">
             <description><![CDATA[
-            The Ludic language server. Built by <code>bin/ludic dev tools</code>.
+            The Ludic language server. Built by <code>bin/ludic-dev tools</code>.
             ]]></description>
         </server>
         <languageMapping language="Ludic" serverId="ludic"/>

tools/editors/vscode/README.md

@@ -23,7 +23,7 @@ for the language reference.
 Build the toolchain once, from the repository root:
 
 ```bash
-bin/ludic dev tools
+bin/ludic-dev tools
 ```
 
 That produces `bin/ludic-lsp` and `bin/ludic-fmt`, which the extension finds

tools/editors/vscode/src/extension.js

@@ -98,7 +98,7 @@ async function start(context) {
     // Not an error worth a modal: the grammar still highlights, and plenty of
     // people open a .ludic file without having built the toolchain.
     output.appendLine(
-      'ludic-lsp not found. Install the toolchain (curl -fsSL https://ludic.dev/install.sh | sh), build it from a checkout with `bin/ludic dev tools`, or set "ludic.server.path". ' +
+      'ludic-lsp not found. Install the toolchain (curl -fsSL https://ludic.dev/install.sh | sh), build it from a checkout with `bin/ludic-dev tools`, or set "ludic.server.path". ' +
       'Syntax highlighting works without it; completion and diagnostics do not.'
     );
     return;