Document reliable git push workflow

agent.md

@@ -21,7 +21,18 @@ This project replaces the Excel/VBA workflow named `Catalog maker - 20` with a N
 - Use short, descriptive commit messages that state the completed change.
 - Never commit `.env`, `config/local.json`, passwords, tokens, the Excel workbook or database dumps.
 - Before the first push, initialize Git if needed, configure the project remote and create an initial baseline commit from safe files only.
-- If a push fails, do not expose credentials in the terminal output or in chat; report the failure without printing secrets.
+- Always use Git with the explicit safe directory flag in this workspace:
+  `git -c safe.directory=D:/Codex/01-projekty/catalog-meaker-by-magic-ai ...`
+- Do not combine `git add`, `git commit` and `git push` into one shell command. Run them as separate steps and inspect the output after each step.
+- Reliable push sequence:
+  1. `git -c safe.directory=D:/Codex/01-projekty/catalog-meaker-by-magic-ai status --short`
+  2. `git -c safe.directory=D:/Codex/01-projekty/catalog-meaker-by-magic-ai add <explicit safe files>`
+  3. `git -c safe.directory=D:/Codex/01-projekty/catalog-meaker-by-magic-ai commit -m "<short message>"`
+  4. `git -c safe.directory=D:/Codex/01-projekty/catalog-meaker-by-magic-ai push`
+  5. `git -c safe.directory=D:/Codex/01-projekty/catalog-meaker-by-magic-ai status --short`
+- If push returns `Failed to authenticate user`, retry the same push command once. If it fails again, stop and report the push failure without printing secrets.
+- If there are unrelated modified files, leave them alone. Add only the files that belong to the completed step.
+- For documentation-only changes, tests are optional; for code, UI, scraper or database behavior changes, run the relevant build/test command before committing.
 
 ## UI inspection workflow