Repository navigation
Prepare public community onboarding and release checks - #2
Merged
Merged
Conversation
Number531
marked this pull request as ready for review
September 13, 2026 04:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The public repository's onboarding mixed installed-plugin and checkout instructions, and its documentation still described private access and unavailable security features. This change separates setup routes, explains project and hook trust, and aligns community access, owner-controlled writes, issue reporting and private vulnerability reporting with the current GitHub settings.
The 0.2.1 candidate also adds offline documentation checks to CI, regressions for broken links/anchors and invalid JSON/TOML examples, and release/rollback guidance. Runtime assets, setup, guard logic, skills, agent names and model pins are unchanged. Delegation enforcement stays off by default.
Validation:
0.154.0and Desktop engine0.154.0-alpha.6.2installed the local candidate and exact GitHub commit1ea514efdacb8aa1077e4eb81a8f7d90d1255306into disposable configuration/cache. All 30 package files matched, three skills were present, setup was idempotent, and the guard stayed off. No auth files were copied, hook trust granted or live models called. Later edits are documentation-only.contractscheck and resolved conversations; administrators are included and force-push/deletion are blocked.Remaining release boundaries are explicit: the owner has not selected a distribution license, Desktop UI and separate-account/live-model qualification remain open, and a tag/GitHub release requires its own publication decision. This documentation merge does not adopt a license or publish a versioned release. No real global plugin installation or global configuration change occurred.