From d2a4cb4e645979f20c22a5c46c1c767db460f54a Mon Sep 17 00:00:00 2001 From: "Somhairle H. Marisol" Date: Mon, 21 Sep 2026 15:16:23 +0800 Subject: feat(ship): HNX-01 crewed starship design branch (7-step ship.py, --design ship, 409 replays completed run history) --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index bc96f29..1562333 100644 --- a/README.md +++ b/README.md @@ -124,9 +124,11 @@ The real-probe dataset lives alongside the heritage fixture: steps `src/SomhairlesDream.Modeling/Definitions.fs` (`Design.probeSteps`) and rendered by `stage/blender/probe.py` (7 cumulative bpy exports, clay until `probe-07-livery` applies the livery pass). Steps are selected by project id -prefix: any `probe-…` project id resolves to the probe design both in the -server coordinator and in the CLI (`run --design probe` accepts/uses the -probe id defaults), while all other project ids keep the heritage design. +prefix: any `probe-…` project id resolves to the probe design, any +`ship-…` project id resolves to the crewed-starship design (`Design.shipSteps` +rendered by `stage/blender/ship.py`, same 7-step clay→livery contract), and +all other project ids keep the heritage design. The CLI mirrors this with +`run --design probe` and `run --design ship`, each with its own id defaults. The public landing page boots into a pre-published probe run (`probe-001 / run-probe-real-2`): after startup the frontend fetches -- cgit v1.2.3