docs: nightly production health-check 2026-06-16 (0 fixes, prod healthy)

[njrini99-code]

Summary

Nightly production health-check for 2026-06-16. No actionable production bugs found — opening this PR per the routine's <2 actionable issues → still ship PR with brief rule so the run is visible.

• Production main (b310847…) is READY and serving normally.
• Only 4 error-level runtime logs in the 24h window — all from a single user at 14:02:19 UTC with a stale Supabase refresh-token cookie. The app handles it correctly (307 redirect to /golf/login) and Sentry already ignores AuthApiError via src/instrumentation.ts.
• 1 cron warning (/api/cron/coachhelm-roster-sweep, single occurrence, route returned 200) — designed degradation per the route's own logServerError(…, 'warning').
• 3 FAILED preview deploys are all on PR feat: integration roundup — CoachHelm + stats + demo + a11y + nightly fixes + safe deps #304's branch, all the same parallel-route conflict (golf/(auth)/demo/page.tsx vs golf/demo/route.ts). The duplicate file does NOT exist on main — resolution belongs on PR feat: integration roundup — CoachHelm + stats + demo + a11y + nightly fixes + safe deps #304's branch, not here.

Full diagnosis, deployment table, and routine-limitations notes are in the brief: docs/daily-briefs/2026-06-16.md (the only file in this PR).

Fixes applied

None. Triage details for every observed pattern are in the brief, including the explicit reasoning for the two patterns that were classified non-actionable (stale-refresh-token noise = expected behavior + already Sentry-filtered; 1 cron warning = single-occurrence transient that the route already handles by design).

Routine limitations encountered (action requested)

The brief Step-1 promised query results from admin_events, error_logs, and pg_stat_statements, but the Supabase MCP failed to authenticate because mcp.supabase.com is not in this environment's network egress allowlist. To get full DB-side coverage on tomorrow's run, please add the host to the routine environment's egress allowlist and re-authenticate the Supabase MCP. The Sentry MCP also needs first-use OAuth, which an unattended routine can't complete.

Test plan

• Verify docs/daily-briefs/2026-06-16.md is the only changed file
• Confirm production deployment status (dpl_CWeGKBJ97QwkJnzh9i4oTFddMJZx should still be the active production target)
• If the Supabase MCP egress is allowlisted, re-run a manual triage of error_logs / admin_events for 2026-06-15 → 2026-06-16 to confirm nothing was hidden from this run
• Do not auto-merge — human review only (per nightly hard constraint)

🤖 Generated by Claude Code nightly health-check routine

---

Generated by Claude Code

Greptile Summary

This PR adds a single documentation file (docs/daily-briefs/2026-06-16.md) as part of the automated nightly health-check routine. No production code, migrations, or configuration is changed.

• The brief documents a healthy production state: 4 error-level logs (all stale Supabase refresh-token, correctly handled + already Sentry-filtered), 1 cron warning (designed degradation, single occurrence), and 3 failed preview builds on PR feat: integration roundup — CoachHelm + stats + demo + a11y + nightly fixes + safe deps #304's branch — none of which are actionable on main.
• Section 5 of the brief surfaces a secondary observation: src/proxy.ts appears to be dead code (no imports found in src/**). The brief correctly classifies this as out-of-nightly-scope cleanup, but it may warrant a dedicated housekeeping PR.

Confidence Score: 5/5

Documentation-only change with no code, migrations, or configuration touched — safe to merge after human review.

A single markdown file is added under docs/daily-briefs/. It contains no executable code, no schema changes, and no configuration. The triage reasoning in the brief is sound: the stale-refresh-token pattern is correctly classified as expected behavior already handled by both the app and Sentry, and the three preview failures are correctly scoped to PR #304's branch. The only follow-up surfaced by the brief (dead code in src/proxy.ts) is pre-existing and out-of-scope for this PR.

No files require special attention. src/proxy.ts is flagged in the brief as potentially dead code and may warrant a separate cleanup PR.

Important Files Changed

Filename	Overview
docs/daily-briefs/2026-06-16.md	New nightly health-check brief; documentation-only, no code changes. Well-structured triage with clear reasoning for all non-actionable items.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Nightly Routine Starts] --> B[Fetch Vercel runtime logs & deployment status]
    B --> C{Supabase MCP authenticated?}
    C -- No --> D[Skip DB-side queries admin_events / error_logs / pg_stat_statements]
    C -- Yes --> E[Query DB health tables]
    D --> F[Triage runtime error patterns]
    E --> F
    F --> G{Pattern 1: AuthApiError 4 occurrences}
    G --> H[Single user, stale cookie, 307 redirect to login, Sentry already filters - NOT actionable]
    F --> I{Pattern 2: Cron sweep warning 1 occurrence}
    I --> J[Designed degradation, Route returned 200, Single occurrence - NOT actionable]
    F --> K{Preview deploy failures x3?}
    K --> L[All on PR 304 branch, Parallel-route conflict, Not present on main - NOT actionable here]
    H --> M{Total actionable issues?}
    J --> M
    L --> M
    M -- 0 issues < 2 threshold --> N[Ship PR with brief only per routine clause]
    N --> O[docs/daily-briefs/2026-06-16.md committed to main]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Nightly Routine Starts] --> B[Fetch Vercel runtime logs & deployment status]
    B --> C{Supabase MCP authenticated?}
    C -- No --> D[Skip DB-side queries admin_events / error_logs / pg_stat_statements]
    C -- Yes --> E[Query DB health tables]
    D --> F[Triage runtime error patterns]
    E --> F
    F --> G{Pattern 1: AuthApiError 4 occurrences}
    G --> H[Single user, stale cookie, 307 redirect to login, Sentry already filters - NOT actionable]
    F --> I{Pattern 2: Cron sweep warning 1 occurrence}
    I --> J[Designed degradation, Route returned 200, Single occurrence - NOT actionable]
    F --> K{Preview deploy failures x3?}
    K --> L[All on PR 304 branch, Parallel-route conflict, Not present on main - NOT actionable here]
    H --> M{Total actionable issues?}
    J --> M
    L --> M
    M -- 0 issues < 2 threshold --> N[Ship PR with brief only per routine clause]
    N --> O[docs/daily-briefs/2026-06-16.md committed to main]

Loading

_{Reviews (1): Last reviewed commit: "docs(nightly): 2026-06-16 production hea..." | Re-trigger Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
helmv3	Ready	Preview, Comment	Jun 16, 2026 4:15am

[coderabbitai]

Walkthrough

Adds docs/daily-briefs/2026-06-16.md, a 103-line nightly report documenting production health, Invalid Refresh Token auth log noise, a single roster-sweep cron warning, Supabase MCP observability gaps, and three PR #304-scoped preview deployment failures caused by a parallel-route compile conflict.

Changes

Daily Review Brief

Layer / File(s)	Summary
2026-06-16 nightly brief docs/daily-briefs/2026-06-16.md	Full brief added: production health status, error/warning log counts, cron warning, deployment outcomes (no prod failures, 3 preview failures on PR #304), unaddressed items, and next-run steps (Supabase MCP allowlist, Sentry OAuth).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

• Ignore

❌ Failed checks (2 errors)

Check name	Status	Explanation	Resolution
Auth Check In Server Actions	❌ Error	11 exported async functions in server actions lack explicit supabase.auth.getUser() calls before database operations: src/app/actions/demo-request.ts:43, src/app/baseball/actions/auth.ts:158, src/a...	Add supabase.auth.getUser() call at start of each function before any .from()/.rpc() call, e.g.: const {data:{user}, error} = await supabase.auth.getUser(); if (!user) return {error:'Unauthorized'};.
Sport-Prefixed Table Names	❌ Error	.coderabbit/semgrep/test/positive-bare-table.ts:17-19 contains unprefixed Supabase table queries: supabase.from('coaches'), supabase.from('players'), supabase.from('teams').	Either exclude test fixtures from this check, or replace unprefixed table names with prefixed versions (golf_coaches, baseball_players, etc.) in the test fixture file.

✅ Passed checks (10 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
No Service-Role In Client Bundles	✅ Passed	PR is documentation-only (adds docs/daily-briefs/2026-06-16.md). No code files modified, no SUPABASE_SERVICE_ROLE_KEY or service-role references anywhere. Check not applicable; passes by scope.
Rls Coverage On New Tables	✅ Passed	PR contains only documentation file (docs/daily-briefs/2026-06-16.md); no migrations or CREATE TABLE statements present. Check inapplicable.
No Destructive Writes	✅ Passed	PR modifies only docs/daily-briefs/2026-06-16.md (markdown documentation). No code paths exist to audit for destructive writes; check not applicable to documentation-only PRs.
No Edits To Historical Migrations	✅ Passed	This PR only adds docs/daily-briefs/2026-06-16.md; no migrations are modified (M status). While migrations with timestamps ≤20260527120000 appear in the commit, they are all marked as "A" (Added),...
Conventional Commits	✅ Passed	Commit subject docs(nightly): 2026-06-16 production health-check brief (0 fixes) matches the Conventional Commits pattern with type docs and scope (nightly).
Title check	✅ Passed	Title follows Conventional Commits format with 'docs:' scope (which is in the required list) and clearly describes the change: a nightly production health-check brief for 2026-06-16 with 0 fixes and production healthy status.
Description check	✅ Passed	Description is directly related to the changeset, providing detailed context for the nightly health-check brief, triage rationale for non-actionable patterns, routine limitations, and test plan.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/awesome-babbage-r0nfjc

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[njrini99-code]

Closing stale draft nightly health-check PR during branch/PR cleanup. Reopen or recreate if still needed.