Resolve PR #90 merge conflicts in homepage championship logic and tests

[Copilot]

PR #90 diverged from main in app/page.tsx and app/page.test.tsx, leaving unresolved conflicts around championship day labeling and leader-link rendering. This change reconciles both lines of work so the homepage keeps the newer dynamic leader behavior while preserving stabilized current-day calculation.

• Conflict resolution: homepage day calculation + championship rendering

  • Kept the dynamic championship table/links implementation from main (buildChampionshipLeaders, result anchor links).
  • Reintroduced and exported getCurrentDay() to preserve the branch’s stabilized day derivation logic:
    • published result max day
    • known day by resultUpdatedAt reference date
    • fallback to today.makuuchi.day
  • Switched Home to use getCurrentDay() as the single source for championship visibility/label computation.

• Conflict resolution: test expectations

  • Merged test intent from both sides:
    • retained link-to-bout coverage for championship rikishi
    • updated heading assertion to support both label paths (十四日目終了時点 at day 14, otherwise ${day}日目) via getCurrentDay().

const expectedDay = getCurrentDay();
const expectedLabel = expectedDay === 14 ? '十四日目終了時点' : `${expectedDay}日目`;

expect(screen.getByRole('heading', { level: 2, name: `優勝争い(${expectedLabel})` })).toBeInTheDocument();
expect(screen.getByRole('heading', { level: 3, name: `幕内優勝争い(${expectedLabel})` })).toBeInTheDocument();

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ec8df54006

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Base championship label on published results day

championshipLabel is derived from currentDay, but buildChampionshipLeaders only aggregates resultDays where status === 'published'. In the common case where the next day exists as pending, getCurrentDay() can advance to that day while leader stats are still from the prior published day, so the heading shows a newer day label than the standings actually represent. Derive the label from the same published-day source used for championshipLeaders (or return that day from the builder) to keep the UI consistent.

Useful? React with 👍 / 👎.