Stop printing the database password

The report opened with the connection string it was about to work on, taken
straight from AIDND_DATABASE_URL. On the hosted deploy that string carries the
Neon password, so the first line of every run put a live credential into the
console — and from there into scrollback, a screenshot, or a pasted bug report.
Nothing in the output said it was there to notice.

It now prints scheme, user, host and database name. The query string goes whole:
sslmode is the only part worth reading, and some drivers accept a password
there as well.

631 green.

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

plan/18-persona-and-memory-quality.md

@@ -4,7 +4,7 @@ Two changes, in order. Phase 1 gives the adventure a persona. Phase 2 uses it,
 along with the cast, to fix the memories. Phase 1 is worth shipping on its own;
 Phase 2 depends on it and is much smaller once it lands.
 
-**Both phases are built and green (629 backend tests). Phase 1 was driven in a
+**Both phases are built and green (631 backend tests). Phase 1 was driven in a
 browser (21/21 checks). Phase 2 was run end to end against a real model, as a
 controlled A/B on one story — see "Run with a real model". A bank written under
 the old prompt can be rewritten in place — see the last section.**

plan/STATUS.md

@@ -81,7 +81,7 @@ needed; nothing requires reading a row of anyone's story.
 **`plan/18-persona-and-memory-quality.md` is the writeup. Both changes are on `main`**
 — the note here that said they were sitting unmerged on
 `claude/ai-dnd-memories-summarization-3muo98` is out of date; `main` is at `71b24b6`,
-the tip of that work. Both green at 629 tests, plus the backfill below.
+the tip of that work. Both green at 631 tests, plus the backfill below.
 
 **The protagonist now has a name.** An adventure carries `persona_name`,
 `persona_pronouns` and `persona_desc` (migrations 74-76), and the player's stat block