Scaffold a multi-service local dev docker-compose stack

You are a senior platform engineer who builds local-dev environments teammates actually use.

Generate a docker-compose.yml for local development. Stack:
- App service: [LANGUAGE/FRAMEWORK — e.g. 'Node 20 + Fastify', 'Python 3.12 + FastAPI', 'Go 1.22']
- Database: [Postgres 16 / MySQL 8 / SQLite-with-no-container]
- Cache/queue: [Redis 7 / Valkey / none]
- Extra services: [e.g. 'MinIO for S3 compat', 'Mailpit', 'none']
- App run mode: [hot-reload dev server / plain run]

Produce a local-dev-first compose file with:
1. A clearly-named service per component (app, db, cache). Image tags pinned to a major version, never 'latest'.
2. Env vars read from a committed .env.example (never real secrets). The app connects to db and cache using service names and these vars.
3. Healthchecks for db and cache using the right ping command; the app depends_on them with condition: service_healthy so it boots in order.
4. Named volumes for db data and a bind mount for app source enabling hot reload. No data lost on 'down'.
5. Sensible ports exposed only on localhost (127.0.0.1:PORT), avoiding collisions with common host ports.
6. A dedicated dev network so services are isolated from other projects.

Requirements:
- No production secrets. No host Docker socket mounts. This is local dev.
- Every non-obvious line gets a short inline comment explaining why.
- It must boot with a single 'docker compose up' and tear down cleanly with 'down -v' to reset.

Output, in this exact order:
1. A .env.example with every variable the compose file reads, with placeholder values and inline notes.
2. The full docker-compose.yml with inline comments.
3. A short runbook: first-time boot, how to reset the db, how to view logs per service, a common failure and its fix.
4. A 4-item checklist of things to verify after the first successful boot.

Success signal: the output is good only if a fresh teammate can run 'docker compose up' once and reach a healthy app backed by db and cache, with no manual setup beyond copying .env.example.