Update to Token Weather

{
  "description": "Check local runtime access and help a person use the Skills-only Token Weather package in a Codex project.",
  "included_files": [],
  "name": "token-weather-setup",
  "skill_md_contents": "---\nname: token-weather-setup\ndescription: Check local runtime access and help a person use the Skills-only Token Weather package in a Codex project.\n---\n\n# Set up Token Weather\n\nFind this skill's plugin folder two levels up. Run\n`python3 \"<plugin-root>/scripts/weather.py\" --help` to check the bundled helper.\nIt needs Python 3.11 or later; if unavailable, explain how to choose an already\ninstalled interpreter with TOKEN_WEATHER_PYTHON. Do not download dependencies\nor change Codex's installed settings to check setup.\n\nUse the current project's absolute workspace and exact current root chat ID\nfrom trusted host metadata. Follow token-weather for one on-demand reading.\nIf local access or the record format is unavailable, explain the limitation;\ndo not guess a different chat or invent numbers.\n\nBefore first data access, explain the limited source and storage scope in\n[local data and privacy](../../docs/PRIVACY.md). A one-off reading stores no\nhistory and reads no config by default. Saved history and the persistent page\nare explicit choices. `privacy-status` reports chosen local data locations\nwithout creating folders; it does not delete anything.\n\nThis edition includes a separate numeric MCP and optional local helper scripts.\nThis local setup does not connect/deploy the MCP; it has no lifecycle hooks or automatic alerts. Do not register a project hook bridge,\nchange trust settings or enable a server connection. The full local plugin\nremains a separate edition. Only start the loopback weather page when asked;\nclosing a browser tab does not stop its collector. Use weather-service stop\nwith the same chat ID to stop it. Checkpoint setup is separate and requires\nan explicit request to enrol a workflow.\n"
}