Skip to content

docs: add TweetClaw social routing - #1

Open
kriptoburak wants to merge 1 commit into
MARUCIE:mainfrom
kriptoburak:codex/add-tweetclaw-social-routing
Open

docs: add TweetClaw social routing#1
kriptoburak wants to merge 1 commit into
MARUCIE:mainfrom
kriptoburak:codex/add-tweetclaw-social-routing

Conversation

@kriptoburak

Copy link
Copy Markdown

Summary

  • Adds TweetClaw to the Social Media & Community and Content & New Media Operations routing lists for X/Twitter workflows that need more than search or browser-only posting.
  • Adds README coverage with the OpenClaw install command and concrete jobs: scrape tweets, search tweets, search tweet replies, post tweets, follower export, user lookup, media, DMs, monitors, webhooks, and giveaway draws.
  • Keeps credential handling local by directing users to OpenClaw config or protected local storage instead of prompts, screenshots, issues, or exported blueprints.

Checks

  • npm ci --ignore-scripts --no-audit --no-fund
  • npx tsc --noEmit
  • Targeted route check: social routing includes tweetclaw
  • git diff --check
  • Added-line dash and sensitive-string scan
  • README URL sweep: new TweetClaw URL, GitHub, Shields, and Cloudflare signup URLs checked; localhost examples skipped; pre-existing https://openclaw-foundry.pages.dev still does not resolve and is left unchanged because the README/HANDOFF notes say the production URL migration is HITL-tracked separately.

MARUCIE pushed a commit that referenced this pull request May 18, 2026
…ys early

Signal #2 (reconciler in deploy pipeline): closed via 7cc7560 wiring
reconcile-catalog-integrity.py into web/package.json prebuild npm hook so it
fires on every `next build` (and therefore every CF Pages deploy). Re-evaluation
criterion now shifts to "≥5 of next 10 deploys carry fresh meta.reconcileSummary".

Signal #3 (live fresh-clone install verification): closed via 8-of-8 non-stub
pack coverage. Total 167 manifest items installed across 8 packs in /tmp
sandbox via live agent-foundry.pages.dev curl-pipe-bash:
  - backend-engineer 22/22 · compliance-expert 21/21 · frontend-engineer 22/22
  - product-manager 24/24 · scenario-planner 20/20 · test-engineer 22/22
  - research-analyst 21/21 · prototype-designer 15/15
Skill + MCP axes remain structural N/A until catalog gains the respective
entry types (R3.1 IDE-MCP gate auto-activates when first mcp-registry entry
appears; R2.1+R2.2 local-private gates auto-deactivate when catalog gains
publicly-installable skill entries).

Signals #1 (no new headline lies) and #4 (zero F1-F10 re-opens) remain on
30-day Lindy clock per original spec.

Closure status: 2 of 4 verify_by signals closed early. If #1+#4 fail by
2026-06-18, escalation path to programmatic PreToolUse/pre-commit hook
remains documented and ready to execute.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant