Yoke v1.15.0 — Federated Code Intelligence

Highlights

• Add opt-in federated Code Intelligence that composes Graft, Graphify and Serena behind one Yoke-controlled MCP facade.
• Add six stable tools for context, symbols, traces, impact and guarded edit workflows.
• Add pinned backend adapters, provenance/freshness evidence, content-addressed snapshots, bounded policy checks and isolated edit previews.
• Preserve the legacy codeGraph path with off, shadow and active modes.
• Keep Yoke's existing review, verification and commit gates authoritative.

Backend pins

• Graft 0.17.0 — 05760b07abc0e427f5af8ad378889ee402c5afc6
• Graphify 0.9.56 — 67f99bd0059dd1bac9e44382907ef9f10098b39f
• Serena 1.7.1-dev — 701e7c843f46c6a649203a488cece1bf19f1df90

Validation

• 139 test files
• 1268 tests passed
• Lint, build, canon validation, documentation metadata and package checks passed
• GitHub Actions CI passed on Ubuntu and Windows with Node 20 and 24

Existing projects remain on the legacy path until Code Intelligence is explicitly enabled with yoke setup or yoke retrofit. Backend availability is reported explicitly as partial coverage or an unavailable capability; it is never silently treated as complete evidence.

v1.14.0 - Dashboard Control Room

Added

• Local-first workspace control room with project ranking, search, filters, UTC scopes, and restorable views.
• Workspace and project analytics with time buckets, token/call/duration/outcome summaries, rankings, comparisons, and measurement coverage.
• Project live operations with safe-boundary pause/resume, worker metadata, event timeline, operator notes, and queued changes.
• Responsive dark/light dashboard shell with keyboard, reduced-motion, and narrow-screen support.

Fixed

• Dashboard loop verification is scoped to the intended local project.
• Light-theme active navigation contrast and long project-name overflow are fixed.

See CHANGELOG.md in the tag for migration notes and validation limits.

v1.13.0

Added\n- First-class OpenCode, Kilo and Pi integrations across setup, retrofit, loop execution, routing, reviews, quality roles, goals, PRD affinity, dashboard status and telemetry.\n- Idiomatic native skill/config artifacts, OpenCode/Kilo MCP translation, read-only reviewer artifacts and Pi tool allowlists.\n- Provider/model/variant routing for OpenCode and Kilo; provider/model/thinking routing for Pi.\n\n## Changed\n- Seven supported harnesses are now listed consistently in CLI, canon, manifests, README and plugin metadata.\n- Kilo JSONC retrofit merging preserves comments, trailing commas and user settings.\n\n## Limits\n- External CLIs still require separate installation/authentication. No authenticated provider matrix or OS-sandbox equivalence claim is made. Pi has no native MCP, sub-agent or plan layer. See docs/HARNESSES.md and CHANGELOG.md.

Yoke 1.12.0

What's Changed

• Fix Qwen Code integration and add DeepSeek/Kimi model profiles by @HECer in #6

Full Changelog: v1.11.0...v1.12.0

Yoke 1.10.0

Added

• Adopt the Yoke wordmark in the GitHub and npm README.
• Prepare task assessments in one bounded planning call with yoke prd assess; draft and inbox planning bind assessments to requirements, upstream dependencies and the approved brief.
• Separate planning.agent/model/reasoningEffort from execution settings. New setups require prepared assessments and block missing worker profiles; existing configurations retain on-demand planning and parent fallback.
• Add selective reassessment, planning input limits and routing.maxTier to bound automatic model selection and escalation.
• Add attention-first project search and status filters, with separate goal/loop states and explicit stale activity warnings.
• Restore dashboard views and UTC period controls through URL links, browser history and refresh; cancel obsolete requests and bound project comparison concurrency.
• Compare recorded tokens, accepted tasks and reported costs against the preceding equal-duration period without inventing missing measurements or percentages from zero baselines.

Fixed

• Fix Windows safe-mode Codex execution by screening Store PowerShell/aliases and probing a native shell under the same sandbox before model work; keep permissions intact.
• Launch Windows provider executables/npm entry points with literal argv; bound preflight and provider lifetime, recognize streamed infrastructure failures, retain failed-worktree/process evidence, and guard against unconfirmed termination before another worker starts.
• Separate provider liveness, supervisor heartbeat, output and successful-tool progress in status/dashboard; label backlog percentages and preserve explicit bare startup through capability routing. See Windows runner validation.
• Keep local loop locks and dashboard status out of implementation commits and clean-worktree checks.
• Stage implementation files safely when runtime history directories are already ignored, including literal filenames and tracked deletions, for serial commits and parallel candidate snapshots.

Migration and validation limits

• Existing routing configurations retain on-demand assessment and parent fallback. Use yoke prd assess to prepare task packages; configure planning.agent, planning.model, planning.reasoningEffort and routing.maxTier to separate planning from bounded execution. New setups require prepared assessments and block missing profiles.
• Update installed packages and restart the dashboard/runner to use the new code. Existing running processes are not upgraded or instrumented retroactively. Windows preflight preserves sandbox permissions and changes only the provider environment.
• Dashboard comparisons report recorded measurements, not reconstructed history or calibrated savings. Tokens per minute are consumption rates, not generation speed. Live routed Windows validation covered Codex on the documented machine; cross-provider performance and universal Windows compatibility are not established. See the linked dashboard, batch-planning and runner validation records.

Yoke 1.9.0

Added

• Add capability-based routing with persisted task assessments, explicit model/effort tiers, role eligibility and conservative use of independent task-class outcomes.
• Keep planning on the start model; reuse assessments across attempts/worktrees and invalidate them when task requirements change.
• Add bounded repair and tier escalation after mechanical gate failures, retaining the patch and forwarding failure evidence. Infrastructure failures do not trigger capability escalation.
• Apply task-based profiles to reviews, quality critics/repairs and goal execution; display implementation selection reasons and next escalation in the dashboard.
• Add setup options --routing-strategy=capability and --routing-preset for explicit migration. Preserve existing strategies and custom profiles by default.

Validation limits

• Initial profile tiers are configurable hypotheses, not authenticated model benchmarks, price estimates or calibrated success probabilities. See capability routing for defaults and bounds.

Yoke 1.8.0

Added

• Add persistent local measurement history and dashboard views for current work, usage/time and results, including UTC day/week/month filters, model history, project comparisons and consumption charts.
• Display current tasks, worker phases, integration progress and status age, with automatic refresh of the current-work view.
• Record explicit acceptances and show measured tokens and time per acceptance. Attribute available reviewer, critic and repair usage; distinguish actual reported models, unknown calls and partial costs.

Changed

• Enable routing in new setups and automatically select up to three parallel workers when all pending tasks declare write scopes. Dependencies and overlapping scopes still constrain dispatch. Preserve explicit opt-outs and use isolated worktrees by default.
• Share routing decisions between synchronous and asynchronous runners; support routed parallel workers, stable recovery history and explicit provider affinity.
• Reserve execution capacity through integration and disable native delegation for loop providers; preserve Gemini system policy in a temporary bounded-execution configuration.
• Require a dated changelog entry, synchronized version metadata and verified release checks for every new version in the project instructions.

Fixed

• Avoid conflicting Codex sandbox arguments and prevent Codex-only options from leaking into Gemini workers.
• Keep compact measurement history after recent activity expires, deduplicate archived events, and report incomplete history instead of treating missing usage as zero.
• Preserve reviewer telemetry and worker/model attribution across parallel execution and recovery.

Migration and validation limits

• Use --parallel=N to choose a worker limit, --parallel=auto for automatic selection, --no-routing to opt out of routing, and --no-isolate to opt out of default isolation. Explicit existing configuration remains authoritative. Unknown write scopes, tool actions and worktree recovery select serial execution in auto mode.
• Automatic routing needs configured profiles; otherwise it keeps the selected parent provider. Explicit --routing without profiles reports a configuration error.
• Missing historical usage cannot be reconstructed. Tokens per minute describe interval or summed call consumption, not measured generation speed. Live authenticated provider benchmarks, resource-adaptive concurrency and calibrated time/cost predictions are not established by this release.

Yoke 1.7.0

Yoke 1.7.0 adds verified project goals and one local dashboard for all registered projects.

New workflows

• Register projects with yoke projects add <path> and open yoke dashboard --no-register for goals, tasks, evidence, worker state, recorded consumption and per-task time estimates.
• Run yoke check without retrofit, map executable acceptance criteria and protect their test infrastructure.
• Persist bounded goals across Codex, Claude and Gemini runs with independent checks, provider handoff, interruption accounting and explicit budget changes.
• Resume retained failed serial worktrees against their original target commit and PRD.

More efficient execution

• Explicit routing rules bypass controller calls and persist gate-driven escalation across restarts.
• Configured tool actions require no model call; context packets select relevant source-referenced material within a character budget.
• Parallel scheduling respects dependencies, areas and advisory write scopes. Local events retain phase/attempt durations and prediction errors.

Reliability

• Gemini streaming telemetry and RTK hook integration corrected; unsupported provider selections rejected explicitly.
• Protected acceptance is rechecked after gates and repair. Partial usage/costs remain visibly incomplete, and runtime evidence stays out of commits.
• Shared goal state rejects symbolic links; completed goals are revalidated and interrupted provider processes reconciled before continuation.

The README now includes multi-project dashboard setup, all new commands and their limits. Registration is explicit and local to one computer. Time ranges are empirical, token limits apply between provider calls, and equivalent model quality or comparative savings are not claimed. Browser proof requires configured smoke flows.

Local implementation validation: 1,098 tests passed, 2 platform skips, plus build, canon, documentation metadata and package checks. Release CI validates Linux and Windows on Node 20 and 24.

Upgrade: npm install -g @hecer/yoke@1.7.0

Usage guide: https://github.com/HECer/yoke/blob/v1.7.0/docs/VERIFIED-PROJECTS.md

Yoke 1.6.2

What's Changed

• ci: publish npm releases with trusted OIDC by @HECer in #4

Full Changelog: v1.6.1...v1.6.2

Yoke 1.6.1

Patch release for deterministic cross-platform release metadata and reliable provider cleanup.\n\nFixed:\n- Count platform-conditional tests consistently on Windows and Ubuntu, preventing docs:check drift.\n- Reconfirm provider termination after process close so Windows does not retain stale ownership records.\n- Give the process-heavy Phase 5 integration test a realistic bounded timeout on slower Windows Node 20 runners.\n\nValidated on Ubuntu and Windows with Node 20 and 24.