feat: wire team sync push into ship, retro, qa, and greptile skills

Add non-fatal sync steps to all 4 skill templates:
- /ship Step 8.5: write ship log JSON + push after PR creation
- /retro Step 13: push snapshot after JSON save
- /qa Phase 6.7: write qa-sync.json + push after health score
- greptile-triage: push each triage entry after history file writes

All calls use || true for zero disruption. Silent when sync not
configured.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

review/greptile-triage.md

@@ -204,6 +204,25 @@ Example entries:
 2026-03-13 | garrytan/myapp | already-fixed | lib/payments.rb | error-handling
 ```
 
+## Team Sync (non-fatal)
+
+After appending to both history files, sync each triage entry to the team store. For each triaged comment, write a JSON entry and push:
+
+```bash
+cat > /tmp/gstack-greptile-entry.json << 'GEOF'
+{
+  "date": "<YYYY-MM-DD>",
+  "repo": "<owner/repo from REMOTE_SLUG>",
+  "triage_type": "<fp|fix|already-fixed>",
+  "file_pattern": "<file-pattern>",
+  "category": "<category>"
+}
+GEOF
+~/.claude/skills/gstack/bin/gstack-sync push-greptile /tmp/gstack-greptile-entry.json 2>/dev/null || true
+```
+
+If multiple comments were triaged, push each one individually (overwrite the temp file each time). Non-fatal — failures are queued for retry. Silent if sync is not configured.
+
 ---
 
 ## Output Format