fix(harden): secure profiler telemetry logging

[google-labs-jules]

Generated by: .github/nightly-prompts/01-hardening.md

Reasoning:

[Threat Statement]: If standard info-level telemetry trace messages inside the headhunter-scanner profiler are logged to stderr using console.error, then system telemetry is polluted with false-positive alerts.
[Blast Radius]: headhunter-scanner Edge Function (stages/profiler.ts).
[Rationale]: Standardizes trace/info log routing to stdout instead of stderr, ensuring clean logs on modern cloud streams while preserving true operational errors on console.error.

Changes:

• [Backend/supabase/functions/headhunter-scanner/stages/profiler.ts]: Refactored post-ingestion fate-check tracing statements to use console.log, strictly reserving console.error for actual database and runtime errors.
• [.github/nightly-logs/01-hardening-coverage.log]: Appended log entries for the July 24, 2026 daily audit.
• [.github/nightly-logs/00-pr-history.md]: Executed pre-flight aging pass and prepended T1 block for the audit run.

Verification:

• [Automated]: Full monorepo Vitest suite (1409 passed) completed with 100% success.
• [Automated/Audit]: Verified that the threat identified in the Threat Statement is completely closed.

Log Updates:

• Updated .github/nightly-logs/01-hardening-coverage.log
• Updated .github/nightly-logs/00-pr-history.md

---

PR created automatically by Jules for task 11325649833798030791 started by @AlbiDR

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[supabase]

This pull request has been ignored for the connected project hucktamloykszinwbtuh because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.