What problem does it solve? The Grok Bot desktop keeps only roughly the last 200 transcript entries per Bot and silently drops the oldest with every new turn, so local history can be lost without anyone noticing. This Skill turns the replica set into a pressure verdict: which replicas sit at the client cap, and whether the archive actually holds the entries the cap is about to rotate away. ## Core Features & Use Cases - Pressure read: Lists every replica with its entry count, flags each one at or above the client cap, and records the cap value and pull timestamp. - Archive verification: Confirms archived status by comparing entry counts on both sides (archive vs. replica), never trusting a manifest row, filename, or exit code alone. - Stale-archive detection: Flags archives too old to cover an at-cap replica's missing turns as the top finding, since that is history actively being lost. - Use Case: Before any cleanup that deletes local state, run the audit to get a dated report with a per-replica verdict (safe, at-cap-and-archived, or at-cap-and-exposed) and the single most consequential exposure with its required action. ## Quick Start Ask the assistant to run the disksaver audit against the current Grok Bot replica set and report which replicas are at the cap and whether the archive verifiably holds them.
