fix: rename blocked sync reason to out-of-sync

Co-Authored-By: Codex <noreply@anthropic.com>

.claude/skills/sync-nowai-leaderboard/SKILL.md

@@ -50,8 +50,8 @@ From the repo root:
   `message/attachments` envelope that template expects — not a raw MessageCard.
 - Cards: green ✅ success (with "Open staging" button), red ❌ failure, amber ⚠️
   sanity-gate abort, amber ⚠️ blocked preflight warning (dirty worktree / wrong
-  branch / fetch failure / local main out of sync with `origin/main`), blue 📋
-  Friday heartbeat (no changes detected — shows last date
+  branch / fetch failure / local main out-of-sync with `origin/main`), blue 📋
+  Friday heartbeat (no changes detected — shows the last date
   `data/leaderboard.json` actually changed). No card on "no changes" Mon–Thu.
 - The daily 14:00 launchd job (`~/.nowai-sync/`) loads `TEAMS_WEBHOOK_URL` from
   `.env`, posts blocked-preflight warnings through `notify-blocked.mjs`, and

.claude/skills/sync-nowai-leaderboard/lib/blocked-notify.mjs

@@ -2,6 +2,8 @@ const REASON_LABELS = {
   'dirty-worktree': 'Worktree has uncommitted files',
   'wrong-branch': 'Current branch is not main',
   'fetch-failed': 'git fetch origin main failed',
+  'out-of-sync': 'Local main is not exactly in sync with origin/main',
+  // Backward-compatible alias for older wrapper revisions.
   'behind-or-diverged': 'Local main is not exactly in sync with origin/main',
 };
 

.claude/skills/sync-nowai-leaderboard/test/blocked-notify.test.mjs

@@ -22,9 +22,9 @@ test('buildBlockedNotification maps dirty-worktree to a warning card payload', (
   ]);
 });
 
-test('buildBlockedNotification uses exact-sync wording for local-ahead blocked runs', () => {
+test('buildBlockedNotification uses out-of-sync as the primary exact-sync reason', () => {
   const out = buildBlockedNotification({
-    reason: 'behind-or-diverged',
+    reason: 'out-of-sync',
     facts: [['Branch', 'main'], ['RemoteAhead', '0'], ['LocalAhead', '1']],
     now: new Date('2026-07-01T21:00:00Z'),
   });
@@ -39,13 +39,13 @@ test('buildBlockedNotification uses exact-sync wording for local-ahead blocked r
 
 test('parseBlockedCliArgs accepts repeated --fact pairs', () => {
   const out = parseBlockedCliArgs([
-    '--reason', 'behind-or-diverged',
+    '--reason', 'out-of-sync',
     '--fact', 'Branch=main',
     '--fact', 'RemoteAhead=2',
     '--fact', 'LocalAhead=0',
   ]);
 
-  assert.equal(out.reason, 'behind-or-diverged');
+  assert.equal(out.reason, 'out-of-sync');
   assert.deepEqual(out.facts, [
     ['Branch', 'main'],
     ['RemoteAhead', '2'],
@@ -53,6 +53,19 @@ test('parseBlockedCliArgs accepts repeated --fact pairs', () => {
   ]);
 });
 
+test('buildBlockedNotification still accepts the legacy behind-or-diverged alias', () => {
+  const out = buildBlockedNotification({
+    reason: 'behind-or-diverged',
+    facts: [['Branch', 'main']],
+    now: new Date('2026-07-01T21:00:00Z'),
+  });
+
+  assert.deepEqual(out.facts, [
+    ['Reason', 'Local main is not exactly in sync with origin/main'],
+    ['Branch', 'main'],
+  ]);
+});
+
 test('parseBlockedCliArgs normalizes lowercase fact keys for stable payload titles', () => {
   const parsed = parseBlockedCliArgs([
     '--reason', 'dirty-worktree',