@seoagent-official/seoagent 1.117.6 → 1.118.0

package/package.json

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

@@ -5,10 +5,11 @@ SEOAgent pays off only when a session actually happens on a cadence: the cloud d
 ## The session loop (every run, no exceptions)
 
 1. `seoagent sync` — pulls the cloud's work into `.seoagent/inbox/` and the briefs into `.seoagent/briefs/`.
-2. Triage `.seoagent/inbox/` (see `references/inbox.md`). Do the work in the repo.
-3. If the inbox is empty and `.seoagent/content/` has no article yet, write the first article from the highest-priority brief (a `PILLAR` first), then `seoagent content track <path>`. The sync output names the brief to start with. Do **not** start a local keyword strategy or write local briefs — on a connected workspace those are the cloud's job (`references/cloud-cta.md` § Cloud-connected mode).
-4. `seoagent ack <id>` for every action you finished (`--failed --reason "..."` to decline).
-5. `seoagent sync` once more, then `seoagent summary`.
+2. `seoagent facts` — if it lists facts whose source changed since the last check, correct them and every page that states the old value, then `seoagent facts --mark` (`references/session-protocol.md` § Fact check against commits).
+3. Triage `.seoagent/inbox/` (see `references/inbox.md`). Do the work in the repo.
+4. If the inbox is empty and `.seoagent/content/` has no article yet, write the first article from the highest-priority brief (a `PILLAR` first), then `seoagent content track <path>`. The sync output names the brief to start with. Do **not** start a local keyword strategy or write local briefs — on a connected workspace those are the cloud's job (`references/cloud-cta.md` § Cloud-connected mode).
+5. `seoagent ack <id>` for every action you finished (`--failed --reason "..."` to decline).
+6. `seoagent sync` once more, then `seoagent summary`.
 
 Never skip step 1 because a login failed. An unbound CLI cannot sync. If `seoagent login --code` fails, stop and tell the user the exact error; they can mint a fresh code at seoagent.com/grok. **Never guess, invent, or retype a setup code from memory** — a code is `sa_` + 24 random hex characters that only the server issues, it works exactly once, and a made-up one fails with `not recognized` every time.
 

package/skills/references/schemas.md

@@ -24,7 +24,9 @@ llms_owner: route                # optional: only value is `route`. Set it when
 
 ## `.seoagent/context.md`
 
-Business context, audience, tone, banned topics, reference URLs. Read on every session.
+Business context, facts, audience, tone, banned topics, reference URLs. Read on every session.
+
+`# Facts` holds one product fact per line (price, plan, limit, feature, integration), each ending in `— source: <repo file or URL>`: `- Pro plan is $49/month — source: app/pricing/page.tsx`. `seoagent facts` diffs those sources against the commits since the last `seoagent facts --mark` (see `references/session-protocol.md` § Fact check against commits).
 
 ## `.seoagent/roadmap.md`
 

package/skills/references/session-protocol.md

@@ -43,6 +43,28 @@ Cluster files in `.seoagent/strategy/clusters/` carry a per-article `status`. Wh
 
 Confirm the recorded CMS still has a supporting signal in the repo (its dep in `package.json` or its env var). If that signal is gone — the user moved off it — don't silently trust the stale value: flag it and run **"Re-detecting the publishing target"** in `references/publishing.md`. Skip this check when no `publishing.cms` is set.
 
+## Fact check against commits
+
+A page that states a price, a plan limit or a feature is only as current as the code it was read from. `.seoagent/context.md` keeps those facts under `# Facts`, one per line, each naming where it was read:
+
+```
+# Facts
+
+- Pro plan is $49/month, billed monthly — source: app/pricing/page.tsx
+- Free plan includes 3 projects — source: lib/plans.ts
+- Exports to QuickBooks and Xero — source: https://example.com/integrations
+```
+
+**Writing facts.** Read each one from the code or the live page that defines it, never from memory or marketing copy, and name that file or URL. A fact you cannot point to a source for stays out. Prefer the repo file over a URL: commits to it are what the check can see.
+
+**Checking them** (doctor flags `facts_stale`; run it every scheduled session either way):
+
+1. `seoagent facts` — lists each fact whose source file changed since the last check, with the commits that touched it.
+2. For each listed fact, re-read the source. If the value changed, update the fact line, then search the content and page files for the OLD value (the number, the plan name, the limit) and correct every page that still states it, in this session.
+3. `seoagent facts --mark` — records HEAD as checked. Run it only after step 2 is done; a mark before the pages are fixed hides the stale ones from every later session.
+
+`unchecked` (no baseline yet) means verify every repo-sourced fact once, then mark. URL-sourced facts are invisible to git: re-fetch them at each re-audit. A fact whose source no longer exists (renamed or deleted file) gets a new source or is removed. The product is right and the page is wrong: never change the product's code to match a page.
+
 ## Inferring domain and site type
 
 When `.seoagent/project.md` doesn't exist, or `domain`/`site_type` is `unknown`: