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>

examples/README.md

@@ -1,7 +1,7 @@
 # Examples
 
 A curated tour of Ludic, grouped by intent. Every example here is exercised by
-the test suite (`bin/ludic dev test` / `bin/ludic dev selfhost-test`), so nothing in this
+the test suite (`bin/ludic-dev test` / `bin/ludic-dev selfhost-test`), so nothing in this
 directory silently rots.
 
 Run any program straight from the repository root (so `assets/` resolves):

examples/lang/detach.ludic

@@ -11,7 +11,7 @@
 #   25   @OnDetach(Shield): reads the outgoing amount 5, prints 5 + 20
 #   0    the Shield is gone — nothing matches
 #
-#   bin/ludic dev game-build bin/ludicc examples/lang/detach.ludic /tmp/detach
+#   bin/ludic-dev game-build bin/ludicc examples/lang/detach.ludic /tmp/detach
 #   /tmp/detach </dev/null
 program Detach {
   property Tag    { v: int = 0 }

examples/lang/reason.ludic

@@ -9,7 +9,7 @@
 #   503    Enemy A despawned in-world (Despawned): drop its loot, 3 + 500
 #   1009   Enemy B outlived the run; at quit (Quit) it skips loot, 9 + 1000
 #
-#   bin/ludic dev game-build bin/ludicc examples/lang/reason.ludic /tmp/reason
+#   bin/ludic-dev game-build bin/ludicc examples/lang/reason.ludic /tmp/reason
 #   /tmp/reason </dev/null
 program Reasons {
   property Health { hp: int = 0 }

examples/lang/scenes.ludic

@@ -12,7 +12,7 @@
 #     201 900  frame 3: Play.World.Step, then Hud.Draw
 #     202 900  frame 4: Step reaches 2 -> quit(); Hud.Draw paints the last frame
 #
-#   bin/ludic dev game-build bin/ludicc examples/lang/scenes.ludic /tmp/scenes
+#   bin/ludic-dev game-build bin/ludicc examples/lang/scenes.ludic /tmp/scenes
 #   printf 'aaaa' | /tmp/scenes
 program SceneDemo {
   var counter: int = 0

examples/library/coverage.ludic

@@ -1,6 +1,6 @@
-# coverage.ludic — a spec built to be measured by `bin/ludic dev test --coverage` (issue
+# coverage.ludic — a spec built to be measured by `bin/ludic-dev test --coverage` (issue
 # #45). Compiled with `--coverage`, every statement bumps a per-source-line hit
-# counter; at exit the counts are dumped and `bin/ludic dev test --coverage` turns them
+# counter; at exit the counts are dumped and `bin/ludic-dev test --coverage` turns them
 # into a per-file line-coverage report.
 #
 # The tests below exercise `sign` fully but only the taken branches of `grade`,