Update learning rules: docs go in the same PR, not after

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: vitbokisch

.claude/rules/workflow.md

@@ -99,15 +99,15 @@ If any step fails, fix it before pushing. Do not push broken code.
 
 ## Continuous Learning — MANDATORY
 
-After every PR, review what happened and update the rules:
+Every PR must include updates to rules and docs alongside the code changes. Don't submit code-only PRs when something was learned — update the rules in the SAME PR:
 
-- **New anti-pattern discovered?** Add it to `anti-patterns.md` with the "why" so future sessions avoid it.
-- **New development pattern established?** Add it to `development.md` so future sessions follow it consistently.
-- **API changed upstream?** Update `CLAUDE.md`, template `CLAUDE.md`, and `building.md` with the new API.
-- **Bun/TypeScript quirk found?** Document it in `development.md` under "Bun Quirks" so it's not rediscovered.
-- **Workaround added?** Document WHY in a code comment AND add to anti-patterns so it gets removed when the upstream fix lands.
+- **New anti-pattern discovered?** Add it to `anti-patterns.md` in the same commit.
+- **New development pattern established?** Add it to `development.md` in the same PR.
+- **API changed upstream?** Update `CLAUDE.md`, template `CLAUDE.md`, and `building.md` as part of the dep bump PR.
+- **Bun/TypeScript quirk found?** Document it in `development.md` under "Bun Quirks" immediately.
+- **Workaround added?** Document WHY in a code comment AND add to anti-patterns in the same commit.
 
-The rules files are your institutional memory. If you learn something in this session that would help a future session, write it down NOW — not later. Every PR is an opportunity to make the next PR better.
+The rules files are your institutional memory. Update them as you work, not as a separate follow-up. A PR that changes behavior without updating docs is incomplete.
 
 ## Context Management