Operator: validate the v1.89.0→v1.102.0 campaign locally

[CheeryProgrammer]

The whole backlog campaign was merged, tagged, and released via CI (this sandbox has no Docker/Postgres). This issue is the manual confirmation on your own machine. Nothing here changes data — it uses a throwaway DB and a separate compose project.

1. Confirm the releases exist

git fetch --tags
git tag --sort=-v:refname | grep '^v1\.' | head -20        # expect v1.89.0 … v1.102.0
gh run list --workflow=release.yml --limit 6               # all green
gh pr list --state merged --limit 15

• Tags v1.89.0 … v1.102.0 present
• Release runs green (GHCR images published)

2. Run the full test suite (throwaway pgvector, non-default port — never touches your live stack)

git checkout main && git pull

docker run -d --rm --name brainiac-test-db \
  -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=brainiac_test \
  -p 55432:5432 pgvector/pgvector:pg16
until docker exec brainiac-test-db pg_isready -U postgres >/dev/null 2>&1; do sleep 1; done

DATABASE_URL='postgres://postgres:postgres@localhost:55432/brainiac_test?sslmode=disable' go test ./...

docker stop brainiac-test-db

• go test ./... passes

3. Confirm one-command deploy still works (isolated project, then torn down)

docker compose -p brainiac-validate up -d --build
docker compose -p brainiac-validate logs -f app   # watch migrations apply + Ollama model pull
# Ctrl-C, then:
docker compose -p brainiac-validate down -v

• App boots, migrations apply automatically, no manual steps beyond .env

4. Sanity: minimal config unchanged

With only DATABASE_URL set (no new env vars), the app behaves exactly as before — all new features default OFF. Confirm your existing .env needs no edits to keep working.

• Existing .env still valid; nothing new required

🤖 Generated with Claude Code