openclaw - 💡(How to fix) Fix Bootstrap health check: auto-detect oversized MD files and suggest bootstrap-optimizer

Summary

Add a bootstrap file size check in openclaw doctor or HEARTBEAT that warns when bootstrap MD files exceed a size threshold and suggests installing bootstrap-optimizer skill to fix it.

Problem to solve

Bootstrap MD files (MEMORY.md, TOOLS.md, AGENTS.md, etc.) grow over time with no automatic detection mechanism. Users discover the problem only when performance degrades — there is no proactive warning.

TOOLS.md is a known case: it routinely exceeds 12KB, making it expensive to load at every session startup. Users have no way to know this is the cause of slow startup or context pollution.

Proposed solution

In openclaw doctor or as a startup HEARTBEAT check, run a lightweight scan of bootstrap files and emit a warning if any exceed a size threshold (e.g., TOOLS.md > 3KB, or total bootstrap size > 20KB). The warning should include:

1. Which file is oversized
2. Why it matters (load time impact, context pollution)
3. A direct command to install the bootstrap-optimizer skill that fixes it: clawhub install bootstrap-optimizer

This does not change core logic — it is a diagnostic + referral mechanism.

Alternatives considered

• Leave it to users to discover manually — current state, leads to prolonged performance issues
• Build this into OpenClaw core as a CLI command — requires more implementation work and ongoing maintenance; the bootstrap-optimizer ClawHub skill already handles the actual fix

Impact

• Affected users: anyone whose bootstrap files have grown unchecked
• Severity: annoying — not critical, but erodes trust in startup performance
• Frequency: very common; most long-running deployments have this problem
• Consequence: slow startup, context pollution, user does not know why