add projects page and settings

[DragonSenseiGuy]

Added project page and settings see screenshots below.

[Copilot]

Pull request overview

This PR adds a comprehensive projects management system to the Resolution application, including dedicated pages for viewing, creating, and managing user projects, along with a settings page for account management and an FAQ page for user support.

Changes:

• Adds a new Project model to the database schema with user relationship and cascade deletion
• Implements complete CRUD operations for projects with form validation using Zod
• Introduces a bottom navigation bar layout pattern for the app with settings and FAQ links
• Redirects the main app route to the projects page for improved user experience

Reviewed changes

Copilot reviewed 13 out of 14 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
resolution-frontend/prisma/schema.prisma	Adds Project model with userId, name, description fields and cascade delete relation
resolution-frontend/src/routes/app/+layout.svelte	Introduces fixed bottom navigation with Projects, FAQ links and settings icon
resolution-frontend/src/routes/app/+page.svelte	Implements automatic redirect to /app/projects on mount
resolution-frontend/src/routes/app/projects/+page.svelte	Projects list page with time countdown, empty state, and project grid display
resolution-frontend/src/routes/app/projects/+page.server.ts	Fetches user's projects ordered by creation date
resolution-frontend/src/routes/app/projects/create/+page.svelte	Project creation form with character counters and real-time validation
resolution-frontend/src/routes/app/projects/create/+page.server.ts	Handles project creation with Zod validation and redirects to detail page
resolution-frontend/src/routes/app/projects/[id]/+page.svelte	Project detail page displaying name, description, creation date with card preview
resolution-frontend/src/routes/app/projects/[id]/+page.server.ts	Loads project with authorization check ensuring user owns the project
resolution-frontend/src/routes/app/settings/+page.svelte	Settings page with centered logout button
resolution-frontend/src/routes/app/settings/+page.server.ts	Provides user data to settings page
resolution-frontend/src/routes/app/faq/+page.svelte	FAQ page with accordion-style Q&A display and animations
resolution-frontend/src/routes/app/faq/+page.server.ts	Returns hardcoded FAQ data for display
resolution-frontend/bun.lock	Updates dependencies including zod, adds project-related packages

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Missing database index on userId field. Since projects are queried by userId in the projects list page (line 7-9 of +page.server.ts), add an index to improve query performance. Add @@index([userId]) after the relation definition to optimize lookups.

Suggested change

	user User @relation(fields: [userId], references: [id], onDelete: Cascade)
	user User @relation(fields: [userId], references: [id], onDelete: Cascade)
	@@index([userId])

[Copilot]

The navigation highlighting is hardcoded with "nav-primary" always applied to the Projects link. This means the Projects link will always be highlighted in gold, even when viewing other pages like FAQ or Settings. Consider using the $page store from $app/stores to dynamically apply the active state based on the current route.

[Copilot]

The logout button is duplicated both in this page header and in the bottom navigation layout (settings icon). This creates a confusing user experience. Since the bottom navigation already has a settings icon that leads to a settings page with logout functionality, this logout button should be removed from the projects page to maintain consistency and reduce duplication.

Suggested change

	<form method="POST" action="/api/auth/logout" class="logout-form">
	<button type="submit" class="logout-btn">Logout</button>
	</form>

[Copilot]

The data variable is destructured from props but never used in this component. The parent layout already provides the user data, and this page doesn't need to use it directly. Consider removing this unused variable to clean up the code.

Suggested change

	<script lang="ts">
	import type { PageData } from './$types';
	let { data }: { data: PageData } = $props();
	</script>

[Copilot]

The back-btn styles are duplicated between this file and the project detail page ([id]/+page.svelte). Consider extracting this into a shared component or CSS class in a global stylesheet to follow the DRY principle and make styling updates easier to maintain.

[Copilot]

The logout-btn styles are duplicated between this file and the settings page. Consider extracting common button styles into a shared component or global CSS class to reduce code duplication and make maintenance easier.