3 Commits

Include renames

Author	SHA1	Message	Date
rmancinasandClaude Opus 5	121952fdc1	chore(release): v1.0.1 ... v1.0.0's images were built from db2bd54, which predates the full-hash footer. Deploying 1.0.0 would ship the abbreviated footer, so the version that actually goes to galactus is 1.0.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-30 16:38:06 -07:00
rmancinasandClaude Opus 5	db2bd545a1	chore(release): v1.0.0 ... Every manifest still read 0.1.0 while the deployed images were addressed by the moving tag `latest`. That combination is what hid the stale-image bug: a checkout could not be placed against a running container, and `latest` silently kept serving two-commit-old web code through a green deploy. Tagging v1.0.0 makes docker/metadata-action publish immutable `1.0.0` and `1.0` image tags, so deploys can name a version instead of a moving target. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-30 16:21:35 -07:00
rmancinas	27118f0df2	Initial scaffold: unified customer/insurance/utilities platform ... Next.js + NestJS + Prisma (MySQL) monorepo replacing the legacy PHP internal app. Includes a session-based auth module with Argon2 password hashing and global input validation (replacing the old app's SQL injection and plaintext password comparison), the full target Prisma schema for customers/insurance/utilities/shared ledger/bank register, Docker Compose + Dockerfiles, and an Access-to-staging migration pipeline (migration/) already run against the real source databases. See PLAN.md and RESUME.md for the full architecture and session history.	2026-07-22 01:29:56 -07:00