docs: update PHPDoc comments

[shimomo]

PHPDoc コメントを修正しました。

Summary by CodeRabbit

• ドキュメント
  • 型注釈と戻り値の説明を、より包括的なコレクション型に統一しました。
  • 開発者向けドキュメントの整合性・可読性を改善しました。
  • 実行時の動作やユーザー向け機能への影響はありません。

[coderabbitai]

Walkthrough

src/ProgramScraper.php のDocBlock/psalm注釈を ScrapedStadiumRaces から ScrapedRaces に更新。ScraperInterface からの Psalm 型インポートを追加。実行ロジックやシグネチャ変更はなし。

Changes

コホート / ファイル群	変更概要
DocBlock型注釈の更新 src/ProgramScraper.php	- ScraperInterface から ScrapedRaces を Psalm 型インポート追加 - scrape() の戻り注釈を ScrapedStadiumRaces → ScrapedRaces に変更 - scrape() 内 $programs の psalm-var を ScrapedRaces に変更 - normalize() の戻り注釈を ScrapedStadiumRaces → ScrapedRaces に変更 - normalize() 内 psalm-var を ScrapedRaces に変更

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

ぼくはレビュー野原のうさぎです
型の雲が入れ替わる、空はすっきり
Stadium から広がる Races の風
耳ぴょこり、注釈だけで旅完了
きゅっ、と整列、にんじん印の OK ✅

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/update-phpdoc-comments

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4a0d329 and 638304b.

📒 Files selected for processing (1)

• src/ProgramScraper.php (4 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

src/ProgramScraper.php (3)

src/ScraperAdapter.php (2)

• ScraperAdapter (15-40)
• Override (34-39)

tests/ProgramScraperTest.php (2)

• ProgramScraperTest (17-86)
• testScrape (24-35)

src/ScraperInterface.php (2)

• ScraperInterface (51-61)
• scrapePrograms (60-60)

🔇 Additional comments (3)

src/ProgramScraper.php (3)

30-30: scrape() の @psalm-return を ScrapedRaces に更新 — OK

返り値の実体（normalize 済みの配列）と一致しています。

---

45-45: normalize() の @psalm-return を ScrapedRaces に更新 — OK

関数の処理（フラット化と boats の再インデックス）と整合しています。

---

11-11: ScrapedRaces と ScrapedStadiumRaces の import 定義が ScraperInterface 側で正しく定義されていることを確認しました。問題ありません。

[coderabbitai]

⚠️ Potential issue

psalm-var に変数名が欠落しています（$newPrograms を明示してください）。

変数名なしの @psalm-var は型付与されず、Psalm の恩恵が得られません。$newPrograms を対象に指定してください。

適用案:

-        /** @psalm-var ScrapedRaces */
+        /** @psalm-var ScrapedRaces $newPrograms */
         return $newPrograms;

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	/** @psalm-var ScrapedRaces */
	/** @psalm-var ScrapedRaces $newPrograms */
	return $newPrograms;

🤖 Prompt for AI Agents

In src/ProgramScraper.php around line 63, the @psalm-var annotation is missing
the variable name so Psalm won't apply the type to $newPrograms; update the
docblock to include the variable name after the type (e.g. use "@psalm-var
ScrapedRaces $newPrograms") so that $newPrograms is correctly type-annotated for
static analysis.

[shimomo]

Psalm は変数名なしの型付与が可能なので無視します。
Off-label usage of the @var tag

[coderabbitai]

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!