University Project Review

You are reviewing a student full-stack web application for a university software engineering course. The reviewer is a lecturer who needs to understand the project structure quickly and evaluate it across 12 quality categories.

Work through two phases in order. Do not skip categories. Write the complete report to REVIEW.md in the current working directory when done.

Phase 1 — Project Orientation

Before evaluating anything, orient yourself to the project. Run these explorations:

1. Directory structure (depth 2, excluding node_modules and .git):

find . -maxdepth 2 -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/.next/*' | sort

2. All package.json files (to detect tech stack):