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.

Open content/1-hour/4-add-feature.md and review Step 4 and its existing Python test command. Add implementation-agnostic manual checks and API examples for each filter combination, refresh behavior, clearing filters, no results, and pagination. Done means all acceptance cases are documented and the existing Python tests still pass.