docs: correct docs against portal-auth and mysql integration - #223
Merged
kevinrutledge merged 5 commits intoJun 3, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Developer
Kevin Rutledge
What changed?
Documentation corrections plus toolchain housekeeping, on one branch.
Docs corrected against the merged integration (#217-#222). Login now validates through the portal's
validatetokenand the app mints its ownprfc_authcookie, so architecture.md and the auth-patterns ADR were rewritten and a nonexistent/api/checksumroute removed. The prisma-mysql ADR notes production runs MariaDB 5.5 through@prisma/adapter-mariadbwith a hand-created schema, the ci-cd ADR notes the build no longer runsmigrate deploy, getting-started.md drops the stale "e2e suite is skipped" note, src/README.md drops a nonexistentconfig/directory, and test/README.md fixes the Vitest environment description.docs/architecture.md,docs/decisions/auth-patterns.md,docs/decisions/prisma-mysql.md,docs/decisions/ci-cd-pipeline.md,docs/getting-started.md,src/README.md,test/README.mdBump vitest
^4.0.16to^4.1.8. Clears GHSA-5xrq-8626-4rwp, a dev-only Vitest UI server advisory and the only current finding fromnpm audit.package.json,package-lock.jsonDrop the deprecated tsconfig
baseUrl. TypeScript 7.0 deprecates it. Set the alias to"@/*": ["./src/*"], which resolves the same way relative to the config file. NoignoreDeprecationsshim.tsconfig.jsonRemove the Prisma seed and the deprecated package.json
prismakey. Prisma 7 moves seed config toprisma.config.ts. The seed was unused by CI and e2e, so it was deleted along with thedb:seedscript and the package.jsonprismakey. faker stays, sincemock-members.tsstill uses it.prisma/seed.ts(deleted),package.json,docs/getting-started.mdStop assigning
undefinedtoprocess.envin the getSecret tests. Clears Node DEP0104, a pending deprecation, and a latent bug where the restore set the var to the string"undefined"instead of unsetting it.test/auth/auth-flow.test.tsHow to test
npm run buildpasses,npm testpasses (707), andnpx tsc --noEmitis cleannpm auditreports 0 vulnerabilitiesnpm testunderNODE_OPTIONS=--pending-deprecationno longer emits DEP0104 (the remaining DEP0169 and DEP0144 come from Tailwind v3 and Next internals)npx prisma validateloadsprisma.config.tsand the schema is validChecklist