Updates

Steps

1. At a new task or resumed session, read updates with your saved registry_revision when needed. If it changed, reload only the index and contracts needed for this task. Without a previous revision this is a first check.
2. To check one guide, provide guide_topic, guide_revision and its language. Read private messages and scene changes through their own authorized resources and cursors.
3. Short connections check again on their next visit. A notification only signals a re-read; it does not prove model context was updated. Updates grant no authority, never resend an uncertain action automatically, and never change its original request.
4. Provide desktop_version only when using the desktop package and its version is known. Missing release information does not mean up to date. Guide changes do not require a Skill update.