Rename displayed product to SolidCraft and add header bug reporting

docs/book/src/dev/architecture.md

@@ -1,6 +1,6 @@
 # Architecture
 
-SolveCraft is a Cargo workspace in layers. A crate only depends on crates in lower layers, and
+SolidCraft is a Cargo workspace in layers. A crate only depends on crates in lower layers, and
 `cargo xtask layers` fails the build otherwise.
 
 {{#include ../../../../README.md:architecture}}
@@ -11,7 +11,7 @@ The web app, `apps/solvecraft-web`, is the desktop front end compiled to wasm wi
 
 A few rules follow from the layering:
 
-- **Only `crates/kernel` touches truck.** Everything above it sees SolveCraft's own types:
+- **Only `crates/kernel` touches truck.** Everything above it sees SolidCraft's own types:
   bodies, faces, edges, meshes and measures. See [The kernel boundary](kernel.md).
 - **The document knows nothing about commands or the UI.** `crates/doc` holds the parameters,
   the feature timeline and the component tree, and evaluates them into a model.

docs/book/src/dev/kernel.md

@@ -1,9 +1,9 @@
 # The kernel boundary and truck
 
-`crates/kernel` is SolveCraft's B-rep kernel. It wraps
+`crates/kernel` is SolidCraft's B-rep kernel. It wraps
 [truck](https://github.com/ricosjp/truck) (Apache-2.0) for topology, NURBS geometry, booleans,
 tessellation and STEP parsing, and it is the only crate allowed to use truck. Callers get
-SolveCraft types (`Body`, face and edge indices, meshes, measures) and a
+SolidCraft types (`Body`, face and edge indices, meshes, measures) and a
 `KernelError` instead of truck types and panics.
 
 ## `guard`
@@ -20,7 +20,7 @@ A failing feature shows an error on the timeline; it never takes the app down.
 
 ## What is our own
 
-truck has no fillets, chamfers, shells or face edits, so these are SolveCraft code in the
+truck has no fillets, chamfers, shells or face edits, so these are SolidCraft code in the
 kernel: constant, chord and variable-radius fillets with corner blends, chamfers, shell and
 offset, Delete Face, Split Face, Replace Face, sewing, STEP and IGES reading and writing beyond
 truck's parser, and face provenance (which input face each output face came from, for

docs/book/src/dev/naming.md

@@ -2,7 +2,7 @@
 
 A fillet stores the edges it rounds, and a sketch stores the face it sits on. If those were face
 and edge *indices*, an upstream edit that adds a face would move the fillet to the wrong edge.
-SolveCraft stores **names** instead (`crates/doc/src/naming.rs`):
+SolidCraft stores **names** instead (`crates/doc/src/naming.rs`):
 
 - A face of an evaluated body is named after how it was made. A face lying on a face of the
   feature's input keeps that face's name; a face new to the feature is named by its role: