Skip to content
KTL Curator

Playbooks

  • Contributing to the plugin checked by automation only, still a draft
    Development setup, npm run check (build, lint and smoke test, the same three steps CI’s build.yml runs), the seven pure modules the smoke test covers, and the pull-request checklist: verb write limits, the changelog line, sibling links, the vocab refresh, releasing pull request titles, and the skills pin, which knowledge-sync.yaml and knowledge-sync.sh move with every template the release’s knowledge-sync.manifest lists.

  • Knowledge registrar gate checked by automation only, still a draft
    The knowledge-registrar.yaml workflow: validates the bundle and its relation targets on every pull request that touches it, and ties every human: confirmation a pull request adds, changes or removes to that person’s approval of the pull request or their verified signature on the commit, with an environment reviewer’s attestation as the fallback.

  • Knowledge sources checked by automation only, still a draft
    Where this bundle’s concepts are derived from, and how to re-check each source on a later librarian run.

  • Knowledge website checked by automation only, still a draft
    The website/ folder and the knowledge-website.yaml workflow: an Astro Starlight site built from the bundle, the README, docs/ and the changelog, with a trust label on every concept page, built on pull requests and published to GitHub Pages at https://noelmcloughlin.github.io/obsidian-ktl-curator/ once the repository variable KNOWLEDGE_WEBSITE_ENABLED is true.

  • Releasing a new version checked by automation only
    Semantic-release computes the version and promotes CHANGELOG.md on a merge to main, behind the release Environment; release.yml then builds, attests and opens a draft release, from semantic-release’s call, a hand-pushed tag, or a hand-run dispatch.