Update repo agent guidance

This commit is contained in:
J8k3 2026-05-16 10:39:46 -04:00
parent 17c004a66b
commit 46228977d6

View File

@ -12,6 +12,22 @@
- Do not commit repo changes whose only purpose is to make local Windows execution work. - Do not commit repo changes whose only purpose is to make local Windows execution work.
- If a failure appears only in the local Windows shell, do not treat it as a code regression until it reproduces in Docker/Linux. - If a failure appears only in the local Windows shell, do not treat it as a code regression until it reproduces in Docker/Linux.
## Session Start
- At the start of a session, sync with `origin/master` before doing substantive work.
- Preferred command:
- `git pull --rebase origin master`
- Only do this automatically when the worktree is clean.
- If there are local changes already present, do not pull/rebase blindly; inspect first and avoid overwriting user work.
## Commit Scope
- Keep commits small and reviewable by default.
- Prefer one commit per individual recipe change when that is practical.
- Otherwise group a commit around one coherent class of change, not multiple unrelated fixes or refactors.
- Split work before committing when a reviewer would benefit from evaluating the pieces independently.
- Only keep changes together when separating them would make the behavior harder to understand, test, or revert.
## Current Project Preference ## Current Project Preference
- For this fork, validate payment-related changes through the Docker-based workflow before judging safety to commit. - For this fork, validate payment-related changes through the Docker-based workflow before judging safety to commit.