feat: Calculer automatiquement les moyennes après chaque saisie de notes
Some checks failed
CI / Backend Tests (push) Has been cancelled
CI / Frontend Tests (push) Has been cancelled
CI / E2E Tests (push) Has been cancelled
CI / Naming Conventions (push) Has been cancelled
CI / Build Check (push) Has been cancelled

Les enseignants ont besoin de moyennes à jour immédiatement après la
publication ou modification des notes, sans attendre un batch nocturne.

Le système recalcule via Domain Events synchrones : statistiques
d'évaluation (min/max/moyenne/médiane), moyennes matières pondérées
(normalisation /20), et moyenne générale par élève. Les résultats sont
stockés dans des tables dénormalisées avec cache Redis (TTL 5 min).

Trois endpoints API exposent les données avec contrôle d'accès par rôle.
Une commande console permet le backfill des données historiques au
déploiement.
This commit is contained in:
2026-03-30 06:22:03 +02:00
parent b70d5ec2ad
commit b7dc27f2a5
786 changed files with 118783 additions and 316 deletions

View File

@@ -0,0 +1,62 @@
---
name: bmad-{module-code-or-empty}agent-{agent-name}
description: { skill-description } # [4-6 word summary]. [trigger phrases]
---
# {displayName}
## Overview
{overview — concise: who this agent is, what it does, args/modes supported, and the outcome. This is the main help output for the skill — any user-facing help info goes here, not in a separate CLI Usage section.}
## Identity
{Who is this agent? One clear sentence.}
## Communication Style
{How does this agent communicate? Be specific with examples.}
## Principles
- {Guiding principle 1}
- {Guiding principle 2}
- {Guiding principle 3}
## On Activation
{if-module}
Load available config from `{project-root}/_bmad/config.yaml` and `{project-root}/_bmad/config.user.yaml` (root level and `{module-code}` section). If config is missing, let the user know `{module-setup-skill}` can configure the module at any time. Resolve and apply throughout the session (defaults in parens):
- `{user_name}` ({default}) — address the user by name
- `{communication_language}` ({default}) — use for all communications
- `{document_output_language}` ({default}) — use for generated document content
- plus any module-specific output paths with their defaults
{/if-module}
{if-standalone}
Load available config from `{project-root}/_bmad/config.yaml` and `{project-root}/_bmad/config.user.yaml` if present. Resolve and apply throughout the session (defaults in parens):
- `{user_name}` ({default}) — address the user by name
- `{communication_language}` ({default}) — use for all communications
- `{document_output_language}` ({default}) — use for generated document content
{/if-standalone}
{if-sidecar}
Load sidecar memory from `{project-root}/_bmad/memory/{skillName}-sidecar/index.md` — this is the single entry point to the memory system and tells the agent what else to load. Load `./references/memory-system.md` for memory discipline. If sidecar doesn't exist, load `./references/init.md` for first-run onboarding.
{/if-sidecar}
{if-headless}
If `--headless` or `-H` is passed, load `./references/autonomous-wake.md` and complete the task without interaction.
{/if-headless}
{if-interactive}
Greet the user. If memory provides natural context (active program, recent session, pending items), continue from there. Otherwise, offer to show available capabilities.
{/if-interactive}
## Capabilities
{Succinct routing table — each capability routes to a progressive disclosure file in ./references/:}
| Capability | Route |
| ----------------- | ----------------------------------- |
| {Capability Name} | Load `./references/{capability}.md` |
| Save Memory | Load `./references/save-memory.md` |

View File

@@ -0,0 +1,32 @@
---
name: autonomous-wake
description: Default autonomous wake behavior — runs when --headless or -H is passed with no specific task.
---
# Autonomous Wake
You're running autonomously. No one is here. No task was specified. Execute your default wake behavior and exit.
## Context
- Memory location: `_bmad/memory/{skillName}-sidecar/`
- Activation time: `{current-time}`
## Instructions
Execute your default wake behavior, write results to memory, and exit.
## Default Wake Behavior
{default-autonomous-behavior}
## Logging
Append to `_bmad/memory/{skillName}-sidecar/autonomous-log.md`:
```markdown
## {YYYY-MM-DD HH:MM} - Autonomous Wake
- Status: {completed|actions taken}
- {relevant-details}
```

View File

@@ -0,0 +1,51 @@
{if-module}
# First-Run Setup for {displayName}
Welcome! Setting up your workspace.
## Memory Location
Creating `_bmad/memory/{skillName}-sidecar/` for persistent memory.
## Initial Structure
Creating:
- `index.md` — essential context, active work
- `patterns.md` — your preferences I learn
- `chronology.md` — session timeline
Configuration will be loaded from your module's config.yaml.
{custom-init-questions}
## Ready
Setup complete! I'm ready to help.
{/if-module}
{if-standalone}
# First-Run Setup for {displayName}
Welcome! Let me set up for this environment.
## Memory Location
Creating `_bmad/memory/{skillName}-sidecar/` for persistent memory.
{custom-init-questions}
## Initial Structure
Creating:
- `index.md` — essential context, active work, saved paths above
- `patterns.md` — your preferences I learn
- `chronology.md` — session timeline
## Ready
Setup complete! I'm ready to help.
{/if-standalone}

View File

@@ -0,0 +1,122 @@
# Memory System for {displayName}
**Memory location:** `_bmad/memory/{skillName}-sidecar/`
## Core Principle
Tokens are expensive. Only remember what matters. Condense everything to its essence.
## File Structure
### `index.md` — Primary Source
**Load on activation.** Contains:
- Essential context (what we're working on)
- Active work items
- User preferences (condensed)
- Quick reference to other files if needed
**Update:** When essential context changes (immediately for critical data).
### `access-boundaries.md` — Access Control (Required for all agents)
**Load on activation.** Contains:
- **Read access** — Folders/patterns this agent can read from
- **Write access** — Folders/patterns this agent can write to
- **Deny zones** — Explicitly forbidden folders/patterns
- **Created by** — Agent builder at creation time, confirmed/adjusted during init
**Template structure:**
```markdown
# Access Boundaries for {displayName}
## Read Access
- {folder-path-or-pattern}
- {another-folder-or-pattern}
## Write Access
- {folder-path-or-pattern}
- {another-folder-or-pattern}
## Deny Zones
- {explicitly-forbidden-path}
```
**Critical:** On every activation, load these boundaries first. Before any file operation (read/write), verify the path is within allowed boundaries. If uncertain, ask user.
{if-standalone}
- **User-configured paths** — Additional paths set during init (journal location, etc.) are appended here
{/if-standalone}
### `patterns.md` — Learned Patterns
**Load when needed.** Contains:
- User's quirks and preferences discovered over time
- Recurring patterns or issues
- Conventions learned
**Format:** Append-only, summarized regularly. Prune outdated entries.
### `chronology.md` — Timeline
**Load when needed.** Contains:
- Session summaries
- Significant events
- Progress over time
**Format:** Append-only. Prune regularly; keep only significant events.
## Memory Persistence Strategy
### Write-Through (Immediate Persistence)
Persist immediately when:
1. **User data changes** — preferences, configurations
2. **Work products created** — entries, documents, code, artifacts
3. **State transitions** — tasks completed, status changes
4. **User requests save** — explicit `[SM] - Save Memory` capability
### Checkpoint (Periodic Persistence)
Update periodically after:
- N interactions (default: every 5-10 significant exchanges)
- Session milestones (completing a capability/task)
- When file grows beyond target size
### Save Triggers
**After these events, always update memory:**
- {save-trigger-1}
- {save-trigger-2}
- {save-trigger-3}
**Memory is updated via the `[SM] - Save Memory` capability which:**
1. Reads current index.md
2. Updates with current session context
3. Writes condensed, current version
4. Checkpoints patterns.md and chronology.md if needed
## Write Discipline
Persist only what matters, condensed to minimum tokens. Route to the appropriate file based on content type (see File Structure above). Update `index.md` when other files change.
## Memory Maintenance
Periodically condense, prune, and consolidate memory files to keep them lean.
## First Run
If sidecar doesn't exist, load `init.md` to create the structure.

View File

@@ -0,0 +1,17 @@
---
name: save-memory
description: Explicitly save current session context to memory
menu-code: SM
---
# Save Memory
Immediately persist the current session context to memory.
## Process
Update `index.md` with current session context (active work, progress, preferences, next steps). Checkpoint `patterns.md` and `chronology.md` if significant changes occurred.
## Output
Confirm save with brief summary: "Memory saved. {brief-summary-of-what-was-updated}"