Add explicit approval gates for discussion and issue comments

Author: cristianrgreco

AGENTS.md

@@ -29,12 +29,13 @@ It captures practical rules that prevent avoidable CI and PR churn.
 2. Create a branch prefixed with `codex/`.
 3. Implement scoped changes only.
 4. Run required checks: `npm run format`, `npm run lint`, and targeted tests.
-5. Verify git diff only contains intended files.
+5. Verify git diff only contains intended files. If changes are still being discussed, share the diff and get user approval before committing or pushing.
 6. Commit with focused message(s), using `git commit --no-verify`.
-7. Push branch.
+7. Push branch. Ask for explicit user permission before any force push.
 8. Open PR against `main` using a human-readable title (no `feat(...)` / `fix(...)` prefixes).
-9. Add labels for both change type and semantic version impact.
-10. Ensure PR body includes:
+9. Before posting any comment on GitHub issues or PRs, share the proposed message with the user and get explicit approval.
+10. Add labels for both change type and semantic version impact.
+11. Ensure PR body includes:
     - summary of changes
     - verification commands run
     - test results summary