fix(formula): Clarify commits ahead report for crew on main (gt-9yz70)

Update mol-sync-workspace generate-report step to distinguish:
- Feature branches: 'Commits ahead of main: N'
- Crew on main: 'Unpushed commits: N'

The 'commits ahead of main' was confusing for crew workers who work
directly on main branch. 'Unpushed commits' is clearer for that case.

Also added explicit git commands for checking divergence.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

.beads/formulas/mol-sync-workspace.formula.toml

@@ -412,14 +412,24 @@ needs = ["run-tests"]
 description = """
 Summarize sync results for broadcast response.
 
-**Report format:**
+**Git status check:**
+```bash
+# Get current branch
+BRANCH=$(git rev-parse --abbrev-ref HEAD)
+
+# Check divergence from origin/main
+BEHIND=$(git rev-list HEAD..origin/main --count)
+AHEAD=$(git rev-list origin/main..HEAD --count)
+```
+
+**Report format (for feature branches):**
 ```
 SYNC COMPLETE: <agent-name>
 
 Git:
   - Branch: <branch>
-  - Commits behind main: 0
-  - Commits ahead: <n>
+  - Commits behind main: <n>
+  - Commits ahead of main: <n>
   - Conflicts resolved: <y/n, details if yes>
 
 Beads:
@@ -434,6 +444,27 @@ Worktrees cleaned: <count>
 Ready for work: YES | NO (<reason>)
 ```
 
+**Report format (for crew on main):**
+
+When the agent is on the main branch directly (common for crew workers),
+use "Unpushed commits" instead of "Commits ahead of main":
+
+```
+SYNC COMPLETE: <agent-name>
+
+Git:
+  - Branch: main
+  - Commits behind origin: <n>
+  - Unpushed commits: <n>
+  - Conflicts resolved: <y/n, details if yes>
+...
+```
+
+This distinction is important because:
+- Crew workers often work directly on main
+- "Commits ahead of main" is confusing when you ARE on main
+- "Unpushed commits" is clearer - it means local work not yet on origin
+
 **Exit criteria:** Report generated."""
 
 [[steps]]