[kendrick]

This bumps the version to 0.1.1 so the maintainer can push a v0.1.1 tag. v0.1.0's darwin assets on the GitHub release fail codesign --verify --strict, and #184's sign-macos job re-signs binaries only in a release cut from a new tag. No behavior changes.

Refs #186

The issue asks for a PR that bumps package.json "and changes nothing else", yet .claude-plugin/plugin.json and the <!-- VERSION --> line in each of the three skills/*/SKILL.md files move too. test/plugin/versions.test.ts holds all four to package.json, so leaving them at 0.1.0 turns the suite red. #182 changed the same five files for 0.1.0.

After merge, the maintainer pushes the annotated tag v0.1.1 on the merge commit. The issue's other criteria (the Release run, releases/latest, codesign on the downloaded assets, and the comment on #183) follow from that push, and nothing on this branch can check them.

Verification

A separate reproducer re-ran the worker's claims without seeing its reasoning. caller marks a claim driven through the CLI entry point production runs, and seam marks one checked only at the file or the test suite.

bun src/cli/bin.ts --version, then the same with --json (caller, through src/cli/run.ts):

0.1.1
{"version":"0.1.1","schemas":[1]}

bun run typecheck && bun test (seam: the suite is what reads plugin.json and the skill VERSION lines, and no production code in this repo runs them):

$ tsc --noEmit
 1737 pass
 3 skip
 0 fail
Ran 1740 tests across 89 files. [178.45s]

The counts match the run before the bump, and no file under test/ changed.

git grep -n '0\.1\.0' HEAD -- package.json .claude-plugin skills (seam, a grep over data files with no production caller) prints nothing and exits 1.

git diff shows one line in each of the five files going from 0.1.0 to 0.1.1 (seam, data files with no code seam).

Left out

• guide/m365-copilot.md:59 and guide/maintenance.md:41 still show LTM_VERSION: "0.1.0" in sample workflows. The issue rules out doc changes, and chore(release): bump version to 0.1.0 #182 left these examples alone too. A sample pinned to a published version still works.
• The 0.1.0 values in test/scripts/eval-gate.test.ts are fixture versions that never read package.json.
• No evals/results/0.1.1/ baseline, per the issue's Non-Goals.