v1.0.0:3 — post-cutover seed strip

Removes the one-time `/data` snapshot from the deployed Docker image now
that the cutover from the legacy `workout-log` package is verified done
(v1.0.0:1 + :2 in production).

Dockerfile
- Drops `COPY start9/0.4/seed/data /app/seed/data`.
- Drops the `WORKOUT_BAKED_SEED_DB_PATH` env var.
- Comment block explains the rationale + how to re-seed if ever needed.

docker_entrypoint.sh
- Step 1 collapses to single-branch fallback: if /data is empty AND
  /app/prisma/data/app.db exists, copy the empty-schema fallback. The
  baked-seed branch is gone.
- Comment cross-references v1.0.0:3 for the rationale.

start9/0.4/seed/README.md rewritten to reflect historical-only status
+ how to re-seed for the rare "spin up another instance with this
history" case.

Version graph
- Adds startos/versions/v1.0.0.3.ts with empty up/down migrations and
  release notes.
- Promotes v1.0.0:3 to `current`; v1.0.0:1 and :2 move to `other` so
  hosts on either upgrade in place.

No schema changes, no data migration. /data on existing installs is
left exactly as-is. Image size drops by ~1.7MB (the snapshot size).

start9/0.4/startos/versions/index.ts

@@ -1,21 +1,23 @@
 import { VersionGraph } from '@start9labs/start-sdk'
 import { v_1_0_0_1 } from './v1.0.0.1'
 import { v_1_0_0_2 } from './v1.0.0.2'
+import { v_1_0_0_3 } from './v1.0.0.3'
 
 /**
  * Version graph for the `proof-of-work` package.
  *
  * v1.0.0:1 — initial release, seeded cutover from the legacy
  *            `workout-log` package.
- * v1.0.0:2 — CSP fix (reverts the over-strict nonce-based CSP that
+ * v1.0.0:2 — CSP fix (reverted the over-strict nonce-based CSP that
  *            broke first paint in v1.0.0:1).
+ * v1.0.0:3 — post-cutover seed strip (baked /data snapshot removed
+ *            from the image now that the cutover is verified done).
  *
  * StartOS picks `current` as the install target; `other` lists every
- * node that can upgrade into `current`. Hosts on v1.0.0:1 upgrade to
- * v1.0.0:2 via the no-op up migration; fresh installs land directly
- * on v1.0.0:2.
+ * node that can upgrade into `current`. Hosts on v1.0.0:1 or :2
+ * upgrade to :3 via no-op up migrations; fresh installs land on :3.
  */
 export const versionGraph = VersionGraph.of({
-  current: v_1_0_0_2,
-  other: [v_1_0_0_1],
+  current: v_1_0_0_3,
+  other: [v_1_0_0_1, v_1_0_0_2],
 })