Release 0.2.2 — published plugin cache lacks the #131 driver working-directory fix

[robercano-ghbot]

Problem

The published plugin (0.2.1, pinned at sha 614f703) predates PR #131. Any consumer whose loop runs plugin-cache code — or that re-vendors from the cache — gets the #119 transient-unit spawn WITHOUT the --working-directory fix: drivers start in $HOME, never load the repo permission profile, and exit phantom (the exact failure that burned issue #97's whole attempt budget on 2026-07-16).

Do

• Cut 0.2.2 from current main (carries Loop: driver one-shot contract needs enforcement + tests — background orchestration produced phantom-success drivers and wedged the queue #111, Loop: decouple driver lifetime from the daemon — transient systemd unit per driver, startup re-attach, halt helper #119, fix(worktree): link main checkout's .env into fresh worktrees on setup #125, feat(loop): spend ceilings — stop-after self-disarm, per-issue attempt budget, daily ceiling (#95) #127/Loop: spend ceilings — per-tick caps, daily budget with auto-halt, stop-after self-disarm #95, fix(loop): pin transient driver units to the repo root via --working-directory #131, feat(loop): dependency-aware census selection via the blocking graph #135/Loop: dependency-aware issue selection — census must consult the blocking graph it already parses #97).
• Update the stale install scopes on this machine: user-scope is at 0.2.0 (serves reDeFi), website is local-scope 0.1.4.
• Adopt a policy: any loop-critical fix (spawn path, census, gates) triggers a release — a fix that only lives on main protects nobody downstream.

🤖 Generated with Claude Code

[robercano-ghbot]

Closing as superseded by #178 (Release v0.3.0): the milestone release ships everything the 0.2.2 publish would have, including the #131 working-directory fix, and consumers migrate via #141's sync v2 rather than a cache re-publish.