fix(selfhost): avoid postgres url argv leaks

[JSONbored]

Motivation

• Prevent accidental disclosure of Postgres credentials by removing expanded Postgres URLs from psql and process argv, since command-line arguments can be read by other local users on typical systems.

Description

• Route Postgres calls in the Grafana reporting exporter through libpq environment variable PGDATABASE instead of passing the full URL as a psql positional argument in scripts/export-grafana-reporting-db.sh.
• Prefer environment-based usage by changing the self-host documentation example to DATABASE_URL=… and removing the expanded --postgres-url "$DATABASE_URL" command-line example in apps/gittensory-ui/src/routes/docs.self-hosting-backup-scaling.tsx.
• Update the migrator usage text in scripts/migrate-selfhost-sqlite-to-postgres.ts to recommend DATABASE_URL and warn against using --postgres-url on shared hosts.
• Add a regression assertion to the fake psql helper in test/unit/selfhost-grafana-reporting.test.ts that fails if a Postgres URL appears in psql argv or if the URL is not supplied via PGDATABASE.

Testing

• Ran the unit suite for the modified exporter tests with npx vitest run test/unit/selfhost-grafana-reporting.test.ts, which passed (all tests green).
• Ran UI lint with npm run ui:lint, which completed successfully with existing warnings only (no errors).
• Ran type checking with npm run typecheck, which completed successfully.
• Ran git diff --check and local formatting commands, which reported no blocking issues; npm run test:ci and npm audit --audit-level=moderate could not complete due to external network/setup constraints and therefore were not fully exercised.

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	6511de4	Commit Preview URL Branch Preview URL	Jul 02 2026, 06:23 AM

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-02 06:25:36 UTC}

4 files · no blockers · readiness 68/100 · CI pending · blocked

⏸️ Suggested Action - Manual Review

• The AI review could not be completed for this change, so the gate is held for a human reviewer rather than passed automatically. It re-evaluates on the next update.

Review summary
AI review is already running for this PR head in another Gittensory pass. Gittensory is holding this PR for manual review until that pass completes.

Nits — 2 non-blocking

• AI review already in progress for this PR head — The gate is held for a human reviewer rather than passed automatically; it re-evaluates once the in-flight review completes or on the next update.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Signal	Result	Evidence
Code review	✅ No blockers	No AI review summary
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	⚠️ 2 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (size label size:S; no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 65 registered-repo PR(s), 55 merged, 548 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 65 PR(s), 548 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 65 PR(s), 548 issue(s).
• Related work: Titles/paths share 7 meaningful terms. (PR #2459)
• Related work: Titles/paths share 6 meaningful terms. (PR #2470, PR #2473)

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Review top overlaps.
• Add a concise scope and risk note.
• Triage stale or unlinked PRs.
• No action.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.
• Check active issues and PRs before submitting.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.83%. Comparing base (9e657e1) to head (6511de4).
⚠️ Report is 81 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2461   +/-   ##
=======================================
  Coverage   95.83%   95.83%           
=======================================
  Files         224      224           
  Lines       24996    24996           
  Branches     9091     9091           
=======================================
  Hits        23954    23954           
  Misses        428      428           
  Partials      614      614           

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.