Skip to content

Document component compatibility checks and automatic recovery - #31

Merged
wangdiandao merged 1 commit into
mainfrom
docs/30-component-compatibility
Nov 2, 2026
Merged

wangdiandao merged 1 commit into
mainfrom
docs/30-component-compatibility

Conversation

@wangdiandao

@wangdiandao wangdiandao commented Nov 2, 2026 •

Copy link
Copy Markdown
Owner

Declare mandatory host features independently of SDK release numbers. Unsupported interface generations and missing features block execution while preserving enabled intent and user data. Failed updates retain the active version; compatibility recovery resumes enabled components and respects explicit disable actions.

Synchronizes host authorities in docs/contracts/component.md, docs/contracts/layout.md, docs/modules/development.md and SDK 0.1.2; updates Chinese/English package guidance, compatibility references and the existing development skill. The generated snapshot also includes the current host Workshop contract.

Validation passed: host snapshot --check, npm run check, npm run docs:build, remote policy/validation/Pages, Release x64 build, 1549 native service checks, HTTP proxy and bundled upgrade/restart, real-host compatibility block/recovery and KV preservation, SDK behavior/distribution, strict TypeScript and localization. Host lifecycle checks use isolated fixtures; physical input, multi-display and real old-release upgrade paths were not tested. Installed local plugin content matches merged main across 97 files and remains enabled.

Closes #30

@wangdiandao
wangdiandao merged commit ae7e602 into main Nov 2, 2026
2 checks passed
@wangdiandao
wangdiandao deleted the docs/30-component-compatibility branch November 2, 2026 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document component compatibility requirements and recovery

1 participant