feat: add mentor framework v2 (#364)

Author: FelixTJDietrich

.github/actions/setup-caches/action.yml

@@ -37,15 +37,15 @@ runs:
 
     # Java/Maven caching
     - name: Set up JDK 21
-      if: contains(fromJSON('["application-server-unit", "application-server-integration", "application-server-architecture", "application-server-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation"]'), inputs.cache-type)
+      if: contains(fromJSON('["application-server-unit", "application-server-integration", "application-server-architecture", "application-server-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation", "database-models-validation"]'), inputs.cache-type)
       uses: actions/setup-java@v4
       with:
         distribution: 'temurin'
         java-version: '21'
         cache: maven
 
     - name: Cache Maven dependencies
-      if: contains(fromJSON('["application-server-unit", "application-server-integration", "application-server-architecture", "application-server-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation"]'), inputs.cache-type)
+      if: contains(fromJSON('["application-server-unit", "application-server-integration", "application-server-architecture", "application-server-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation", "database-models-validation"]'), inputs.cache-type)
       uses: actions/cache@v4
       with:
         path: |
@@ -58,21 +58,21 @@ runs:
 
     # Python/Poetry caching
     - name: Set up Python 3.13
-      if: contains(fromJSON('["intelligence-service-quality", "webhook-ingest-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation"]'), inputs.cache-type)
+      if: contains(fromJSON('["intelligence-service-quality", "webhook-ingest-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation", "database-models-validation"]'), inputs.cache-type)
       uses: actions/setup-python@v4
       with:
         python-version: 3.13
 
     - name: Install Poetry
-      if: contains(fromJSON('["intelligence-service-quality", "webhook-ingest-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation"]'), inputs.cache-type)
+      if: contains(fromJSON('["intelligence-service-quality", "webhook-ingest-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation", "database-models-validation"]'), inputs.cache-type)
       uses: snok/install-poetry@v1
       with:
         version: 2.1.1
         virtualenvs-create: true
         virtualenvs-in-project: true
 
     - name: Cache Poetry dependencies
-      if: contains(fromJSON('["intelligence-service-quality", "webhook-ingest-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation"]'), inputs.cache-type)
+      if: contains(fromJSON('["intelligence-service-quality", "webhook-ingest-quality", "openapi-validation", "database-schema-validation", "database-documentation-validation", "database-models-validation"]'), inputs.cache-type)
       uses: actions/cache@v4
       with:
         path: |

.github/instructions/java-tests.instructions.md

@@ -0,0 +1,18 @@
+---
+applyTo: "server/application-server/src/test/**/*.java"
+---
+
+Follow this mantra for high-value test cases:
+* Single responsibility: one behavior/assertion per test
+* Clear & concise: state the objective simply
+* Independent: no hidden dependencies
+* Traceable: link directly to requirements
+* Repeatable: consistent setup and data
+* Maintainable: easy to update when things change
+* Focus on risk: cover critical flows first
+* Minimal setup: avoid unnecessary steps
+* Fast execution: fit seamlessly into CI pipelines
+* Realistic data: use representative scenarios
+* Concise expected results: one clear outcome per test
+* Arrange-Act-Assert (AAA): keep structure clear
+* Tests may run in parallel, avoid required cleanup and assume that there might be data from previous tests in the database

.github/instructions/storybook.instructions.md

@@ -3,91 +3,197 @@ applyTo: "**/*.stories.ts,**/*.stories.tsx"
 ---
 # Storybook Guidelines
 
-## Structure & Basic Setup
+## Core Principles
 
-- Co-locate story files with component files
+We create stories that **accelerate development** and **improve team communication**. Stories should be practical tools that help developers work faster, not documentation overhead.
+
+## Structure & Setup
+
+- **Co-locate** story files with component files (`Component.stories.tsx`)
 - Use `satisfies Meta<typeof Component>` for type safety
-- Use `tags: ["autodocs"]` to generate documentation
+- Always include `tags: ["autodocs"]` for automatic documentation generation
+- Favor auto-generated titles (omit `title` property)
+
+## Documentation Strategy
 
-## Documentation
+### Component-Level Documentation
+- Add a **concise JSDoc comment** above the `meta` object explaining the component's purpose and key capabilities
+- Focus on **when to use** the component, not implementation details
+
+```typescript
+/**
+ * CodeBlock component for displaying code snippets and terminal output.
+ * Supports both inline code and multi-line code blocks with syntax highlighting.
+ */
+```
 
-- Add a JSDoc comment above the `meta` object describing the component's purpose
-- Add JSDoc comments for each story variant explaining its use case
+### Story-Level Documentation
+- Add **brief JSDoc comments** for each story explaining its specific use case
+- Use action-oriented descriptions that help developers choose the right variant
 
 ```typescript
 /**
- * Button component for user interactions with multiple variants and states.
+ * Multi-line code block for displaying formatted code snippets.
  */
+export const CodeBlock: Story = { /* ... */ };
 ```
 
-## Component Controls
+## Controls Configuration
 
-- Document props using `argTypes` with clear descriptions
-- Use appropriate controls for each prop type (boolean, select, text, etc.)
-- Set default values for common props
+### Selective argTypes
+- Only configure `argTypes` for props that **benefit from interactive controls**
+- Let Storybook infer most controls automatically 
+- Add `description` for complex or non-obvious props
 
 ```typescript
 argTypes: {
-  size: { 
-    control: 'select',
-    options: ['default', 'sm', 'lg'],
-    description: 'Button size',
+  inline: {
+    control: 'boolean',
+    description: 'Whether to display as inline code or a code block',
   },
-  variant: { 
-    control: 'select', 
-    description: 'Visual style',
+  className: {
+    description: 'Additional CSS classes for styling',
   },
 }
 ```
 
-## Example Story
+### Default Values
+- Set meaningful defaults using `args` at the meta level
+- Avoid setting `defaultValue` in argTypes (deprecated pattern)
+
+```typescript
+const meta = {
+  component: CodeBlock,
+  args: {
+    inline: false,
+    className: '',
+    children: 'console.log("Hello, world!");',
+  },
+} satisfies Meta<typeof CodeBlock>;
+```
+
+## Story Patterns
+
+### Essential Stories
+Every component should have these core stories:
+1. **Default** - Standard usage with common props
+2. **Variants** - Different visual styles/states
+3. **Edge Cases** - Empty states, long content, error states
+
+### Interactive Stories
+- Use realistic content that demonstrates actual usage patterns
+- Include examples with both short and long content to test layout
+- Show different states and configurations
+
+### Content Guidelines
+- Use **realistic, relevant content** that reflects actual usage
+- Follow our platform's **friendly, supportive engineering voice**
+- Use consistent terminology across all components
+- Include practical examples developers would actually encounter
+
+## Layout & Presentation
+
+### Parameters
+- Use `layout: 'centered'` for isolated components
+- Use `layout: 'fullscreen'` for page-level components
+- Add appropriate decorators when components need context
+
+```typescript
+parameters: {
+  layout: 'centered',
+  docs: {
+    description: {
+      component: 'Additional context if the JSDoc comment is insufficient',
+    },
+  },
+},
+decorators: [
+  (Story) => (
+    <div className="max-w-4xl p-6 bg-background">
+      <Story />
+    </div>
+  ),
+],
+```
+
+## Advanced Patterns
+
+### Composition Stories
+Create stories that show components working together:
+
+```typescript
+export const InContext: Story = {
+  render: () => (
+    <div className="prose">
+      <p>Here's how to use the API:</p>
+      <CodeBlock inline={false} className="">
+        {`const response = await fetch('/api/users');
+const users = await response.json();`}
+      </CodeBlock>
+    </div>
+  ),
+};
+```
+
+### Data-Driven Stories
+For components with complex requirements, create realistic mock data and scenarios.
+
+## Quality Standards
+
+- **Simplicity over complexity** - Don't over-engineer stories
+- **Practical scenarios** - Focus on real use cases over edge cases
+- **Visual clarity** - Stories should immediately show component capabilities
+- **Performance** - Avoid heavy computations or API calls in stories
+- **Maintenance** - Keep stories simple enough that they don't become a burden
+
+## Example Story Structure
 
 ```typescript
 import type { Meta, StoryObj } from '@storybook/react';
-import { fn } from '@storybook/test';
-import { Button } from './Button';
+import { CodeBlock } from './CodeBlock';
 
 /**
- * Button component for user interactions.
+ * CodeBlock component for displaying code snippets and terminal output.
+ * Supports both inline code and multi-line code blocks with proper formatting.
  */
 const meta = {
-  // No title needed, we should favor auto-generated titles
-  component: Button,
+  component: CodeBlock,
   parameters: { layout: 'centered' },
   tags: ['autodocs'],
   argTypes: {
-    size: { control: 'select', options: ['small', 'large'] },
-    backgroundColor: { control: 'color' },
+    inline: {
+      control: 'boolean',
+      description: 'Whether to display as inline code or a code block',
+    },
+    className: {
+      description: 'Additional CSS classes for styling',
+    },
   },
-  args: { onClick: fn() },
-} satisfies Meta<typeof Button>;
+  args: {
+    inline: false,
+    className: '',
+  },
+} satisfies Meta<typeof CodeBlock>;
 
 export default meta;
 type Story = StoryObj<typeof meta>;
 
 /**
- * Primary button for main actions.
+ * Multi-line code block for displaying formatted code snippets.
  */
-export const Primary: Story = {
+export const Default: Story = {
   args: {
-    primary: true,
-    label: 'Button',
+    children: 'console.log("Hello, world!");',
   },
 };
 
 /**
- * Secondary button for less important actions.
+ * Inline code for referencing variables or short snippets within text.
  */
-export const Secondary: Story = {
+export const Inline: Story = {
   args: {
-    label: 'Button',
+    inline: true,
+    children: 'useState',
   },
 };
 ```
-
-## UX Writing
-
-- Use realistic and relevant content in stories
-- Follow our platform's friendly, supportive voice
-- Keep text clear and concise
-- Use consistent terminology across components