yetong-update

YETONG Update

This module is responsible for version maintenance of the current installed instance. The update source is fixed to yetongzhu463-stack/yetong-fitness-xhs of main; the specific version, members, and files are read from the manifest released with the package, and no hardcoded skill count is used.Update Method explains verification, backup, and recovery boundaries.

Default to a Chinese report, preserving original status codes and errors. A network failure does not mean the user account or skills are damaged; call it rate limiting only when there is clear evidence of rate limiting, do not attribute all HTTP 403 responses to the same cause, and do not guarantee that it will automatically recover at a certain time.

Identify the Request

• "Check for updates" and "Is there a new version" only check; "update", "update YETONG skills", and "upgrade YETONG" have already authorized this update and do not require asking again whether to update.
• "Update my character profile / city / customer information" goes back to the character DNA module; "revise this copy" is not a software update.
• This module does not read character profiles and does not require DNA activation. Do not turn an update request into an interview.

Execute

Pre-installation protection for reinstall/import: whether due to a missing update module or failure to retrieve from an old updater, first verify ownership of the directory with the same name, back up the original files in the directory, and confirm that character profiles are outside the package and that the platform instance is the same. The installer may empty a directory with the same name, and cannot guarantee that unknown files will be preserved during reinstallation; if ownership is unclear, stop overwriting. The suggestions below for onboarding a new version are all subject to this rule.

1. First confirm that the current Agent has file reading, Python 3, network access, and write capability for the current Skill installation directory. Run from the directory where this Skill is located python3 scripts/update_bundle.py check; the script locates the current skill root directory through its own real path and does not scan the user's other environments.
2. When the user explicitly requests an update, run python3 scripts/update_bundle.py apply. The script's absolute path may also be used. Use --target <Skills 根目录>only when the installation location has already been determined by the Agent's real file state; do not guess the directory or treat the maintainer's source workspace as the student's installation directory.
3. The script first pins the remote commit, then checks the release manifest, file hashes, and registration relationships; when the API cannot return a valid commit, use the official archive metadata to obtain the commit number, then re-download the snapshot of that immutable commit, and do not directly install floating branch content. Before changes, save the old files, and automatically restore on failure. It takes over only files that the old manifest or old registry can prove belong to this package; when unknown content with the same name conflicts, stop and do not overwrite on the user's behalf. Unknown files, character profiles, other skills, and module directories removed in the old version are preserved.
4. Only when the script reports updated or up_to_date and completes runtime file verification, say that the current installed instance has been updated / is already the latest complete file version.repair_needed indicates that files of the same version are damaged or missing, and it is necessary to run apply Repair. When all official acquisition channels fail, stop and do not repeatedly hammer requests; clarify whether this time nothing was written, or whether it has been restored and the backup location, do not present incomplete work as success, and do not create retry reminders or scheduled updates on your own. If the old update module cannot obtain a snapshot, you may explain that the new updater can be integrated using the original official installation method; before reinstalling, verify that the character profile is outside the package and that the platform instance is the same. Download completion or file verification must not be treated as host loading and persistence verification.
5. After updating, show the real version, newly available skills, and the main entry menu. The current conversation may still cache old instructions; according to the host's capabilities, re-read yetong/SKILL.md and the registry, and if necessary prompt to refresh the skill list or start a new conversation.

Mobile and Cloud

The phone is only an access point. If its cloud task environment actually provides Python, network access, and a persistently writable directory, the update may be performed in that actual environment; the script checks this one instance. If the host only supports uploading skills, has no execution tool, or the installation directory is not writable, clearly state that the latest package needs to be re-imported on the host's skill management page, and deliver a fixed repository link and an acceptance checklist. A write during a one-off temporary task does not equal an account-level persistent installation; you must not claim cross-platform automatic upgrades, background automatic updates, or that all Agents have been updated.

If the old version has not yet installed this module, you must first reinstall the entire skill set once using the original installation method, and only then can you invoke this module through "Update Yetong Skills".