ci(replatform): load the app as a component (fix ingest 404 → parity never passed)

The Replatform Parity workflow has never succeeded — every run fails at "Ingest
corpus" with `Ingest begin failed: 404 Not found`, so nothing past unit tests
(integration, e2e, parity, search-eval, chat-grounding) has ever actually run.

Root cause: the workflow started Harper with `harper start`, which boots a bare
installed instance with none of the app's custom resources. The ingest client
POSTs to /Ingest (an exported Resource), which only exists when app/ is loaded as
a COMPONENT. Confirmed locally: /Ingest returns 401/500 under `harper dev/run .`
but 404 under `harper start`.

Fix: run the app as a component — `harper run .` from app/, backgrounded (env,
including the API keys, is inherited). Also wait on / then fail fast with the app
log if /Ingest still 404s, so a component-load regression is obvious instead of
silently cascading into the ingest step.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Eijma5uKcPZi9tqV2aJBeh

Author: nizzlenitz

.github/workflows/replatform-parity.yaml

@@ -74,10 +74,24 @@ jobs:
           harper install --TC_AGREEMENT=yes --HDB_ADMIN_USERNAME="$HDB_ADMIN_USERNAME" \
             --HDB_ADMIN_PASSWORD="$HDB_ADMIN_PASSWORD" --ROOTPATH="$ROOTPATH" \
             --HTTP_PORT=9936 --OPERATIONSAPI_NETWORK_PORT=9935
-          (cd app && ROOTPATH="$ROOTPATH" harper start)
-          for i in $(seq 1 30); do
+          # Run the app as a COMPONENT — `harper run .` loads app/ (its custom
+          # resources: /Ingest, /api/*, /admin/*), whereas `harper start` boots a
+          # bare instance with none of them (so ingest 404'd). Backgrounded so the
+          # later steps run against it; env (incl. the API keys) is inherited.
+          (cd app && ROOTPATH="$ROOTPATH" nohup harper run . > "$ROOTPATH/harper-run.log" 2>&1 &)
+          for i in $(seq 1 45); do
             curl -sf -o /dev/null "http://127.0.0.1:9936/" && break || sleep 2
           done
+          curl -s -o /dev/null -w "Harper up: HTTP %{http_code} on /\n" "http://127.0.0.1:9936/" || true
+          # Fail fast (with the app log) if the component didn't register its routes:
+          # a 404 on /Ingest means the app didn't load; any other code means it did.
+          ingest_code=$(curl -s -o /dev/null -w '%{http_code}' "http://127.0.0.1:9936/Ingest")
+          echo "/Ingest probe: HTTP $ingest_code"
+          if [ "$ingest_code" = "404" ]; then
+            echo "::error::/Ingest 404 — app component did not load its routes"
+            tail -80 "$ROOTPATH/harper-run.log" || true
+            exit 1
+          fi
 
       - name: Ingest corpus
         env: