Sync messaging: retired, not paused/rebuilt

[AnobleSCM]

Summary

Small truthfulness fix before the 0.2.1 npm publish (version stays 0.2.1 — this rides the same unpublished release). The CLI and README still claimed devcat.dev was "being rebuilt" and that "sync returns with the site." Both are now false: the dynamic devcat.dev app is permanently retired, and hosted sync/profiles are not coming back absent an explicit evidence gate nobody should promise.

• src/cli.ts: sync command description — (paused while the site is rebuilt) → (hosted sync retired)
• src/commands/sync.ts: doc comment above the message constant no longer says "being rebuilt" or "delete this gate when devcat.dev is back"; SYNC_PAUSED_MESSAGE now reads:

  Profile sync is retired — devcat.dev no longer hosts profiles. Your local stack report still works — run npx devcat-cli.

• test/integration/sync.paused.test.ts: header comment, describe title, and the message assertion updated to match (red → green verified locally: updated the test first, confirmed it failed against the unchanged message, then fixed the source).
• README.md: Commands table row, the sync env-var sentence, the DEVCAT_SYNC_ENABLED table row, and the whole "Profile sync" section (heading, intro, quoted output block, "Sync returns with the site." sentence removed, self-host paragraph reframed as "hosted service retired; self-host path remains"). The quoted terminal block is byte-identical to the actual runtime stderr line (verified against a failing-test diff, not just eyeballed).
• CHANGELOG.md: added one bullet to the existing 0.2.1 entry noting the sync messaging change. The 0.2.0 historical entry (which still says "politely paused while devcat.dev is offline") is untouched — it's a record of what shipped then, not a current claim.

Also grepped the whole tracked tree for rebuilt, returns with the site, while the site, comes back, paused, temporar*, and currently unavailable. Two other hits were investigated and left alone as out of scope:

• src/lib/errorMap.ts sync_disabled → "DevCat sync is temporarily disabled. Try again shortly." — this is a generic mapped message for an API-returned error code on the (still-functional) self-host path, not a claim about devcat.dev's retirement.
• test/unit/auth/deviceFlow.test.ts — an MSW-mocked HTTP 500 fixture body ("Service temporarily unavailable"), never shown to a real user.

No behavior changes beyond these strings: sync still exits immediately with the same exit code (1) when the hosted default applies; scan/--markdown/--json/logout untouched.

Gate evidence (this worktree, npm ci --no-audit --no-fund per AGENTS.md)

• npm run lint — clean (eslint ., 0 findings)
• npm run build — clean (tsc + chmod, exit 0)
• npm test — 252/252 passing, 33/33 test files
• npm pack --dry-run — 67 files, devcat-cli@0.2.1, package size 51.5 kB

Test plan

• npm ci --no-audit --no-fund && npm run lint && npm run build && npm test && npm pack --dry-run all green in a fresh worktree off origin/main
• Confirmed red→green on the updated assertion (test failed against the old message before the source fix, passed after)
• Re-grepped tracked tree post-edit for stale terms; only the untouched 0.2.0 CHANGELOG entry and internal SYNC_PAUSED_MESSAGE/isSyncPaused identifier names remain (left as-is — not user-facing, no behavior change, out of scope for a wording-only fix)
• Cross-vendor review (follows this PR)

Not merged, not published — draft only, per instructions.

🤖 Generated with Claude Code

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.