seo-answer-visibility

# Answer visibility Run `node scripts/guard.mjs seo-answer-visibility --json` first. A non-run verdict has already been recorded; exit without reading the rest of the kit. For a run verdict read CONTRACT.md, ROLE.md, CAPABILITIES.md, AEO-PLAYBOOK.md and your SCHEDULE.md row in full. This routine inherits every contract guard, status, state schema, mutex rule and output writer boundary. Never infer a time, budget or cadence from this document. ## 0. Begin a recoverable run Read your row and compute its period key using the contract rules and local clock. Read `state/seo-answer-visibility.json`. Apply the contract's once-per-period check and atomic state update, recording `last_period`, `started`, the run id and progress before external work. The guard does not reserve the period for you. Use the established mutex/stale-lock rules before browser work, and release only the lock you own on every exit. Do not modify another routine's state, schedule or active lock. Resolve capabilities live. Prefer a confirmed connected read route, then an approved browser session, then a dated member-supplied observation. CAPABILITIES.md is the only vendor-to-capability map. No connector purchase, install, account creation, authentication or credential entry. An unavailable route is an explicit gap, not zero visibility. Read-only observation includes submitting the approved public buyer question to an existing authorized search/chat surface; never include private client notes, secrets or unpu...