Squadsight HQ

Drone-as-a-service operations platform for BVLOS aerial security.

---

Post-merge validation failures are log-only

Post-merge checks are safety gates. When one fails, the Replit workflow exits non-zero and writes the exact failed step to the workflow log. It never sends email, opens an SMTP connection, invokes a webhook, or calls a notification script — even if email-related environment variables are configured.

Run the regression guard locally with:

bash scripts/test-post-merge-no-mail.sh

The guard forces a named API coverage-gate failure with email variables present, then verifies the result is non-zero, log-only, and free of email-delivery signals. It is registered as a validation workflow to prevent a later change from restoring post-merge email delivery.

Operational alert policy: SMS-only

Operational security and safety notifications must go to the responsible on-shift people by SMS text message. They are separate from post-merge validation output; do not add a normal-inbox email fallback while investigating a failed merge or an operational alarm.

---

Development

# Install dependencies
pnpm install

# Start API server (hot-reload)
pnpm --filter @workspace/api-server run dev

# Start frontend (hot-reload)
pnpm --filter @workspace/squadsight run dev

# Run API server tests
pnpm --filter @workspace/api-server test

# Run fresh-DB smoke test
bash scripts/smoke-test.sh

# Run migration lint (ALTER TABLE guard)
bash scripts/migration-lint.sh

Validation

The project workflow runs type checks, fresh-database checks, migration lint, and the focused post-merge guards. A failed validation is visible in its Replit workflow log and blocks its gate; it does not create an email notification.