---
title: ImpactFlow Discovery README refreshed to match current code (2026-05-27)
type: observation
topics: [impactflow-discovery, documentation, alembic, migration-bootstrap]
people: [jsalmon]
---

Refreshed `README.md` for `impactflow-discovery` so it matches the code as of
2026-05-27. Repo state, routes, schemas, env vars, and dependency pins were
already accurate; the doc had drifted in four specific places.

## What changed

1. **Important files table** — added rows for `app/migration_bootstrap.py`,
   `tests/test_migration_bootstrap.py`, `tests/test_static_discovery.py`,
   and `tests/fixtures/{gut,head,heart}_type_responses.json`.
2. **App Startup section** — replaced the one-line "Docker startup also runs
   Alembic migrations" with the actual three-step container CMD:
   `python -m app.migration_bootstrap && alembic upgrade head && uvicorn ...`,
   plus a note that the Dockerfile also runs `alembic upgrade head` at build
   time as a sanity check against a throwaway in-image DB.
3. **Frontend Behavior — discovery.html** — documented the `createUserId()`
   helper and its `crypto.getRandomValues()` fallback so the flow keeps
   working in insecure (non-HTTPS) contexts like LAN/Tailscale.
4. No content removed; every existing claim still checks out against code.

## Why this matters

`app/migration_bootstrap.py` is the load-bearing piece for anyone whose local
`data/discovery.db` predates Alembic — it stamps the existing schema as
revision `001` so the next `alembic upgrade head` doesn't crash trying to
recreate tables that already exist. That behavior was previously invisible
to new readers of the repo.

## Files touched

- `C:\SyncData\impactflow-discovery\README.md`

## Verification

- Every backtick-quoted file path in the README maps to a real file on disk.
- Every `/discovery/*` route in the README matches a handler in
  `app/routers/discovery.py`.
- `createUserId()` and `getRandomValues` both confirmed present in
  `app/static/discovery.html`.