Move the seed scripts out to the private workspace root

Several of them describe this installation specifically — its broker, its
aircon, its DMX wiring — and this repository is about to be public. The
test and client-generation scripts stay; CI depends on scripts/test.sh.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Makefile

@@ -3,7 +3,7 @@
 # The workspace root delegates to these (see ../Makefile).
 
 .PHONY: dev-utils dev dev-local dev-lan up down update install dev-backend dev-frontend \
-        generate-client seed-example seed-demo sync-example seed-house seed-aircon seed-tinyhouse seed-hosted-demo test test-backend test-frontend soak bench-startup lint lint-backend \
+        generate-client sync-example test test-backend test-frontend soak bench-startup lint lint-backend \
         lint-frontend format-frontend umami build docs docs-serve clean help
 
 COMPOSE_ROOT := $(CURDIR)
@@ -100,49 +100,12 @@ dev-frontend:  ## Start the Vite dev server (local)
 generate-client:  ## Regenerate the frontend SDK from the backend's OpenAPI schema
 	bash scripts/generate-client.sh
 
-seed-example:  ## Seed the querying-chart example (needs a running stack + InfluxDB)
-	cd backend && uv run python ../scripts/seed_example_chart.py
-
-seed-demo:  ## Seed the training-run example: a batch flow and its dashboard
-	cd backend && uv run python ../scripts/seed_demo_training.py
-
 sync-example:  ## Upload `examples/myresearch` the way a data scientist would
 	# The same command the docs give, against whichever engine `fluksio login`
 	# last talked to. The nodes import the package from this checkout, so the
 	# engine has to be one that can see this path.
 	cd backend && uv run fluksio sync ../examples/myresearch
 
-seed-house:  ## Seed the house write-path rig (needs the real broker reachable)
-	cd backend && uv run python ../scripts/seed_house_control.py
-
-seed-aircon:  ## Seed the aircon write-path rig (needs the unit reachable)
-	cd backend && uv run python ../scripts/seed_aircon_control.py
-
-# The house itself. Reads ../house.json for this installation's addresses and
-# DMX wiring; everything it creates is published and stopped. ARGS=--dry checks
-# the whole set without an installation and pushes nothing.
-seed-tinyhouse:  ## Seed the TinyHouse flows (ARGS=--dry to check only)
-	@user=$$(grep -E '^FIRST_SUPERUSER=' $(COMPOSE_ROOT)/.env 2>/dev/null | head -1 | cut -d= -f2-); \
-	pass=$$(grep -E '^FIRST_SUPERUSER_PASSWORD=' $(COMPOSE_ROOT)/.env 2>/dev/null | head -1 | cut -d= -f2-); \
-	cd backend && \
-	  FIRST_SUPERUSER="$${FIRST_SUPERUSER:-$$user}" \
-	  FIRST_SUPERUSER_PASSWORD="$${FIRST_SUPERUSER_PASSWORD:-$$pass}" \
-	  uv run python ../scripts/seed_tinyhouse.py $(ARGS)
-
-# Operators of the hosted demo only — NOT part of any deployment, and nothing a
-# self-hosted instance needs. It wipes and recreates its three flows and its
-# dashboard, so re-running it is how the public demo is reset.
-# `uv run` does not read .env, so the credentials are lifted out of it here;
-# anything already exported wins, which is how a remote instance is targeted:
-#   API_URL=https://api.example.com make seed-hosted-demo
-seed-hosted-demo:  ## Seed the hosted demo panel (operators only; API_URL selects the instance)
-	@user=$$(grep -E '^FIRST_SUPERUSER=' $(COMPOSE_ROOT)/.env 2>/dev/null | head -1 | cut -d= -f2-); \
-	pass=$$(grep -E '^FIRST_SUPERUSER_PASSWORD=' $(COMPOSE_ROOT)/.env 2>/dev/null | head -1 | cut -d= -f2-); \
-	cd backend && \
-	  FIRST_SUPERUSER="$${FIRST_SUPERUSER:-$$user}" \
-	  FIRST_SUPERUSER_PASSWORD="$${FIRST_SUPERUSER_PASSWORD:-$$pass}" \
-	  uv run python ../scripts/seed_demo.py
-
 # ── Testing ───────────────────────────────────────────────────────
 
 test: test-backend test-frontend  ## Run all tests (backend + frontend)