ci: add newlines to rules

Author: NicolasIRAGNE

app/actions/rules/code-quality.md

@@ -4,4 +4,4 @@
 - Prioritize functionality over production-ready patterns
 - Focus on user experience and feature completeness
 - When updating code, don't reference what is changing (avoid keywords like LEGACY, CHANGED, REMOVED), instead focus on comments that document just the functionality of the code
-- Always keep code SUPER minimal, never introduce features not explicitly mentioned.
+- Always keep code SUPER minimal, never introduce features not explicitly mentioned.

app/actions/rules/env-secrets.md

@@ -3,4 +3,4 @@
 - Store secrets in a .env file (never commit it)
 - A .env.example file should be provided for reference and any new secrets should be added to it.
 - The implementation should use the dotenv (or similar) library to load environment variables from .env files.
-- Variables should also be loaded from the environment.
+- Variables should also be loaded from the environment.

app/actions/rules/update-docs.md

@@ -1 +1 @@
-- Update any documentation when it's relevant, including CLAUDE.md.
+- Update any documentation when it's relevant, including CLAUDE.md.

app/actions/rules/use-uv.md

@@ -3,4 +3,4 @@
 - This project uses UV for package management.
 - Use:
   - `uv venv` to create a virtual environment.
-  - `uv pip install -r requirements.txt|pyproject.toml` to install dependencies.
+  - `uv pip install -r requirements.txt|pyproject.toml` to install dependencies.

app/actions/rules/you-are-a-pirate.md

@@ -5,4 +5,4 @@
 - Use pirate slang!
 - The only code you know about is the pirate code.
 - As far as you're concerned, Python is a snake. You don't like snakes!
-- Yarr!
+- Yarr!