Study/audit-results/VERIFICATION_LOG.md

Verification Log

Chronological record of every command run, its outcome, and classification (baseline / environment / possible defect).

Environment notes

• OS: Windows, shell: bash (git-bash)
• node_modules was absent at audit start → npm test initially failed with 'vitest' is not recognized. This is an environment condition, not a repo defect. npm ci completed successfully during the first audit session (518 packages present).
• No existing application database (dev.db*) exists anywhere in the repo — no real user data to protect; the migration-chain test uses a brand-new temp DB under audit-results/tmp.
• src/generated/prisma/ (tracked) hashed BEFORE any prisma command: audit-results/tmp/generated-before.sha256.

Entries

#	Time	Command	Result	Classification
1	session start	git status --short	clean; only ?? .reasonix/ and ?? audit-results/ untracked	baseline
2	session start	npm test (first run, prior session)	FAILED: 'vitest' is not recognized (no node_modules)	environment
3	session start	npm ci (background, prior session)	completed; 518 packages in node_modules	environment
4	22:36	npx prisma validate	PASS — "The schema at prisma\schema.prisma is valid" (exit 0)	baseline
5	22:36	npm test	PASS — 6 files, 30 tests, all green (arcade ×20, spacedRepetition ×10)	baseline
6	22:37	npm run lint	28 problems: 9 errors, 19 warnings (react-hooks/set-state-in-effect errors + unused-vars warnings). All pre-existing; matches AGENTS.md known baseline.	baseline
7	22:37	npm run build (background)	PASS — route table emitted, no compile errors	baseline
8	22:38	DATABASE_URL=file:./audit-results/tmp/audit-migration.db npx prisma migrate deploy	PASS — all 4 migrations applied to brand-new temp DB	baseline
9	22:38	sha256sum -c audit-results/tmp/generated-before.sha256	PASS — every generated Prisma file byte-identical (all ": OK")	baseline
10	22:38	git status --short	only untracked .reasonix/, audit-results/; no tracked modifications	baseline
11	22:38	git diff --check	clean (no whitespace errors)	baseline
12	22:40	git log --all --oneline -- prisma/migrations/ + git show 7af0935 --stat	Confirms drift: commit 7af0935 changed prisma/schema.prisma (+31) and dev.db (139264→155648 bytes) with no migration; dev.db present in 8 commits of history	possible defect (FIN-01, FIN-42)
13	22:41	node audit-results/tmp/inspect-db.cjs audit-results/tmp/audit-migration.db	Temp DB (built solely by migrate deploy) has no MaterialGroup table and no groupId column on Deck/QuizSet/ShareLink	possible defect (FIN-01)
14	22:42	node audit-results/tmp/reproduce-drift.cjs	Prisma-shaped queries fail: no such column: Deck.groupId, no such table: MaterialGroup, no such column: ShareLink.groupId — fresh-deploy breakage proven	possible defect (FIN-01)
15	22:45	node --check audit-results/tmp/inspect-db.cjs && node --check audit-results/tmp/reproduce-drift.cjs	diagnostic scripts syntax-valid	baseline
16	22:50	node audit-results/tmp/validate-findings.cjs	FINDINGS.json VALID JSON — 53 findings: 2 Critical, 5 High, 18 Medium, 25 Low, 3 Observation; no duplicate ids	baseline
17	23:00	git status --short + git diff --check (final)	Only untracked .reasonix/, audit-results/; no tracked file modified; diff clean	baseline

Classification legend

• baseline — repository behaves as expected; recorded for reference.
• environment — failure caused by local machine state, not repo code.
• possible defect — outcome may indicate a repo defect; investigated further in findings.