fix: enforce commit-AND-push in all agent instructions

Commit without push is half the job. Updated CLAUDE.md, all templates
(CLAUDE.md, CONVENTIONS.md, .cursorrules, .windsurfrules, copilot-
instructions.md) to say 'commit AND push' everywhere.

Author: vivek7405

CLAUDE.md

@@ -24,12 +24,12 @@ commit messages, fix failing tests and violations. Same quality bar.
 **Every change to this framework MUST include — automatically, without the
 user asking:**
 
-### 1. Commit often
+### 1. Commit and push often
 
-**Commit after each logical unit of work** — a completed feature, a
-passing test, a doc update. Don't accumulate 50 files of uncommitted
-changes. Small focused commits with meaningful messages. No AI
-attribution trailers.
+**Commit AND push after each logical unit of work** — a completed
+feature, a passing test, a doc update. Don't accumulate uncommitted
+or unpushed changes. Small focused commits with meaningful messages.
+No AI attribution trailers. Always `git push` after committing.
 
 ### 2. Tests
 

packages/cli/templates/.cursorrules

@@ -38,8 +38,8 @@ Quality bar stays the same — just no blocking on questions.
 
 ## Git rules
 
-- COMMIT OFTEN. After each logical unit of work — don't accumulate changes.
-  Committing is automatic, the user should never have to ask.
+- COMMIT AND PUSH OFTEN. After each logical unit of work — don't accumulate
+  changes. Always `git push` after committing. This is automatic.
 - Write meaningful commit messages: what changed and why, not "update files"
 - NEVER add "Co-Authored-By", "Generated by", "AI-assisted" or similar
   attribution trailers to commits

packages/cli/templates/.github/copilot-instructions.md

@@ -22,8 +22,8 @@ If running without interactive approval (sandbox, auto-approve, etc.):
 ## Mandatory workflow
 
 Every code change must include:
-1. Commits — COMMIT OFTEN after each logical unit of work. Don't accumulate
-   changes. Committing is automatic, the user should never have to ask.
+1. Commit and push — COMMIT AND PUSH after each logical unit of work.
+   Always `git push` after committing. Don't accumulate changes. Automatic.
 2. Unit tests in test/unit/*.test.ts (server actions, components, utilities)
 3. E2E tests in test/e2e/*.test.ts for user-facing features (Puppeteer)
 4. Documentation updates (AGENTS.md for API, docs/ for user guides)

packages/cli/templates/.windsurfrules

@@ -32,8 +32,8 @@ The user should never have to ask for tests or documentation.
 
 ## Git rules
 
-- COMMIT OFTEN. After each logical unit of work — don't accumulate changes.
-  Committing is automatic, the user should never have to ask.
+- COMMIT AND PUSH OFTEN. After each logical unit of work — don't accumulate
+  changes. Always `git push` after committing. This is automatic.
 - Meaningful commit messages: what changed and why
 - NEVER add Co-Authored-By or AI attribution trailers to commits
 - Work on feature branches, never push directly to main

packages/cli/templates/CLAUDE.md

@@ -16,13 +16,13 @@ This file instructs AI coding agents on how to work in this project.
 **CRITICAL: Every code change MUST include the following — automatically,
 without the user having to ask:**
 
-### 1. Commit often (mandatory, never skip)
+### 1. Commit and push often (mandatory, never skip)
 
-**Commit after each logical unit of work** — a completed feature, a
-passing test, a doc update. Don't accumulate many files of uncommitted
-changes. Small focused commits with meaningful messages. No AI
-attribution trailers. Committing is automatic — the user should never
-have to ask.
+**Commit AND push after each logical unit of work** — a completed
+feature, a passing test, a doc update. Don't accumulate uncommitted
+or unpushed changes. Small focused commits with meaningful messages.
+No AI attribution trailers. Always `git push` after committing.
+This is automatic — the user should never have to ask.
 
 ### 2. Tests (mandatory, never skip)
 

packages/cli/templates/CONVENTIONS.md

@@ -26,9 +26,10 @@ even if the user doesn't explicitly ask.**
 
 ### Every code change must include:
 
-1. **Commits** — Commit after each logical unit of work. Small, focused
-   commits with meaningful messages. Don't accumulate dozens of changed
-   files. Committing is automatic — the user should never have to ask.
+1. **Commit and push** — Commit AND push after each logical unit of work.
+   Small, focused commits with meaningful messages. Always `git push`
+   after committing. Don't accumulate uncommitted or unpushed changes.
+   This is automatic — the user should never have to ask.
 
 2. **Tests** — Unit test for logic, E2E test for user-facing behavior.
    See the "Testing" section below for what type of test each change needs.