Rename SolveCraft to SolidCraft everywhere, with compatibility shims (#389)

* WIP deep rename (not for push)

* WIP2

* WIP3

* WIP4 wxs fix

* rustfmt

* Rename the remaining identifiers in merged crash-report code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RjGw4gA5ZvKrU8MQP6sBgT

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

docs/book/src/dev/architecture.md

@@ -5,7 +5,7 @@ SolidCraft is a Cargo workspace in layers. A crate only depends on crates in low
 
 {{#include ../../../../README.md:architecture}}
 
-The web app, `apps/solvecraft-web`, is the desktop front end compiled to wasm with
+The web app, `apps/solidcraft-web`, is the desktop front end compiled to wasm with
 [trunk](https://trunkrs.dev). `xtask` holds the repository's own tooling: `cargo xtask ci`,
 `layers`, `assets`, `features`, `oracle` and `book`.
 

docs/book/src/dev/commands.md

@@ -16,7 +16,7 @@ CommandSpec::new("solid.fillet", "Fillet", fillet)
 
 `run` is `fn(&mut Session, &Value) -> Result<Value>`, and `enabled` is
 `fn(&Session) -> Result<(), String>`; the error string is the disabled-button tooltip. The
-`params` string is the one-line documentation shown by `solvecraft-cli commands`, MCP's
+`params` string is the one-line documentation shown by `solidcraft-cli commands`, MCP's
 `list_commands` and the [command reference](../reference/commands.md).
 
 A command that changes the design is undoable by default: the session snapshots the document

docs/book/src/dev/kernel.md

@@ -9,7 +9,7 @@ SolidCraft types (`Body`, face and edge indices, meshes, measures) and a
 ## `guard`
 
 truck can panic on geometry it doesn't handle. Every call into it goes through
-`solvecraft_kernel::guard`, which catches the panic and turns it into
+`solidcraft_kernel::guard`, which catches the panic and turns it into
 `KernelError::Internal`, leaving the model unchanged:
 
 ```rust

docs/book/src/dev/naming.md

@@ -2,7 +2,7 @@
 
 A fillet stores the edges it rounds, a sketch the face it sits on, a shell the faces it opens.
 If those were face and edge *indices*, an upstream edit that adds a face would move the fillet
-to another edge. SolveCraft stores **names**, and finds them again every time the timeline
+to another edge. SolidCraft stores **names**, and finds them again every time the timeline
 evaluates.
 
 ## Why names follow the kernel's history

docs/book/src/dev/testing.md

@@ -11,8 +11,8 @@ profile and the wasm build check.
 | Sketch fuzz | `crates/engine/src/cmd/sketch_fuzz_tests.rs` | random sketches through the solver and profile finder |
 | UI scenarios | `crates/ui-egui/tests/scenarios/*.json` | the real app, headless: clicks, keys, drags, assertions |
 | Layout tests | `crates/ui-egui/tests/ui_layout.rs`, `window_widths.rs` | panels and dialogs at every window width |
-| Design-file corpus | `apps/solvecraft-cli/tests/corpus` | every saved file version still opens and evaluates the same |
-| Kill mid-save | `apps/solvecraft-cli/tests/kill_mid_save.rs` | a save killed at any moment leaves a readable file |
+| Design-file corpus | `apps/solidcraft-cli/tests/corpus` | every saved file version still opens and evaluates the same |
+| Kill mid-save | `apps/solidcraft-cli/tests/kill_mid_save.rs` | a save killed at any moment leaves a readable file |
 | Reference tests | `cargo xtask oracle` → [docs/oracle.md](oracle.md) | parts rebuilt from `tests/oracle/*/recipe.json`, compared with analytic or FreeCAD expected values |
 
 ## UI scenarios
@@ -54,12 +54,12 @@ On GitHub, one job builds the tests into a
 Pull requests skip a few heavy tests (each takes one to four minutes); they run on every push to
 `main`, nightly, and in `cargo xtask test`:
 
-- `solvecraft-engine`: `tests::hostile_params_never_panic`, everything in `tests::robustness`,
+- `solidcraft-engine`: `tests::hostile_params_never_panic`, everything in `tests::robustness`,
   `pattern_suppress_tests::enclosure_arc_extinction_keeps_a_real_sharp_inner_lip_after_resize_and_reopen`,
   `pattern_suppress_tests::enclosure_datums_follow_wall_height_and_board_depth_with_material_proofs`,
   `cmd::plastic::tests::enclosure_snap_fit_follows_resized_front_wall`
-- `solvecraft-kernel`: `tests::boolean_identity_on_tangent_primitives`
-- `solvecraft-ui-egui` scenarios: `acceptance_sensor_enclosure`
+- `solidcraft-kernel`: `tests::boolean_identity_on_tangent_primitives`
+- `solidcraft-ui-egui` scenarios: `acceptance_sensor_enclosure`
 
 To run exactly what a pull request runs: `cargo nextest run --cargo-profile ci --profile ci`;
 add `--ignore-default-filter` for the full set. A new test that takes over a minute on CI can