feat(billing): receipt capture — outstanding workflow, batch by check, reconciliation

Implements docs/RECEIPT_CAPTURE_SPEC.md §1, the legacy "Editor"
replacement, on top of the single-movement capture from plan step 6.
No new abilities: batching and resolving are both capturing.

- outstanding (legacy NOPAGO): capture flag, ?outstanding= filter, and
  POST /billing/:id/resolve-outstanding (gated ledger:create, not
  ledger:void — resolving completes a capture rather than reversing
  one). Outstanding rows are excluded from every balance aggregate,
  matching the legacy SALDOS ULTIMO 0 query's HAVING NOPAGO = 0, but
  still count in the movement browser's filtered totals.
- POST /billing/batch: many customers' receipts against one check, in
  one $transaction. Deliberately not a persisted batch entity —
  checkNumber is already a column and grouping by it answers every
  legacy by-check query.
- GET /billing/by-check + a cheque-count report, replacing REPORTE
  CHEQUE COUNT / REPORTE POR CHEQUE / EDITA CHEQUE ALF|COUNT|NUM. Print,
  PDF, CSV and XLSX come free from the existing /reportes/:slug machinery.
- Web: /estado-cuenta/lote (the Editor screen, with live reconciliation
  against the physical check amount), an "Estado de pago" filter, a
  "sin fondos" row tag and a Resolver dialog, plus a top-level "Captura"
  nav entry.

Integration seam for the OCR auto-capture module (spec §2), which is
required to post through createBatch rather than writing Transaction
rows itself: items[i] maps to lines[i] so postedTransactionId can be
zipped back on; opts.refs[i] stamps captureRef with a duplicate-post
guard that a voided row deliberately does not block; opts.source is
service-level only, so an HTTP client cannot label hand-keyed rows as
machine-captured. captureSource/captureRef are nullable so the 40,136
migrated rows stay NULL rather than being mislabelled.

Fixes two pre-existing bugs found while building this:

- statement() filtered legacySourceTable with `notIn`, which compiles to
  SQL NOT IN — and `NULL NOT IN (...)` is NULL, so every app-captured
  movement was invisible on the customer statement (438 rows in the
  movement browser vs 392 on the statement) while showing everywhere
  else. This would have made the whole capture feature look broken.
- The balances count query omitted the void filter its own page query
  applied, so the total disagreed with the rows.

Nav highlighting now resolves by longest match; the previous
first-startsWith logic lit up both the parent and any nested entry.

Verified end-to-end against the dev DB, API and browser; all test rows
removed afterwards. Also corrects RESUME.md, which documented the dev
ports as :3001/:3000 — they are :4501/:4500, from the env files.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

packages/database/prisma/schema.prisma

@@ -26,6 +26,18 @@ enum TransactionDomain {
   TRUST
 }
 
+/// How a ledger row entered the system. Every capture path funnels through
+/// BillingService (single write path, single audit trail); this records which
+/// one, so an auto-captured receipt is auditable without joining the statement
+/// tables. `OCR` is reserved for the statement auto-capture pipeline
+/// (docs/RECEIPT_CAPTURE_SPEC.md §2), which posts through the same batch path
+/// as hand-keyed check batches.
+enum TransactionCaptureSource {
+  MANUAL
+  BATCH
+  OCR
+}
+
 enum ServiceKind {
   WATER
   ELECTRIC
@@ -443,6 +455,17 @@ model Transaction {
   checkNumber       String?
   message           String? @db.Text
   outstanding       Boolean           @default(false)
+  /// How this row was captured. NULL = migrated from Access (the legacy*
+  /// columns below say which table). Set explicitly on everything the app
+  /// books, so an OCR-posted receipt is distinguishable from a hand-keyed one
+  /// without joining the statement tables.
+  captureSource     TransactionCaptureSource?
+  /// Back-pointer to the artifact that produced this row — a
+  /// `StatementDocument.id` for OCR captures (see RECEIPT_CAPTURE_SPEC §2).
+  /// Unique among live rows via the app's duplicate guard, not a DB constraint,
+  /// because a voided row must not block a corrected re-post of the same
+  /// document.
+  captureRef        String?
   // Append + void: booked rows are never edited or hard-deleted. A non-null
   // voidedAt reverses the movement — it MUST be excluded from every balance
   // and total (SUM/count) so a voided amount stops affecting the books.
@@ -454,6 +477,11 @@ model Transaction {
   createdAt         DateTime          @default(now())
 
   @@index([customerId, transactionDate])
+  // By-check reconciliation (billing.byCheck / the cheque-count report) looks
+  // rows up by check number alone — the legacy EDITA CHEQUE COUNT lookup.
+  @@index([checkNumber])
+  // Drives the duplicate-post guard in BillingService.createBatch.
+  @@index([captureRef])
   @@unique([legacySourceDb, legacySourceTable, legacyId])
   @@map("transactions")
 }