docs: add TweetClaw workflow and repair Wiki safety

[kriptoburak]

Summary

• add a current TweetClaw workflow for gathering public X context and storing reviewed summaries in Membase Wiki
• include examples/ in the npm package so the README workflow remains available after installation
• remove the README banner whose GitHub attachment returns HTTP 404
• reject sensitive Wiki content locally without triggering the update checker or any network request
• clear capture timers and buffers between independent runs so retries cannot leak into another client
• merge the current upstream v0.5.0 changes and drop stale Biome metadata from the earlier branch

Validation

• bun test: 42 passed, 0 failed
• randomized src/membase-tools.test.ts seeds 101, 202, and 303: 24 passed each
• bun run check-types
• bun run lint: 29 files checked with no findings
• bun run build: 22 modules bundled
• npm pack --dry-run --json: 28 files, including examples/tweetclaw-x-memory.md and excluding tests
• README and example link checks; the Discord invite independently returns HTTP 200
• git diff --check plus dash and sensitive-string scans
• npm view @xquik/tweetclaw version openclaw.install --json: current 1.6.37 ClawHub install metadata confirmed

[kriptoburak]

Repair update is live in 63252296fa609fc84d5abeab6315217e3e741aa6.

I refreshed the branch onto current upstream v0.5.0, updated the TweetClaw install and Membase Wiki workflow, and kept the Xquik integration intact.

The same update includes 3 independent repository repairs:

• removes the README banner whose attachment returns HTTP 404
• keeps secret-content rejection fully local, with 0 API or update-check requests
• clears capture state between independent runs, fixing randomized retry leakage

Validation is green: 42/42 tests, randomized seeds 101/202/303, TypeScript, Biome, build, npm pack, links, and diff safety checks.