[devin-ai-integration]

Summary

• rename the application display name from SPA Development Reference to SPA Reference to match the renamed repository
  • browser title (frontend/index.html)
  • application header and signed-out card (APP_TITLE in frontend/src/app/App.tsx)
  • OpenAPI info.title (SPA Reference API)
• regenerate all 16 local-demo screenshots in doc/images/getting-started/ from an empty database with the same UI workflow, so doc/GETTING_STARTED.md section 13 shows the new name

Validation

• git grep -n "SPA Development Reference" returns no match
• all 16 image links in doc/GETTING_STARTED.md resolve
• git diff --check, npm run format:check, npm run lint, npm run typecheck, npm test, npm run build, npm run openapi:lint, and npm run api:check pass
• local demo from npm run demo:reset / npm run demo shows SPA Reference in the tab title and header, with all three role buttons

Scope

Display name and screenshots only. The repository slug, the generic "SPA development reference application" prose, @spa-ref/* package names, and the Compose project and volume names are unchanged.

Post-merge first-time-user test

Tested master at c07374cb97da45832a502f9a9e2454d1ca982f1a (this PR merged, plus the doc/VERSIONS v1.0 date update) from a fresh clone of https://github.com/id774/spa-reference.git, following only README.md and doc/GETTING_STARTED.md, after removing the previous demo container, volume, network, and the postgres:17 image.

Area	Result
Documentation understanding	PASS
First local start (npm ci, npm run demo)	PASS
First browser display	PASS
No external credential required	PASS
No tracked-file change	PASS

• Environment: Git 2.34.1, Node.js v24.19.0 (.nvmrc = 24), npm 10.8.3, Docker 29.7.2, Docker Compose v5.4.0; no AWS environment variables or ~/.aws
• npm ci exits 0
• npm run demo pulls postgres:17, waits until healthy, generates the Prisma client, applies 20261003054124_init, starts the backend ("mode":"local") and the frontend, then prints Local demo is ready.; no .env, AWS, or Cognito is requested
• PostgreSQL is healthy and pg_isready accepts connections; /health/ready returns HTTP 200 {"status":"ok"}; the frontend returns HTTP 200 with <title>SPA Reference</title>; ports 5173, 3000, and 55432 listen on 127.0.0.1 only
• the browser tab and header show SPA Reference; the signed-out screen shows Continue as Requester / Approver / Administrator, and Continue as Requester reaches My Requests ("There are no requests yet."), matching screenshots 01 and 02 in section 13
• Ctrl+C leaves no tsx, vite, or demo.mjs process, releases ports 5173 and 3000, and keeps the PostgreSQL container and volume as documented
• git status --short is empty before and after the test

Finding (MINOR, not fixed): during "Generating the Prisma client", the Prisma CLI showed an interactive prompt ("Install Prisma's agent skills ...? Yes / No", closes in 30s, suppressible with --no-hints). Without an answer it continued after 30 seconds and recorded the offer in ~/.config/prisma-nodejs/skills-offer.json, so it is not shown again for the same user. Startup was not blocked.

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring