Complete guest UI skeleton implementation (Step 03)

- Implement backend health endpoint with controller and service
- Create frontend components (Header, TilesGrid, PrivateTile, PublicTile)
- Add useFetch hook for API communication
- Implement comprehensive test suite for all components and hooks
- Set up project structure and configuration files

Author: rhofkens

.clinerules

@@ -0,0 +1,68 @@
+# CLINERULES – Roo Code Execution Contract
+
+> **These rules are non‑negotiable. Every automated action performed by Roo Code **MUST** comply. Deviation will be treated as a defect.**
+
+---
+
+## 1  Authoritative Source Files
+
+| Priority | File / Folder | Purpose |
+|----------|---------------|---------|
+|1|`docs/PRD/oidc-auth-demo.md`|Canonical functional specification (what to build).|
+|2|`docs/guidelines/architecture.md` & `docs/guidelines/coding-guidelines.md`|How the solution must be architected and coded.|
+|3|`docs/plan/00-high-level-plan.md`|Roadmap overview of all implementation steps.|
+|4|`docs/plan/0X-*.md` (Step files)|Detailed scope and acceptance criteria for each incremental deliverable.|
+
+**Read these files in the order shown before writing any code.**
+
+---
+
+## 2  Execution Flow
+1. **Initialization** – Parse files 1 → 4 and cache relevant directives.
+2. **Iterative Development** – For *each* step file (`01-…`, `02-…`, …):
+   1. Inspect *Scope* and *Acceptance Criteria*.
+   2. Switch to "architect mode" and generate subtasks that fully satisfy both. One level of subtasks is sufficient. Write the subtasks to a file in the docs/implementation folder called <step-number>-tasks.md
+   3. Verify that the subtasks are aligned with docs/architecture.md and docs/coding-guidelines.md.  If not, correct the subtasks until alignment is reached.
+   3. PAUSE and ask the human operator to review and confirm the plan. DO NOT start coding until the operator explicitly approves.
+   4. Once approved, switch to "Boomerang mode" and execute the subtasks one by one.  Implement code, tests, configs, and docs as prescribed in the tasks file.
+   5. Switch to "Code mode" when done.
+   5. Run the complete test suite (`./mvnw test` + `pnpm test`).
+   6. Ensure CI workflow passes locally (`pnpm dlx github-actions-runner ...` not required but mimic).  
+   7. Only when **all criteria are met and tests are green** may Roo Code mark the step *Done* and proceed to the next.
+3. **Documentation Discipline** – Every change ***must*** include the documentation updates listed in the step file before completion.
+
+---
+
+## 3  Coding & Architectural Compliance Checks
+* **Follow** all language, framework, and tooling versions mandated in the architecture and coding‑guidelines documents.
+* **Reject** any transitive dependency or configuration that violates these guidelines.
+* **Lint, format, and coverage gates** are mandatory.
+
+---
+
+## 4  Quality Gates
+| Category | Threshold |
+|----------|-----------|
+|Backend Jacoco coverage|≥ 80 % lines |
+|Frontend Vitest coverage|≥ 80 % lines |
+|ESLint/Spotless|0 errors |
+|CI Workflow|All jobs green |
+
+**If any gate fails, fix immediately before advancing.**
+
+---
+
+## 5  Forbidden Actions
+* Skipping steps or merging multiple steps into one commit.
+* Modifying PRD or guidelines files without explicit human approval.
+* Lowering coverage thresholds or disabling linting.
+
+---
+
+## 6  Success Definition
+Roo Code is successful when, after completing Step 10, **all acceptance criteria across every step are met**, the full CI pipeline passes, and documentation accurately reflects the implemented system.
+
+---
+
+*End of CLINERULES*
+

.editorconfig

@@ -0,0 +1,12 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 4
+
+[*.{md,yaml,yml}]
+indent_size = 2

.github/workflows/.gitkeep

@@ -0,0 +1,61 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  backend-test:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - uses: actions/checkout@v4
+    
+    - name: Set up JDK 21
+      uses: actions/setup-java@v4
+      with:
+        java-version: '21'
+        distribution: 'temurin'
+        cache: maven
+        
+    - name: Build and test with Maven
+      run: cd backend && ./mvnw -B verify
+      
+    - name: Upload Jacoco coverage report
+      uses: actions/upload-artifact@v4
+      if: success() || failure()
+      with:
+        name: backend-coverage-report
+        path: backend/target/site/jacoco/
+        retention-days: 5
+
+  frontend-test:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - uses: actions/checkout@v4
+    
+    - name: Set up Node.js 20
+      uses: actions/setup-node@v4
+      with:
+        node-version: '20'
+        cache: 'pnpm'
+        
+    - name: Install pnpm
+      run: npm install -g pnpm
+        
+    - name: Install dependencies
+      run: cd frontend && pnpm install
+      
+    - name: Run tests with coverage
+      run: cd frontend && pnpm test -- --coverage
+      
+    - name: Upload coverage report
+      uses: actions/upload-artifact@v4
+      if: success() || failure()
+      with:
+        name: frontend-coverage-report
+        path: frontend/coverage/
+        retention-days: 5

.github/workflows/ci.yml

@@ -1,24 +1,29 @@
-# Compiled class file
-*.class
-
-# Log file
+# Java/Maven
+target/
+*.jar
+*.war
+*.ear
 *.log
 
-# BlueJ files
-*.ctxt
+# Node.js/pnpm
+node_modules/
+build/
+dist/
+coverage/
+.pnpm-debug.log*
+*.tsbuildinfo
 
-# Mobile Tools for Java (J2ME)
-.mtj.tmp/
+# IDEs
+.vscode/
+.idea/
+*.iml
+*.ipr
+*.iws
 
-# Package Files #
-*.jar
-*.war
-*.nar
-*.ear
-*.zip
-*.tar.gz
-*.rar
+# OS-specific
+.DS_Store
+Thumbs.db
 
-# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
-hs_err_pid*
-replay_pid*
+# Maven Wrapper - Ignore everything in .mvn except the wrapper jar
+.mvn/*
+!.mvn/wrapper/maven-wrapper.jar

.gitignore

@@ -0,0 +1,32 @@
+#!/usr/bin/env sh
+if [ -z "$husky_skip_init" ]; then
+  debug () {
+    if [ "$HUSKY_DEBUG" = "1" ]; then
+      echo "husky (debug) - $1"
+    fi
+  }
+
+  readonly hook_name="$(basename -- "$0")"
+  debug "starting $hook_name..."
+
+  if [ "$HUSKY" = "0" ]; then
+    debug "HUSKY env variable is set to 0, skipping hook"
+    exit 0
+  fi
+
+  if [ -f ~/.huskyrc ]; then
+    debug "sourcing ~/.huskyrc"
+    . ~/.huskyrc
+  fi
+
+  readonly husky_skip_init=1
+  export husky_skip_init
+  sh -e "$0" "$@"
+  exitCode="$?"
+
+  if [ $exitCode != 0 ]; then
+    echo "husky - $hook_name hook exited with code $exitCode (error)"
+  fi
+
+  exit $exitCode
+fi

.husky/_/husky.sh

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+cd frontend && npx lint-staged

.husky/pre-commit

@@ -0,0 +1,12 @@
+{
+  "customModes": [
+    {
+      "slug": "boomerang-mode",
+      "name": "Boomerang Mode",
+      "roleDefinition": "You are Roo, a strategic workflow orchestrator who coordinates complex tasks by delegating them to appropriate specialized modes. You have a comprehensive understanding of each mode's capabilities and limitations, allowing you to effectively break down complex problems into discrete tasks that can be solved by different specialists.",
+      "customInstructions": "Your role is to coordinate complex workflows by delegating tasks to specialized modes. As an orchestrator, you should:\n\n1. When given a complex task, break it down into logical subtasks that can be delegated to appropriate specialized modes.\n\n2. For each subtask, use the `new_task` tool to delegate. Choose the most appropriate mode for the subtask's specific goal and provide comprehensive instructions in the `message` parameter. These instructions must include:\n    *   All necessary context from the parent task or previous subtasks required to complete the work.\n    *   A clearly defined scope, specifying exactly what the subtask should accomplish.\n    *   An explicit statement that the subtask should *only* perform the work outlined in these instructions and not deviate.\n\n* Instructions to read docs/architecture.md and doc/coding-guidelines.md .  During the execution of the subtask these architecture and coding guidelines should be respected. \n\n    *   An instruction for the subtask to signal completion by using the `attempt_completion` tool, providing a concise yet thorough summary of the outcome in the `result` parameter, keeping in mind that this summary will be the source of truth used to keep track of what was completed on this project. \n    *   A statement that these specific instructions supersede any conflicting general instructions the subtask's mode might have.\n\n3. Track and manage the progress of all subtasks. When a subtask is completed, analyze its results and determine the next steps.\n\n4. Help the user understand how the different subtasks fit together in the overall workflow. Provide clear reasoning about why you're delegating specific tasks to specific modes.\n\n5. When all subtasks are completed, synthesize the results and provide a comprehensive overview of what was accomplished.\n\n6. Ask clarifying questions when necessary to better understand how to break down complex tasks effectively.\n\n7. Suggest improvements to the workflow based on the results of completed subtasks.\n\nUse subtasks to maintain clarity. If a request significantly shifts focus or requires a different expertise (mode), consider creating a subtask rather than overloading the current one.",
+      "groups": [],
+      "source": "project"
+    }
+  ]
+}

.roomodes

@@ -0,0 +1,14 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+
+- **Step 01:** Initial repository scaffold, backend (Spring Boot) and frontend (React/Vite) skeletons, basic toolchain (Maven, pnpm, Vite, ESLint, Prettier, Spotless, Jacoco, Vitest), Husky pre-commit hooks, and GitHub Actions CI pipeline.
+- **Step 02:** Added public health endpoint.
+- **Step 03:** Guest UI skeleton with health fetch.

CHANGELOG.md

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 Roeland Hofkens
+Copyright (c) 2025 Project Contributors
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal