@hecer/yoke 1.17.0 → 1.19.0

package/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "yoke",
   "displayName": "Yoke",
-  "version": "1.17.0",
+  "version": "1.19.0",
   "description": "Cross-agent coding harness for Claude, Codex, Gemini, Qwen, OpenCode, Kilo, Pi and Hermes: one curated skill canon plus mechanical safety gates and an autonomous loop via the yoke CLI.",
   "author": { "name": "HECer", "url": "https://github.com/HECer" },
   "homepage": "https://github.com/HECer/yoke#readme",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "yoke",
-  "version": "1.17.0",
+  "version": "1.19.0",
   "description": "Cross-agent coding discipline, mechanical gates, and release workflows for eight supported harnesses",
   "skills": "./canon/skills/",
   "hooks": "./hooks/hooks.json"

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # Changelog
 
+## 1.19.0 — 2026-09-28
+
+### Added
+- Add optional, per-project SoL-Pi controls for Pi, including dashboard settings and temporary configuration for each opted-in invocation. SoL-Pi remains disabled by default and is pinned to a reviewed upstream commit.
+
+### Fixed
+- Write SoL-Pi options to its project-local `.pi/sol-pi.json` configuration path and restore the prior file after each invocation, so enabled mechanisms are read by the extension.
+- Map Hermes reasoning selection to the CLI's `--reasoning` option.
+- Normalize federated Code Intelligence stdio evidence across adapters and the coordinator.
+
+### Changed
+- Replace the long README with a concise feature overview, a workflow diagram, a quick start and links to detailed guides.
+- Raise test-only child-process and Windows integration timeouts to reduce false failures under host load; production timeout defaults are unchanged.
+
+### Migration and validation limits
+- SoL-Pi's pinned upstream lists Node.js 22.19+ and `@earendil-works/pi-coding-agent@0.84.2` as its tested baseline. Yoke checks Node.js but does not enforce the Pi version; other releases are unverified. Pi project trust may be required. Yoke does not install Pi, grant trust, or configure provider credentials. SoL-Pi remains opt-in, and the upstream paper results are not a savings guarantee for a Yoke project.
+- Continuous exploration and parallel workers remain independently opt-in/configurable; see the [continuous exploration](docs/CONTINUOUS-EXPLORATION.md) and [parallel execution](docs/parallel-execution.md) guides for safe-boundary and resource limits.
+- Local release checks on Windows with Node.js 24.13.0 passed: lint, build, canon, README metadata, npm audit (0 vulnerabilities), package dry-run, and 1,337 tests (2 skipped). The GitHub Node 20/24 Linux/Windows CI matrix remains the cross-platform release gate.
+
+## 1.18.0 — 2026-09-27
+
+### Added
+- Add opt-in continuous exploration with evidence-filtered task discovery, validated PRD additions, isolated implementation, bounded history compaction, automatic provider recovery, stop detection, and `yoke loop pause`.
+- Add optional `--explore-limit=<Nh|Nd|Nw>` durations. Exploration remains unbounded when omitted; when the limit expires, Yoke stops launching work and pauses after active workers finish their normal gates and integration.
+
+### Changed
+- Keep exploration status and narrative focused on newly accepted work, the next planned action, provider recovery, and safe stop state.
+- Process finite-duration runs in bounded task batches so the supervisor can honor the deadline while retaining configured parallel workers.
+
+### Migration and validation limits
+- Exploration is opt-in and requires isolated story worktrees. Use `--explore-limit=12h`, `3d`, or `2w` to bound one invocation; expiry exits with code `3`, and a later resume starts a new duration. Without a limit or a user pause, it continues while the process and machine remain available.
+- Auto-discovered work is limited to repository-evidenced proposals that pass confidence, risk, write-scope, acceptance-criteria and criterion-test checks. This does not guarantee project maturity or model quality; provider credentials, configured gates and machine availability still determine progress.
+- A time limit does not interrupt an active story or integration. Active work finishes through the normal gates before the loop stops, so wall-clock completion can exceed the requested duration by the time needed for that safe boundary.
+
 ## 1.17.0 — 2026-09-27
 
 ### Added