From 64ce42421c7ade8717427a62896470def18e5bb6 Mon Sep 17 00:00:00 2001 From: Jage9 Date: Sat, 21 Feb 2026 17:44:33 -0500 Subject: [PATCH] Document no-backward-compat rule for development phase --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index aa99e27..6d59c4f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -23,6 +23,7 @@ ## Coding Style & Naming Conventions - TypeScript: strict typing, `camelCase`, small focused modules. - Python: PEP 8, 4 spaces, `snake_case`, typed Pydantic models. +- Backward compatibility: not required during current development phase; prefer simpler clean-cut changes over compatibility shims/migrations unless the user asks otherwise. - Python docstrings: for `server/app` changes, include module docstring, class docstring, and docstrings for public functions/methods where behavior/contracts matter. - Shared logic first: when behavior is reused across modes/features, implement it in shared helpers/modules rather than duplicating branch-specific logic. - Keep protocol changes synced in `client/src/network/protocol.ts` and `server/app/models.py`.