6.v1.0.0

The Problem in Real Life

"It Works for Me" vs. Something Others Can Use, Run and Trust

Documentation, a README, GitHub, a Development Workflow and a Production Release

• The README — the sign on the door (Acts 16, 24, 25): what it is (one sentence and a screenshot); the live link; features; the tech stack; how to run it locally (exact commands — docker compose up, migrations, seed data); the environment variables (names only, with .env.example); how to run tests; the API endpoints; the folder map; and known limitations and next ideas. She writes it, then follows it herself on a fresh clone to prove it works.
• Other documentation (Act 24): .env.example with every real variable (checked against the code, Act 25), short comments where the "why" isn't obvious (the unique constraint, the position query), and a docs/decisions.md with two short decision records: why sessions instead of JWTs, why positions are calculated rather than stored.
• A public GitHub repository — check before you publish (Acts 15, 22): before making the repository public, she checks the whole history, not just the current files: secret scanning, a search of git log -p for anything like a key or password, and confirms .env was ignored from the first commit. (If a secret had ever been committed: rotate it first, then clean history — Act 22.) She adds a licence and a short description.
• A development workflow — how changes reach production (Acts 15, 18, 19): main is protected: changes arrive through pull requests (yes, even from herself) that must pass CI. Merging to main builds the image and deploys it automatically, with migrations and a health check. Rollback means redeploying the previous image. She writes this in the README too.
• A production release (Act 18): she tags the first release v1.0.0 (Act 16's semantic versioning) with short release notes: what it does, how to use it, what's next. From now on, a new feature means a new MINOR version, a fix a PATCH.

git log -p | grep -iE "secret|password|api[_-]?key|sk_live"   # search ALL history, not just today
git ls-files | grep -E "^\.env$"                               # must print nothing

git switch main && git pull
git tag v1.0.0 -m "Event Waitlist v1.0.0 — first production release"
git push origin v1.0.0