gentle-pi v2.1.1

gentle-pi v2.1.1

A focused Pi patch that fixes three receipt-driven development integration gaps without moving the package-local provider: consent-binding failures now expose precise local diagnostics, wrapper-created authority governs the contributor workspace while reviewers retain immutable candidate views, and RDD-off git -C publication correctly reconsults the targeted linked worktree.

Highlights

• Consent-binding failures are typed and actionable (#249, closes #248): contract, cwd, target, projection, answer, option, unknown-answer, and non-START mismatches now raise NativeReviewConsentBindingError with stable reason codes. The controller reports consent-binding-invalid, native_invocation_attempted: false, no lineage, no mutation, and next_action: resolve-consent-binding instead of disguising a local pre-launch mismatch as a provider outage. Detection remains name-aware because bundled and source module instances can coexist. This addresses the opaque diagnostics that initially obscured the root cause in #247.
• Wrapper authority now governs the contributor workspace (#247): wrapper START and consent follow-up execute against the contributor workspace with its exact prebound target identity and projection, so resulting receipts can govern lifecycle operations in that workspace. Before native START, Pi verifies that the immutable candidate view matches the workspace target's base tree, candidate tree, projection, and paths; drift still fails closed without launching the provider. actor_binding continues to expose the separate immutable candidate_root, candidate tree, and path set used by reviewer actors.
• RDD-off linked-worktree publication works again (#246): direct git -C <linked-worktree> commit and push commands now reconsult review mode in the canonical target worktree rather than the Pi session workspace. Git Bash /c/... paths and native Windows drive paths normalize to one drive-qualified identity, existing aliases resolve through realpath, and the exact typed Git selector remains preserved for execution. An effective mode of off admits organic delivery as disabled/unmanaged; an unavailable or unprovable mode still fails closed.
• Release fixtures and runtime mirrors are aligned: stale workspace-authority and lock-status fixtures now build real candidate projections and assert workspace-bound START requests, generated runtime code mirrors the TypeScript fixes, and the package manifest is pinned to 2.1.1.

Upgrade notes

• pi install npm:gentle-pi@2.1.1 provisions the same stable package-local Gentle AI v2.2.2 used by 2.1.0; no provider contract migration is required.
• Workspace authority is intentional: review authority and consent bind to the workspace where lifecycle commands run, while reviewer actors remain confined to the immutable candidate view named by actor_binding. This is a corrected separation of authority and inspection, not a relaxation of candidate binding.
• RDD-off remains evidence-based: commit or push proceeds organically only after the exact command target reports effective mode off. A failed reconsult still blocks, and disabled/unmanaged never means reviewed or approved.
• Windows trust boundary is unchanged: where signed upstream Windows assets are unavailable, v2.2.2 still uses the pinned Go module, SumDB checksum, sealed build inputs, and package-local integrity manifest introduced in 2.1.0. This is not equivalent to Authenticode or a signed upstream archive.
• RDD remains an unstable development line. The standing fallback for normal use without native RDD is pi install npm:gentle-pi@0.14.0.

Verification

• The exact release boundary c30175cd44edfb2a451c067539585b337f774184 passed the exact green CI run 30583482082, verify job 91009241021: 970 tests, 969 passing, zero failures, and one expected Windows-only skip; the runtime harness completed in the same successful test step.
• Package verification passed with 129 required files and 64 exact byte-identical v2.2.2 contract artifacts. Packed installation loaded gentle-pi 2.1.1 with Gentle AI 2.2.2 and passed all 13 runner states.
• The release review disposition is disabled/unmanaged: the maintainer's global RDD switch remained off, so no review receipt was issued, validated, or implied. Exact-SHA CI is verification evidence, not receipt approval.

Deferred

• Current gentle-ai main parity remains separate: this release intentionally retains stable package-local Gentle AI v2.2.2. Parity work covering current gentle-ai main, including large repository path-manifest scalability tracked in #2058 and provider-defect reporting behavior from #2060, is deferred to a later release.

Full changelog: v2.1.0...v2.1.1