feat: add make dummy-run for fixture-driven dev

Same as `make run` but forces OTELA_FIXTURE_PATH at the synthesised
upgraded fixture, so the model card UI shows the v0.0.6-shape payload
(hostname, version, labels, multi-node demo) without depending on live
prod state or whatever's in the developer's .env.

Use `make run` to hit live prod, `make dummy-run` to iterate on the UI.

Author: robmsmt

Makefile

@@ -1,4 +1,4 @@
-.PHONY: install install-dev format check test run db-up db-down migrate _ensure-env _ensure-frontend-env
+.PHONY: install install-dev format check test run dummy-run db-up db-down migrate _ensure-env _ensure-frontend-env
 
 UV_EXTRA ?=
 
@@ -80,3 +80,12 @@ run: _ensure-env _ensure-frontend-env db-up migrate
 	uvicorn backend.main:app --reload --host 0.0.0.0 --port 8080 & \
 	cd frontend && npm run dev & \
 	wait
+
+# Same as `run` but forces the model list to come from the synthesised
+# upgraded fixture instead of the live OpenTela endpoint. Useful for
+# iterating on the model-card UI without depending on prod state.
+dummy-run: _ensure-env _ensure-frontend-env db-up migrate
+	OTELA_FIXTURE_PATH=$(PWD)/backend/tests/fixtures/dnt_table_upgraded.json \
+	uvicorn backend.main:app --reload --host 0.0.0.0 --port 8080 & \
+	cd frontend && npm run dev & \
+	wait