v3.6.1 — Pi arranca limpio y la delegacion ODD vuelve a ser proporcional
Patch chiquito pero que te destraba cosas reales. Gentle Pi ahora trae su propio ask_user_question, asi que el paquete de terceros que hacia colision de nombres y te impedia cargar Pi deja de estar gestionado: install y sync te lo podan del home existente. Ojo con esto: si sos usuario de Pi, corre gentle-ai sync despues de actualizar o te quedas con el paquete viejo.
Tambien se arreglo el diagnostico del skill-registry en OpenCode: un fallo de spawn se reportaba como PATH faltante aunque el ejecutable estuviera visible. Ahora describe el fallo real sin adivinar la causa y te deja seguir con un refresh accionable. Y la guia de routing ODD se afino: delega cuando el trabajo toca dos o mas archivos no triviales, sin contar una edicion mecanica posterior como segundo archivo no trivial.
Numeros del rango: 12 commits no-merge, 4 PRs mergeados, 2 autores. El provider contract sigue congelado en 1.2.0.
v3.6.0 — PI_CODING_AGENT_DIR y hooks SDD mas seguros en Windows
Minor con una capacidad nueva y tres fixes. gentle-ai install y sync ahora respetan PI_CODING_AGENT_DIR, la misma variable que lee Pi: ruta absoluta se usa tal cual, con ~ se expande contra el home, y relativa resuelve contra el directorio desde donde corre gentle-ai, con fallback a ~/.pi/agent. Los procesos hijos como pi install y pi-engram init heredan la variable. El config root ~/.pi no sigue el override nunca, y el manifest npm que toca el provisioning de Engram pasa a <agent dir>/npm/package.json. Esto es lo que le permite al launcher gentle-shell provisionar su home aislado sin tocar tu Pi real.
Del lado de los fixes: el hook UserPromptSubmit de Claude Code usaba la forma POSIX || true, que PowerShell 5.1 no puede ejecutar, asi que el refresh del skill-registry fallaba en cada prompt en Windows. Ahora corre por un wrapper PowerShell-safe y se poda la entrada legacy. Ademas, al podar se colaba un segundo hook canonico y el refresh corria dos veces por prompt: la existencia canonica ahora se calcula despues del prune. Y uninstall --help y restore --help devuelven usage real en lugar de un error opaco.
Ojo: todavia quedan rutas del adaptador Pi (persona.json, politica de subagentes, targets de uninstall, scan del skill-registry) que siguen pegadas a ~/.pi literal y no respetan el override. 25 commits no-merge, 4 PRs, 2 autores.
v3.5.0 — Receipt-driven development pasa a estar prendido por defecto
Este minor no te cambia una API: te cambia un default, y eso pesa mas. El switch de review que gatilla el review nativo acotado de un candidato ahora viene habilitado. Hasta v3.4.0 era opt-in, asi que una instalacion fresca nunca corria review y el delivery seguia la politica del repo sin uno. Desde v3.5.0 el modo efectivo es on salvo que un clone o un setting global diga otra cosa, y gentle-ai review mode status te reporta que fuente decidio.
Es cambio de default, no de capacidad: el lifecycle es el mismo que ya tenian los que lo habian prendido a mano — el candidato se congela una vez, las lenses se eligen nativamente por tier de riesgo, se permite a lo sumo una correccion acotada, y se quema un receipt terminal al acknowledge. Apagarlo sigue siendo decision tuya y es un comando: gentle-ai review mode disable.
El resto del release es lo que ese default necesitaba para ser seguro: los writers de whole-state ahora serializan bajo el lock canonico (antes dos paths podian pisarse y perder un update), el source de Gentle Logo se rollbackea si falla su registracion en TUI, y la captura de provider-role en OpenCode ya nombra causas de refusal tipadas en vez de tirar un fallo opaco. Sumale que gentle-ai sync ahora persiste last_synced_at solo cuando termina bien, y que pr-check acepta referencias estrictas a issues que no cierran.
Importante al actualizar: corre gentle-ai sync despues del upgrade, porque los assets de agente, reviewer y runtime estan versionados contra el binario y este release cambia instrucciones de orquestador y assets de reviewer. Sin el sync, un binario v3.5.0 maneja assets v3.4.0.
v3.6.1 — Pi starts clean and ODD delegation goes back to being proportional
A small patch that unblocks real problems. Gentle Pi now ships its own ask_user_question tool, so the older third-party package that collided on tool names and could keep Pi from loading is no longer managed: install and sync prune it from existing homes. If you are a Pi user, run gentle-ai sync after upgrading or you keep the stale package.
OpenCode skill-registry diagnostics were also fixed: a spawn failure was reported as a missing PATH entry even when the executable was visible to OpenCode. It now describes the failure to spawn or resolve without guessing the cause, stays single-line, and lets startup continue with an actionable refresh path. ODD routing guidance was tightened too: delegate when work touches two or more non-trivial files, without counting a later mechanical edit as a second non-trivial file.
Range numbers: 12 non-merge commits, 4 merged pull requests, 2 authors. The provider contract stays byte-frozen at 1.2.0.
v3.6.0 — Pi agent directory override and safer SDD hooks on Windows
A minor release with one new capability and three fixes. gentle-ai install and sync now honor PI_CODING_AGENT_DIR, the same override Pi reads: an absolute path is used as-is, a ~-prefixed path expands against the home directory, and a relative path resolves against the directory gentle-ai runs from, falling back to ~/.pi/agent. Child processes such as pi install and pi-engram init inherit the variable unchanged. The Pi config root ~/.pi never follows the override, and the npm manifest Engram provisioning edits moves to <agent dir>/npm/package.json. That is what lets the standalone gentle-shell launcher provision its isolated agent home without touching a real Pi install.
On the fix side: the generated Claude Code UserPromptSubmit hook used the POSIX || true form, which PowerShell 5.1 cannot run, so the skill-registry refresh failed on every prompt on Windows. It now runs through a PowerShell-safe wrapper and the legacy literal is pruned and persisted. Pruning also used to append a second canonical hook — the existence check was guarded on nothing having been pruned — so the refresh ran twice per prompt; canonical existence is now computed after the prune. And uninstall --help and restore --help answer with real usage instead of an opaque sentinel error.
Still open: the Pi adapter's persona.json, background-subagents policy, uninstall targets and skill-registry scan still join ~/.pi literally and do not follow the override. 25 non-merge commits, 4 pull requests, 2 authors.
v3.5.0 — Receipt-driven development is on by default
This minor release changes a default, not an API — and that carries more weight. The review switch that gates bounded native review of a candidate now ships enabled. Until v3.4.0 it was opt-in, so a default installation never ran a review and delivery followed ordinary repository policy without one. From v3.5.0 the effective mode is on unless a clone or a global setting says otherwise, and gentle-ai review mode status reports which source decided it.
This is a change of default, not of capability. The lifecycle is the same one opt-in users already had: a candidate is frozen once, lenses are selected natively by risk tier, at most one bounded correction is permitted, and a terminal receipt is burned on acknowledgement. Turning it off stays the user's decision and is one command: gentle-ai review mode disable.
The rest of the release is what that default needed to be safe to ship: whole-state writers now serialize under the canonical lock (two independent paths could previously write concurrently and lose an update), the Gentle Logo source is rolled back when its own TUI registration fails, and OpenCode provider-role capture now names typed refusal causes instead of reporting an opaque failure. On top of that, gentle-ai sync persists last_synced_at only after a sync completes successfully, and pr-check accepts strict non-closing issue references.
Important on upgrade: run gentle-ai sync, because managed agent, reviewer and runtime assets are versioned against the installed binary and this release changes orchestrator instructions and reviewer assets. Without the sync, a v3.5.0 binary drives v3.4.0 assets.
v3.6.1 — Pi demarre proprement et la delegation ODD redevient proportionnee
Un petit patch qui debloque de vrais problemes. Gentle Pi fournit desormais son propre outil ask_user_question, donc l'ancien paquet tiers qui entrait en collision de noms et pouvait empecher Pi de charger n'est plus gere : install et sync le retirent des homes existants. Utilisateurs de Pi : lancez gentle-ai sync apres la mise a jour.
Les diagnostics du skill-registry OpenCode sont corriges : un echec de spawn etait signale comme une entree PATH manquante meme quand l'executable etait visible. Le message decrit maintenant l'echec sans deviner la cause et laisse le demarrage continuer. La guidance de routing ODD a aussi ete affinee.
Chiffres : 12 commits non-merge, 4 pull requests fusionnees, 2 auteurs. Le contrat provider reste fige a 1.2.0.
v3.6.0 — surcharge du repertoire agent Pi et hooks SDD plus surs sous Windows
Une version mineure avec une nouvelle capacite et trois correctifs. gentle-ai install et sync respectent maintenant PI_CODING_AGENT_DIR, la meme surcharge que lit Pi : chemin absolu tel quel, chemin avec ~ etendu contre le home, chemin relatif resolu contre le repertoire d'execution, avec repli sur ~/.pi/agent. Les processus enfants heritent de la variable. La racine de config ~/.pi ne suit jamais la surcharge.
Cote correctifs : le hook UserPromptSubmit de Claude Code utilisait la forme POSIX || true, impossible a executer sous PowerShell 5.1, donc le refresh du skill-registry echouait a chaque prompt sous Windows. Il passe maintenant par un wrapper compatible PowerShell. Le nettoyage ajoutait aussi un second hook canonique ; l'existence canonique est desormais calculee apres le nettoyage. Enfin, uninstall --help et restore --help renvoient une vraie aide.
25 commits non-merge, 4 pull requests, 2 auteurs.
v3.5.0 — Le receipt-driven development est active par defaut
Cette version mineure change un defaut, pas une API. Le commutateur de review qui declenche la review native bornee d'un candidat est desormais active par defaut. Jusqu'a v3.4.0 il fallait l'activer, donc une installation par defaut ne lancait jamais de review. Depuis v3.5.0 le mode effectif est on sauf si un clone ou un reglage global dit le contraire, et gentle-ai review mode status indique quelle source a decide.
C'est un changement de defaut, pas de capacite : le cycle de vie est identique — le candidat est fige une fois, les lentilles sont choisies nativement par niveau de risque, au plus une correction bornee est permise, et un recu terminal est consomme a l'acquittement. Le desactiver reste votre decision : gentle-ai review mode disable.
Le reste de la version est ce que ce defaut exigeait : les ecrivains d'etat global serialisent sous le verrou canonique, la source Gentle Logo est annulee si son enregistrement TUI echoue, et la capture de role provider OpenCode nomme des causes de refus typees. En prime, gentle-ai sync persiste last_synced_at uniquement apres un succes, et pr-check accepte les references d'issue strictes sans fermeture.
Important : lancez gentle-ai sync apres la mise a jour, sinon un binaire v3.5.0 pilote des assets v3.4.0.