1-hour workshop: Add concrete validation scenarios for the filter feature

Problem

Step 4 tells learners to review the generated code, open the site, run the existing Python tests, and confirm that the functionality works. The current unit tests cover the original dog-list response but do not prove generated breed or availability filtering. The workshop does not give learners concrete expected cases, so an implementation can appear complete while filters are ignored, combined incorrectly, or break pagination.

Because generated solutions vary, behavior-based validation is especially important here.

Suggested change

Add a short manual acceptance checklist and API examples to content/1-hour/4-add-feature.md. Keep it implementation-agnostic.

Acceptance criteria

• Learners verify breed-only filtering.
• Learners verify available-only filtering.
• Learners verify both filters together.
• Changing a control automatically refreshes results as required.
• Clearing filters restores the unfiltered list.
• No-result behavior and pagination/filter interaction are checked.
• The documented Python test command continues to pass.

content/1-hour/4-add-feature.md を開き、Step 4 と既存の Python テストコマンドを確認します。各フィルターの組み合わせ、更新時の動作、フィルターのクリア、結果がない場合、ページネーションについて、実装に依存しない手動チェックと API の例を追加します。すべての受け入れケースが文書化され、既存の Python テストが引き続きパスすれば完了です。