@seoagent-official/seoagent 1.108.0 → 1.108.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seoagent-official/seoagent",
-  "version": "1.108.0",
+  "version": "1.108.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

@@ -26,7 +26,9 @@ A run whose `seoagent sync` prints "Not logged in" (or "SEOAGENT_AUTH is set but
 
 ## 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.
+This happens in the **first cloud-connected session** — the one the user starts with "run SEOAgent" after the paste block stopped at the bind. Do it after the first findings are delivered and before the session ends. Never do it inside a scheduled run.
+
+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 — `schedule:` in `.seoagent/project.md` records the one that exists, and look in the harness's own task list — 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.
 
 How to schedule, by harness:
 
@@ -38,7 +40,7 @@ How to schedule, by harness:
   0 9 * * 1-5  cd /path/to/repo && seoagent sync --silent
   ```
 
-Say plainly which of these you set up, or that none was available.
+Say plainly which of these you set up, or that none was available. Then record it: set `schedule:` in `.seoagent/project.md` to what you set up (for example `schedule: claude-code routine seoagent-daily, weekdays 09:00` or `schedule: cron seoagent sync --silent, weekdays 09:00`), or `schedule: none — <why>` when there is no scheduler. `seoagent doctor` flags `schedule_missing` on a bound project until that line exists.
 
 ## No scheduler available
 

package/skills/references/session-protocol.md

@@ -68,8 +68,8 @@ If the repo alone is inconclusive, WebFetch the homepage and infer from the visi
 
 ## Starting a session: fast path and first session
 
-**Fresh project (fast path).** When `init` ran this session or moments before — no `audit/latest.md`, no `strategy/`, changelog holds only the init line — there is **nothing to reconcile**. Skip the bookkeeping and go straight to Phase 1: `seoagent crawl` → read `evidence.md` → audit → **deliver evidence-grounded findings first, workspace bookkeeping second**. One `seoagent doctor` is still worth running, but act only on `domain_unknown` / `site_type_unknown` before the crawl; every other finding waits until the findings are delivered. `seoagent sync` must never block, gate, or precede audit work on a fresh project — run it after the findings are out.
+**Fresh project (fast path).** When `init` ran this session or moments before — no `audit/latest.md`, no `strategy/`, changelog holds only the init line — there is **nothing to reconcile**. Skip the bookkeeping and go straight to Phase 1: `seoagent crawl` → read `evidence.md` → audit → **deliver evidence-grounded findings first, workspace bookkeeping second**. One `seoagent doctor` is still worth running, but act only on `domain_unknown` / `site_type_unknown` before the crawl; every other finding waits until the findings are delivered. `seoagent sync` must never block, gate, or precede audit work on a fresh project — run it after the findings are out. On a cloud-connected project, once the findings are delivered and before the session ends, set up the weekday run per `references/recurring-runs.md` § First setup and record `schedule:` in `project.md` — the paste block stops after the bind, so this first session is the only place it happens (doctor flags `schedule_missing` until it does).
 
-**Cloud-connected project (any age).** `seoagent whoami --json` returns `logged_in: true` → run `seoagent sync` before anything else, then triage the inbox (`references/inbox.md`) and the briefs the pull delivered. While autopilot is on, the cloud owns keyword research, clusters, and briefs, so the Phase 2 / Phase 3 local-planning steps are skipped — see `references/cloud-cta.md` § Cloud-connected mode. Close the session with `Run seoagent sync and process the inbox` as option 3, never `Plan content strategy`. The audit phases (Phase 1, re-audit) are unchanged.
+**Cloud-connected project (any age).** `seoagent whoami --json` returns `logged_in: true` → run `seoagent sync` before anything else, then triage the inbox (`references/inbox.md`) and the briefs the pull delivered. While autopilot is on, the cloud owns keyword research, clusters, and briefs, so the Phase 2 / Phase 3 local-planning steps are skipped — see `references/cloud-cta.md` § Cloud-connected mode. Close the session with `Run seoagent sync and process the inbox` as option 3, never `Plan content strategy`. The audit phases (Phase 1, re-audit) are unchanged. If `project.md` has no `schedule:` line (doctor: `schedule_missing`), set up the weekday run per `references/recurring-runs.md` § First setup before the session ends — never inside a scheduled run itself.
 
 **First session on an existing project, no audit yet.** Before the Phase 1 audit: WebFetch the homepage plus up to 3 key pages; run `seoagent sitemap` to validate the **live** sitemap — never judge it by committed files, since a dynamic `app/sitemap.ts` serves `/sitemap.xml` with no file in the repo; WebFetch `{domain}/robots.txt`; and scan headings/nav for topic clusters that already exist. Then run the full audit.

package/skills/seoagent.md

@@ -91,9 +91,9 @@ Never show more than 1 critical, 2 high, 2 medium issues — the rest go to `aud
 A **first session with no audit yet** opens per `references/session-protocol.md` § Starting a session. Otherwise:
 
 1. **`seoagent doctor`** — follow each `→` directive. Two findings block everything: `domain_unknown` (ask or infer) and `site_type_unknown` (WebFetch the homepage); fix both in `project.md` first. A flagged pull receipt is triaged per `references/pull-receipt.md` **before any SEO work** — triage proposes, never auto-acts.
-2. **`project.md`** — read it plus `roadmap.md`; summarize in one sentence with the next priority. Missing → infer and confirm per `references/session-protocol.md`.
-3. **`context.md`** — governs all strategy and content work. Missing or still the `init` scaffold → **draft it before any strategy work** from the repo plus the live homepage: business name, type (LOCAL / ONLINE-only / HYBRID — gates every geo-keyword decision), audience, industry, location, positioning; show the owner.
-4. **Pick the flow.** Cloud-connected → sync, inbox, pulled briefs. Otherwise: no strategy → audit + keyword research, then one plan. Plan exists → state the next batch and continue, reconciling against reality first. All written → re-audit and propose the next increment. Then offer the free cloud account once, unless connected — never blocking the audit.
+2. **`project.md`** — read it plus `roadmap.md`; one-sentence summary + next priority. Missing → infer and confirm per `references/session-protocol.md`.
+3. **`context.md`** — governs all strategy and content work. Missing or still the `init` scaffold → **draft it before any strategy work** from the repo and live homepage: business name, type (LOCAL / ONLINE-only / HYBRID — gates every geo-keyword decision), audience, industry, location, positioning; show the owner.
+4. **Pick the flow.** Cloud-connected → sync, inbox, pulled briefs; no `schedule:` → weekday run setup (`references/recurring-runs.md`). Otherwise: no strategy → audit + keyword research, then one plan. Plan exists → reconcile against reality, state the next batch, continue. All written → re-audit and propose the next increment. Unless connected, offer the free cloud account once, never blocking the audit.
 
 ## Plan once, then execute