ops-social-planner

# /ops-social-planner — engine-agnostic planned-content viewer Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). Read-only dashboard of **every** scheduled post and ad, grouped **identity/project → channel → time**, **regardless of posting engine**. Personal/founder identity and project brands stay strictly separated (see `/ops-socials` identity rules). See `SPEC.md` for the full design. ## What it does 1. `bin/ops-social-planner collect` reads `$PREFS_PATH/preferences.json` (`marketing.social_identities.personal.*` + `marketing.projects.*.social`), dispatches a **per-engine fetcher** keyed on `social.engine.primary`, normalizes to one schema, and writes `$OPS_DATA_DIR/social-planner/state.json` (**owner data — never committed**, Rule 0). 2. It then serves the static UI (`ui/`) on localhost and opens the browser. ## Engines | `engine.primary` | Source | Status | | ------------------------- | -------------------------------------------------------------------------------------- | ---------------------------- | | `typefully` | `GET /v2/social-sets/{id}/drafts` (Bearer; key from `~/.config/typefully/config.json`) | ✅ wired ...