Revise AI tools policy for clarity and expectations

Updated the AI tools policy section to clarify usage guidelines and expectations for applicants.

Author: wslany

pages/development/google-summer-of-code/2026.md

@@ -16,10 +16,10 @@ We are thrilled to share our carefully curated project ideas for this year's Goo
 
 These ideas are just some topics we came up with, where currently nobody is working on. However, Catrobat is a project with a wide range of possibilities and we're aware of our blindspots: So let's live the spirit of Open Source and come up with improvements (e.g., new features, extensions, ...) that are related to the project and in which you're interested in. We do have many senior contributors who would be happy to mentor such a project. Don't be shy and check out the last point on the list: Your idea!
 
-## AI stance
+## AI tools policy
 {: .no_toc }
 
-We explicitly encourage applicants to use AI tools as much as they like (for brainstorming, code generation, refactoring, testing, documentation, and review). We believe this can significantly improve quality and learning when used thoughtfully. You remain fully responsible for the result: correctness, clean code, maintainability, and test quality. Please be prepared to explain and defend your design and tests (e.g., in a short video walkthrough) and do not use AI as a substitute for understanding. Also ensure that anything you submit is compatible with our license and contribution guidelines.
+You may use AI tools as much as you like (brainstorming, code generation, refactoring, tests, documentation, review). We believe this can significantly improve quality and learning when used thoughtfully. What matters is the outcome: correctness, maintainability, Clean Code and tests. You must be able to explain and justify your implementation and tests.
 
 ## General Knowledge Prerequisites for all Projects
 {: .no_toc }