fix: replace hardcoded POSTGRES_PASSWORD with runtime-generated random password

[Copilot]

GitGuardian flagged a hardcoded POSTGRES_PASSWORD=postgres in the drift manifest generation script. While this only affects a disposable local scratch Docker container, the hardcoded credential triggers secret scanning alerts and sets a bad precedent.

Changes

• scripts/generate-drift-manifest.ts: Import randomBytes from node:crypto and generate a 32-char hex password at runtime instead of using the hardcoded "postgres" literal

+import { randomBytes } from "node:crypto";
 ...
+const scratchPassword = randomBytes(16).toString("hex");
-docker(["run", "-d", "--name", CONTAINER, "-e", "POSTGRES_PASSWORD=postgres", ...]);
+docker(["run", "-d", "--name", CONTAINER, "-e", `POSTGRES_PASSWORD=${scratchPassword}`, ...]);

The password is only needed for container initialisation — subsequent psql calls use docker exec (peer/trust auth inside the container) and are unaffected.

Verification

• npm run verify:cheap
• npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed
• npm run verify:release before release or handoff confidence claims
• npm run format:check
• npm run eval:retrieval:quality (must stay 36/36) when retrieval, ranking, selection, chunking, or scoring behavior changed — CI cannot run it (needs live keys), so run it locally and paste the summary. A metadata/governance-weighting change once buried correct docs (recall 1.0→0.76) and only this eval caught it.
• npm run eval:rag -- --limit 15 + npm run eval:quality -- --rag-only when answer generation, the synthesis prompt, or answer post-processing changed (grounded-supported must not drop; citation-failure 0)
• npm run check:production-readiness when clinical workflow, privacy, environment, Supabase, source governance, or deployment behavior changed
• npm run check:deployment-readiness when deployment startup, hosting, or rollout behavior changed

Clinical Governance Preflight

Complete this section when the change touches ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output.

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes

• No new dependencies — node:crypto is a Node.js built-in.
• CodeQL and secret scanning both pass clean after this change.

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[BigSimmo]

foos