docs(skills): latency-forensics — lean-ON supersession (#683/#685 fixed; now production+QA default)

[100yenadmin]

What

Docs-only fix to .claude/skills/worldos-latency-forensics/SKILL.md, which still carried the 2026-06-05 "lean-ON is BROKEN — keep lean OFF" guidance in its REFUTED section. That guidance was superseded on 2026-06-06 by #683 (pin the lean re-ground to the engine-authoritative LIVE campaign — kills the #640 contamination root) and #685 (lean output-discipline). lean-ON is now both the production default (qa/run_duo.sh defaults CLAWDND_LEAN_BEATS:-1) and the VM QA default (qa/vm/sweep_v2.sh exports CLAWDND_LEAN_BEATS=1, "production-matching; #683/#685-fixed").

A future agent following the stale skill text would have disabled a production-default lever (and re-incurred 3–5+ min/beat Opus transcript replays).

Changes

• LEVER TAXONOMY: the "Compact scene_context digest" entry is rewritten as the shipped lean re-ground (CLAWDND_LEAN_BEATS=1), now the production AND QA default, with an explicit "do NOT turn lean OFF" warning.
• REFUTED → SUPERSEDED: the lean entry moves out of REFUTED into a new SUPERSEDED section that keeps the full 2026-06-05 A/B findings (cross-chronicle contamination + dropped beats, G3 #1 blocker: is_live_view freeze/lockout from multi-campaign divergence (3/5 personas) #640 root) as history so they aren't re-litigated, and records the fix(#640): pin lean re-ground to the engine-authoritative LIVE campaign (stop cross-chronicle contamination) #683/fix(lean): output-discipline for Opus lean re-ground + duo cold-open craft #685 fix.
• Corrects the factually wrong sentence claiming qa/vm/sweep_v2.sh "runs with lean intentionally OFF" — the script exports lean-ON and says so in its header.

No engine/content/QA-harness changes; skill doc only.

Summary by CodeRabbit

• Documentation
  • Updated internal latency forensics guidance to reflect recent improvements and clarify testing procedures.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 068dbec2-7a41-444e-88c7-ef145e415288

📥 Commits

Reviewing files that changed from the base of the PR and between a245a2c and 9dabbd4.

📒 Files selected for processing (1)

• .claude/skills/worldos-latency-forensics/SKILL.md

---

📝 Walkthrough

Walkthrough

The pull request updates latency forensics skill documentation to reflect that lean-ON behavior, previously documented as broken on 2026-06-05, was fixed by #683/#685. The changes reorganize guidance around CLAWDND_LEAN_BEATS=1 lean grounding, remove obsolete failure explanations, and add historical context to prevent re-investigation of resolved issues.

Changes

Lean behavior documentation

Layer / File(s)

Summary

Lean taxonomy and superseded history .claude/skills/worldos-latency-forensics/SKILL.md

LEVER TAXONOMY section now positions lean re-ground as production/QA default, clarifying that lean continues from persisted truth (snapshot + session-log) rather than full transcript. Removed prior "lean-ON is BROKEN" explanation from REFUTED section. Added new SUPERSEDED section documenting that 2026-06-05 breakage findings were superseded by #683/#685 fixes, stating that qa/run_duo.sh and VM sweep exports keep lean=1 by default, and instructing future reports to reproduce on post-fix builds before disabling the flag.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• electricsheephq/WorldOS#683: The fix referenced in this documentation update that resolved lean-ON breakage.
• electricsheephq/WorldOS#685: Another fix referenced in this documentation update that resolved lean-ON breakage.
• electricsheephq/WorldOS#417: Earlier PR that introduced CLAWDND_LEAN_BEATS flag and scene_context(...recent_narration...) grounding contract that this documentation clarifies.

Poem

🐰 The lean was broken, now it's mended,
Fix those beats—the truth transcended!
From snapshot-log, the scene takes shape,
No more chasing broken tape.
History's kept, but we move on,
Lean-ON is here, the old is gone! 🎯

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description comprehensively covers what changed and why, but is missing the required Licensing/CLA checklist and Validation section from the template.	Complete the pull request description by adding the Licensing/CLA checklist with checked items and a Validation section listing the checks that were run.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: updating documentation about the lean-ON feature being superseded and now the default, with reference to the specific PRs (#683/#685) that fixed it.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}