feat(cli): ship the binary from the published crate (#217)

`cargo install rustmotion` could not work. The README documents it, and the
crate's own description calls it "a CLI tool", but the published crate carried
only a `[lib]`: the `rustmotion` binary was declared in `rustmotion-cli`, which
is `publish = false`. Installing it gave a library and no command.

The binary now lives in `crates/rustmotion` and `rustmotion-cli` is gone.

The studio subcommand could not come along, and not for want of trying: an
optional dependency does not help, because `rustmotion-studio` depends on
`rustmotion`, so cargo rejects the cycle before compiling anything. No capability
is lost — `rustmotion-studio` already declares its own binary of that name, so
the studio is launched directly instead of through a subcommand.

Moving the CLI exposed a second defect, latent while the crate was unpublished
and the same class as the themes bug fixed in #216: `build.rs` walked
`.claude/skills/rustmotion/` and `skills.rs` embedded `CLAUDE.md`, both outside
the package directory. `cargo package` archives only what lives under the crate,
so the tarball did not compile — the verify step failed on a missing SKILL.md.

Both now live inside the crate, with symlinks at their old paths so Claude Code
still finds them. One copy, not two: this repository already learned in #165 what
a duplicated skill list costs when it drifts, and the test that caught that drift
is what still guards it.

The install destination is unchanged. `build.rs` embeds the path the file will be
written to rather than the path it came from, and running the built binary in an
empty directory writes 59 files to `.claude/skills/rustmotion/` as before.

Author: LeadcodeDev

.claude/skills/rustmotion

@@ -0,0 +1 @@
+../../crates/rustmotion/skills

.github/workflows/publish.yaml

@@ -62,6 +62,6 @@ jobs:
       # pouvait donc jamais reussir, et la release 0.6.0 s'est arretee la — apres
       # avoir publie rustmotion-core, definitivement.
       #
-      # studio et cli portent `publish = false` : cargo les saute tout seul.
+      # rustmotion-studio porte `publish = false` : cargo la saute tout seul.
       - name: Publish all crates
         run: cargo publish --workspace --token ${{ secrets.CARGO_REGISTRY_TOKEN }}

CLAUDE.md

@@ -0,0 +1 @@
+crates/rustmotion/CLAUDE.md

CLAUDE.md

@@ -4,12 +4,11 @@ members = [
     "crates/rustmotion-core",
     "crates/rustmotion-components",
     "crates/rustmotion",
-    "crates/rustmotion-cli",
     "crates/rustmotion-studio",
     "crates/rustmotion-html",
 ]
 
-# Les six crates avancent ensemble. La version se change ici, et nulle part
+# Les cinq crates avancent ensemble. La version se change ici, et nulle part
 # ailleurs : elle était auparavant répétée dix fois — une par manifeste, plus une
 # par dépendance interne — et une seule oubliée fait échouer la publication après
 # que les précédentes soient parties, ce qui ne se rattrape pas.

Cargo.lock

@@ -116,7 +116,7 @@ pub struct TextIntrinsic {
 impl TextIntrinsic {
     /// M1: `white-space: nowrap|pre` disables wrapping — the geometry
     /// validator's `unwrappable_text_overflow`/`ContentOverflowsBox` checks
-    /// (crates/rustmotion-cli/src/commands/geometry.rs) already branch on
+    /// (crates/rustmotion/src/cli/commands/geometry.rs) already branch on
     /// exactly this pair of variants and re-measure via this same
     /// `TextIntrinsic`, so the wrap decision here must match theirs exactly
     /// or the validator's assumption about what the renderer produces is
@@ -164,7 +164,7 @@ impl TextIntrinsic {
         // No *real* `LengthContext` (real viewport, real parent width) is
         // reachable here without changing this constructor's signature —
         // its only callers are `box_builder.rs` and
-        // `rustmotion-cli/src/commands/geometry.rs`, both outside this
+        // `rustmotion/src/cli/commands/geometry.rs`, both outside this
         // workstream's scope (box_builder.rs is a sibling's live file this
         // wave; the geometry validator re-measures via this exact type and
         // must keep agreeing with it byte-for-byte, so changing what it

Cargo.toml

@@ -319,7 +319,7 @@ pub struct ChildComponent {
     /// `style` property — `CssStyle` is `deny_unknown_fields` and belongs to
     /// no one this wave. Defaults to `false`: no existing scenario changes
     /// behaviour. Exempts only `viewport_overflow` and `animated_text_overflow`
-    /// (see `crates/rustmotion-cli/src/commands/geometry.rs`); it does NOT
+    /// (see `crates/rustmotion/src/cli/commands/geometry.rs`); it does NOT
     /// exempt `content_overflows_box` — content larger than its own box stays
     /// a reported defect regardless of `bleed`. Applies to this component
     /// only: a bled container does not suppress checks on its children, since

crates/rustmotion-cli/Cargo.toml

@@ -13,10 +13,10 @@ use super::units::{Length, LengthContext, LengthPercentage, ParsedLength};
 // shape either way — a css-local mirror would only duplicate the struct.
 use crate::schema::{deserialize_animation_effects, AnimationEffect, GradientBorder, InnerShadow};
 
-// ─── Legibility floor (relocated from `rustmotion-cli/src/commands/
+// ─── Legibility floor (relocated from `rustmotion/src/cli/commands/
 // geometry.rs`'s `check_legibility`, issue #110/#102 — moved here, not
 // duplicated, so `text-autofit` below can shrink down to the exact same
-// calibrated threshold instead of inventing a second one; `rustmotion-cli`
+// calibrated threshold instead of inventing a second one; `rustmotion`
 // depends on `rustmotion-core`, never the other way around, so the shared
 // value has to live on this side of that boundary) ─────────────────────────
 //
@@ -124,7 +124,7 @@ pub struct CssStyle {
     /// instead of overflowing it. This is what lets an author declare "this
     /// text must fit here" and closes `ContentOverflowsBox` as a possible
     /// validator failure for that node — see `apply_fixes`
-    /// (`rustmotion-cli/src/commands/validate.rs`)'s comment on why it
+    /// (`rustmotion/src/cli/commands/validate.rs`)'s comment on why it
     /// deliberately refuses to auto-fix that violation today: growing the
     /// box, shrinking the font, and shortening the copy are all legitimate
     /// fixes, and picking one was never this tool's call to make silently.
@@ -163,7 +163,7 @@ pub struct CssStyle {
     ///
     /// **The floor.** Never shrinks below [`TEXT_AUTOFIT_MIN_FONT_PX`] — the
     /// same calibrated legibility ratio `check_legibility`
-    /// (`rustmotion-cli/src/commands/geometry.rs`) already enforces, not a
+    /// (`rustmotion/src/cli/commands/geometry.rs`) already enforces, not a
     /// new threshold. If the content still doesn't fit at the floor, the
     /// floor size is used anyway (illegible-but-smallest beats an even
     /// larger overflow) and the geometry validator's `ContentOverflowsBox`