chore: PRs #108 and #109 contain undocumented documents.ts changes not referenced in PR body

[bmersereau]

Problem

Both PR #108 (fix/101+102) and PR #109 (fix/103) include changes to backend/src/routes/documents.ts that remove PII-laden console.log calls from the handleEditResolution handler. These changes are not mentioned in either PR's body and the commits reference Closes #94 — an unrelated issue number.

The documents.ts diff is identical in both branches, which means:

1. The change will apply cleanly on the first merge but be a no-op on the second merge.
2. Reviewers cannot determine from the PR body whether these changes are intentional or accidental carry-over.
3. The audit trail is unclear — it is impossible to tell from the PR which issue this work closes.

Fix required

• Determine the correct issue number for the PII logging removal in handleEditResolution.
• Update the PR body for fix: S3Client singleton and R2 error logging #108 and/or fix: singleton Supabase admin client in requireAuth middleware #109 to explicitly reference that issue with a Closes #N keyword.
• Consider splitting the documents.ts change into its own PR to keep scope clear, or at minimum document it in the PR body.

[bmersereau]

Fixed in PRs #108 and #109. The stray editResolutionLogging.test.ts (copied from the fix/71-remove-pii-logging branch) and the undocumented documents.ts changes have been removed from both branches via git checkout origin/main -- backend/src/routes/documents.ts. Closes when PR #108 or #109 merges.