Skip to content

gentle-pi v3.2.0

Choose a tag to compare

View all tags
@Alan-TheGentleman Alan-TheGentleman released this 17 Sep 13:19
· 372 commits to main since this release
v3.2.0
2b579c8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

gentle-pi v3.2.0 ships the Organic Driven Development contract that closes every task with a work-unit commit and reviews per commit or per PR slice, fixes background subagents so the policy actually changes the runtime default, names the accepted base reference forms when a review rejects one, and pins the matching Gentle AI v3.1.0 runtime.

What's new

ODD closes each task with a work-unit commit and reviews per commit or slice (#1146, #1147)

Every ODD task now ends with at least one work-unit commit on the feature branch, with tests and docs alongside the behavior and the commit identity recorded in the feature document. After each commit, when RDD is enabled, the orchestrator assesses it with gentle_review {"operation":"assess"} and baseRef set to the last reviewed boundary (committedOnly: true). Passive or low stays silent; high, or an unavailable or failed assessment, starts the native review on that commit right away; medium defers to the PR slice bounded by the delivery budget of about 400 authored changed lines and reviews at slice close. Every reviewed boundary becomes the next base. The delivery strategy and chained pull requests (work-unit-commits and chained-pr skills) now apply to organic work too. Parity with Gentle AI v3.1.0 (gentle-ai #4714).

Base references are explained when rejected (#1150, #1151)

A rejected baseRef now names the accepted forms: HEAD, a full 40- or 64-character commit id, or a ref name; abbreviated commit ids are rejected explicitly. A full id that names a tree instead of a commit is base-ref-unresolvable with "it does not name a commit" instead of a misleading git failure. The blocked payload carries a hint, the tool description states the forms, and the docs cover the orphan-branch boundary.

Gentle AI v3.1.0 pinned (#1152)

The package-local runtime is now Gentle AI v3.1.0 on the /v3 module, with signed release archives for Darwin and Linux and the SumDB-verified source build for Windows. The provider contract stays at 1.2.0; the native CLI contract row for 3.1.0 repeats 3.0.1 because zero contract bytes changed.

What was fixed

Background subagents policy on ran subagents in the foreground (#1148, #1149)

The policy only rendered the prompt status line; the real mode was params.mode ?? agent.mode ?? defaultMode with a hardcoded task default, so background happened only when the model passed mode: "background" itself. subagent_run now defaults to background at the runtime level when the policy is on and the parent is interactive or RPC. Print mode keeps task (background is rejected there by design), and an explicit mode still wins. The pure policy resolver moved to lib/background-subagents-policy.ts so both extensions read one source, and the test suite scopes GENTLE_PI_CONFIG_HOME so a developer's real policy file cannot leak into fixtures.

Upgrade

pi install npm:gentle-pi@3.2.0

Restart Pi, then run gentle-ai sync so the managed orchestrator assets match the pinned runtime.

Verification

  • pnpm test green on macOS (Windows-only suite skipped locally, run in CI).
  • Package verification, npm pack --dry-run, and the packed-runner check against the pinned v3.1.0 release assets.
  • Every change in this release went through the native review under the new contract: high commits reviewed alone with four lenses, medium commits at slice close, all approved and acknowledged with zero blocking findings.
Assets 2
Loading