v2.7.6 (#600)

Co-authored-by: Clément Sirieix <clement.sirieix@mistral.ai>
Co-authored-by: Kim-Adeline Miguel <51720070+kimadeline@users.noreply.github.com>
Co-authored-by: Mathias Gesbert <mathias.gesbert@mistral.ai>
Co-authored-by: Maxime Dolores <maxime.dolores@ext.mistral.ai>
Co-authored-by: Michel Thomazo <51709227+michelTho@users.noreply.github.com>
Co-authored-by: Paul Cacheux <paul.cacheux@mistral.ai>
Co-authored-by: Quentin <quentin.torroba@mistral.ai>
Co-authored-by: Simon <80467011+sorgfresser@users.noreply.github.com>
Co-authored-by: angelapopopo <angele.lenglemetz@mistral.ai>
Co-authored-by: Mistral Vibe <vibe@mistral.ai>

AGENTS.md

@@ -154,3 +154,12 @@ guidelines:
       - Use the workspace snippets: type the prefix (e.g. acpschema, acphelpers, vibetypes, vibeconfig) and accept the suggestion to insert the import line, then change the symbol name.
       - Or ask Cursor: select the undefined symbol, then Cmd+K and request "Add the missing import for <symbol>".
       - Or copy the import from an existing file in the repo (e.g. acp.schema, acp.helpers, vibe.core.*).
+
+  - title: "No Docstrings in Tests"
+    description: >
+      Do not add docstrings to test functions, test methods, or test classes.
+      Test names should be descriptive enough to convey intent (e.g.,
+      `test_create_user_returns_403_when_unauthorized`). Docstrings in tests add
+      noise, duplicate the function name, and can suppress pytest's default output
+      (pytest displays the docstring instead of the node id when one is present).
+      Use inline comments sparingly for non-obvious setup or assertions instead.