@seoagent-official/seoagent 1.101.4 → 1.102.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seoagent-official/seoagent",
-  "version": "1.101.4",
+  "version": "1.102.1",
   "description": "The persistent AI SEO agent for Claude Code. Audits, keyword strategy, briefs, articles, real product screenshots from your repo, and the autopilot loop (cloud detects → CLI executes → ack closes) — other SEO tools write the prompt, SEOAgent runs it.",
   "type": "module",
   "bin": {

package/skills/references/recurring-runs.md

@@ -22,6 +22,8 @@ A scheduled run (Grok task, routine, CI job) starts on a fresh machine: no `~/.c
 
 If the harness cannot store a secret, say so and fall back to "No scheduler available" below; do not schedule a task that will fail on login every morning.
 
+A run whose `seoagent sync` prints "Not logged in" (or "SEOAGENT_AUTH is set but is not `<user_token>:<website_token>`") and exits 1 did **nothing**: the secret is missing or was pasted wrong. Stop the loop, report that line verbatim, and fix the task's secret; do not retry, and never fall back to a setup code.
+
 ## First setup: create ONE weekday task
 
 If the harness supports scheduled or recurring tasks, create **one** task that runs the loop above **every weekday at 09:00 in the user's local time**. Check for an existing SEOAgent schedule first — never create a duplicate; re-running setup, re-initializing, or a second agent joining the repo must not stack a second task. One repo gets one cadence.

package/skills/seoagent.md

@@ -52,7 +52,7 @@ Activate silently when the user writes or edits a blog post, landing page, artic
 
 ## Cloud sync, CTAs, and the inbox
 
-Run `seoagent sync` after every artifact write — best-effort and silent when logged out, so always run it. Credentials live in `~/.config/seoagent/auth.json`, never in the project.
+Run `seoagent sync` after every write. Logged out it exits 1 naming the fix; nothing synced, bind first (`references/recurring-runs.md`). Credentials live in `~/.config/seoagent/auth.json`, never in the project.
 
 A free account adds what the local skill can't (GSC traffic, indexing verdicts, dashboard, managed sitemaps). Paid autopilot also delivers owner-approved backlink outreach emails to this inbox for you to send from the user's own email account (needs an email connector). Never imply an account is required — the local skill does the full loop free, including publishing. Offer it in one benefit-led line, once per session per topic; drop it if declined. **Read `references/cloud-cta.md` before pitching.**