chore(sync): log pulseagent.io registration outage (backend /app/api/* 502)

[iPythoning]

Summary

User reported "pulseagent.io 又无法注册了" (registration broken again). I probed the live site to diagnose, then recorded the incident in .sync/ — matching how this repo already tracks service outages (e.g. the WeChat HTTP-500 queue failures).

Diagnosis

Layer	URL	Result
Marketing site	https://pulseagent.io	✅ 200
App shell (SPA)	/app/login, /app/register	✅ 200 (static, via Cloudflare)
Registration config	/app/api/auth/registration-config	❌ 502
Register	/app/api/auth/register	❌ 502
Login	/app/api/auth/login	❌ 502
Session	/app/api/auth/me	❌ 502

Root cause: every /app/api/* route returns a Cloudflare-origin 502 Bad Gateway (server: cloudflare, 16-byte error code: 502 body), consistent across 3 retries. The static frontend is healthy; the API origin backend is down/crash-looping. The SPA hardcodes API base Bn = "/app/api", so the failing first call (GET …/registration-config) blocks the signup form. This is a full backend auth outage, not a registration-specific bug and not a frontend/DNS issue.

Scope

The pulseagent.io API backend is not part of this template repo (which ships docs, skills, deploy scripts, and the .sync/ content pipeline only). Remediation is on the backend deployment: restart/redeploy the API origin and confirm registration-config returns 200. This PR only records the incident + evidence + a recovery-verification command.

Files

• .sync/incident-2026-07-registration-502.md — full incident report + verification command
• .sync/sync-log.md — incident entry prepended

Verification

for p in registration-config register login me; do
  printf '%s -> ' "$p"
  curl -s -o /dev/null -w '%{http_code}\n' "https://pulseagent.io/app/api/auth/$p"
done
# 502 = still down · 200/4xx = recovered

🤖 Generated with Claude Code

https://claude.ai/code/session_019Jm8mfc9PqLepqS93v4H7M

---

Generated by Claude Code