Widen scratch iteration 011 with fixture-backed integrations QA

docs/INSTALL_GUIDE.md

@@ -40,6 +40,7 @@ The fastest way to get running. The setup scripts validate prerequisites, config
 ```powershell
 .\scripts\setup.ps1              # full setup
 .\scripts\setup.ps1 -InfraOnly   # infrastructure only (PostgreSQL, Valkey, RustFS, Rekor, Zot)
+.\scripts\setup.ps1 -QaIntegrationFixtures # full setup plus Harbor/GitHub App QA fixtures
 ```
 
 **Linux / macOS:**
@@ -47,6 +48,7 @@ The fastest way to get running. The setup scripts validate prerequisites, config
 ```bash
 ./scripts/setup.sh               # full setup
 ./scripts/setup.sh --infra-only  # infrastructure only
+./scripts/setup.sh --qa-integration-fixtures # full setup plus Harbor/GitHub App QA fixtures
 ```
 
 The scripts will:
@@ -57,6 +59,7 @@ The scripts will:
 5. Create or reuse the external frontdoor Docker network from `.env` (`FRONTDOOR_NETWORK`, default `stellaops_frontdoor`)
 6. Stop repo-local host-run Stella services that would lock build outputs, then build repo-owned .NET solutions and publish backend services locally into small Docker contexts before building hardened runtime images (vendored or generated trees such as `node_modules`, `dist`, `coverage`, and `output` are excluded)
 7. Launch the full platform with health checks, perform one bounded restart pass for services that stay unhealthy after first boot, wait for the first-user frontdoor bootstrap path (`/welcome`, `/envsettings.json`, OIDC discovery, `/connect/authorize`), then complete an authenticated convergence gate that proves topology inventory, notifications administration overrides, and promotion bootstrap flows load cleanly before reporting success
+8. If `-QaIntegrationFixtures` / `--qa-integration-fixtures` is enabled, start deterministic Harbor and GitHub App fixtures and verify them so the local Integrations Hub can be exercised with successful UI onboarding
 
 Open **https://stella-ops.local** when setup completes.
 
@@ -85,6 +88,8 @@ Stella Ops services bind to unique loopback IPs so all can use port 443 without
 
 Runtime URL convention remains `*.stella-ops.local`; `hosts.stellaops.local` is the template file name only.
 
+The same template also carries the optional `harbor-fixture.stella-ops.local` and `github-app-fixture.stella-ops.local` aliases used by the fixture-backed integrations QA lane.
+
 - **Windows:** `C:\Windows\System32\drivers\etc\hosts` (run editor as Administrator)
 - **Linux / macOS:** `sudo sh -c 'cat devops/compose/hosts.stellaops.local >> /etc/hosts'`