chore(growth): keep playbook internal and trim public x copy

Author: Rex

docs-site/blog/index.md

@@ -6,7 +6,6 @@ Practical notes for builders choosing an Agent OS and scaling from local prototy
 
 - [What Is LoopForge? (Formerly LoopForge)](what-is-loopforge.md)
 - [LoopForge vs OpenFang/OpenClaw (Builder View)](rexos-vs-openfang-openclaw.md)
-- [OpenClaw Trend: LoopForge Optimization + X Playbook](openclaw-trend-x-playbook.md)
 - [Editorial Calendar](editorial-calendar.md)
 
 ## Suggested reading order
@@ -15,5 +14,4 @@ Practical notes for builders choosing an Agent OS and scaling from local prototy
 2. First successful run: [New User Walkthrough](../tutorials/new-user-walkthrough.md)
 3. Practical templates: [10 Copy/Paste Tasks](../examples/case-tasks/ten-copy-paste-tasks.md)
 4. Positioning and alternatives: [LoopForge vs OpenFang/OpenClaw (Builder View)](rexos-vs-openfang-openclaw.md)
-5. This week's growth playbook: [OpenClaw Trend: LoopForge Optimization + X Playbook](openclaw-trend-x-playbook.md)
-6. Publishing rhythm: [Editorial Calendar](editorial-calendar.md)
+5. Publishing rhythm: [Editorial Calendar](editorial-calendar.md)

docs-site/blog/openclaw-trend-x-playbook.md

@@ -6,7 +6,6 @@
 
 - [什么是 LoopForge？（原 RexOS）](what-is-loopforge.md)
 - [LoopForge 与 OpenFang/OpenClaw 对比（开发者视角）](rexos-vs-openfang-openclaw.md)
-- [OpenClaw 风口：LoopForge 优化与 X 推广作战页](openclaw-trend-x-playbook.md)
 - [内容发布日历](editorial-calendar.md)
 
 ## 建议阅读顺序
@@ -15,5 +14,4 @@
 2. 再跑通首条链路： [新人复习](../tutorials/new-user-walkthrough.md)
 3. 最后套模板实操： [10 个可复制任务](../examples/case-tasks/ten-copy-paste-tasks.md)
 4. 对比竞品场景： [LoopForge 与 OpenFang/OpenClaw 对比（开发者视角）](rexos-vs-openfang-openclaw.md)
-5. 本周增长打法： [OpenClaw 风口：LoopForge 优化与 X 推广作战页](openclaw-trend-x-playbook.md)
-6. 固定输出节奏： [内容发布日历](editorial-calendar.md)
+5. 固定输出节奏： [内容发布日历](editorial-calendar.md)

docs-site/zh-CN/blog/index.md

@@ -14,7 +14,3 @@ OpenClaw owns multi-channel assistant breadth. LoopForge focuses on code deliver
 Shipping with AI should be measurable. We now log onboarding outcomes and failure categories by default, then roll up daily reports for reliability baselines. This is the kind of evidence teams can act on. #LoopForge #DevRel
 ---
 Trend hook: "assistant experience is hot". Counter-position: "engineering reliability is scarce". If you care about passing verifiers and preserving artifact trails, start from LoopForge, not from a generic chat shell. #OpenClaw #AIInfra
----
-Before posting to X, lint your copy in repo:
-`python3 scripts/x_post_lint.py --file docs/marketing/openclaw-trend-x-posts.en.txt --limit 280 --warn-at 260`
-No surprises at publish time.

docs-site/zh-CN/blog/openclaw-trend-x-playbook.md

@@ -14,6 +14,3 @@ OpenClaw 的强项是多渠道个人助手覆盖；LoopForge 的强项是工程
 AI 落地要看证据，不看口号。我们默认记录 onboarding 成功/失败与失败类别，再做日聚合报告。这样团队每周都能看到真实改进。#LoopForge #工程效率
 ---
 借 OpenClaw 风口的正确姿势：不抄“助手叙事”，而是放大“可复现交付”。如果你在做代码任务闭环，先跑 LoopForge 的 harness 链路。#OpenClaw #AIInfra #LoopForge
----
-发 X 前先验字数，避免临门改稿：
-`python3 scripts/x_post_lint.py --file docs/marketing/openclaw-trend-x-posts.zh-CN.txt --limit 280 --warn-at 260`