Add agent rules for auth and versioning
This commit is contained in:
@@ -2,6 +2,13 @@
|
||||
|
||||
This documentation workspace uses Taskmaster as the source of truth for agent work.
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- Repository-wide operating rules live in `../RTK.md`; follow them in addition to this file.
|
||||
- For product or code changes that affect frontend or backend, keep `frontend` and `backend` package versions/build numbers bumped together and synchronized unless the user explicitly asks otherwise.
|
||||
- Preserve Telegram Mini App auth retry behavior: `/api/auth/telegram` must accept repeated valid `initData` for the same launch session; replay rejection belongs only on one-time routes such as webhook/session creation.
|
||||
- In the final response, mention version/build bumps and verification commands when they were part of the work.
|
||||
|
||||
## Taskmaster Workflow
|
||||
|
||||
- Before choosing implementation or documentation work, run `task-master next` from the repository root.
|
||||
|
||||
Reference in New Issue
Block a user