milestone 13 discrepancies: redact credentials from urls in logs, metrics and cli output

src/storage/repositories/clients_repo.zig

@@ -2,8 +2,11 @@
 //!
 //! `listClients` returns only `hand_edited = 1` rows. A client the server
 //! materialised from live traffic is runtime state, not configuration, and must
-//! not appear in an export. `countClients` counts **all** rows, because S5's
-//! "has this database ever been configured" predicate needs the true count.
+//! not appear in an export. `hand_edited` is the only marker of operator intent
+//! in this table, so it also decides what `import.isEmpty` counts: a database
+//! carrying nothing but materialised rows has never been configured, and a seed
+//! file must still be able to fill it. `countClients` counts **all** rows and is
+//! a test helper — it deliberately does not answer that question.
 //!
 //! The import path is list / insert / deleteAll / count, plus the two runtime
 //! calls `upsertSeen` and `pruneStale` that the Phase 7 client tracker owns.
@@ -134,7 +137,8 @@ pub fn deleteAllClients(database: *db.Db) db.Error!void {
     return database.exec("DELETE FROM clients;");
 }
 
-/// Counts every row, including the ones `listClients` filters out.
+/// Counts every row, including the materialised ones `listClients` filters out.
+/// Used by tests; `import.isEmpty` counts operator intent instead.
 pub fn countClients(database: *db.Db) db.Error!i64 {
     return database.queryInt("SELECT count(*) FROM clients");
 }