1-hour workshop: Include the page data owner in the filter exercise context

Problem

Step 4 asks learners to add only app/server/app.py and app/client/src/components/DogList.astro to Copilot Edits. However, app/client/src/pages/index.astro owns the /api/dogs request, reads URL query parameters, and renders pagination. DogList.astro only receives and renders a dogs prop.

Without the page file in context, Copilot can produce a partial client-side filter or miss the request and pagination changes needed for the documented server-side filtering flow.

Suggested change

Update content/1-hour/4-add-feature.md to include app/client/src/pages/index.astro in the required context and explain at a high level which file owns the API request versus presentation.

Acceptance criteria

• Step 4 includes app/client/src/pages/index.astro in the files supplied to Copilot.
• The expected flow from filter controls to URL/API query parameters is stated.
• Existing pagination parameters are preserved, or the page is deliberately reset, when filters change.
• The exercise is validated from a fresh template copy.

Start with content/1-hour/4-add-feature.md, then read app/client/src/pages/index.astro, app/client/src/components/DogList.astro, and app/server/app.py to distinguish request, filtering, pagination, and presentation responsibilities. Validate the workshop from a fresh template copy; done means Step 4 names the page file, explains the query flow, and documents how pagination behaves when filters change.