docs: add PR template + "packaging your submission" run/repro guidance

Ship .github/PULL_REQUEST_TEMPLATE.md so the PR body auto-fills (what built /
how to review / how to run / extra / self-check), and add a README section on
reviewer-ready, reproducible submissions: run from a clean clone against the
reviewer's own Postgres, and commit screenshots for the private dev_<name>
data and Metabase Questions a reviewer cannot run.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: Lasse Benninga

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+## What I built
+- Metabase dashboard (Week 11 Submissions collection): <link>
+- Streamlit app: `week11-streamlit/app.py` (KPIs, hour-of-day trend, freshness, payment-type filter)
+- Presentation recording (private / unlisted): <link>
+
+## How to review
+- Metabase: open the dashboard link above, or see the committed screenshots / PDF export.
+- Streamlit: see the committed screenshots, or run it yourself with the steps below.
+- Metric definitions: `week11-streamlit/metric_definitions.md`
+- AI usage: `AI_ASSIST.md`
+
+## How to run the Streamlit app
+From a clean clone, with your own Postgres access:
+
+```bash
+cd week11-streamlit
+uv sync
+cp .env.example .env      # set your own POSTGRES_URL (with ?sslmode=require) + DB_SCHEMA
+uv run streamlit run app.py
+```
+
+Prerequisite: your own `fct_trips` mart populated in your `dev_<name>` schema (from Week 10).
+
+## Extra completed
+- [ ] Metabase date filter on >=2 Questions
+- [ ] Streamlit auto-refresh
+
+## Self-check
+- [ ] `bash .hyf/test.sh` passes
+- [ ] No credentials committed (no password in `app.py`, `.env` is gitignored)
+- [ ] Screenshots of the Metabase dashboard and the running Streamlit app are committed

README.md

@@ -60,6 +60,15 @@ Fill in `week11-streamlit/metric_definitions.md`: a five-field definition (name,
 
 Prefer to keep it in Azure? The assignment chapter documents an **optional advanced path**: upload the recording to the shared `student-submissions` blob container (teachers get read access, nothing is public) and share a read-only link. The container is shared, so name your file after yourself: `week-11/<your-name>.mp4` (e.g. `week-11/jane-doe.mp4`). See "Optional (advanced): host the recording on Azure Blob Storage" in the Week 11 Assignment chapter.
 
+## Packaging your submission for review
+
+Your pull request should review itself: a reviewer should be able to understand and check it without asking you anything. When you open the PR, GitHub loads a template (`.github/PULL_REQUEST_TEMPLATE.md`) into the description, fill in every section. Two things carry the most weight:
+
+- **Reproducible run instructions.** The Streamlit steps above must work from a clean clone against the reviewer's *own* Postgres: `uv sync`, copy `.env.example` to `.env`, set their own `POSTGRES_URL` (with `?sslmode=require`) and `DB_SCHEMA`, then `uv run streamlit run app.py`. Name every prerequisite, including your own `fct_trips` mart from Week 10. If a step only works on your machine, it is not reproducible.
+- **Proof for what a reviewer cannot run.** A reviewer cannot open your private `dev_<name>` schema or your Metabase Questions, so commit screenshots (or a PDF export) of your Metabase dashboard and your running Streamlit app. Screenshots are how you prove "it runs on my data."
+
+See "Package your pull request for review" in the Week 11 Assignment chapter for the full rationale.
+
 ## Check your score locally
 
 The autograder runs static checks (required files present, secrets hygiene, Streamlit code patterns, metric-definition coverage):