Repository navigation
Maintainer Update Procedure
The wiki's own Git repository is the canonical editable source for these pages. Preserve its history and existing pages. Update through GitHub's wiki editor or a normal wiki-repository checkout; source-code branches and Marketplace packages are separate delivery targets.
- Before delivery begins, add a dated entry to Release Notes. Update Home and Release Channels with the current confirmed stable version, confirmed preview version, and any pending candidate. Use pending or in progress until publication is verified.
- State the user-visible problem, affected versions, fix or workaround, remaining uncertainty and safe next action. Keep authentication/access errors, package integrity errors and channel-delivery problems distinct.
- Before stable publication would overtake the preview version, coordinate an authorized newer preview. Do not treat an older preview in version history as proof that channel switching still works.
- After publication, verify the exact public identity/version, release versus pre-release flags, Marketplace validation and channel-switch eligibility. Record the verification date and evidence. Separate catalog evidence from local installation, smoke testing and human acceptance.
- Update Home, Release Channels and Release Notes together after those checks. If delivery fails, leave an explicit failure/pending notice and recovery guidance rather than silently announcing completion.
- Update Troubleshooting and Getting Started when a shipped fix changes visible behavior, recovery steps or labels. Cross-check the source changelog and actual released package.
- Review the rendered wiki, links, spelling, version numbers and status consistency. Commit the wiki update with a descriptive message; preserve the commit ID in the release evidence.
- Wiki publication does not publish extension code or approve a production release.
- A pipeline run, package, catalog entry and a native-loaded extension are separate facts.
- Do not claim installation on users' computers from Marketplace metadata or a disposable test profile.
- Do not put private paths, credentials, private skills, account access details or team/personnel records in this public wiki.
- Respect the current bug-fix-only release freeze and the owner's publication decision.
When a correction is needed, explain it plainly in the release notice and retain the prior context in wiki history.
When settings, buttons or folder behavior change, cross-check the four fields shown by SkillJetty's gear → Extension Settings, the current manifest defaults and the actual workflow. Keep Settings and Repository Setup, Concepts and Folders, Repository Layout and the optional Command Palette Walkthrough consistent. A proposed interface is not the published interface.
The six diagram pictures are generated from their pages' Mermaid blocks by images/render_diagrams.py in this wiki repository. Maintainers can regenerate them with python images/render_diagrams.py after installing the standard matplotlib plotting library in their authoring environment. The renderer keeps layout positions separately; update those positions when changing the set of diagram nodes. Compare the resulting PNG pictures, Mermaid relationships and text alternatives, then verify the actual images on GitHub. The static pictures keep the guide usable when GitHub's interactive Mermaid renderer is unavailable.
SkillJetty by DAF-TECH · Release status · Support