Document no-backward-compat rule for development phase

This commit is contained in:
Jage9
2026-02-21 17:44:33 -05:00
parent 10e8395af1
commit 64ce42421c

View File

@@ -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`.