v0.1.2: Config moves to patchula.pkl at the repository root; local runs reuse your mise tools

The Count now finds his invitation at the root of each repository, and local runs borrow tool versions you already have in mise instead of downloading them.

Breaking Changes

Repository config moves to patchula.pkl at the root. .github/patchula.pkl is no longer read, so a repository that only has that file is skipped. Move the file to the root and update its amends line, since the schema module has also been renamed from Patchula.pkl to PatchulaConfig.pkl (#5, @sweepies):

// 0.1.1: .github/patchula.pkl
amends "../Patchula.pkl"

// 0.1.2: patchula.pkl at the repository root
amends "PatchulaConfig.pkl"

prs { dashboard = true }

If you vendored the schema, regenerate it under its new name with patchula config schema > PatchulaConfig.pkl. A vendored PatchulaConfig.pkl is the copy that gets evaluated, so keep it in step with the Count you run. A leftover Patchula.pkl is not used. Organization modules and --config-dir policy files that amend Patchula.pkl need the same change.

Added

• Local runs (patchula run, lookup, tui and tools install) hard-link a matching tool version from your own mise install into the Count's tool store, rather than downloading it. Node, Go, Bun, aube, Yarn, uv and Terraform are covered. On a fresh store, patchula tools install took 35 s with borrowing against 68 s without, on a fast connection. The source is MISE_DATA_DIR, or ~/.local/share/mise, and it must be on the same filesystem as the store. Python, Ruby, PHP and .NET are always installed fresh. The server never borrows. Pruning only removes the store's own links, never your installs (#6, @sweepies).

Changed

• The GitHub Action resolves version: latest through GitHub releases rather than the public versions mirror, which can lag behind a new release (#5, @sweepies).

Fixed

• A fresh tool store no longer logs "unproven tool install was not removed" for versions that are not installed yet (#6, @sweepies).

Full Changelog: v0.1.1...v0.1.2