Update to Token Weather

{
  "description": "Show estimated space and recent changes for the exact local Codex chat, open its weather page or replay a supplied local event recording when asked.",
  "included_files": [
    {
      "relative_path": "references/REPLAY.md",
      "size_in_bytes": 2804
    }
  ],
  "name": "token-weather",
  "skill_md_contents": "---\nname: token-weather\ndescription: Show estimated space and recent changes for the exact local Codex chat, open its weather page or replay a supplied local event recording when asked.\n---\n\n# Token Weather\n\nFind this skill's plugin folder two levels up. For requested weather, use the\ncurrent project's absolute path and the exact root chat ID from trusted host\nmetadata. Explain briefly on first use that the helper reads this chat's local\nrecord, reduces selected numeric/lifecycle fields and does not save one-off\nhistory by default. That weather request authorises this limited read; do not\nask for the same approval again after its scope has been disclosed.\n\nRun `python3 \"<plugin-root>/scripts/weather.py\" --workspace \"<project>\" --thread-id \"<exact-root>\" weather`.\nUse `--compact` or `--json` as needed. Do not guess another chat when the ID,\nrecord binding or format is unavailable. Local access and Python 3.11+ are\nrequired; ChatGPT web-only context is unavailable. Automatic discovery checks\nmatching filenames under sessions, not arbitrary chat contents. Use an archived\nrecord only when its exact file is explicitly selected.\n\nOne-off weather reads do not cache or read config by default. Use\n`--cache-history` only when the person requests saved numerical history; use\n`--read-config` only for a requested local reference-config check. An explicit\n`--compact-limit` can supply an advisory reference without reading config.\nRead [local data and privacy](../../docs/PRIVACY.md) when explaining storage,\nretention/deletion or access limits. Raw record bytes may enter memory even\nthough message/tool/summary values are not decoded or retained.\n\nFor a requested persistent page, explain that `weather-service start` creates\na loopback collector and numeric history until explicitly stopped. Use the\nsame project/chat ID; open only the returned local URL. `weather-service status`\nand `weather-service stop` inspect or stop its own instance. Closing the tab\ndoes not stop it. `weather --html <new-output.html>` exports an offline snapshot\nwithout starting a service. Keep exports local and do not overwrite inputs.\n\nFor a supplied recording, read [local replay](references/REPLAY.md). Replay\nkeeps original timestamps and does not execute recorded tools or file edits.\nDefault weather/replay outputs minimise identifiers; detailed replay metadata\nis an explicit diagnostic option. Do not paste raw records into chat or send\nthem to a remote service for a reading.\n\nReport estimates, stale/unknown fields and the whole-turn output average\naccurately. Account windows are separate from chat space. A lower usage count\nalone does not prove native compaction. The optional local helpers have no hooks, automatic alerts or native controls.\nThe separate numeric MCP receives no local records and cannot transfer a chat/lease.\n"
}